XXHighEnd - The Ultra HighEnd Audio Player
February 22, 2019, 05:44:00 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: August 6, 2017 : Phasure Webshop open ! Go to the Shop
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 2 3 4 5 6 7 8 [9] 10
 81 
 on: January 16, 2019, 01:55:29 pm 
Started by phantomax - Last post by PeterSt

Maxi,

Once in a while I make a new one from the ground up. Last time was a month or so ago (for a new W10 Build). But because it was some longer ago, I couldn't do it and found errors in my own notes. And then to think that *each* time I create a new one, those notes have to be adjusted, just because it is such a huge pile of things to do, and often you forget to wite down instructions. So that surfaces the next time ...
Eh, good luck ?
(but I still can hand you the expansion procedure)

Peter

 82 
 on: January 16, 2019, 01:34:25 pm 
Started by phantomax - Last post by phantomax
Hello Peter,

Understood (I think), obviously I was missing something: the larger OS on the SDD.
The truth is that I I never thought about the possibility/necessity/convenience of make the space for the OS larger. I made it of 11,4 GB and the system tells me that I have only 821 MB free.
I simply thought it was better not to make it too big considering the available RAM.
The OS load quite faster, but I only had in mind have a copy because although I was taking notes when I did the original disk I am not sure I can reply the whole process succesfully swoon.


Thank you very much!

Maxi

 83 
 on: January 16, 2019, 12:36:22 pm 
Started by phantomax - Last post by PeterSt

Hi there Maxi,

The RAM-OS SSD as we sell it, is an SSD for one reason only : it boots faster with the larger OS which is pre-installed.

So the story is a bit different from your idea about it :
First people have 32GB of RAM, then it is convenient to have more space for the OS (on the HDD as how we ship it, this is IIRC 9GB), like 17GB or so (I forgot the number). Thus, the OS file which is loaded in RAM aned which ends up as Drive C:, has been made larger and together with that it was put on an SSD because this is read faster during the copying to memory. But on an HDD it would have worked just the same.

The other way around (your case) :
If you just put the OS, in its container of 9GB to an SSD, it remains 9GB. It will load again faster, but the HDD was fast enough. And so nothing really changed.

I guess what you want(ed to do) is make the space for the OS larger. Well, this can be done by means of expanding the OS file. If you need that, I can send the procedure to you by email. Or maybe not, because you made the whole thing yourself and already will know how to do that ? Anyway you can apply the exact same to the HDD and the SSD, as long as they contain sufficient space.

And now this has all been said : the SSD we ship is half smaller than the HDD (SSD is 240-250GB, HDD is 500-750GB).

Best regards,
Peter

 84 
 on: January 16, 2019, 12:26:57 pm 
Started by Robert - Last post by PeterSt

People shouldn't miss this.

Happy

 85 
 on: January 16, 2019, 12:25:26 pm 
Started by PeterSt - Last post by PeterSt

Hey hey ...

A:B-W-Y-R, B:B-W-R

This has been the configuration for many months. Maybe from of today we can change it to this one :

A:B-W-Y, B:B-W

with thanks to kurb1980.

Unless it is me or my ears or electrical charge from outer space ... this is such a refreshing one ... hard to believe it is real. Many things in there I never experienced before.

First odd thing : I never noticed a real change on day one of listening to this. Maybe the wrong music for it, hard to tell. But this goes in combination with day two, where it was one large jaw dropping experience (this was yesterday).

Odd: Bass sounds like with too much energy, but at second thought and "seeing through" it is about a layer under what you here foremost, that layer implying extra-low frequency.

Odd: When walking through the middle of the sweet spot (crossing the room from left to right and back), in the middle there's a clear increase of volume. I did not check with the SPL meter, but I guess it will be easily detectable. Anyway, like all adds up on the sweet spot.
I know, this may be logical to happen, but I never noticed it, and the increase is really quite much (feels like 6dB).

Odd: The depth of the sound stage is as flat as can be.
Huh ?
Yes, but in combination with a sound stage which never has been wider.
Huh^2 ?
Before trying it out, try to envision that. To me it seems impossible from theories. Still it is so. There is no depth but there is infinite width. And the most troubling issue : I can not detect where this bothers me. I mean, the speakers are not detectable anyway (and that with this flat stage ??) and it just is a most pleasant presentation.

There is detail in an again lower area which brings forward all kinds of sounds and voices and mumbling and a 100 things I never heard before. This also does a lot to cymbals and percussion instruments. I am also confident that this attributes to the (music) reality level ... not-normal.

But supposed you know my way of thinking, something quite else is going on ...

I (or we) already know of what happens to the "accuracy" as such, when the stage is made wider by what I call unnatural means. The sugar cubes are an example of that. You end up in a church but in the end all is more vague. The idea ? the energy in the sound waves is spread (by whatever voodoo force Happy) and therefore all becomes less accurate (it is torn apart). Get the idea ?
All right. This Lush^2 configuration works a kind of other way around;

