If I copy/paste/merge automation from one track to another, the resulting automation points are usually placed incorrectly into the timeline by DP.
Often it's offset by what DP is describing as one sample. When this happens, at least visually, the points that are offset appear to be between sample locations. I'm not even sure how that works lol but that's what it shows. I thought "the sample" was DP's sorta Plank length but hey sometimes DP makes no f'ing sense at all so yeah.
As an example, let's say I'm copying volume auto from guitar 1 to guitar 2. I view the volume lanes on both int he sequence editor and copy gtr 1's volume auto. I click on the track name for gtr 2, the same time range is now selected on gtr2, and I hit merge ("merge" meaning the command similar to paste, not "merge soundbites"). The result is off, sometimes by one sample but other times it's off by much more. This happens whether or not I've included a sort of dummy point at time 0. Other times it works fine, which is almost worse haha
Sometimes it only happens in some sections of the automation, while other parts pasted or merged in the same action are placed fine. Going through busy automations data, one point at a time, can be infuriating to track down and correct.
Using the view filter and doing these operations from the Tracks window is occasionally ok as a workaround, except that it's not as reliable. I'll skip the description of why, as it would be length and anyone answering this already is aware of these limitations re the tracks window and automation data.
This was not only driving me nuts over the last few days but was slowing down my work big time. DP is such a damn headache sometimes....
Is this happening with anyone else? Anyone know a cure?
Edit for my info:
DP 11.31
macOS 12.7.6
Mac Studio M1 Max
24GB RAM
Merging automation inaccuracies
Moderator: James Steele
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.
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.
-
- Posts: 105
- Joined: Sun Jan 29, 2023 5:09 pm
- Primary DAW OS: MacOS
Re: Merging automation inaccuracies
I don’t know the cure. Not sure I even understand the ailment. But on what you call the “plank”, the manual has a mention of DP’s internal timing resolution, and IIRC it’s a lot finer than one sample. Could your problem be some sort of snap setting?
2018 Mini i7 32G macOS 12.7.6, DP 11.33, Mixbus 10, Logic 10.7.9, Scarlett 18i8, MB Air M2, macOS 14.7.6, DP 11.33, Logic 11
-
- Posts: 105
- Joined: Sun Jan 29, 2023 5:09 pm
- Primary DAW OS: MacOS
Re: Merging automation inaccuracies
Sorry I misspelled Planck, it's a term from physics
I realize describing it made for a complicated story. Basically the ailment is that when copying automation data between tracks, DP doesn't apply the copied data to the correct place in the timeline.
Thank you for the suggestion about snapping, I hadn't considered its I just tested it. The issue is still there with snapping turned on or off.
I realize describing it made for a complicated story. Basically the ailment is that when copying automation data between tracks, DP doesn't apply the copied data to the correct place in the timeline.
Thank you for the suggestion about snapping, I hadn't considered its I just tested it. The issue is still there with snapping turned on or off.
Re: Merging automation inaccuracies
I can reproduce this if I"m not careful with the mouse pointer. I rarely copy and past automation so haven't noticed this before. I tried it with MIDI and that does paste exactly where it should be. Audio works OK too, at least here.
The manual tells us that data will be pasted at the start of the selected range if there is one. So I tried making sure that when I selected the automation, the selection range for that data remained in place when I selected the target track. Doing this, the automation was pasted at exactly the same place in the target as it was in the source. This works consistently for me.
Is it possible that in your copy and past process you are not leaving the original selection in place, perhaps by clicking in the target track, or even the source track somewhere, before pasting.?
The manual tells us that data will be pasted at the start of the selected range if there is one. So I tried making sure that when I selected the automation, the selection range for that data remained in place when I selected the target track. Doing this, the automation was pasted at exactly the same place in the target as it was in the source. This works consistently for me.
Is it possible that in your copy and past process you are not leaving the original selection in place, perhaps by clicking in the target track, or even the source track somewhere, before pasting.?
2018 Mini i7 32G macOS 12.7.6, DP 11.33, Mixbus 10, Logic 10.7.9, Scarlett 18i8, MB Air M2, macOS 14.7.6, DP 11.33, Logic 11