Amos wrote:nofuturenocore wrote:Hello ,
Something that would be great is to have for each CC the name of the corresponding control, this would be very helpful for mouse automation.
I saw that there is actually some of the CC that have a name ( Example: Pitch bend ) and other that have a name but not the same as the Sub Phatty (Example: OSC 2 Freq named as Effect Control 2).
Have all of them as they are written on the Sub Phatty would be really helpful for easier and faster access.
hi, this is something else the Editor can help you to do. If in your DAW you automate the knobs of the editor plugin, it will send the appropriate CCs to the Sub Phatty, and at 14-bit resolution.
Also, the parameters of the plugin all have proper readable names when doing automation.
So, you can do this instead of automating the direct MIDI CCs.
Hello Amos,
Good idea
But I see that I have still this #### problem with ramp automation 96000 Bitrate doesnt solved the problem, but I'm now sure that the problem is coming from my soundcard because with my builtin realtek the SubP receive correctly ramp automation so I'm now speaking with Motu support...I think i'll blow this card on my wall.
Edit:
Now Plugin Window doesn't work anymore with the SubP. I have a crackling sound when I modulate a parameter from the Plug Window but it sounds good directly from the editor... is this normal with editor 0.9.3 ?
Re Edit: So this morning when I turn up the Sub Phatty I get a "Stuck Note" in Active Panel before I touch anything; In Ableton, with the Standalone Editor and without any connection between the computer and the Sub Phatty, I turn it off / on, same problem, I have make a firmware update, same problem....
When I go in preset mode and hit a key, the stuck note disappear, and when I go back in Active Panel it Stuck again before I hit any key....
Edit : Stuck Note Solved -> Bug on the Gate source, edit from the Editor solved the problem.
Edit:
Now Plugin Window doesn't work anymore with the SubP. I have a crackling sound when I modulate a parameter from the Plug Window but it sounds good directly from the editor... is this normal with editor 0.9.3 ?
-> I see that the Moog is receiving the midi correctly but it still make a crunchy sound, but what is weird is that the VST do not send midi to ableton but directly to the Sub Phatty, is this normal ?
Re edit: Okay Apparently the problem come from CPU... 75 % just with 1 max for live lfo on the filter cutoff very weird... Gonna go back to 32 bit it was working way better.