|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Automation Being Written on Untouched Track
I'm using the Command|8 with PT v6.4.1cs3.
Problem: When writing volume automation with channel 1, some automation is being written to channel 2. Reproducible: Yes. Steps to Reproduce: 1. Enable auto write/touch/latch on channel 1. 2. Press play. 3. Write volume automation using channel 1. 4. Press stop. What should happen: Automation should be written on channel 1. What does happen: Automation is written on channel 1 and some automation is written to channel 2. Other info: The automation being written to channel 2 does not appear to be correlated in any fashion. Writing automation on channel 2 does not result in automation being written to any other channel. Has anyone ever observed this behavior? Any suggestions are appreciated.
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
#2
|
|||
|
|||
Re: Automation Being Written on Untouched Track
I thought I was the only one.
Here's what I think is happening; there's a grounding problem somewhere or something. If you have your finger touching the metal plate where the numbers are (light gray area) it seems to conduct a bit of finger heat to the adjacent fader #2 at certain times. If you have your index finger on the first fader, then touch the screw below the 2nd fader with another finger on that hand, it activates that fader EVERY TIME and you can see it on the scribble strip. Only with the 1st fader, do I have to conciously raise my wrist off the Command|8. No other faders seem to be affected. |
#3
|
|||
|
|||
Re: Automation Being Written on Untouched Track
The angle at which I was testing this could not have implicated my wrist touching the Command|8 as the source of the problem. Nevertheless, Mike Z @ Digi set me up with an RMA to get the "jittery fader" mod in hopes that it would fix my problem (our Command|8s were from the pre "jittery fader" mod introduction).
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
#4
|
||||
|
||||
Re: Automation Being Written on Untouched Track
This started happening to me today. I'm gonna investigate further tomorrow. It seems it's only if the track in question is controlled from the first fader of the C8, then the second track gets written to as well. If you move it to another controller fader it won't affect the next track.
|
#5
|
|||
|
|||
Re: Automation Being Written on Untouched Track
Precisely, but who wants to create a useless track 2, 10, 18, 26, 34, 42, 50, 58, etc.? The place where our Command|8 is at won't have it ready at the earliest until next Wednesday I reckon. I'll let you know if it works when I get it back.
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
#6
|
||||
|
||||
Re: Automation Being Written on Untouched Track
I can only get this to happen with a certain number of tracks and under certain conditions. For instance 8 stereo tracks will exhibit this, 8 mono channels won't.
Here is a surefire reproducible case for me. 8 stereo tracks, all in touch mode, then write automation to all tracks Then write automation to first track and the second will be altered. At any rate even with just 2 mono tracks writing automation to the first will create breakpoints in the second BTW that's C8 with 6.9.2cs1 |
#7
|
|||
|
|||
Re: Automation Being Written on Untouched Track
So either this is a bug in the software that has existed since day 1, or a rev G Command|8 fixes the problem. We shall find out in 1 week!
My $ is on the rev G. I haven't had the engineer that caught this report it since, though the Command|8 he's using isn't rev G either...hmmm...
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
#8
|
|||
|
|||
Re: Automation Being Written on Untouched Track
Thanks to you all for your posts - very informative.
I too am having the exact problem described: touching fader 1 causes fader 2 to "think" it's being touched, although intermittently; sure looks like a grounding issue to me - surface area of my hand touching the metal part of the chassis seems to have some effect - i.e. touching ONLY fader 1, fader 2 seems stable, resting my hand on the Command|8 and touching fader 1, fader 2 has data written. I'll be contacting Digi tomorrow for an RMA. Another very helpful session at the User's Conference. Tonight I sleep not feeling quite so alone! Thanks again, Kent |
#9
|
|||
|
|||
Re: Automation Being Written on Untouched Track
Rev G appears to have done the trick. Thank you Digidesign!
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
#10
|
|||
|
|||
Re: Automation Being Written on Untouched Track
what do yu mean by rev G ?
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Muted track unmutes when I hit play with no automation written? | jjboogie | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 8 | 09-16-2023 08:00 PM |
Adjusting volume after automation is written | rock15478 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 3 | 09-02-2015 06:42 AM |
extra automation written | viaspiaggia | Post - Surround - Video | 4 | 06-14-2013 12:28 PM |
Automation won´t work when written with controller | Audiophil85 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 0 | 01-16-2008 09:14 AM |
"No automation could be written.... | dkroger | ICON & C|24 | 4 | 12-19-2005 08:43 AM |