Project Start is at minus 8 bars and won't move back?

[Scott Jackson]

Finally, once you have your start back to 1111, is it generally good policy to start your regions on this mark, or a bar later?

 

I always keep my Start Marker at 1111 and always start my recordings at 2111.

[Rev. Juda Sleaze]

I always keep my Start Marker at 1111 and always start my recordings at 2111.

 

Me too.

[Scott Jackson]

The "song end" handle just seems to determine how long your grid is going to be, and you don't need it to be 2000 bars long if you're only going to use 150 bars - it just makes the scrollbars tiny.

 

Why is your End Marker at bar 2000?

 

When you create a New Empty Project the Start Marker is at 130 by default. It will move while Recording if your recording gets near the End Marker but not so much as to jump to bar 2000.

[afx]

I'm not really sure how it ended up like that, to be honest! I started dragging it back then reset it more quickly using the transport area.

 

Things seem to be okay in this now, and I'm also starting regions on bar 2. Thanks.

[Scott Jackson]

Things seem to be okay in this now, and I'm also starting regions on bar 2. Thanks.

 

You're welcome.

[ski]

The "song end" handle just seems to determine how long your grid is going to be, and you don't need it to be 2000 bars long if you're only going to use 150 bars - it just makes the scrollbars tiny.

 

Why is your End Marker at bar 2000?

 

When you create a New Empty Project the Start Marker is at 130 by default. It will move while Recording if your recording gets near the End Marker but not so much as to jump to bar 2000.

 

FWIW, the Song End marker will very often move on its own. Logic's been doing this since Logic 4. I routinely find that it will move to extraordinarily high values for no reason whatsoever.

 

AFX, in the project you posted about, are you working in a time signature other than 4/4, or do you have mixed meters in your project?

[Scott Jackson]

FWIW, the Song End marker will very often move on its own. Logic's been doing this since Logic 4. I routinely find that it will move to extraordinarily high values for no reason whatsoever.

 

Strange bug. I've never ran into that before. The only time my Song End Marker moves by itself is when I'm recording audio and then it only moves about as far as the length of the region currently being recorded. There must be some reason why you and AXF and others have experienced this.

[afx]

Hi ski,

 

The project is fairly new and is set to standard 4/4. No mixed metres in it. In my last one I did slow down the tempo at the end, but not in this one as yet.

 

As mentioned elsewhere I have not long been using Logic, having used Cubase on the PC in previous years. Of course, it's great, but I think I have seen these things a couple of times in the previous few files I have made, as you say. Both the negative shift and the extraordinary amount of bars. Not quite sure how that came about or what I might have done to cause it. Like you say, maybe Logic just does it on its own sometimes - a bug.

 

I just created a new project to test and right enough the song start is at 1111 and the song end is set at 130. The bars extend to 134.5 which seems a slightly odd amount but there we go.

[Scott Jackson]

I just created a new project to test and right enough the song start is at 1111 and the song end is set at 130. The bars extend to 134.5 which seems a slightly odd amount but there we go.

 

That's normal.

[ttocscire]

none of the options snip / insert silence work / i tired move . don't move

 

 

 

Sorry to hear you can't make it work. Let's focus on the only option that works: to insert silence. Personally, I have never been in a situation where that solution does not work.

 

 

 

1) Did you click-hold your start marker to check the exact position? What is that position?

 

 

 

2) When you insert silence, can you describe as accurately as possible what happens to your regions? To your automation?

 

 

 

3) After inserting silence, do you still see any automation at all before 1 1 1 1?

 

 

 

Before and after screenshots would help a lot.

 

 

Hi David -

 

I'm new to the forums and recently started using Logic Pro 9.1.8 - struggling with this issue on a project with a lot of automation where I most likely accidently moved the start locator to -8 bars. This is the best post of this issue I've found so far. When I insert silence it just bumps the tracks 8 bars ahead, that's all it does, I cannot move the start locator and/or delete the space before 1 1 1 1.

 

I'm not clear on the exact steps to take resolve this. Seems like "not a bug but a feature" type thing. I cannot find any instructions in the 2 Apple LP9 cert training books i recently purchased. Hard to believe more others are not having the same problem. If there's an easier way to manipulate the project file directly that would be save a lot of grief. Any help would be appreciated.

 

Thanks - Eric

[ncalonne]

Hello Guy above me (just hit quote, forgot your name). I was having a similar issue. Inserting silence didn't work, nor did inserting a section.

 

What DID work was the solution below. If you follow his directions carefully it's actually not that time consuming.

 

I just went through a 100+ track session in 10 minutes. Of course, only about 20 have automation so far, but still. What I did was popped it into automation view so I could see which tracks had automation. I used the "Hide" function (press H by default, click the little "H" that appears on the track header, press H again) to hide all the tracks that did not have automation.

 

It's best to pencil in a region at the 1.1 mark and then once you have all of them drag it back. If you try to copy paste it will just jump forward to the 1.1 anyway.

 

One difference for me (9.1.6?) was that after I had snipped the extraneous (now region-based) automation, when I checked the secret automation arrange window there were still some regions showing up. None of these actually had any automation written, however, and the tracks which I had cleaned up were clear. I think they showed up because they had some parameter other than "volume" toggled.

 

 

Yeah, I understand, do what the boss says. But in this case he's using a feature of Logic that is inherently bug-ridden. Trust me on this. And inform your boss that it's one of those situations where just because Logic lets you do something doesn't mean it's a good idea.

 

So here's what you do to fix it:

 

EASY FIX: if you don't have any meaningful automation written in just yet, use the function to delete all automation of all tracks. Once this is done, move the song start marker to 1 1 1 1 and never touch it again.

 

IF the above is not the case, then things get more complicated...

 

THE LONG FIX

1) for EACH track that has automation, use the "new track with same channel strip/instrument" function and create a duplicate track.

 

2) on each track, pencil in a region at the very start of the project (I guess this is bar -8 or whatever).

 

3) stretch each track to be the length of the project, and then select them all. Open the color palette and make them all a color that doesn't belong to any other region. This makes it easy to select them all using the "select regions by color" function if necessary. Read on...

 

4) with all of those blank regions selected, use the function to move all track-based automation to regions

 

5) now you have to double-check that this worked: select any track that had automation on it, open the automation event list, and then hit CMD-1. This will show you the normally hidden automation arrange page. If it's empty (and it should be), close it and the auto. event list.

 

6) now set your playhead to 1 1 1 1, select all of those regions you made (here, using the 'select by color' function makes quick work of this) and split at playhead. Delete the regions before bar 1.

 

7) move the song start marker to 1 1 1 1 and never touch it again.

 

FINAL STEPS:

 

8a) select all of those regions you made and use the function to move all region automation to track automation

 

8b) use the function "select empty regions" and make sure that all of those regions are actually empty now (they should be). If so, delete those regions.

 

8c) go into each track's automation and add at least one node somewhere in the beginning to re-establish nodes starting from bar 1 1 1 1 (you'll see what I mean when you try it)