I switched in the new Zipped Engine 3 and still get the same error.
Well, currently I really don't know how to proceed on this one. Maybe this tip helps you at helping me what is going on :
At a "No Track given" error, XXEngine3 expects a next track to have been prepared by XXHighEnd. There is 14 seconds to do so before XXEngine3 gives up and presents the message.
Now, when you look at XXHighEnd (Attended) you'll see the selection bar disappearing, which is the time XXHighEnd starts preparing the track. "Preparing" means a.o. conversion from FLAC to WAV when in order. After this XXEngine3 has to do some things as well, and this is included in the 14 seconds. Thus, the time XXHighEnd needs plus the time XXEngine3 needs can last 14 seconds at maximum.
There are a few reasons (besides bugs ! -> appearently there was a bug also, since solving something solved it for Leo) that these 14 seconds can be too short :
1.
The disk where the file has to be loaded from is sleeping and has to spinup. This takes time, and how long depends on the drive.
This reason by itself should encourage you to test with files on the OS disk. Chances are little or zero that this disk will sleep ever.
2.
The drive is very slow or the track is very long (and the combination of course). For example, an USB disk just *is* slow.
This reason by itself may encourage you to test from a drive of which you know it should be fast. Direct SATAII is the fastest (for consumer PCs).
Do not tick "Copy to XX-drive by standard" (at testing this).
3.
The CPU is not the fastest. Note that this sure is not about the clock speed only, and things like second (lots of) level cache contribute highly to the speed. For example, might you hace a Celeron CPU, I'd almost say "drop that".
The CPU is needed within the preparation stage of XXEngine3, and it is also needed within the preparation stage of XXHighEnd when conversions need to take place.
This reason by itself should encourage you to test with native .WAV files first.
Also, do not tick the "AA" checkbox.
Note : To me it seems logic that your CPU might nog be the fastest, because the changes from 0.9v to some later version from 0.9w(-5 I think) are about more CPU activity in XXEngine3. If I am right on this, you should (for testing purposes) set "Split File at size" to the minimum of 12MB. Furthermore you can tick the Mem checkbox (main area) which avoids an in-memory copy, and lastly you could tell the system (again for these test purposes) that your DAC is 16 bits.
4.
Your DAC runs too fast.
When the DAC runs too fast, XXEngine3 will be finished with the track earlier than XXHighEnd expects. Note that the time bar from XXHighEnd is unrelated to the actual playing position from XXEngine3.
To check this, you should take your stopwatch and measure tracks for their consumed length. If a 5 minute track is over 2% fast, you will run into problems. Besides that you will have another problem.
Please let me know if you can make it work by means of the above "tweaks", and which one(s) did it, if so.
If nothing helps, don't forget to send me the log files, as I asked for earlier.
Also, if I fast forward XX usng the progress bar on the bottom of the screen, XX will crash my computer (Task Manager won't even engage).
Now this is something that really smells to something else being very wrong, most probably related to the other problem;
I really can't think of what, because repositioning this slider actually does nothing. However, it will restart XXEngine3 and incurs for some temporary heavy load. Is this bad ? I wouldn't know why except for encouraging for some additional delay in things. But this hanging up the whole PC ?
This occurring phenomenon makes me believe you should try another PC if available. From there on you possibly can learn what is actually going on.
But note : Somehow you call this "fast forward" while really it is nothing of that kind. It just skips (or goes back to whatever position you dictate). Now, you
could be just clicking besides the slider to skip a piece of the track, or even hold down the mouse button and move it around. The latter will let skip the pointer faster than holding it still. However, this will start XXEngine3 over and over and over and *that* may incur for a total system crash.
So if you are dowing it like this instead of picking up the pointer and dragging it to somewhere else ... don't. Also, don't pick it up for dragging when playback has not commenced yet.
Well, good luck with all, and keep in mind : there still can be a normal stupid bug in there.
Peter