How Mute a Vocal Track in Logic Pro X When on Latch

• New Sponsor: ShipNerd, Ship Your Gear with Us... for less! Click Here.

• Home
• Forums
• The Gear Page Lounge
• Recording/Live Sound

Exporting stems in Logic Pro X - Why does it sound different?

• Thread starter elationalways
• Start date Yesterday at 12:50 PM

• Tags

  logic pro x mixbus mixing stems

• #1

Hello all,

I feel like I have tried everything and can't figure out what I am missing. Here's my situation:

The project is pretty simple. 10 tracks:

• two direct-in guitars (gross, I know)
• six virtual/midi instruments
• two sampled sounds

When I export the stems to have someone mix and master, then pulled the exported files into a new/blank Logic session, it sounds different. -- I know this description will be annoying to some, but please take it for what it's worth. Exporting the stems should be an easy part of the process. It just sounds different. It's lacking warmth. The mix feels messier.

I do have two instances in this project where I am sending two instruments to the same mix bus to add more reverb to both. When I export, this reverb is nowhere to be found in the tracks on elsewhere. So, I decided to create a track for each of the two buses. This did create an export which seemed to be the missing effects. But it still isn't quite right.

I feel like I am making this more difficult than it has to be. PLEASE HELP! What am I missing!?

• #2

Caveat, I've rarely exported tracks or stems myself so you'll likely get far better answers.

The two things that come to mind are that 1) the relative levels are different in the new session vs the old...I'm not sure if the process of exporting the stems are maybe normalizing, or ignoring the fader level and just using the gain pre-fader (?) Meaning that when you pull them into the new session then the mix is simply different. If these are mono tracks then the panning would be different in the new session (everything center), stereo ones should have the same balance.

If you have buss processing (compression, saturation, delay/verb) right on the buss (assuming you use busses), then perhaps the individual stems are being exported pre-buss.

I have not had this issue when I send tracks to a friend of mine, but the way I'm exporting tracks is typically soloing each track and then bouncing to an audio file, and that seems to get any fx or buss processing (and automation). Typically I'm just sending him a track here or there so it works for me. It's possible that if you are doing a mass export then it works differently?

Again, apologies as I asked more questions than provided answers

• #3

How are you "exporting" stems?

Do you have effects on your master bus?

What other effects are you using in addition to the send for reverb?

• #4

@Stokely

1) I have normalize turned off and automation/panning exporting with the tracks. So, they are stereo.
2) I believe the stems are exporting pre-bus. However, I have been able to export the bus as a track also. This part feels hacky to me.
3) Hm. That might work. That is, exporting soloed tracks in order to get the bus processing included with the track. Good call! And yes, I am exporting all tracks, so this would technically fix that but again, feels a little hacky. I wish Logic would just clarify this in the export in order to avoid all of this.

No apology necessary. I really appreciate the thoughtful response!

@sws1

As mentioned above, I am exporting "all tracks as audio files" - File > Export > Export All Tracks As Audio Files.

From there, I'm including audio trail, including volume/pan automation, and turning OFF normalize.

I do have effects on the master bus. EQ and Compression. That's a good thought, but even after adding the same settings to the same plugins on the master track in the new session, it sounds different. The warmth is a little better but it still isn't exact and that really, REALLY bothers me.

Both buses have reverb, one of them has a compressor (for synths only).

• #5

Well... I'm not quite clear on what's happening or hoping to be accomplished but a few thoughts anyway.

Typically when exporting tracks they won't include any sort of processing like EQ compression etc that might be inserted. It would/should just be raw audio. If you want to include the processing they would need to be rendered/printed and then exported...

Also worth checking & triple checking to make sure that the export sample rate & bit depth is the same as what you recorded... that you aren't up or downsampling which can certainly change things!

Second? As a mix for hire guy I wouldn't want all of your panning automation & processing anyway. If you've hired someone to mix why tie their hands? What's the point? If I got tracks like that I'd kick 'em back.

As a Logic guy there are often times when I'll take the project as-is and the first thing I do is go through and turn off most of the processing and automation so I'm not chasing my tail around. No matter if its 10 tracks or 50+ I need to build my own session.

Obviously, probably best to talk about this directly with whomever you hired to do the mix & mastering. You need to give them what they want & need, which may or may not be what you think is best.

Last edited: Yesterday at 3:46 PM

• #6

@jmoose

Really appreciate this perspective. This is actually what my guy requested. He likes where the mix is at but wants to tweak a few things before mastering.

That said, to your first point, I might give printing, then exporting a try. As it stands, all of the virtual instruments are still in midi.

• #7

Is your guy working in Logic? Why not do a "save as - new name" and send him the session as is? That's what I'd ask for in this situation. Its less work for you and maybe a little more on my end but then we're not trying to reinvent the wheel either.

FWIW I always request that any MIDI instruments get printed as audio. Fairly standard... nobody has all the VI libraries there's too many. If its a stock logic sound that's one thing but otherwise? Always print.

• #8

As you mentioned above, you would need to "bounce" your tracks in order to pick up any plugin processing. Exporting the track just dumps the audio that you see on the screen...pre-processing.

• #9

As you mentioned above, you would need to "bounce" your tracks in order to pick up any plugin processing. Exporting the track just dumps the audio that you see on the screen...pre-processing.

Exactly, yep, was just about to say this

• #10

Thanks, all. This is all really helpful.

@jmoose unfortunately he is a Pro Tools guy.

• #11

Make sure you're also bouncing using the same bit and sampling rate. Often times the default downsamples.

• #12

@taez555 Yeah! I caught that. That one almost got me. I wish Logic didn't do that.

• #13

My collaborator is also a Pro Tools guy so wav files are what we decided on.

Good point above about keeping things natural for the mix person. In my case, I tended to not use EQ and very little compression or fx on my keys tracks I was sending unless I considered them integral to the sound. Even then I might send a dry copy, and he usually wanted a midi file in case he wanted to replace the sound entirely. (I have better IMO instrument plugins, but if he's the producer then he might have very specific sounds in mind and that can be tedious to try to impart that to someone). Or heck even tweak the performance since it's midi. So pretty obviously the roles of the two people can play a big part here, toes can get stepped on and egos bruised at times!

For one of our tunes, roles were reversed and I was doing the mixing, and he sent me his guitar parts. I requested the DI tracks as well as the processed ones from his amp sims, in case I felt like tweaking the amps or cabs. Again you have to watch out for hurt feelings when doing this collaboration...if hiring someone to mix the roles are very well defined so not an issue!

• Home
• Forums
• The Gear Page Lounge
• Recording/Live Sound

How Mute a Vocal Track in Logic Pro X When on Latch

Source: https://www.thegearpage.net/board/index.php?threads/exporting-stems-in-logic-pro-x-why-does-it-sound-different.2311656/

Share this post