Logic Pro Question about merging files in logic, please help!

[Cortezguitar]

I use Digital Performer and my friend uses Logic. Not sure which version but I'll bet my question doesn't pertain to a specific version.

In DP there is a function called merge track that creates a new track which is a compilation of all the punches and closes up all the open spaces. If you have performed edits, it consolidates the edits into one track. This is useful for editing and also for sharing files.

My friend doesn't know how to do this in Logic and is performing bounces of his tracks to compile his edits and share his files. I contend he is creating inferior files this way, and that Logic must have a proper way to do it, although it is probably called by a different name.

Does anyone know how to "merge tracks" in Logic? Thanks in advance.

 

[Eli]

While it certainly is possible to merge all the regions in a track to one consolidate dnew region/audio file. The command is called "join" and the key command is Command J.

However, I would not suggest doing it this way if the goal is to export files to another system. I would suggest using the Export All Files As Audio Tracks function from under the file menu. It will consolidate each track into one contiguous file starting at bar 1, with the option to include/exclude plug-in processing. And if it's a big project, you don't have to do them one by one. It's a one shot deal. Hit the command, go have a coffee and come back later; they'll all be done. See the enclosed screen shot.

 

[Peter Ostry]

In addition to what Eli said:
Bouncing a track in Logic should not produce a file with bad quality, actually bouncing is the usual way to render audio files. You did not say what "inferior quality" means in this case, but if the tracks are ok in the mix, they come out in very good quality. If they don't, there must be something wrong in the process.

 

[Cortezguitar]

Thanks guys

Thanks for the info guys! Very helpful.

Just to clarify... my pal was using the bounce command to create copies of the individual track files. He would solo the track and run a bounce, then solo the next track and so on. For one thing, that took way longer than it needed to, but it also yielded stereo tracks, where there had been mono, effectively doubling the file sizes on my end. I wasn't sure either, if his faders were properly set, since the first set of files he sent me had very weak levels. Finally, the bounce command passes whatever is selected through the main bus, which is theoretically clean, but is still unnecessary and may or may not create digital artifacts, depending on bounce settings and other variables between our two systems.

We've been working on a project of his that has multiple problems. As I've tried to determine the causes and solutions, I wanted to eliminate anything that may have been creating deviations of any kind. Thankfully, with your help, I am now looking at the same files he is, and we can eliminate some of the theories, and were able to get to the heart of his issues. Now I can focus on solving those problems.

Thanks again! You guys were lifesavers!