- Thread Author
- #1
Roon 1.3 Is Live!
- Thread starter joeinid
- Start date
jdandy
New member
This paragraph is a bit disconcerting:
When experimenting with the new DSP features, proceed with caution. When DSP goes wrong, it can produce loud, potentially damaging sounds. Set volume levels conservatively at first, and do not take undue risks with expensive gear (or ears!) until you have built some confidence.
What exactly are they trying to say with that comment, "until you have built some confidence" ? Do they mean I am supposed to keep my fingers crossed and pray the code doesn't go haywire and blow out my expensive midrange and tweeters? I guess once a certain amount of time has successfully passed I can then crank it up a bit and keep my fingers crossed I'm good.
When experimenting with the new DSP features, proceed with caution. When DSP goes wrong, it can produce loud, potentially damaging sounds. Set volume levels conservatively at first, and do not take undue risks with expensive gear (or ears!) until you have built some confidence.
What exactly are they trying to say with that comment, "until you have built some confidence" ? Do they mean I am supposed to keep my fingers crossed and pray the code doesn't go haywire and blow out my expensive midrange and tweeters? I guess once a certain amount of time has successfully passed I can then crank it up a bit and keep my fingers crossed I'm good.
My interpretation is that user misconfiguration (rather than software bugs) can be harmful. Besides, convolution requires a convolution filter file created by a third party software.
Previously I said it means user misconfiguration of DSP can be harmful. Here is the perfect example:
https://community.roonlabs.com/t/crackling-after-using-the-parametric-eq/22264
To avoid it, Roon provides headroom management, and an indicator of whether music signal clips when using DSP.