Logic will not bounce beginning of song!

Did you try to defining the Bounce Range with Cycle function engaged like explained down here?

http://help.apple.com/logicpro/mac/9.1.6/en/logicpro/usermanual/#chapter=29%26se ction=3

Have a nice day!

RMB2005 wrote:

Logic is only able to bounce from bar 1.

Sorry, but that's not true. It is true however, that it is not recommended to start any project before 1 1 1 1, because Logic can become unreliable. Still, if there's sound before bar 1, and the bounce is set to begin at bar 0 or -1 or so, it should still bounce.

Yes, as I said, it is not recommended to start Logic projects before 1 1 1 1, as all sorts of weird stuff can happen, and the problem is that it is not at all predictable what will (or won't) happen. Sometimes everything just works. And sometimes not. If Jeremy's project does start before 1 1 1 1, it certainly is a good tip to move everything so it starts at or after 1 1 1 1.

Jeremymatthew11 wrote:

Hey,

I am trying to bounce (export) my song that I made in Logic Pro, however every time I do so, Logic pro refuses to bounce the first measure of my project. I set the song beginning and ending markers in the right place, but this doesn't fix my problem..

Jeremy,

Logic does not buffer data until the sequencer starts running, if you have any "look ahead" plugins in the project Logic will almost always skip data at the beginning of a bounce, this is why it's recommended give Logic a bit of "run time" before the bounce starts.

I have started EVERY logic song I've ever made before bar 1 (0/4/4/1) to allow me to put a cc#7 message before the start of the song to reset the level after a fade out at the end. I'm a full time audio pro, so that is literally thousands of songs. Starting before the 1 is not a problem in logic.

DSS

I have started EVERY logic song I've ever made before bar 1 (0/4/4/1) to allow me to put a cc#7 message before the start of the song to reset the level after a fade out at the end.

Then you have been extremely lucky as starting projects prior to 1.1.1.1 is a well documented 'problem area' with Logic for many, many users.... and has been for a long time now.

It may that be you are only (if that is what you meant?) putting Control Data prior to 1.1.1.1 but I couldn't say for sure... but I have personally experienced all kinds of weird issues, and not just those related to bouncing alone.. though not consistantly.. when I have ignored this advice in the past... and placed midi notes, automation or audio files prior to 1.1.1.1

I think you mean 1.1.1.1? ;-)

LOL.. Yes... Been watching too much motorsports today and my brain is fried... (F1 Monaco.. Indy 500 and more to come..)

Updated prior post to correct my idiotic mistake...

Thanks CCT...

kcstudio wrote:

You can count in my thousand of bounces too, never had any problem of missing bars.

Must be luck I guess......

I think it depends on how you work and what plugins you have in use.

Including but not limited to:

-The size of the I/O buffer

-Whether you have played the project through a few times

-How much RAM the machine has (low on RAM and the system disk will be swapping causing a possible skip)

-How you have Plug-In-Delay-Compensation set.

-How much background processing is going on (downloading in the background, many programs running...etc)

-Using the System Disk as your recording/sample drive.

I think it depends on how you work and what plugins you have in use.

Including but not limited to:

-The size of the I/O buffer

-Whether you have played the project through a few times

-How much RAM the machine has (low on RAM and the system disk will be swapping causing a possible skip)

-How you have Plug-In-Delay-Compensation set.

-How much background processing is going on (downloading in the background, many programs running...etc)

-Using the System Disk as your recording/sample drive.

Then I would suggest that the issue is with the items above and not with the song start.

I have a midi region containing the cc#7 at 0/4/4/1. I also used to have regions containing sysex data before the 1.

I don't recall any times when song start position was suggested as the remedy for a problem where it actually solved the problem when tried.

Data Stream Studio wrote:

I think it depends on how you work and what plugins you have in use.

Including but not limited to:

-The size of the I/O buffer

-Whether you have played the project through a few times

-How much RAM the machine has (low on RAM and the system disk will be swapping causing a possible skip)

-How you have Plug-In-Delay-Compensation set.

-How much background processing is going on (downloading in the background, many programs running...etc)

-Using the System Disk as your recording/sample drive.

Then I would suggest that the issue is with the items above and not with the song start.

I have a midi region containing the cc#7 at 0/4/4/1. I also used to have regions containing sysex data before the 1.

I don't recall any times when song start position was suggested as the remedy for a problem where it actually solved the problem when tried.

The two examples you posted cc#7 and sysex are both MIDI, for my part I was only speaking about audio and audio plugins and to a certain extent, some, but not all virtual instruments.

I can verify that projects, my own and former clients bounce/loop problems were corrected by moving all data/audio files to bar 2.

Logic does not buffer data, or activate plugins until the sequencer starts running and it can cause various problems depending on plugins used. (I bet this will change with Logic X). Beginnings of loops being cut-off is one of the most frequently posted. I'm not saying it's a flaw with Logic as it's by design, but it can cause problems if someone is new to Logic. One of the easiest ways to make Logic choke at bar one is to load several CPU intensive plugins that need to be engaged at bar 1, Space Designer..Delay Designer.. Kontakt.. if the CPU is hit hard and Logic is simultaneously trying to pull data off the drive it almost always loses data at bar 1.

One other important item I left out off the list... Bouncing Offline or in Real-time.

I think new users are prone to these kind of problems simply because they don't understand the limitations of "Native" DAW systems.

That is an excellent pre bounce checklist and I do agree these are important criteria. As I said, I must have been very fortunate not to get into troubles in the past. My experience with Logic acting weird while bouncing, can be narrowed down to two important things: Realtime bounce or Offline bounce. Occasionally Logic just refused to bounce offline at all, no alert, nothing. Choosing Realtime was the only remedy and the resulting bounce had no flaw at all. And really I'm not kidding, I never experienced the loss of bar one.

Have a nice day

I Know this is an led thread but it was a new problem for me and I have just solved it. This is my first forum post ever, I am so happy and want to share the solution🙂.

w.when you first select bounce from the file menu and you go to the save window where you select MP3 or PCs etc there is a start and end point option. I don't know why mine has moved away from 1111 or whatever (something to do with markers perhaps) but setting it at the point of bounce solves the problem short term. Hope this does it for you and you don't lose hours of precious time like I did.

philloff

Logic is only able to bounce from bar 1. Make sure that your song doesn't start before this point.

I stand corrected, but it can happen. I had a song given to me to mix which started at bar 0 and it would not bounce the first measure until I moved everything beyond bar 1.

Thank you, this solve my issue trying to export a single track from 0 0 0 0.