The sound stage is wider, true. But the reason now is : all is compressed in a flat space (if I say it is 1 meter deep then I will exaggerate). And notice me dealing with the "energy does not get lost" law of physics. What I plainly hear is this :

All the energy is in this tight space (you could do the math on it, and compare with a depth of e.g. 3-4 meters as how it was previously). There it fights for space. This is the buzzing of the bass but which only happens when not listening at the right position. This is also related to the 6dB (?) of higher level which is perceived when being right in the middle (of the speakers) - hence at the sweet spot again. All there beams as should, comes together where intended and "adds up".

If by now you think I really lost it, then be happy as it is and leave it be. swoon

All the again extra detail which is there now, comes from the far better accuracy because of the more compact sound (more compressed ?). Much more collides and much more literally energizes.

Warning : I have the clear idea that this now requires the Custom Filter Low setting, although I did not try plain Arc Prediction (each second of trialling things feels like a complete waste of time - haha).
The other and more important warning is about letting this config be for a first day and only judge at the second (it is too hard to imagine that I just missed this all on the first day).

I noticed that it was impossible for me to judge the quality of the "sound" because the music itself attracted too much (this is always a good thing, IMO). However, I was continuously and throughout pointed at the new sounds I heard everywhere. In amount, think twice as many (I am serious).
I coincidentally started out with some old hit (Turtles - Happy Together (1967)) and was open mouthed from the super clear sound and how undistortedly beautiful the lead singer brought this song to me. A-ma-zing. And with a channel separation of which I readily knew I never heard it before.

An other odd thing is that while on one side there's super speed exhibiting, there's an unsurpassed palpability at the same time. Listen to the snare drums and you'll understand what I mean. Full with body, never sharp and just how it sounds in reality.

Out of here
Peter

 86 
 on: January 16, 2019, 12:05:57 pm 
Started by phantomax - Last post by phantomax
Hello Peter,

Since my RAM OS was in an old recycled HDD I decided make a backup copy in an SDD just looking to the  future because rigth now I only have 16 GB RAM. Once copied I tried it just to verify that it was OK but for my surprise  all run flawlessly with only 16GB.                               
Am I wrong or it was supposed that you need 32GB RAM to use the RAM OS on SSD? scratching. Of course you have checked, my RAM OS is sui generis and probably  I am missing  something, but I would like to let you know because there maybe someone who doesn't purchase an SSD RAM OS just because not enough RAM.   

Best Regards

Maxi

PS. BTW the sound with the last settings is the best i've ever had.

 87 
 on: January 16, 2019, 10:49:01 am 
Started by Robert - Last post by PeterSt

Coen, you tempt me ...

But many years ago I worked on it for as long as was needed to find out that this is about a deep down Windows driver bug. This, with the notice that KS Special Mode is highly illegal to begin with, so there really won't be anyone feeling compelled to solve that bug. And when the driver is used in normal fashion, this bug doesn't surface ...

Peter

 88 
 on: January 16, 2019, 10:10:58 am 
Started by Robert - Last post by CoenP
Btw, if possible for your DAC, try to use KS Special Mode. If it works without ticks or buffer errors, it is "the best" (sadly not possible for NOS1 users).

like never possible?
 Cry

When fiddling with the settings and ignoring the ticks (for a short time) running in KS Special mode produced the best sound I ever had. I guess we have to enjoy superb yet imperfect sound forever....

regards, Coen

 89 
 on: January 15, 2019, 11:57:25 pm 
Started by hudesigns - Last post by hudesigns
Thanks much Peter! Looking forward to the next iteration. ZH

 90 
 on: January 15, 2019, 07:48:10 pm 
Started by Robert - Last post by PeterSt
No imagination, I think. Btw, if possible for your DAC, try to use KS Special Mode. If it works without ticks or buffer errors, it is "the best" (sadly not possible for NOS1 users).

Anyway, you are completely correct in your stance that the upsampling changes the buffer sizes inherently, etc. This is exactly why I created the NOS1 such that electrically this all does not matter (and the software cooperates  Happy).

Also notice that most DAC's will let themselves "overrule" for the filtering, hence, an e.g. 88.2 will not engage filtering for 44.1 (read : will not roll off under 22.05). This means that "our filtering" will be effective in maximum fashion. But if the DAC does not understand this way of working, then the overruling merely becomes "messing with". And then you will have quite contradictionary filters on top of it all. This is why a DAC actually should be Non Oversampling; now we can guarantee that our filters will be applied for 100% (not messed with even the slightest).

And oh, notice that each Q1 setting below zero, is a special application for the WASAPI engine. Maybe set xQ1 to 1 and Device Buffer Size to 1024 (I recall that ever back I made it for these settings and I forgot whether this is all taken into account). Minimum of Q1 for WASAPI is -4.

Have fun !
Peter

Pages: 1 2 3 4 5 6 7 8 [9] 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.069 seconds with 10 queries.