MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
It used to be that when you dragged a new dot of cc data it would do a slope to the new point.
Ever since updating to 11 I’m getting this instead.
I have been working around the problem by using the pencil tool but it’s clunky and more time intensive.
Any clues?
Haven’t found any relevant preferences to address this.
I see that issue here. It seems if I click-hold-drag to create a new node/dot and drag it all in a single click operation it mostly behaves this way.
However, if you first click and release (without dragging) to create a new node-dot, then click again to drag the dot, it seems to work normally. If you click and drag an existing dot, it will either work the 'broken' way or the expected way, depending on how it was created.
M1 MBP; OS 12, FF800, DP 11.3, Kontakt 7, Reaktor 6, PC3K7, K2661S, iPad6, Godin XTSA, Two Ibanez 5 string basses (1 fretted, 1 fretless), FM3, SY-1000, etc.
What's weird to me is that you clicked the the right of the existing dot, and then a new one appeared and the previous one to the left disappeared. When I put my arrow cursor over the automation line, it becomes the hand with the finger. It doesn't stay as an arrow like yours. Anyway... I was trying with audio volume automation on DP 11.31 and I can't make that happen on my system. Not sure why.
What Mac are you using and what version of OS? You might consider adding that to your signature in the User Control Panel (click on your username at the upper right) so others know what version of OS, type of processor, etc.
This might be limited to MIDI CC automation lanes. Also perhaps notice whether grid on/off state has something to do with whether it "grabbing" an existing handle/node vs creating a new one.
M1 MBP; OS 12, FF800, DP 11.3, Kontakt 7, Reaktor 6, PC3K7, K2661S, iPad6, Godin XTSA, Two Ibanez 5 string basses (1 fretted, 1 fretless), FM3, SY-1000, etc.
James Steele wrote: ↑Tue May 07, 2024 7:32 pm
What controller value is it? (Probably doesn't matter... just curious.). I'll see if that happens for me, but I don't think it will. That's very odd.
In this case it's volume but it is the same with all MIDI data, not a problem with audio automation.
Mac Pro (Late 2013)
MacOS 12.7.5
DP 11.31
Symphony I/o MkII
NI Komplete Kontrol s61
stubbsonic wrote: ↑Tue May 07, 2024 7:43 pm
IHowever, if you first click and release (without dragging) to create a new node-dot, then click again to drag the dot, it seems to work normally. If you click and drag an existing dot, it will either work the 'broken' way or the expected way, depending on how it was created.
The result is the same using either method over here.
Mac Pro (Late 2013)
MacOS 12.7.5
DP 11.31
Symphony I/o MkII
NI Komplete Kontrol s61
Garbage.mov
