Patch.init() CV inputs automatically slewed?

Troubleshooting and Support
1

Hello, I’m trying to figure out what’s going on with CVs inputs on the Patch.Init() module. Using it as a sound source, when I change the pitch using a CV input (like CV_5 or CV_6) the change in pitch comes out with a slight slew so that when the notes are played fast the phrase is “blured”. The incoming pitch signal comes from another module without any slew.
I made the patch in gen~ with oopsy, and didn’t put any smoothing function into it so there is no slew on the max version of the patch.
I probably missed something, but can it be an issue coming from the module itself or related to oopsy when flashing the patch into the module ?
Thanks

1 Like
2

Same issue here, anyone else?
Can this be prevented?

3

I can look into this and reply over here: Unwanted pitch glide in this max patch for daisy, suggestions?

Thank you for the wait!

1 Like
4

Hi @Takumi_Ogata , have you got a chance to look at this problem already ? I really wish I’d be able to design a custom synth in patch.init() but the slew makes it not realistically playable. Thanks

5

We unfortunately haven’t had the chance yet. I’m sorry to keep you waiting.
I will bring this up to the team again.

1 Like
6

I just took a minute to test this using Patch.Init and C++.
I’m running a random stepped voltage into CV_5, and I don’t hear any slewing.

On further thought, because the CV inputs are sampled periodically, weirdness is inevitable as the frequency of input changes gets higher.

So, just how fast are the inputs changing?

7

Thank you for the wait, I posted how you can adjust the value over on this thread: Unwanted pitch glide in this max patch for daisy, suggestions?