z05 | Q1 Factor (huge latency setting - more advanced usage)

[PeterSt]

For Engine#4 / Kernel Streaming, the Q1 Factor slider acts as a multiplier for Q1.

Watch out : Whether a net Q1 value of above 30 can be used, very much depends on the device / interface / driver. It is expected that Asynchronous USB devices are able to utilize it (on Vista / W7 / W8), but time must tell whether this really is the case. For the Phasure NOS1 Async USB DAC it for sure works.

A net Q1 value of 30 vs 31 and beyond, does not imply special settings. It is just that the latency becomes larger and the larger latency can be seen as a "strategy" as how it was first applied to the NOS1 (per July 2011) and which requires Kernel Streaming Adaptive Mode. This, opposed to that other "lowest latency" strategy  (achieved by means of Kernel Streaming Special Mode). Both strategies operate in opposite directions and imply a very different sound. We could say that the low latency implies super detail but which is a kind of stressy, while the high latency creates ease all over, and where other means of good reproduction must "create" the high level of detail again.

It is to be noticed that the really higher settings imply a memory usage which can be unbearable for your PC. For example, with 8GB of internal memory (OS = 64 bit), a Device Buffer Size of 4096 (which is also in the equation), Q1 at 30 and Q1Factor at 40, an SFS of our usual 430 will put forward anomalies sooner or later. It may run, but it just as well may not and produce an error (also see the ToolTip on Q1Factor). An SFS of 370 with these further settings is OK though.
It is not said, nor was it tested, that more memory allows a higher SFS setting.

High latency *really* is high latency, and you can easily think of 30 seconds. So indeed, you press Stop, and only after 30 seconds playback stops. But, this is with certain other (new) settings only; Be prepared anyway.
With the further settings the same, a Q1Factor value of 13 is very well doable in all circumstances (of other settings). Anyway it is the advice of trying the extremes for sure, but keep in mind that there's also conveniency in order.

Advance usage

Not a special paragraph, but it has to be emphasized that working with the "huge latency" settings, implies constraints for technical reasons, and they can't be overcome, nor is it hard to warn for them by the program itself. For example, the means how internal buffers are applied, means that the SFS has to be at a minimum size (or setting) in order to let all keep on operating (playing). You may well think of something like when the latency of the Q1 Factor is 30 seconds, the SFS is not allowed to be less than that. The (math) rule for this exists, but is too hard too explain (about sample rate, bit depth, factor of upsampling, "DAC Needs" and some more).

As a general rule think like the SFS must be near the maximum your system allows, that making the high Q1 Factor values possible.
There is also a relation to the file size, and when playing in Attended Mode, the running time of the file can't be smaller than the latency implies. A bit of the same story.

Similarly, but important to remember, is that Attended Mode in general does not allow high Q1 Factor settings for proper playback. A message when attemtping a too high value will tell you that most 99% probable playback will stop after the track played.

And so, important : The huge latency settings implied by the Q1 Factor can be used in Unattended Mode only and then *still* constraints are in order (as said above).

To keep in mind : The latency we talk about here is a factor of the Device Buffer Size setting in XXHighEnd, the Q1 value and the Q1 Factor value;
Neither individual setting will do something special to the sound, and it is only the result of the multiplication which counts. So, 4096 (dev. Buf) x 30 (Q1) x 10 (Q1F) is the same as 2048 x 15 x 40.