Range automation - is this a bug or me?

[FrankM]

Hard to believe this is a bug but it sure looks like it. Does anyone here record automation using the Range Latch or Range Touch modes?

The manual says this: "when recording automation using the Range modes, moving controls will change automation data only within a defined time range. The settings for the data on either side of the affected time range will be preserved."

I select a time range, start playing, then when the wiper is inside the range I move the fader to record it. As soon as I stop playback the wiper locates to the very beginning (1|1|000). All automation data before the range is gone! A single point is written at 1|1|000 which is the last value of the slider I was recording automation for.

This also happens in Range Touch mode. Automation after the range end is not affected.

I'm happy to be schooled and told this is some mistake on my part and not a bug, but it sure seems like a bug.

Below are two screen shots, a before & after I record automation inside the range:

range edit bug before.png (348.53 KiB) Viewed 2301 times

AFTER I do my automation move:

range edit bug after.png (357.43 KiB) Viewed 2301 times

I can't attach an mp4 here, so here's a link to a very small (360K) 20-second video that shows exactly what happens:

https://www.dropbox.com/scl/fi/zyo52tyr ... 3qt3v&dl=0

I have a two-hour show with multiple songs and need to edit automation over ranges as each song is different. This is quite the impediment to me getting this done. This is me, right? I can't believe this is a bug nobody has noticed or that MOTU hasn't fixed by now. Maybe a new bug? I'm on DP 11.33 on an M2 MacBook Air with Ventura 13.6.9. Thanks to anybody that can enlighten me!

[EDIT = to answer the inevitable Q, I do have a ticket open with MOTU, but since this is the first time I've used this automation mode, I thought it would be at least as valuable to know if any of the many DP users here might have encountered this issue. I did do a quick search and found a few messages describing similar issues - those posts are 15 years old! No way this could be a bug MOTU hasn't addressed in that long.... right?!]

[FrankM]

The plot thickens - I created a new empty project, put an audio file into a track and messed with automating the volume fader. Range touch and latch work as expected! I'm at a loss.

[HCMarkus]

Shite happens. Might you try Loading the project with issues into a new Project?

[FrankM]

Thanks for that suggestion, I tried it and it didn't work but then I found the solution... and it has me scratching my head but I'm not going to complain; I can go on mixing now.

Turns out the issue I was seeing was only on that one track. All other tracks behaved normally wrt Range Touch and Range Latch automation. I had the idea of checking the Automation Setup dialog for that track and saw something strange - all my other tracks were set to Enable "ALL" automation, except the misbehaving track. Instead, it showed this:

auto setup 1.jpg (31.17 KiB) Viewed 2194 times

What's strange is that there's two entries for volume. I looked in the manual to see what the difference was between "Audio Volume: Internal" and plain "Volume" but found no references to this. AAMOF if you start with nothing, select "Only" then go to the little drop-down on the right and select "Volume", that's how it appears in the box - not "Audio Volume: Internal."

auto setup 2.jpg (40.04 KiB) Viewed 2194 times

Anyway - I deleted the two entries I saw, selected "ALL" for "Enable Automation Types:" and now Range Touch and Range Latch work as they should.

I'm calling this a software "glitch." I don't remember messing with these parameters at all. Back to work!

[HCMarkus]

Thanks for the update!