![]() ![]() But be warned that the soxr resamplers have roughly 5-20 times higher latency than speex-float, in terms of time the worst case for soxr-mq/hq can be as high as 20 ms while soxr-vhq latency can in few specific setups reach over 27 ms. In particular resample-method = soxr-mq should provide acceptable quality while even the higher quality and hence slower soxr-hq is still cheaper than the default speex-float-1. Starting with version 7.0 there is also soxr resamplers made available by enabling the sox USE flag. Since re-sampling is done per each channel per input, channel configuration and number of applications can affect performance as well. re-sampling 44.1 kHz to 48 kHz is faster than re-sampling either to 192 kHz). Re-sampling can require quite a lot of computational power, PA defaults are rather conservative but in certain cases can still take a significant toll, in such cases edit /etc/pulse/nf and consider changing resample-method to something less CPU intensive, default-sample-format and default-sample-rate can also affect CPU utilization with higher bit-depth and larger difference in sample-rate generally needing more resources (e.g. In case of buffer under-run latencies are never decreasedĬurrently, if a buffer under-run occurs, PA buffers for longer increasing latency, but it then never tries to buffer for less until restart. This can be be milliseconds to hundreds of a millisecond without regard to what applications require. Close the program and reconfigure it to use PulseAudio.Ĭurrently PA provides whatever latency is possible at the moment. Solution: There is probably an issue with the Pulse server. Problem: Audio has strange distortion or static when playing an output. Deleting ~/.pulse* configuration files and forcing fresh ones to be generated by restarting the daemon may fix no sound condition.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |