[Lcjones]

MCH,

Sounds like you have plenty of guts. Yes, I use Audacity. I'm currently using the beta 1.30 Windows port. And I also have the 1.24 version.

Let's clarify "dubbing" vs "multi-tracking". First Audacity has virtually unlimited multi-track abilities but that is limited only by your equipment.

Dubbing is when you literally lay sound over top of another sound on the same track. Literally "dubbing it in".

Multi-tracking is a layered process, much like todays graphics programs. You almost have to think in dimensions.

The Dylan song I posted had, I believe, 6 tracks:
2 tracks main guitar
1 track secondary guitar
1 track bass
2 track vocals

I think this is whats happening for you. Your first "track" is literally being recorded into your second track.

To explain. You make your first recording, perhaps your main guitar rhythm. When you start your second track, the sounds from the first track are "again" recorded into the second track. That is where your dubbing is coming into play. As you build each successive track, the previous tracks are recorded into the new track. So by the time you get to your last track, all that sound from all the other tracks are "muddied" into the last track.

So, if thats the case, then thats your latency issue. Perhaps not literal latency, just over-dubbing. And when over dubbing takes place, you can't control the timing. If your first track is at a specific speed, based on your systems abilities, when you record the second track it may be a few milli-seconds different than the first....BUT... that first track is being recorded into the second track and doesn't "time match", hence "perceived latency problems".

[edited to add this .....]

In the case as I mention above, each succesive track you make, even though in the same "work space", "IS" a new recording and not a seperate track.

hmm ... Did that make sense ?????


Les