XXHighEnd

I think this issue is related to playlists cause it doesn't seem to happen when playing all the songs on one cd. With engine 3, 2x arc prediction, when changing tracks with a playlist I get one of the following error messages: Logs for first message are attached.

Funny ...

You get this (first) message because it was built in 5-03 just for protection of Engine#4 (remember, your hiss). But, it was built in at a more general place so it also protects Engine#3, which actually is protected for the hiss by other means. Btw, 5-04 will just correct it, and won't give any messages.
So, done, I thought.

But as it appears now (by your beautiful experience), the *cause* of this to happen is not a track ending at an uneven boundary (which showed before in your case) but two different rips (from different prrograms) both having different data offsets in the file. And so, as it turns out now, this changing offset is not incorporated in the check while the offset itself is part of it. Before this was no problem, but the check/message/now correction uses it (the playback already did, and therefore no hiss because of this -> now it stops because of the message :swoon:).

Once again, thank you very much for your sharp observations ...
Peter

About the second message ... it seems that this hardly can occur during normal playback; only when playback starts right after clicking Play (or Next). *Maybe* with Attended from one track to the other, but I'll need the X3 and XX log files to judge it.

Notice that this message occurs when (for example) you chose Engine#3 but a KS: sound device. It is just what it says and can only happen for Engine#3.

boleary, can you please keep in mind to test the issue with the first message "somehow" for 5-04 ? So, it is solved, but I have no way to test it. That said, it will be hard to test, because everything will go unnoticed anyway, and only if I did something wrong there might be a little tick, or hiss again when I did *really* wrong. The best way would be if you could send me the two subsequent tracks where this happened, so I can check it in the code.

No obligation, but if you send them I will check it. And if you do, don't change the formats (meaning : leave it WAVs or FLACs as they were).

Thanks,
Peter

Okay, do you want the tracks now or after testing with 5-04?

Now please. So I' can be ahead of you. :)

Hahaha, I started those three tracks very faint in the background while watching some TV, and while I heard the second track sounding different from the first (hence tracks were changed) I thought "but oops, what if my correction doesn't work" and waited for some blasts (remember, I use digital volume only, and when static is in order attenuation won't attenuate static). So, telling nothing to my wife I let it all continue, ready for a heart attack.

In the end all 3 tracks played normally, and the log files showed 3 different rip sources. You really know your abouts !

Anyway, solved for 5-04.
Thanks for your help !
Peter

Wonderful getting that one so fast. Now I've waited all day for the "Wanted Sound Device Could Not Be intitialised" to return....and,finally, it did. Again, 9y--5.03., Engine #3, AP. Logs attached, but they don't show much.

The error happened after I stopped play to see what track was playing. Restarting the track from the beginning seemed to "cause" the error message.

Here's another invalid buffer error. This was changing tracks from the same cd. (9y-5.03, #3, AP) Last track failed and error message appeared. Logs attached.

I didn't look into it yet, but just noticed it myself at using Next (Engine#3). Completely repeatable.

Hi Peter, have you noticed that engine 3 in 9y-5.02 is much more stable than in 9y-5.03? With .02 I don't get the messages at the beginning of this thread when playing tracks from the same rip or cd, or even when playing a series of tracks that used different ripping software. It seems with .03 I get the messages whether the tracks were from the same rip or not.

Hi - Well, I guess it needs more in-depth reading of what I all told about it. :)
The messages got in for Engine#4 (just for protection, not for solution), but went in a "general" place, so it affected Engine#3 as well.
Also, Engine#3 corrects this already, dus a. the message is useless for Engine#3 and b. without message there wasn't a problem.

In the end, exactly what you notice.

For 5-04 the messages have gone, and the "correction" is there for both Engine #3 and #4.

But hey, better mention too much than too few ! So thank you, as usual.
Peter

Slow learner here..... :)

Well, you probably know what de-bugging means. I'm a bugger.
:whistle: