|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
automation bug in bypass lane
I have been having trouble with bypass automation. Existing bypass breakpoints are often not overwritten, which makes plugins bypass/unbypass at unexpected times. It seems that automation breakpoints are no longer written (when capturing plugins and editing) if the value to be written is the same as the existing value already in the automation. It is new behavior I believe. This is probably a bug within that new code.
These screengrabs illustrate the problem. http://www.pharoahaudio.com/bypassbug.html |
#2
|
||||
|
||||
Re: automation bug in bypass lane
I found a similar issue writing volume automation after preview.
Write to all wouldn't overwrite the automation within regions but it would outside the regions. This happened on newly created tracks. Which makes me think it is related to a problem we are having with automation not playing back properly on some tracks after track counts have changed in the session. Restarting session helps. http://duc.avid.com/showthread.php?t=313329 EDIT: This happens only if I have the "Write to next breakpoint on stop" enabled. |
#3
|
|||
|
|||
Re: automation bug in bypass lane
I am only seeing this happen to bypass automation.
|
#4
|
|||
|
|||
Re: automation bug in bypass lane
I spoke too soon. Yesterday I found some EQ3 single band plugins that were not changing filter type properly. They were peaking instead of notching across 3 dialog tracks in a section I had spend a lot of time in. Closer examination revealed the same problems on filter type parameter lanes as I have documented on the bypass lane. Other eq parameters were being set to correct values but not filter type. Once I manually fixed the filter type lanes I got my dialog premix back.
The problem is created while writing settings using command-option-/. It seems to happen while overwriting previous settings. It is about as close to a showstopper bug as I will get before going back to an earlier version. |
#5
|
|||
|
|||
Re: automation bug in bypass lane
Found more today. I've found a workaround is to key in command-option-/ TWICE in a row, that seems to overwrite correctly...at least so far. What a friggin pain.
|
#6
|
||||
|
||||
Re: automation bug in bypass lane
Thanks for the info and screenshots, Eng is looking into this.
|
#7
|
|||
|
|||
Re: automation bug in bypass lane
Thank you for letting us know!
|
#8
|
||||
|
||||
Re: automation bug in bypass lane
I also found making a copy of a region by "option" control+click or dragging sometimes does not carry the automation information, you have to use copy+paste (yes double checked, and automation follows edit was enabled).
|
#9
|
|||
|
|||
Re: automation bug in bypass lane
I suppose we are all talking about PT10.0 here. I've seen the bypass bug in my mixes as well (just didn't have time to investigate and manually edited the breakpoints).
I almost never use command-alt-/ btw, but use (punch)preview instead. I've also had quite a few issues with automation not playing back, which is a PT10 issue in another thread, but since Avid replied here I jump on it Often I get the feeling that these issues might have to do with de-activating and activating tracks in a session. I also mixed a project in 5.1 recently, where I used native processing on the source tracks (I tend to stick with TDM for everything). This also gave me a less confident feeling during the mix (more ticks and clicks upon stop-starts while monitoring through input-rec stems, than when using TDM only processing). I wonder if the automation problems surface more easily on PT 10 Sessions with native processing enabled or changing a bunch of tracks from TDM to Native, as I did with this mix. I imported tracks from HD2 and HD Native PT rigs, but always made sure the source and destination tracks for imports had the same processing (being TDM or Native). This to avoid the famous other bug from Frank, where automation suddenly can't be copied anymore between tracks. Generally I feel that PT10 has great benefits for editing especially large sessions (Memory management is much better, Disk caching, 24h timeline), but on the mix side PT10 scares me sometimes. Also the D-Control implementation was best at PT8, became slower with PT9 and lost features with PT10 (plug-in learn stuff and CF plugin things)... Sorry to hi-jack part of the thread, but I hope some insights might help troubleshooting. Greetings, Thierry
__________________
http://www.a-sound.com/ |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Volume Trim lane vs Automation | Cliffy_Boy | Pro Tools HDX & HD Native Systems (Mac) | 12 | 03-06-2013 03:19 PM |
No Send Pan automation lane on 9.0.3? | Craig F | macOS | 1 | 04-21-2012 12:12 PM |
Automation lane size not remembered | Gothboy | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 07-07-2010 09:26 AM |
Change all track automation lane types? | postprosound | Post - Surround - Video | 3 | 05-21-2010 08:56 AM |
Midi Controller Lane Automation Error (PT8) | paulrgmusic | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 0 | 01-02-2009 10:11 AM |