XXHighEnd

Hi Peter,
I have some problems with the new version of xx. It occurs quite often that the playback stops, with the error message "End of Track". If I click ok, the track starts again from an earlier position.
This seems to happen especially when I start windows 7 in debug mode. In this mode, most services are shut down and the biggest advantage for me is, that the hard drive makes no "sensless" noises. Also, I can use much bigger sfs and can start more tracks before the sfs error message "make smaler sfs..." appears.
Maybe there is an easys explaination why and a way how it could be solved.
Greetings Adrian

This message shows also in the normal mode as I experienced. But it seems to happen not as often as in debug mode.

I think I know what this is, not sure though ...

There will be services (and I don't know which one or ones) which take care of cacheing or more generally - speed up things related to disk I/O. When this service is not running, for sure it can happen that a file has been deleted, but the "space" is not freed yet. This really can take 30 seconds to my experience (and is VERY annoying).
XX depends on these kind of things, so there it will go wrong.

I don't think this will happen with Unattended (which is far more decently operating anyway).

Btw, can it be so that you use AI filtering ? the other day I noticed that at least with A-B active it is very prone to the End of track thing.

If you have some news on this, let me know; then I will try to solve it.
Peter

I don't use AI filtering. As it turned out, it happens also in normal Windows mode, where all services are running. I just had the problem twice in one track. I think this is related to the small sfs I use (10). Most of the time I use attended playback because the pc is not dedicaded to music only.

Aha !
Yes, there is something in there which relates to that. But I'm afraid I can't to much about it. Also, it depends on the PC how much it bothers you.
But before we drift in the wrong direction, can't you set the SFS somewhat higher to, say, 40 - just play as usual but watch whether the pattern of this has changed ?



I must honestly say that I tend to think that in such a case you shouldn't "complain". Your PC has only to be a little slow-ish to let the audio collapse. Well, with the limits we are using (and crossed).

But also see your other topic. There might be more going on. Quite confusing ... :)

I can use 50 for mixed in normal mode and 110 in debug mode. It also occured with this higher settings. Maybe the sfs is not the only reason or was a misleading idea. There was one track, where directly as the track should start the error message poped up. The remarkable thing is, that I could repeat this 2 or 3 times. I started the track before, about 20 seconds before it's end. Then as the new track should play, the error appeared.


It also happens if the pc is doing "nothing". I would really like xx to be more stable. Then I could wholeheartly recommend it to friends. That is why I am complaining.
I look at it as a kind of science and how it is in science, there are always problems to solve. So I can understand, that there will always be some new problems. But a bug "free", stable version 1.0 of xx would realy be something! Even if it would not have the best sound possible at the moment.
If there are known border crossings that make xx unstable, wouldn't it be a good idea to have a kind of save mode for xx?

Yes. We call that "Unattended". :) :)