XXHighEnd

Next to several other inconsistencies between boots and playsessions caused by WIN8, I am now stuck with a typical situation that the XX timebar is running at about half speed. Maybe it is half speed I am not shure.

I mention the first because WIN8 seems to have a mind of its own. Stange stuff appears and sometimes disappears without my (consious) intervention. This issue appeared after a regular boot some time ago.

I couldn't find an running issue on this, maybe someone raised it allready in another thread.

The thing is that after the music ends (iow the track is finished in the indicated real time), XX plays silence until the timebar time ends (indicating the original playing time). So that is the same track again but without sound!

Sometimes XX stops at the end with the message: "audio device could not be determined" or an "Engine #4 did not start in time".

After applying almost all tricks in this forum, every now and again I hear good things in WIN8 but it is very very véry inconsistent. Too much work and too little pleasure I'm afraid. Let's cross our fingers for 8.1.

Regards, Coen

P.s. i just saw that the systemclock is also slowed down.

:scratching:

A few WIN8 boots later, the timebar runs fine, yet EVERY track ends in an "engine #4 did not start in time" error message.

I lowered q1, q1x and sfs toget rid of it, but without success.

No problems with XX on the spinning disk,it works at the cost of SQ.

Regards, Coen

Coen,

Are you suggesting that playing from RAMDisk causes this ?

Btw, I see people advise to use a 500MB for the RAMDisk where XXHighEnd resides, but that really is too few in my view. I use 2GB for it.

Peter

?
This seems to imply that some processing is written during a session where XXHE resides... Is it related to the number of songs that are in the playlist ? Can you explain a little more ?

So if I use 2GB for XXHE (A: drive) and 2GB for playdrive (B: drive), this means a lot of RAM has to be dedicated. It would mean at least 12GB of RAM to be "on the safe side" ?

Alain

Correct Alain.

The whole mechanism implies that all goes to the "XX Drive" first (on purpose that is, so that won't ever be eliminated). Only WAV won't get there.

Regards,
Peter

I thought that this "filling" on the XXHE disk would happen if the "Copy to XX-drive by standard" was activated... 

Again, correct.
But when the Playback Drive is used this happens also.

Peter

I managed to add an increase to the XX program IMDisk imagesize. Actually a made a new one in NORMAL OS.

I ran a track of 9:12 minutes and the next track started seemlessly. I am cautious to conclude it is due to the larger IMdisk size (2Gigs) it could also be some WIN8 boot magic. Yet it worked, however...

Next problem arose: if I pause or stop the music now (or something similar like pressing the PE button while playing) It won't start anymore. I have to clear the XXEngine3 to get it started again....

Regards, Coen

A reboot cured the last problems, so a "solution" is available :grin:. The post on how to use a RAMdisk was very enlightning and much of my mahem might very well have stemmed from a too small disk. No troubles so far.

Am I happy with this result? Well in one way yes, in another no. I still would like to find out why I am experiencing unacceptable sound quality with windows 8 no matter what settings I try or what I do with the BIOS. Een the best combination is rather poor. I had secret hopes that my inconveniences were a symptom of a problem that also would lead to better sq... No luck this time! :)

Regards, Coen