XXHighEnd - The Ultra HighEnd Audio Player
April 20, 2014, 10:56:36 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Dec. 31, 2012 : XXHighEnd + Phasure NOS1 DAC receive 6moons Blue Moon Award !
** "Lonely at the very top" **
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 2 3 4 5 6 [7] 8 9 10
 61 
 on: April 14, 2014, 09:06:08 am 
Started by CoenP - Last post by acg
But Anthony, I thought you already tried Coen's solution ? Ok, maybe not all of them - I didn't even read about this explicitly (kill hybernation).

But notice this has been described by me as any sorts of possible culprits (but not in this topic maybe) because what W8 applies there is a kind of dirty/dangerous trick. So, what actually happens is that at shut down the memory will be in the hyberfil.sys and at the next boot that is just read into memory so many things don't need to be re-initialised. And I guess that is a too dangerous thing for some parts of the OS, and it could even include SQ itself.

Notice that in the end Coen came up with this indirectly because that second boot needed (from cold). Ok, that would testify some other way around, but alas.

So not that I could reason this out in advance, but it really makes sense to me, once it has been proven that this cures the culprit.
That I missed it or forgot is something else. scratching

Regards,
Peter

Hi Peter,

When I came back to w8 a couple of weeks ago hibernation was already disabled from when I was using w8 before I went to w7, but I got the stops with 1.186(d) installed.

As part of my trying to get things to work I re-enabled hibernation and tried to get music playing stop-free before I re-disabled hibernation, but in over a week of re-starting I could not get stop-free playback.  Of course I did get impatient a few times and disabled hibernation from a a situation of play stopping but like Coen said, it did not work so I re-enabled hibernation in the hope of getting to the situation of stop-free playback so I could then disable hibernation.  And what do you know, for whatever reason today I did get stop-free playback without changing a thing so I disabled hibernation again and it seems to have stuck through some restarts so hopefully it all works tomorrow.

Fingers crossed.

Regards,

Anthony

 62 
 on: April 14, 2014, 08:59:40 am 
Started by CoenP - Last post by PeterSt
In case people need it :

Look for a hyberfil.sys file in the root of our OS disk. It's a plain copy of your memory, just in case the PC falls asleep - never mind you told it to never do that. That too is just maintained (and consumes your precious SSD space ...). Btw, the most unambiguous way to shut it off is to go to the command prompt (cmd in Run) and type this :

powercfg.exe -h off

Don't forget to press Enter, and next reboot.
Notice though that now all your hybernate and sleep whatever options will have disappeared from the menu's. To get them back, change the "off" into "on" for the mentioned command.

Btw, I can imagine this needs a command prompt "Run as administrator".

Peter

 63 
 on: April 14, 2014, 08:55:03 am 
Started by CoenP - Last post by PeterSt
But Anthony, I thought you already tried Coen's solution ? Ok, maybe not all of them - I didn't even read about this explicitly (kill hybernation).

But notice this has been described by me as any sorts of possible culprits (but not in this topic maybe) because what W8 applies there is a kind of dirty/dangerous trick. So, what actually happens is that at shut down the memory will be in the hyberfil.sys and at the next boot that is just read into memory so many things don't need to be re-initialised. And I guess that is a too dangerous thing for some parts of the OS, and it could even include SQ itself.

Notice that in the end Coen came up with this indirectly because that second boot needed (from cold). Ok, that would testify some other way around, but alas.

So not that I could reason this out in advance, but it really makes sense to me, once it has been proven that this cures the culprit.
That I missed it or forgot is something else. scratching

Regards,
Peter

 64 
 on: April 14, 2014, 08:41:30 am 
Started by charliemb - Last post by PeterSt

Hey Charlie,

You have always been special with your findings and good/clear reporting. Ok, in my view that is. yes But maybe also there's something special going on between us. I mean how big are the odds that I start working on this on day 2555 of XXHighEnd's life (which was yesterday) while only 16 or so hours later you ask for it with a couple of "please"'s.
Of course, that post in your topic about 48->176.4 could have been a hint, but still not because you found a dozen of these kind of bugs before. Still, when I started this little project I was thinking of you ...

So I guess something of this will show up in the next version.

Quote
(BTW - I read elsewhere on this forum that you tried noise shaping but could not measure it.   I ask, measure it?   Please.   It is very apparent if you listen with your ears and put away the distortion meter.   And also,  forget about loosing one bit.  Apparently it is better than round-off or truncation because those end up as music dependent error, which according to some is worse than noise.)

And that too. Wink
But let's say I have been ignorant till now because I don't see how any truncated bits which do so in the system noise itself can work out for the better. So please notice I measure reality (DAC output) and not theory (which can show noise at -200dB and better). And as I say so often, as long as things like Q5 etc. at 1 makes such radical differences, well, no way any dither is going to do *that*. So I'm merely in the leage of first things first, but to be honest there is no other first thing that I can see at the moment, so that is why this new project.

Regards,
Peter

PS: I think I will move this to a separate topic.

 65 
 on: April 14, 2014, 08:35:31 am 
Started by CoenP - Last post by acg
I give up, I have no idea what is going on.  This morning I fired up the computer selected an album and suddenly about 40 minutes later the whole thing had played through.  What?  No stops?  I've done nothing since yesterday except shut down the computer and then restart it this morning.  I've not adjusted the BIOS or any windows settings or XXHE settings or anything else.  So what is happening? 

