XXHighEnd

Strange, 09z-2 has been running smoothly on my computer since I installed it over a month ago. However during the last few days,
I noticed that the last song on a playlist always stop about 5-10 second before the end of the track.
If I only have one song on the playlist, everything is fine but if more than 1 song on the playlist, the last song always stop early.
The setting remained exactly the same for the last 3-4 weeks, no new program or anything else added to the computer.
The server is win7, dual core, I use engine 4, power scheme 3, 1024mb buffer on both xxHighend and Lynx card, running 4x arc prediction.

Thanks for any suggestion or help.

Peter,

Having the same problem. Sometime's it stops before end. Did not have much time to investigate how or when it happend's So not 100% sure if it is exact the same thing like Suteekat.

 :)

Ps: Figured out the 110/220 thing yet?

Grtz

Suteetat, this is with Attended I assume ?


:offtopic:

PS: Gerard, not with the stupid supplier (waiting a week for answers, and sent them an email every day). And then to think it is only a matter of getting another kind from their same supplier/manufacturer. I HATE this world.
But it didn't prevent me from building all in the cabinet. After a week waiting for the first answers. :aggressive::aggressive:

Same here. It doesn't happen all the time but it does happen. This is in Attended mode...

I have the same problem (attended and unattended)
Most of the time playing one track is ok, but playing a second  one (or 3rd, 4th...)
the tracks stops frequently 10/15 seconds before the end.

Almost always unattended mode doesn't remove the CD-cover-backdrop
after playing.

Yes, in attendded mode. I will try unattended mode when  I have time this weekend.

I tried unattended mode this morning briefly and all seems fine. For the first time. in attended mode, even if I have one track in the playlist, it also stopped prematurely near
the end.

Suteetat,


I your "Data" folder, there's a file named !Played.xml (actually this is a Playlist). Assuming you don't used that (to look back what you played), you can throw it out.
It is the only thing I can think of that grows over time and may influence.

Peter

Peter, I only found !Played.plxx file which I removed. Unfortunately that did not solve the problem.

This is an old bug, this has never been solved. (Peter is aware of this !)
I have this problem too, for over a year I think.
This has nothing to do with the latest version.
 :)


Hard to solve with no obvious reason were this happens.

Roy

Hmm ... It has been solved allright .. according to what people said. But then with others it came back. :swoon:

In this case I think it *is* a problem of 0.9z-2, related to the "within a few seconds" startup of XXHighEnd at Unattended - of which I already said elsewhere that this is no good and the "20 seconds" will be back in 0.9z-3.

But, not sure this is exactly what a few of you receive now ... indeed it always has been a very nasty problem ... uncopyable.

Peter

Btw, I just played an HDCD album (Unattendely), and I don't think it played even one track fully. So *there* something for sure seems wrong !

I wonder if the problem might have to do with any of the recent update from Window?
Until last week, I never this problem before, at least on regular 16/44.
However, I now recalled that in the past, once in awhile I also had problem with tracks terminated
early but only with high rez 24/92 or 24/192 but never 16/44 and it was more random, it seems.

The only think I can say at this moment is that 0.9z-2 is too "fragile" at determining whether the last track has been played. This is about that "few seconds" thing. For Unattended this shouldn't matter (and it was made for just that -> start XXHighEnd after playback has finished), but it also related to XXHighEnd itself, thus Attended playback;

When the last track has played this is detected by, well, no new one is provided. But this is timed.
Now, when e.g. an upgrade would cause things to being more slow -and don't forget spunoff disks here !- XXEngine3.exe will say "ok, this was it" and quits. This may happen at track boundaries (there's extra "stress" there) but also when there's nothing more found to play and another process of "waiting" starts to be in the loop (while playing by itself still continues from the last part read).

It is (too) difficult to explain, but while I will do something wrong in the basics somewhere (again, this always has been a pain), it *is* encouraged to go wrong when things are more slow. This will be especially in the I/O (disk) area. And upgrades do influence that sometimes ...

You could try to revert those upgrades, but I will look into once again. Somhow what happened to you is informative to me ...

Peter


PS: The Split File size parameter influences this too. Smaller or larger - things work out differently. But please don't fuzz with this to solve it ... I only mention it because you may have changed it recently.

For what it is worth, the problem suddenly went away and I did not really do anything. Just went and used unattended mode
for awhile and came back to use attended mode while I wanted to listen to samples of the new CDs that I just got and voila,
no more problem!

Well, whatever it is that may cause it to be there or not, I am pretty sure it is solved for 0.9z-3.

Btw, maybe you can recognize the temperature has changed, and now is back to when it worked. I am not joking here;
If your DAC is only a little off (like 2%) it just makes *the* difference. Notice that 2% over 5 minutes is 6 seconds.
What was in there (for Attended), was something which redundantly did something with the track time, and I eliminated that.

For Unattended it still is/was the matter of the "within a few seconds" startup of XXHighEnd, which also has been eliminated (back to 20 seconds).

So, I hope it will be solved in 0.9z-3 for everybody.
Peter