A Strange Problem

[BasilF]

Let's say that I create a tune. I work on it. I open up a different track to work things out and then bounce it to the main track. What has started to happen is that the bounced track is three 8th notes behind. Adjusting it is no problem but there's more. In the secondary track, if I bounce it to another track and then bounce that one to the main tune, there is no issue. It shows as being on the 1. I've been using PT since 2005. This is a new one. Any ideas?

[Ben Jenssen]

Originally Posted by BasilF

Let's say that I create a tune. I work on it. I open up a different track to work things out and then bounce it to the main track. What has started to happen is that the bounced track is three 8th notes behind. Adjusting it is no problem but there's more. In the secondary track, if I bounce it to another track and then bounce that one to the main tune, there is no issue. It shows as being on the 1. I've been using PT since 2005. This is a new one. Any ideas?

I find this very difficult to understand. It might be because of the way you use the word 'track'. Outside PT 'track' is often used for a song; a track on an album. In PT a track is a instrument, midi, audio, or aux track in a session. also; "bounce into the main tune", what do you mean. Could you clarify please?

[BasilF]

Thanks for responding. Yea, "track" is confusing. You boot PT. You create a new project. We'll call it project A. You work on it. There may be something that you want to work out, like a solo or orchestration. For that, you create another project. In that one, when I bounce to the original project, it's off by three 8th notes. Yet, in the secondary project, if I bounce it to another track and then bounce THAT track to the original project, it's perfectly aligned on the 1.

[JFreak]

Track is something that has a fader in a mix window. Session is something that has one or more tracks. Project is a session that is stored in the cloud.

[JFreak]

"Channel" is mono input or output. "Channel Strip" is just a marketing name for analog console equivalent of putting EQ and dynamics processing into single plugin.

"Track" also comes from analog world, from the days of us dinosaurs when we recorded audio to magnetic audio tape, thus one "channel" was recorded into a "track" of magnetic data.

[JFreak]

Originally Posted by Robruce

Exactly. The track is the data, the channel is the path.

Yes, but my oversimplification of "something that has fader" is the representation of the data. Once you have done recording, you can disable the "channel", as in no input to your track.

[Ben Jenssen]

Originally Posted by BasilF

Thanks for responding. Yea, "track" is confusing. You boot PT. You create a new project. We'll call it project A. You work on it. There may be something that you want to work out, like a solo or orchestration. For that, you create another project. In that one, when I bounce to the original project, it's off by three 8th notes. Yet, in the secondary project, if I bounce it to another track and then bounce THAT track to the original project, it's perfectly aligned on the 1.

OK.
Are you careful that you select exactly the region that you want to bounce, in both bounce procedures? If you are, I'm out of ideas.

(Actually the term 'project' is also a bit of a problem. Of course we all work on projects all the time, but for those who are using Pro Tools First, it could be a cause for confusion, because: Avid, in their wisdom, decided that they would call the two different types of sessions that PTF can have, is called 'project' - it is stored in the cloud, and 'session' - that is stored on your harddisk.)