So, realising that I had an album play through for the first time since I came back to w8 a couple of weeks ago I took Coens recommendation to disable hibernation and played tunes all day today.  Just to make sure everything was working properly I have shut down and restarted four times and each time have struck no problems.

I'm lost and have no idea what was going on before because I did exactly zero to fix it other than the hibernation thing when I realised all was working properly.  So Peter, problem solved?? scratching

Anthony

 66 
 on: April 13, 2014, 11:55:54 pm 
Started by charliemb - Last post by charliemb
The only thing I'll mention here is that I've got Miska's HQPlayer working at 32/768 with the NOS1. I'm finding it really educational, to the extent that I now feel Arc Prediction may be creating some audible side effects. Offering some minimum-phase filters, and maybe also some noise-shaping schemes, as options in XX would be very welcome.
Mani.

Mani - I agree.

Peter - Not just for NOS1 owners, but also for those us whom don't have an NOS1 (like me at this time).   I've been trying HQPlayer under minimized OS thanks to xxHE and love Miska's asymFIR filter at NS9 noise shaping at 4x for 16/44.1 material.  It sounds so very analog and pure that I am often preferring that sound over even highRes.   For this to work with my OS DAC, I set the filter rolloff to slow, opposite of defaults, and makes this DAC act more like a filterless DAC.   It is very open like this, almost filterless.  My DAC is the W4S DAC2, the original.   Of course I'd also like a minimum phase fiter as well per Mani (by this I mean a min phase reconstruction filter).   

Miska's (HQPLayer) asymFIR filter rings, but the preringing is less than usual and the post ringing is more than usual and so this gives a more analog sound while sounding lush (because of the reconstruction part of this type of filter).  There is some phase shift at some point, but less so than with a minimum phase filter. 
     If I encounter any hardness from a CD, which is rare, I switch to poly-sinc-shrt-mp or poly-sinc-mp (both minimum phase).   And if hardness remains, I downshift to polynomial1 (interpolation) or minringFIR.

Please please please????

Also, can we have some noise shaping with that?   (BTW - I read elsewhere on this forum that you tried noise shaping but could not measure it.   I ask, measure it?   Please.   It is very apparent if you listen with your ears and put away the distortion meter.   And also,  forget about loosing one bit.  Apparently it is better than round-off or truncation because those end up as music dependent error, which according to some is worse than noise.)

 67 
 on: April 13, 2014, 01:59:12 pm 
Started by charliemb - Last post by PeterSt
Looking into that today, and it even comes as a surprise for me that AI can only upsample from 44100 and only that. This, while "earlier on in the program" all is prepared to do all (or at least way more) so to me (and by now) it looks as if all is working. Worse - the general routine for it does not fail on it, but actually it just goes way wrong.

Anyway, working on that now.
Peter

 68 
 on: April 13, 2014, 11:33:47 am 
Started by CoenP - Last post by acg
I have not noticed anything unusual about the monitor in w7 or even when it does turn itself off.  The monitor that I use for the XXHE PC is shared with another computer, so more often than not I start the playlist playing and then switch the monitor to the other computer and then switch back when the music stops.

But I will take some notice in w7 next time.

Anthony

 69 
 on: April 13, 2014, 09:49:27 am 
Started by CoenP - Last post by PeterSt
One other thing Anthony :

My monitor is set to never switch off, and indeed it will never do that (W8). I didn't have it like that for always, but I'd say for way longer than since last December anyway. However, what I noticed is that for W7 this won't "work". I mean, whatever I set, in W7 it will always go off in ? ... an hour ?

Just thought to mention this because you feel the display setting regarding this is related ...

Peter

 70 
 on: April 13, 2014, 09:37:42 am 
Started by CoenP - Last post by acg
And still I never heard of the problem any more since 1.186. And otherwise I maybe recall one occasion. Re: WIN8 stops.

But there's also a report that it is related to the processor speed. Actually two, because in one occasion I suspected it myself. So Anthony, I am sure I ran into the thing daily when my speed was 720MHz or so. But since I run it at 430MHz never again. Back at the time I couln't make this consistent because it was always a bit waiting what would come out of the speed but since I know how to consistently do that ... maybe it is just that. So this is with the BIOS settings as described here : XXHighEnd PC BIOS Settings with the notice that origins from January 17 (so earlier than that topic) and that "weeks" before that I rean with that 430MHz already (but didn't know how to deliberately do it but friggled until it did). So if you like you can set those literal BIOS settings and see.

Another quite interesting thing would be that 1.186(a) itself did not deal with the 16 cores properly. Btw not did the previous versions. However, now it does, so now it impacts the issue ? can well be. This is how Scheme 3-5 can work out differently because this scheme works with the "first" cores which are the same as with not Hyperthreaded. 1-2 works with one of these "physical" cores while the other one is the Hyperthreaded one.
And of course, you used the lot not-Hyperthreaded (with your Xeon) because it just would not work because of this 16 core omission in the software.

All IOW, quite some things changed and actually so many (including your own settings) that it can be anything and also the combination.

Anyway I never saw the problem again since say the end of 2013, and I think the same with others (while *everybody* was suffering from it).

Now what to make of this all ...
Regards,
Peter


I will change my processor speed tomorrow and report back.

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.286 seconds with 15 queries.