Import - Overlay...why doesn't it work??

[JR Fountain]

I've had this question for years...

When importing session data and selecting "Match Tracks" and "Import - Overlay new or existing playlist" the incoming session data always deletes the existing session data...why??

I just did a very simple test
- one clip with volume automation at 01:00:00:00 in session 1
- one clip with volume automation at 01:10:00:00 in session 2
- in session 2, import session data of session 1 using Match Tracks and Import Overlay
- result, the volume automation at 01:10:00:00 is flattened

If you do the test in reverse however it works as expected. In other words, importing session data *after* your existing data works, but importing session data that happens *before* your existing data does not.

Let me know if I'm missing something, but this seems like a bug.

Thx!
J.R.

[Cheesehead]

That's the way its always been.
We just have to work around it and always import audio to matched tracks after any existing audio.
I've got used to it over the years.
Maybe its because you can't make a selection for an AAF import and so it just pastes out to the end of the session?

[JR Fountain]

Bummer. Thx for the reply though!

[TVPostSound]

Originally Posted by Cheesehead

That's the way its always been.
We just have to work around it and always import audio to matched tracks after any existing audio.
I've got used to it over the years.
Maybe its because you can't make a selection for an AAF import and so it just pastes out to the end of the session?

It has not always been that way.
It worked in PT10, stopped working that way on PT11.

[Cheesehead]

Oh, sorry I must have blanked it from my memory, along with the
snappy video reponse of 10. I still miss that!

[TheMuffinMan01]

Originally Posted by Cheesehead

Oh, sorry I must have blanked it from my memory, along with the
snappy video reponse of 10. I still miss that!

Worse sync though if I recall correctly.

[Starcrash]

The downstream automation from session 1 blows away the automation in session 2. It's logical, but not useful or helpful.


One potential solution would be a new feature that allows you to import session data for a specific timeline range. For example, import session data from 01:00:00:00 to 02:00:00:00 and it would leave the timeline before and after that range untouched.


This feature would be very useful for working in a "super session" that contains multiple reels, episodes, or songs.

[TVPostSound]

Originally Posted by Cheesehead

Oh, sorry I must have blanked it from my memory, along with the
snappy video reponse of 10. I still miss that!

I might be wrong with versions.
I do know it worked before Protools became a 24 hour session.