[Dan Monro]

Hey John,

Glad you found it. There is a check box in your user prefs that says “open last project on application launch.” uncheck it and you’ll start with a blank project.

I’ve also been guilty of opening an autosave, and then not re-saving it as the original project, so now my auto-saves are for that auto-save project, if you see what I mean. And the one I’m working on is still in the auto-save folder. Does that make sense?

D

Dan Monro
FCP, PPro, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7, PPro 5 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.3, PPro5.0.3 Quicktime 7.6.6

[Dan Monro]

Dang. Sorry Wes.

Dan Monro
FCP, PPro, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7, PPro 5 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.3, PPro5.0.3 Quicktime 7.6.6

[Dan Monro]

I’d advise using FCP7, too. What cool new features do you want to use? I believe that Automatic Dick is working on a way to get older projects into FCX, but I don’t know how well it would work. And if you’re in the middle of any project, switching will invariably mess everything up (speaking from experience). Is it too late? Have you already “upgraded”? If so, you should still have FC7 on your system, and – again – I’d stick with that.

Dan Monro
FCP, PPro, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7, PPro 5 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.3, PPro5.0.3 Quicktime 7.6.6

[Dan Monro]

My thoughts exactly. Must be a petabyte raid array in his garage…

Nicely done.
D

Dan Monro
FCP, PPro, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7, PPro 5 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.3, PPro5.0.3 Quicktime 7.6.6

[Dan Monro]

This workflow could not be achieved with FCPX. It will work fine with FCP7, and would with several other less expensive options. But you have FCP7, its a great piece of software for what you want to do, and there will be no translation issues going to an FCP7 post facility.

Cheers

Dan Monro
FCP, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.2 Quicktime 7.6.6

[Dan Monro]

Maybe we’re talking about two different things. The Pro Kit update?

Dan Monro
FCP, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.2 Quicktime 7.6.6

[Dan Monro]

I was able to get to it…

Dan Monro
FCP, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.2 Quicktime 7.6.6

[Dan Monro]

Shot in the dark: did Final Cut crash at some point, and you hit “re-open”? If so, maybe you were working in a project named slightly differently, like “name_of_Project_061611-142750” or some such. This happens when you’re using auto-save, which you’re not.

I guess it would have come up in your spotlight search. But worth a look…

Last ditch, I guess I’d open any unidentifiable FCP projects you can find in the system, in case you inadvertently re-named it while saving it.

Good luck,
D

Dan Monro
FCP, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.2 Quicktime 7.6.6

[Dan Monro]

If you’re using the color picker I assume that means you have control over the color. In which case, bring down your brightness and saturation to legal limits.

You could also try dropping the broadcast safe filter on it – I think that affects saturation.

And it was hard for me to not simply reply “never a good idea with alcohol…”

Dan Monro
FCP, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.2 Quicktime 7.6.6

[Dan Monro]

Another option is to:

select all of the audio tracks you want to modify.

Hit “command” + “option” + “L” to get a dialog box that allows you to adjust the gain for all selected channels, either up or down by a relative amount, or adjust all to an absolute level, i.e. -18db.

Or:

select all of the audio tracks you want to modify.

Hold ‘control” and hit the “[” key to lower all selected by -3db at a time (the “]” key does +3db; the “-” and “+” keys +-1db). This also works for any track you’re parked over even if it isn’t selected – as long as it’s track selector light is on…

Hope this helps,
D

Dan Monro
FCP, Avid, AfterFX, Atlanta
MacBook Pro 2.53 GHz Intel Core i5 4 GB ram
Mac OS X 10.6.4
NVIDIA GeForce GT 330M
Final Cut Pro 7 Quicktime 7.6.6
– OR –
2 x 3.2 Quad Xeon; 16 GB ram
Mac OS X 10.6.4
NVIDIA Quadro FX 5600 Final Cut Pro 7.0.2 Quicktime 7.6.6