|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
mhoev
on Feb 22, 2010, 10:03am, edited 1 time(s), last modified on Feb 22, 2010, 10:04am:
Hi all,
This may not be a that typical configuration, but I use Pristine Space as digital XO and for digital room correction. To make usage easier, the engine is always running, even if no music is played, no DVD watched etc.
Brutefir, a convolution engine for Linux, has a nice feature to save power under such conditions; here is the full description taken from their web page:
The powersave feature if activated, will monitor the inputs, and if an input channel provides zero samples, the associated filters will not do any processing, since with zero on the input, BruteFIR knows in advance that there will be zero on the output. BruteFIR will continue run as normal, and filters with non-zero inputs will continue to to process normally. As soon as there is non-zero input on a suspended filter, it starts processing again. This powersave feature is transparent, there will be no convolution errors if it is activated. The reason for having it optional is that one may want to make performance tests, without the need to feed a meaningful signal to BruteFIR.
If analog inputs are used, the input will never be exactly zero, and thus the powersave feature will not be triggered. However, if a value is specified instead of the boolean (for example powersave: -80;), that value is interpreted as the lowest level in dB the input signal can be, before BruteFIR will consider the input as zero, and trigger powersave. Thus, a noise floor can be specified, and then powersave can work together with analog inputs.
Any chance to see this feature also realised in Pristine Space?
Cheers,
mhoev
This may not be a that typical configuration, but I use Pristine Space as digital XO and for digital room correction. To make usage easier, the engine is always running, even if no music is played, no DVD watched etc.
Brutefir, a convolution engine for Linux, has a nice feature to save power under such conditions; here is the full description taken from their web page:
The powersave feature if activated, will monitor the inputs, and if an input channel provides zero samples, the associated filters will not do any processing, since with zero on the input, BruteFIR knows in advance that there will be zero on the output. BruteFIR will continue run as normal, and filters with non-zero inputs will continue to to process normally. As soon as there is non-zero input on a suspended filter, it starts processing again. This powersave feature is transparent, there will be no convolution errors if it is activated. The reason for having it optional is that one may want to make performance tests, without the need to feed a meaningful signal to BruteFIR.
If analog inputs are used, the input will never be exactly zero, and thus the powersave feature will not be triggered. However, if a value is specified instead of the boolean (for example powersave: -80;), that value is interpreted as the lowest level in dB the input signal can be, before BruteFIR will consider the input as zero, and trigger powersave. Thus, a noise floor can be specified, and then powersave can work together with analog inputs.
Any chance to see this feature also realised in Pristine Space?
Cheers,
mhoev
Aleksey Vaneev
on Feb 22, 2010, 6:10pm:
Honestly speaking, I do not find this feature important, because it makes overall CPU load unpredictable in a complex multi-channel project. It's not hard to implement this feature, but in my opinion its usefulness in a professional production environment is very questionable.
mhoev
on Feb 24, 2010, 10:54am:
Well, I can't judge if someone wants to use it in a production environment, but for the intended use in a HTPC it would be definitely a quite beneficial feature (and would create a USP for Space Pristine, as I am not aware of any Windows based concolver offering it yet).
Aleksey Vaneev
on Feb 25, 2010, 7:37pm:
Well, HTPC seems to be a very niche market, while automatic "switch-off" function does require a bit of CPU resources. I'll think about adding such function as an option, but can't guarantee it.
|
This topic was last updated 180 days ago, and thus it can be considered old. Replying is disabled for this topic.
|
Copyright © 2002-2012 Aleksey Vaneev - Terms of Use - Privacy Policy - About Voxengo - Questions & Answers