Losing notes after bouncing tracks

Question

Level 1

11 points

Losing notes after bouncing tracks

Hey folks,

I've got some 90 odd tracks with film score material, and I'm in the process of bouncing individual instrument tracks to audio in order to send to my mix engineer. I'm only working on one 3-minute cue right now, but I'm running into a serious problem.

I solo the intrument track I want to bounce, execute the bounce, and it works fine; but after doing about 3 or 4 of these, I'm finding that the subsequent bounces start excluding more and more MIDI notes. At this point, when I unsolo the track and try to play the entire cue, most of the intruments are not playing, and many of the notes of the instruments that are playing don't sound.

If I close Logic Pro, and reopen it, the same cue plays fine, with every instrument, every note. Starting this process again, results in the same buggy state after doing a few bounces. Anyone know what the problem is here, or how to resolve it?

My system has:

12 cores
3.46 GHz CPU
64GB of RAM
Logic Pro 9
OS X 10.6.8

Thanks in advance for any help you can provide.

Paul Sumares

Mac Pro (Mid 2010), Mac OS X (10.6.8)

Posted on Nov 11, 2013 2:36 PM

Reply

Answer 1

kcstudio

Level 4

1,808 points

Nov 11, 2013 11:51 PM in response to Paul Sumares

Are you at 64 bit and do you have 32 bit plugins running in the bridge? The symptoms you describe give rise to the assumption that this might be the case!

Regards

Reply

Answer 2

Paul Sumares Author

Level 1

11 points

Nov 12, 2013 12:14 AM in response to kcstudio

No. Not using a bridge, unless there is an internal one that Logic uses that I don't know about, and there are some 32-bit plugins I've popped in there without realizing it.

Is that possible?

To the best of my knowledge, all of the sample libraries I've used are 64-bit.

Paul

PS: Thanks for the reply.

Reply

Answer 3

kcstudio

Level 4

1,808 points

Nov 12, 2013 12:25 AM in response to Paul Sumares

When running L9 in 64 bit mode a 32 bit plugin can only be used via the bridge! Therefore if logic runs in 64 bit mode and you notice active 32 bit plugins, then the bridge will be active too.

Regards

Reply

Answer 4

Paul Sumares Author

Level 1

11 points

Nov 12, 2013 12:55 AM in response to kcstudio

I see. I had only heard of using something like Vienna Ensemble Pro to solve the requirement for a 32-bit bridge (which of course lead me to believe there was no internal one).

Okay, I will scan for 32-bit plugins to see if this is my situation.

If this is the case for me, is it a bug, or is there some configuration of the bridge that makes this work properly, for example?

Paul

Reply

Answer 5

Pancenter

Level 6

14,788 points

Nov 12, 2013 1:12 AM in response to Paul Sumares

It sounds like a memory leak of some kind.

Obviously Logic is running at 64-bit, correct?

You have checked info?

Reply

Answer 6

kcstudio

Level 4

1,808 points

Nov 12, 2013 1:12 AM in response to Paul Sumares

On large projects it will get increasingly unstable and in my experience is that even on small projects it will crash on you regularly. It always was like that. The only way around this 32 bit issue, seems VEP indeed, I only heard good reports about its use. It's of little help to you I know, but I would avoid the bridge all together given the choice!

Reply

Answer 7

Paul Sumares Author

Level 1

11 points

Nov 20, 2013 12:46 AM in response to Pancenter

Sorry for the late reply ...

Yes, I am running Logic at 64-bit.

I am not running any 32-bit plugins to my knowledge. I use common tools that I know professionals are using on film scores:

Kontakt 5
EW Play 3.0
EXS24 (built-in)
ES1 (built-in)
Omnisphere 1.5
Superior Drummer 2.3

All 64-bit compatible.

How do the pros possibly get their tracks to an audio engineer when time is of the essence, given that

Logic only allows you to bounce all your selected regions to one audio track
Or bounce EVERY region on EVERY track to separate audio files (gives me an error code anyway)
After bouncing more than 3 or 4 regions separately, it starts dropping MIDI notes
Which means you have to go back and look at your MIDI while playing the audio files one by one until you find the one that started dropping the notes, restart, and go back to bouncing from the latest region that it failed on.

This is practically useless!

I went through every effort to research this Mac Pro system prior to purchasing it, and installing the programs. I've even made sure I set it up to use slightly less than the full number of cores I have available -- as it was reported by many on various forums that setting it to use all 12 lead to problems.

I bought a fairly recent model of the Mac Pro, and upgraded it to have the 12 cores, the fastest CPU I could find a professional to put in for me (3.46 GHz), loaded it with as much RAM as could be stuck into all 8 slots (64GB total). I don't know how to get more power out of such a system short of slaving more beasts.

... and Logic Pro is dropping MIDI notes after bouncing a few regions.

Granted, I have over 90 tracks going, but I know that it's not uncommon for a film score to have over 100 tracks going simultaneously (before it even goes to the orchestrator and Abbey Road for recording the live parts).

Is there a way that I can DISABLE the tracks I am not bouncing, rather than simply soloing the one I want, so that it has a lot less crunching to do while its bouncing my little 2-minute region?

(Sorry for the frustration ... it just doesn't seem reasonable for a "Professional Application" as this forum context suggests.)

Again, any help is appreciated.

Paul

Reply