Region automation not working properly [SOLVED]

Some tracks no longer read the region automation correctly. They don't read correctly if I start playback in the middle of a region. It plays back according to track volume and doesn't read the region automation. If I start before the region, it then reads the region correctly.

 

Has something changed in the way to work with region automation. Maybe a setting somewhere ? This only seemed to have started when I updated to 10.2

 

I hope I'm just missing something. It's almost impossible to edit this way. .

 

thanks for any help..

Have you checked your Chase settings?

Could you provide a screenshot of your region that exhibits this behaviour?

I checked chase settings but I think it's only applicable to midi regions. Here's a screen shot of automation. If I playback the hilighted region in the middle (where the cursor is ) it plays back at -20 db, which is where the track volume is set. If I start before the region it follows the automation curve and playbacks at -3 db.

 

 

I don't think it's related to 10.2 update. It does the same in 10.1. I didn't use much region automation in the past but I thought it would be useful in this project. I've gone back to using track automation only for now.

Not ideal, but have you tried to convert to RBA?

Yes I tried converting the track automation to RBA. It then works OK and follows the region automation as long as I don't touch the track automation in any way. But if I make any track automation adjustments whatsoever it behaves as before.

Zip a version of your project and include only this region.

Attach it here and I'll take a look at it.

Here's a simple project with one region. The behaviour is the same as I indicated. If I start playing back in the middle of the region, the volume level is at -20 (which is the track volume). If I start playback before the region it plays correctly to -3db.

 

RBA project.logicx.zip

 

Maybe I'm misunderstanding how RBA works in Logic.

CONTROL COMMAND E will open the Track Automation Event List. There you will see a Fader event at 1 1 1 1 set to 28, which resets the volume to -20.0 db. Delete the event and it will stop.

 

But I hope Eric comments here, because I have had this issue before, and I'm never quite sure how Fader events like this are created. Setting an initial track volume should not create it -- then it would happen to me a lot more than it does.

Choose File > Project Settings > General > Region automation takes priority over track automation.

Okay, I get it. And this is what's happened to me in the past.

 

I start with TBA and get a node at the beginning of the track. Later in the song, I revert a region to RBA. It only works if the playhead plays through the region. If I stop midway, Logic reads the TBA at the beginning of the song -- especially if the RBA is static at the time I resume playback (in this case, the held 3.0 RBA between bars 23 to 63 approximately).

 

If the RBA was moving when I resumed playback, Logic would pick that up again.

 

Finally, when I switch to RBA, I very likely switch to "Region" display in the Track, which HIDES the TBA node at the beginning of the song. So all I see is the RBA of the region, and I can't figure out why it's resetting.

THANK-YOU very much Eric ! That's exactly what I was looking for. I was hoping it was simple... Much appreciated.

You're welcome!

Thank you Eric, there have been a few different proposed solutions online but this one worked for me (in REVERSE): "Choose File > Project Settings > General > Region automation takes priority over track automation." I unchecked it and then my track automation starting working again (I didn't even know there was region automation option...and it is all set to zero in my project