... but since I never give up, I managed to tweak the unallowed changing of the inherited Appointment (Affinity).



Below a few plots for Scheme-3 (must work out the others), noting that Scheme-3 plays sound on core 2, while the other processes are preferably on core 1.
The spikes represent the track load (hence the preprocessing of it), which went to core 2 with Scheme-3 before.

What I observe (or seem to, relative to how it was) is that there is plenty of headroom now for the 4-6 minute tracks which are loaded here. Normally the cpu shows a horizontal line at the top for the Doubled padded to 32 bits tracks (which for the before situation indeed would indicate some heavy working against itself e.g. heavy core cache switching). No squeezed toes in my shoes "will it do it" now. It just feels good.
Btw, Q1 is -2 here.

I'm near the end of Amused to Death now, and no single hiccup. Does this say anything ?

Oh, note the plots are at full throttle here, and TaskManager itself consumes the most cpu. The most flat lines in the right core are the most representative for what Engine#3 is doing. Where core 2 shows more activity, it's the "dying out" of other services being active at that moment. Picture 03 shows this from off the middle (the track load is not visible anymore (but for in the memory line, near the left).
In 01 vs. 04 (and 02 a bit) you can see that core 2 tends to help core 1. In 01 this apparently was not necessary. By itself this is good balance, because the paying thread now is on both cores temporarily ...

Please provide more detailed info when you can Gerard.

FYI : So far I am not able to solve this by a different Appointment (Affinity) to the loading thread, but also the temporary change of Q1 cannot work. The latter is related to Exclusive Mode not being able to initialize more than once per Ausio Session; with 0.9u-14 I thought I could trick it (according to the concerned properties), but this turns out not to be so.

For now this remains unsolved for those who are bothered by it.

The bug as announced by Johan has been solved in 0.9u-14a.
The problem itself (hiccups for some) has not been colved by this.

Refer to XXHighEnd Model 0.9u-14 (with AA filter for up- and downsampling) for the Release Notes.

This version, 0.9u-14a solves the bug of when Q1 being higher than 14, erroring at loading the next track (XXEngine3 stopped working).
On this matter, the attempt to attack the hiccup at the load of a next track (with the Mem box unticked) has miserably failed.

Sorry for the inconveniences (thus, those hiccups - when you experience them - are still there).

Gerard, this must be something else.
Q1 >= 14, yes. But < 14, it does nothing (different from before).

From one side I heard that you were moving.
From another, that you are looking for a house.

Did you gear up in a camper ?

That's exactly how it already works ...
... but something is wrong in that case I suppose ...

All that remains is finding the proper cable (pair) belonging to that.

Sorry to respond this late Gerard. But do you happen to know when (which version) they still played ?

And when you say "FLAC error", can you tell what the error is (about) ?
This looks like an error from the FLAC decoder itself, which makes it unlikely that it worked before. I mean, I never had another version of this than the one right from the start ...

We didn't read tfm.
At least I am not into manuals. No time you know.

It is strongly advised to not use your system without a preamp (or the pre-amp at max volume for that matter) if you or your speakers won't be able to handle a situation that e.g. the file contains wrongly formatted data or otherwise - because of which cracks may emerge with an energy beyond imagination.

All,

The above is the message accompanying all the 0.9u versions;
But is it still necessary ? Did anyone bump into severe cracks at the latest versions ? Please take into account that "severe" means "dangerous" in the case you have your analogue volume wide open ...

If not, this serious warning can be removed. But if so, I will be glad to hear in what occasion(s) this still can happen ...

One thing I will do anyway : present some (Cancel Yes/No) message when UnAttended playback may incur for some danger regarding this, which will be when the Digital Volume is not at -0dB (suggesting you will not be using a pre-amp in the mix).

?

Ah ! How ? how ! how ?!


But not better than the CMedia I suppose ?

Indeed it takes special skills to get normal audio out of that mixer. Personally I couldn't get any sound from the EMU carde without that mixer, and not including it.
It is a nice thing to get (Proteus) synth (MIDI) sound from it though.

Indeed it seems that hybride has deleted his post about is "second hand" EMU 1212 he bought, with too smooth sound opposed to the CMedia compatible card he uses.