What sample rate are you using, @karlderletzte ?
Maybe, yeah. Thanks for the suggestion!
usually 44,1khz and 24khz.
That’s odd
Are you sure? You can set the sample rate in both the Engine menu as well as the output module. Is one of those set to a low rate maybe?
hello, yes i am sure.
usually i set the pulseaudio server samplerate in VCV Audio to 44,1 khz.
the engine menu i set to 1/2x = 24khz.
the reason is performance.
my patch is too intensive, that it will run full at 44,1khz.
with this setup it works.
I’m on linux ubuntu studio with pipewire emulation.
i tested it again with funs: Oct 4 and above does not work.
Oct 3 a bit.
Oct 0-2 works.
Unfortunately i can not use funs as vco.
but why does funs behave this way?
Sounds as if you have a very strange and unique run environment for VCV.
At 48k, Oct 4 works perfectly for me on Mac Arm. So I don’t think this is Funs behaving oddly in any way.
hello,
but if i reduce sample rate to 24kHz it is the same. so the divider 44,1 / 24 kHz seems not the problem. other vco works without any trouble.
but if it is by design, it is OK. i will then use another vco instead.
I think sometime maybe in the last few updates, the FM input stopped working. I use Funs a lot but rarely the FM, however I do remember it working at some point but now for me it does not.
Good to know!
But my actual problem is using the b parameter.
is it working for you?
Yes, all the other parameters are working for me. (WIndows 11, usually running at 48k sample rate)
i just tested funs at 48kHz alone. it works.
so there is a problem with the parameter b at lower sample rates then 44,1 kHz.
perhaps the developer could help out why.
Yes - I can confirm that the Funs b parameter becomes non-functional when VCV sample rate is 24 kHz or lower. I am running on Windows.
thank you.
we will see, what the developer says.
Thank you all for your feedback!
For me, 44.1k or 48k doesn’t make much difference. I don’t know why it does in your case, @karlderletzte .
@dustractor , yes is just noticed too that FM is broken. My bad. That’s a easy fix that will be done for the next update.
And I’ll loosen the restriction on the b parameter somewhat.
1 Like
the b parameter is not working at 24kHz and below. 44,1 kHz is OK.
as @DaveVenom also wrote.