Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Post Production > Post - Surround - Video

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 11-05-2019, 03:55 PM
Frank Kruse Frank Kruse is offline
Member
 
Join Date: Dec 2002
Location: old europe
Posts: 5,433
Default 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 2019.10 (OSX10.14.6), 8x8x8, MacPro 5,1 3.33Ghz 12-Core, BM DeckLink SDI, SYNC HD, all genlocked via AJA GEN10, 48GB RAM
Reply With Quote
  #2  
Old 11-05-2019, 04:49 PM
Reckless Erik Reckless Erik is offline
Member
 
Join Date: May 2001
Location: Reykjavik,Iceland
Posts: 669
Default 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.
__________________
nickcath@internet.is
Newcomer Audio Post
MacBookPro 2.3GHz i7 16GB RAM OSX 10.14.6, PT 2019.10 HDn, Avid Artist Control, Avid Artist Mix...,
MacPro 3.5GHz 6 core 64GB RAM OSX 10.14.6, PT 2019.10 HDn, Avid Artist Control, Avid Artist Mix, PT Dock...
Reply With Quote
  #3  
Old 11-05-2019, 09:28 PM
bewk's Avatar
bewk bewk is offline
Member
 
Join Date: May 2000
Location: HTX
Posts: 39
Default 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.
__________________
PT HD|Native 2019.6.0 on 10.12.6 (Angelbird SSD) // MacPro (4,1 to 5,1) 12 Core 3.46 GHz // 24GB // AJA Kona LHi // OWC FW800, USB 3.0, eSATA
-
PT HD 11.3.2 on 10.12.6 // MacBook Pro 17" 2.66 GHz i7 8GB RAM
-
PT HD 8 PCIx G5 (192 I/O)

Artist Series Mix & Avid Dock


www.quesound.com
Reply With Quote
  #4  
Old 11-06-2019, 12:14 AM
Frank Kruse Frank Kruse is offline
Member
 
Join Date: Dec 2002
Location: old europe
Posts: 5,433
Default 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 2019.10 (OSX10.14.6), 8x8x8, MacPro 5,1 3.33Ghz 12-Core, BM DeckLink SDI, SYNC HD, all genlocked via AJA GEN10, 48GB RAM
Reply With Quote
  #5  
Old 11-06-2019, 12:29 AM
thierryd thierryd is offline
Member
 
Join Date: Nov 2000
Location: Brussels
Posts: 499
Default 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/
Reply With Quote
  #6  
Old 11-06-2019, 02:36 AM
Frank Kruse Frank Kruse is offline
Member
 
Join Date: Dec 2002
Location: old europe
Posts: 5,433
Default Re: Difference between ctrl-X and cut all automation?

Yes ctrl-x is an odd one.
__________________
PTHDn 2019.10 (OSX10.14.6), 8x8x8, MacPro 5,1 3.33Ghz 12-Core, BM DeckLink SDI, SYNC HD, all genlocked via AJA GEN10, 48GB RAM
Reply With Quote
  #7  
Old 11-06-2019, 04:27 AM
Sonopolis Sonopolis is offline
Member
 
Join Date: Sep 2011
Location: Berlin
Posts: 234
Default Re: Difference between ctrl-X and cut all automation?

Quote:
Originally Posted by Reckless Erik View Post
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.
BTW, so does CTL+Shift+X for Clip Gain. I use it to ramp Clip Gain changes inside regions all the time
Reply With Quote
  #8  
Old 11-06-2019, 04:31 AM
Frank Kruse Frank Kruse is offline
Member
 
Join Date: Dec 2002
Location: old europe
Posts: 5,433
Default Re: Difference between ctrl-X and cut all automation?

Quote:
Originally Posted by Sonopolis View Post
BTW, so does CTL+Shift+X for Clip Gain. I use it to ramp Clip Gain changes inside regions all the time
Yeah but that won't cut any automation break points, just clip-gain.
__________________
PTHDn 2019.10 (OSX10.14.6), 8x8x8, MacPro 5,1 3.33Ghz 12-Core, BM DeckLink SDI, SYNC HD, all genlocked via AJA GEN10, 48GB RAM
Reply With Quote
  #9  
Old 11-06-2019, 07:58 AM
bewk's Avatar
bewk bewk is offline
Member
 
Join Date: May 2000
Location: HTX
Posts: 39
Default 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.
__________________
PT HD|Native 2019.6.0 on 10.12.6 (Angelbird SSD) // MacPro (4,1 to 5,1) 12 Core 3.46 GHz // 24GB // AJA Kona LHi // OWC FW800, USB 3.0, eSATA
-
PT HD 11.3.2 on 10.12.6 // MacBook Pro 17" 2.66 GHz i7 8GB RAM
-
PT HD 8 PCIx G5 (192 I/O)

Artist Series Mix & Avid Dock


www.quesound.com
Reply With Quote
  #10  
Old 11-06-2019, 08:56 AM
Frank Kruse Frank Kruse is offline
Member
 
Join Date: Dec 2002
Location: old europe
Posts: 5,433
Default Re: Difference between ctrl-X and cut all automation?

Quote:
Originally Posted by bewk View Post
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.
Not quite. At least not here. ctrl-X will chop away actual audio when you are in waveform view and in that case won't touch any underlying lanes.
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 2019.10 (OSX10.14.6), 8x8x8, MacPro 5,1 3.33Ghz 12-Core, BM DeckLink SDI, SYNC HD, all genlocked via AJA GEN10, 48GB RAM
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump

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 04:55 PM
What's the difference between clip gain and volume automation on audio? rockguitarist1255 Pro Tools 10 7 12-27-2012 08:20 PM
fine tune automation with ctrl stevedresser83 Windows 7 05-10-2011 02: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 11:10 AM
Trim Automation with 6.9 and CTRL 24 tonicjeff ICON & C|24 2 10-25-2005 01:50 PM


All times are GMT -7. The time now is 04:34 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com