Page 1 of 1
Audio track goes grey while playing and no audio....?
Posted: Thu Aug 14, 2008 7:03 pm
by Hungry_Man
I have a problem thats been plaguing me since i started using ableton
occasionally i'm doing some editng, often moving files around the timeline
then when i hit play to check what i've done, the track goes light grey, and no audio plays back from that track (other tracks play fine). when i solo the track I still dont hear anything
what is causing this? why does it happen and how do i stop it happening?
the only remedy i've found is to copy all audio onto a fresh track, move all plugins, and delete the old track, which is a pain as i'm now working on 60 minute multi track timeline for a gig
undo doesn't help
thanks
H
Posted: Sun Aug 17, 2008 10:12 pm
by Hungry_Man
noone else has experienced this problem ??

Posted: Sun Aug 17, 2008 10:35 pm
by Pitch Black
What that means is something in the Session view (on the same track) has taken over from the Arrangement. i.e. you have triggered a clip (or empty slot) in Session or done some over-riding of automation in Session.
The remedy is to hit the "Back To Arrangement" button (between Overdub and Global Quantize in the transport controls). It turns red when what's in the Arrange View has been deviated from. See how it symbolises "back to the horizontal tracks".

Posted: Wed Aug 20, 2008 6:07 am
by rob lee
Hungry_Man wrote:noone else has experienced this problem ??

Yes this happens to me all the time and it's annoying..im still a new user to live so im still learning..

Posted: Wed Aug 20, 2008 9:50 pm
by benbrown
i have this problem now.. trying to render a track but the back to arrangement button pops up and disables all my automation.
would like to know how to disable this. thanks.
Posted: Wed Aug 27, 2008 3:10 pm
by Hidden Driveways
It's important to keep in mind that Live will only play one clip at a time per track. That's why the Back To Arrangement button exists.
Posted: Thu Aug 28, 2008 2:45 pm
by Atomikat
but it's been a problem in some versions of live...yesterday I recorded a mix (session view in 7.0.9), then I went to arrangement to replay it...but always one of the two or three tracks I mixed were greyed and muted, the "back to arrangement" didn't work (stayed lighted)...it was impossible to hear how the mix really was...then...I switched to 7.0.10, opened the same set, went to arrangement...press play...and voilá, everything worked fine as it was recorded.
That's why I still have the last 4 updates of Live (if one fails...the other rocks)
Posted: Thu Aug 28, 2008 3:00 pm
by jok
Hi,
if the Back To Arrangement Button is lighting up "out of the blue" (eg. without any active triggering/parameter change in Session view) , in many cases the reason for this is that a connected (mapped) controller is sending out cc messages silently.
So the first step to troubleshooting should be to disconnect your Midi controllers and/or delete the mappings in the mapping browser and check, if the problem persists thereafter.
Best,
Jörg
Posted: Thu Sep 04, 2008 8:35 pm
by benbrown
jok wrote:Hi,
if the Back To Arrangement Button is lighting up "out of the blue" (eg. without any active triggering/parameter change in Session view) , in many cases the reason for this is that a connected (mapped) controller is sending out cc messages silently.
So the first step to troubleshooting should be to disconnect your Midi controllers and/or delete the mappings in the mapping browser and check, if the problem persists thereafter.
Best,
Jörg
Jörg, I don't even have any MIDI controllers set up. Just in case, I went in and checked MIDI setting..made sure everything is off. No MIDI mappings exist either. Really odd.
When the track starts, its fine, but when it reaches a point in the track where an Automated MIDI clip starts (in this case running reFx Nexus in the channel) the Back to arrange button triggers on. If i start the track in the middle of the composition, the button will trigger on. If i star the track where there is no midi(just looped samples), the back to arrange button will stay off.
Maybe its a bug with Nexus... It doesn't trigger this behavior with impulse/drumrack.