Volume Automation is now PER TAKE?

Discussion of Digital Performer use, optimization, tips and techniques on MacOS.

Moderator: James Steele

Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
Post Reply
Irimi Nage
Posts: 45
Joined: Sun Jan 29, 2023 5:09 pm
Primary DAW OS: MacOS

Volume Automation is now PER TAKE?

Post by Irimi Nage »

I recently updated DP to the latest. Unless it's just acting buggy it seems that yes volume automation is now written into each take individually. It used to be one volume lane per track, regardless of which take you are using. Now each take can have its own automation.

I always thought it should be per take so this is good news. I didn't see it in the release notes so I though it'd be good to share.
Tidwells@aol.com
Posts: 251
Joined: Tue Jun 12, 2012 10:04 pm
Primary DAW OS: Unspecified

Re: Volume Automation is now PER TAKE?

Post by Tidwells@aol.com »

I can confirm that this is correct in DP 9.12, at least for audio tracks. I don't know about MIDI tracks.

Doug
User avatar
HCMarkus
Posts: 9759
Joined: Tue Jan 10, 2006 9:01 am
Primary DAW OS: MacOS
Location: Rancho Bohemia, California
Contact:

Re: Volume Automation is now PER TAKE?

Post by HCMarkus »

Pretty sure MIDI tracks don't have this feature; volume data is still Per Track.

A irritating aspect of this... turning off Track Automation on MIDI Track does not disable previously written Volume Automation on the track. So, we can't simply turn off the volume automation while re-recording a segment of MIDI data, for instance, which is especially bothersome when the recorded volume data is something at or close to -infinity. We've got to either mute the original track and use another track or erase or re-write the volume automation first.
HC Markus
M1 Mac Studio Ultra • 64GB RAM • 828es • macOS 13.6.4 • DP 11.31
dix
Posts: 2995
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: San Francisco
Contact:

Re: Volume Automation is now PER TAKE?

Post by dix »

HCMarkus wrote: Sun Feb 25, 2024 7:05 am Pretty sure MIDI tracks don't have this feature; volume data is still Per Track.

A irritating aspect of this... turning off Track Automation on MIDI Track does not disable previously written Volume Automation on the track. So, we can't simply turn off the volume automation while re-recording a segment of MIDI data, for instance, which is especially bothersome when the recorded volume data is something at or close to -infinity. We've got to either mute the original track and use another track or erase or re-write the volume automation first.
Huh? Unless I'm misunderstanding something, this is not correct. MIDI automation is per take in DP, and MIDI volume (CC7) automation is disabled when Automation Play is turned off. Other CCs, such as Expression (CC11), Modwheel etc. don't adhere to the Automation Play state, but volume does. ...maybe you're doing volume automation with CC11, or maybe there's a pref?
14-inch MBP M1 Max (2021), 13.6.x, 64GB RAM, UAD Quad Tb Satellite, 4 displays ::: 2009 4,1 > 5,1 MacPro 12-core 3.33 ghz , 10.14.x, 96GB RAM, GeForce GTX 770 , NewerTech eSATA/USB3 PCIe Host Adapter, UAD-2 Quad, ::: 15-inch MBP (2015) 10.14.x, 16GB RAM ::: Lynx Aurora (n) USB ::: DP (latest version), Vienna Ensemble Pro danwool.com
User avatar
HCMarkus
Posts: 9759
Joined: Tue Jan 10, 2006 9:01 am
Primary DAW OS: MacOS
Location: Rancho Bohemia, California
Contact:

Re: Volume Automation is now PER TAKE?

Post by HCMarkus »

dix wrote: Sun Feb 25, 2024 9:12 pm
HCMarkus wrote: Sun Feb 25, 2024 7:05 am Pretty sure MIDI tracks don't have this feature; volume data is still Per Track.

A irritating aspect of this... turning off Track Automation on MIDI Track does not disable previously written Volume Automation on the track. So, we can't simply turn off the volume automation while re-recording a segment of MIDI data, for instance, which is especially bothersome when the recorded volume data is something at or close to -infinity. We've got to either mute the original track and use another track or erase or re-write the volume automation first.
Huh? Unless I'm misunderstanding something, this is not correct. MIDI automation is per take in DP, and MIDI volume (CC7) automation is disabled when Automation Play is turned off. Other CCs, such as Expression (CC11), Modwheel etc. don't adhere to the Automation Play state, but volume does. ...maybe you're doing volume automation with CC11, or maybe there's a pref?
I'll look into it. Thanks!
Post Reply