|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Difference between ctrl-X and cut all automation?
Hi,
does anyone know the official name of the ctrl-X shortcut that I believe is undocumented and essentially cuts all automation through all lanes but only when at least one lane of automation is shown. Versus the cut all automation command that always does just that? I was wondering what the intended use of ctrl-X is? Thanks! Frank.
__________________
PTHDn 2024.3 (OSX13.6.5), 8x8x8, MacPro 14,8, AJA LHi, SYNC HD, all genlocked via AJA GEN10, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#2
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
Control X ramps between the break points whilst cut has no ramping and the auto value is written using the value at the selection start point. Control X is nice when you want to "crossfade" automation parameters.
__________________
[email protected] Newcomer Audio Post MacBookPro 2.3GHz i7 16GB RAM OSX 10.15.7, PT Ultimate 2023.12 HDn, MTRX Studio, 2x Avid S1, PT Dock... Mac M1 Studio Ultra 64GB RAM OSX 13.6, PT Ultimate 2023.12 HDn, MTRX Studio, 2x Avid S1, PT Dock... |
#3
|
||||
|
||||
Re: Difference between ctrl-X and cut all automation?
I use it often when EQ-ing a cut of music under DX for talking head interview stuff. Mostly to brute force some of the instrumentation out that multi-band dynamics isn't chewing on with enough teeth. As mentioned above, I use this to ramp smoothly out of the EQ for that section back to "flat" over time so that the change in EQ isn't obvious. I use it in other ways too but this is a constant in my workflow. Kind of like "AutoMatch" but with a variable length.
__________________
• MacPro (4,1 to 5,1) 12 Core 3.46 GHz // 96GB // AJA Kona LHi // OWC Mercury Elite Pro Quad, USB 3.0, eSATA • PT HD|Native 2024.3 on macOS 12.7.4 (OpenCore Patcher 1.4.3 on Crucial SSD) • Avid Dock, iPad 7th gen & EuCon 2023.11 • DADman/Eucon monitoring • BSS (DAN + 100), QSC DCA 1644, JBL 7 Series • MTRX Studio // 7.1.4 www.quesound.com |
#4
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
Thanks! But isn't cut all auto exactly the same? Only that you don't have to show a lane first? I have used cut all auto to create ramps across all visible and invisible lanes for all these years before someone told me about ctrl-X yesterday.
Frank.
__________________
PTHDn 2024.3 (OSX13.6.5), 8x8x8, MacPro 14,8, AJA LHi, SYNC HD, all genlocked via AJA GEN10, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#5
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
Checking in here remains as useful as ever I never heard of ctrl-X. Thanks for mentioning!
Greetings, Thierry
__________________
http://www.a-sound.com/ |
#6
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
Yes ctrl-x is an odd one.
__________________
PTHDn 2024.3 (OSX13.6.5), 8x8x8, MacPro 14,8, AJA LHi, SYNC HD, all genlocked via AJA GEN10, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#7
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
BTW, so does CTL+Shift+X for Clip Gain. I use it to ramp Clip Gain changes inside regions all the time
|
#8
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
Yeah but that won't cut any automation break points, just clip-gain.
__________________
PTHDn 2024.3 (OSX13.6.5), 8x8x8, MacPro 14,8, AJA LHi, SYNC HD, all genlocked via AJA GEN10, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#9
|
||||
|
||||
Re: Difference between ctrl-X and cut all automation?
I think they're the exact same thing, but as you mentioned, it just isn't documented. Ctrl-X still cuts all lanes of automation even if the track is in waveform view.
__________________
• MacPro (4,1 to 5,1) 12 Core 3.46 GHz // 96GB // AJA Kona LHi // OWC Mercury Elite Pro Quad, USB 3.0, eSATA • PT HD|Native 2024.3 on macOS 12.7.4 (OpenCore Patcher 1.4.3 on Crucial SSD) • Avid Dock, iPad 7th gen & EuCon 2023.11 • DADman/Eucon monitoring • BSS (DAN + 100), QSC DCA 1644, JBL 7 Series • MTRX Studio // 7.1.4 www.quesound.com |
#10
|
|||
|
|||
Re: Difference between ctrl-X and cut all automation?
Quote:
If you want it to cut through all lanes and not chop audio you have to have one auto-lane visible, which one doesn't matter. Only then it won't touch your clip and cut through all lanes. opt-shift-x will always cut all automation regardless of what you're looking at and won't cut clips. ctrl-x almost feels like something they started programming and then stopped at some point and never finished it (?). It's a pretty odd one. One keypress less though ;-)
__________________
PTHDn 2024.3 (OSX13.6.5), 8x8x8, MacPro 14,8, AJA LHi, SYNC HD, all genlocked via AJA GEN10, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
difference between MIDI automation and Audio automation on Instrument Track? | mariam | Getting Started | 5 | 04-28-2016 03:55 PM |
What's the difference between clip gain and volume automation on audio? | rockguitarist1255 | Pro Tools 10 | 7 | 12-27-2012 07:20 PM |
fine tune automation with ctrl | stevedresser83 | Windows | 7 | 05-10-2011 01:47 PM |
ctrl+tab or ctrl+alt+tab not working | Sebastien Richard | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 09-09-2006 10:10 AM |
Trim Automation with 6.9 and CTRL 24 | tonicjeff | ICON & C|24 | 2 | 10-25-2005 12:50 PM |