Hi, I took a patch from the book “generating sound and organizing time” and adapt it to flash it in patch:init . It works fine, and I am improving it step by step, to suit my system.
The only issue that I found is that I can listen a glide in the pitch between notes (V/oct controlled with cv8 input) while playing it with a sequencer or other module that has gate and c/volt outputs.
Does anyone have some time to check it and give me some advice? Thank you very much!
Hi, I posted about the exact same problem yesterday in the Troubleshooting section, I get the glide on all CV ins on my patch.init() module… can’t figure it out yet
hi @Takumi_Ogata , did you manage to replicate the issue?
Hello @Takumi_Ogata , any insight regarding this issue ?
I’m so sorry that it took a while to get back to you two on this.
The Patch SM has a number of controls that it defines itself in the C++, including the CV inputs.
These inputs are using the default slew, which is two milliseconds. This is equivalent to two audio processing blocks with a block size of 48.
Right now, there’s not a lot someone could do to change this except modifying their local copy of libDaisy. So, the following is how you can modify that value:
- Go to
Max 8
→Packages
→oopsy
→source
→libdaisy
→src
→hid
- Open up the file
ctrl.h
- Adjust the slew value on line 37
- Hit save
- Open up a terminal app of your choice as you will need to recompile. For Mac, you can use Terminal.
- Go inside of the libdaisy folder by
cd Documents/Max\ 8/Packages/oopsy/source/libdaisy
(assuming that yourMax 8
folder is inDocuments
) - Then type
make
and hit enter to recompile
I currently don’t have access to the Patch.Init() so please let me know if there was any issue.
Thanks so much @Takumi_Ogata !! I’ll let you know how it works when I get some time to try this.
Best
Thanks Takumi for taking time to check on this.
I followed your precise indications, but in the end, when I hit make in the Mac terminal, this is what I got:
make: *** No rule to make target c\:\users\shensley\desktop\sandbox\daisy\daisytoolchain\windows\lib\gcc\arm-none-eabi\10.2.1\include\stdint.h', needed by
build/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal.o’. Stop.
I am on the right folder, btw. Do you know what is wrong there?
Thanks a lot!
I’m sorry to hear that you ran into an issue.
Which version of Oopsy are you using?
In order to minimize the variables between our setup, could you try again with the “pre-release” version of Oopsy? I recommend having a backup of your current oopsy folder somewhere else safe.
Let me know how that goes, thanks!!
Hello, on my side I was able to change the slew value to 0.000f and recompile then flash my patch in the patch.init(), however the slew is still present when using the module. Is there anything that should be changed in the ctrl.cpp file as well ?
Hi guys, how are you? Just to say that I have the same problem in my MAX patches. The same thing happened to me in plugadata but I managed to solve it since here it is possible to specify the number of milliseconds in the smooth parameter but in max there are no changes even removing the objects recommended by daisy.suggestions for the input parameters. It’s a shame because I haven’t been able to use patches like that.
Well, I am delighted to say that this worked perfectly @Takumi_Ogata. I don’t have the glide sound anymore.
I don’t know why is not working for you @raintear. Did you make sure to have the version that Takumi just sheared?
I think I celebrate too soon. Now, my module is impossible to be on tune. It takes 2 octaves on the keyboard to do 1 octave in sound. Did something else was changed?
Glad to hear that you were able to remove the glide!
It shouldn’t have changed anything else. Changing that value may have effect on tuning.
Will the tuning be back to what you expect when you put the value to what it was before?
And what value did you change to when the tuning issue started happening?
oh, the pitch problem was solved quite easily, actually. The new soft let the patch Init worked between -5v and 5v, right. So when I do the patch in Max, the pitch input should consider between -5 and 5 levels. (before it was between 0 to 5)
Ah I see!
Glad to hear that it’s all working now!!