Closed stnslvk closed 1 year ago
Thanks for the report, I can reproduce and will take a look at some point. Quite a confusing bug though!
Ah I think it's the TZFM DC blocker blowing up, as a workaround until this is fixed - if you disable this from the menu, does the issue go away?
Hi Ewan, thanks for looking into this. Correct, the issue occurs only if 'Filter TZFM DC' option is enabled - forgot to mention this in the description.
Also, please have a look into 'Timber' behavior. With the same conditions, PonyVCO output goes to 'nanV' when it set to the max (1) value.
No problem - could you clarify your second point there with a picture? I can't reproduce that so far.
Interesting, cannot reproduce that on a freshly added PonyVCO instance either. Maybe there was some additional steps i took earlier . Will provide additional info a bit later.
Further related findings are here #41
I think the DC filter is unstable - it uses normalised frequencies so 5Hz / 192kHz is just too small a normalised filter frequency to be used. I switched to RCFilter which is stable even at those rates. There are new builds, can you confirm that this fixes things for you?
At first sight the issue is addressed. There are no more 'NanV' at output. Happy to close this one. Ewan, thank you.
In case 'Filter TZFM DC' option is enabled, PonyVCO's output goes to 'nanV' while FM'ing at sample rates of 192 or 768 kHz.
To reproduce
Outcome
PonyVCO's output goes to nanV
There is no issue in case Rack operates at sample rates other than 192 or 768 kHz.
Rack Engine SR is to 48 kHz - ok Rack Engine SR is set to 176.4 kHz - ok Rack Engine SR is to 192 kHz - issue Rack Engine SR is to 352.8 kHz - ok ... Rack Engine SR is to 768 kHz or higher - issue