No Track Given Error

[PeterSt]

First it does not react during play, which did work with the course version. So procedure is now: stop the play, change volume, restart

I think you misjudge this. It is still working, but you have to use the slider. As before ...
I did this on purpose, but right now I forgot why. Something with remore control (but can't justify that right now ... will grab a beer).

[PeterSt]

Ok, just now (after 36 tracks) it went wrong. But :

As you (Leo) did, I had ticked the "Copy to XX-drive by standard" checkbox, and at the moment it went wrong a first track from another drive had to be loaded. So, this drive had to spinup (takes near 10 seconds I think) ... Also this was a FLAC, and all together there wasn't time enough to present the track to XXEngine3.

But ticking that parameter is wrong for Attended Playback !

It adds nothing for Attended Playback, and the only thing you can get from it is ... not enough time to load the track.
Note that this is not a problem with Unattended Playback, because then all is converted and loaded in advance, and only at the first track the spinup time of the drive plays a role (underway during "loading" the Playlist other drives may spinup, but the first track is then happily playing ... ok, when "Start Engine3 during conversion is ticked"), but which doesn't harm because Engine3 hasn't been started yet at that moment.

Understand ? (I can hardly make it up myself ).

So *this* is a reason anyway.
I will change the code, so that the "Copy to XX-drive" won't be active at Attended Playback.

[Leo]

I had far fewer problems allready, still some however, and now I have unticked the copy to drive. I'll report on tracks that still gave me errors with these settings.

[Leo]

so far no problems, thanks Peter. And now back to just listening for fun instead of waiting for problems. SQ is great, W7 aided extra by putting the B1 buffer of Nelson Pass before the Chipamps.

[PeterSt]

W7 aided extra by putting the B1 buffer of Nelson Pass before the Chipamps.

Hey ... great !
I just laid my Perreaux buffer aside because the DAC can do it herself. Oh yes, that is a she.

[Leo]

A she that can do the driving as well ?  Really I am getting more and more curious about your  NOS!

[KUOYAO]

Peter,

I switched in the new Zipped Engine 3 and still get the same error.

Don't know if this is related...when I play a file in a directory with Chinese characters (unicode), it'll play, but will give me a message saying "Error XXHighEnd-00 : illegal character in path" next time I re-open XX.

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).

Cheers,

Kuo-Yao

[PeterSt]

Did you use the *latest* zip ? there are two in this topic now !
You should have used the one from this post : http://www.phasure.com/index.php?topic=689.msg4966#msg4966

I'll come back on the chinese characters.

[PeterSt]

Leo, do you still have the idea it was solved for you ?

[Leo]

Yep, so far so good.
Some Window messages after new version of xx, messages like Services not available, but just click and they fade away... And they have not returned today.
Just enjoying the music and SQ

[PeterSt]

Thank you Leo.

[PeterSt]

Hi Kuo-Yao,

1. Please read a few posts back too, addressed to you.

2. Can you please send me a track name in chinese ? Send this *and* by means of copy paste in here *and* a copy-paste by email in the email body, *and* via an attachment and copy-paste in a Notepad file. I just don't know how I will receive it.
What I want you to do (when you have the time) is the following :

a.
Load that one track in the Playlist Area of XXHighEnd, and see if you can get the error with that one track only. I hope you can, otherwise things will be too cumbersome for you.

b.
Your track will be in a folder structure, like c:\MyMusic\Dance\The Dance Group\01-First nice track.wav
Now I would like you to copy each piece of that structure separately, so it becomes

c:
MyMusic
Dance
The Dance Group
01-First nice track.wav

Of course you have your own data, including the driver letter !
Copy-paste those lines as how I described before.
From this I will be able to mimic a music track with this folder structure, and see what happens. Probably I can't deal with it anyway because of the codeset I use, but if we don't try we get nowhere.
In the mean time I will look in the program whether I can find a solution from theories.

Another question : I assume you always had this ?

Lastly, please look at the title of this post. Have that in your reply the same, otherwise later I can't find it back. It should have been in a separate topic anyway ...

A lot of questions, but I hope we can solve it. Thanks for your help,
Peter


PS: You can do the copy paste of those parts easily by means of going to each folder (and in the end the file) and start Rename. Instead of renaming it, press ctrl-c to copy the contents.

[KUOYAO]

Peter,

I'm using the newer engine 3 as you specified.  Problem persists.

[PeterSt]

Can you please switch on Loggin (Settings Area), let it go wrong for at least one time, and send me both the XX and X3 log files ? Please be sure that you send all the X3 files from your session where it goes wrong (look at the date/time which is in the file name). Better send too many than too few.

Thank you,
Peter

[PeterSt]

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