Scott Sheriff
Forum Replies Created
-
We always have a cheap fixed lens camera for shooting the scoreboard clock on the truck. Bring it in as a cropped image (DVE) or key it in and matte fill the key so it looks more ‘electronic’, pretty much SOP.
If there is a Chyron there should be a clock in it, but it will tie up one of your output channels. You could lay it off to tape or your replay machine, but that would tie up that resource, which is the same for a FCP generated clock.
See if the truck has a ‘Fox Box’, that will have what you want without using up a tape machine, or one of the Chyron channels. -
720p in a Sony? I thought Sony was 1080i. Most likely it’s a JVC recording, and if it is, Sony deck’s/camera’s won’t play back JVC 720P.
Check your FCP capture settings to make sure they match your source, and check to see what gear your source footage came from. -
Just tried this with FCS2 running with Snow Leopard and it worked as it is supposed to.
-
Did you do a clean install?
I’m running SL and FCS2 on a oct-core and it runs great.
You need to install the OS on a fresh formatted drive, then re-install your pro aps. If you just did an upgrade on the existing system that is most likely the problem.
Check the Final Cut forum, lots of posts on there regarding this. -
Follow up:
I’m assuming you round tripped your mix thru Soundtrack Pro, if not disregard my previous comment. -
If your footage is HDV, I think you have stumbled upon a known STP bug.
When you use channel 2 audio from your source footage, STP reverts it to channel 1, no matter how the channel select is set. Your mix plays fine in STP, but the proper channels don’t make it to the Master, or Subs.
I’m posting a feature right now that this very thing is giving me fits. In my case it only does this when the source is from a Sony HDV 1080i camera master. We have a JVC GY110 720p HDV camera, and don’t have the same problem with the master tapes from it.
One solution is to export the audio clips in the Final Cut timeline (before you send to Soundtrack), that are using ch 2 audio from your source as aif, and then re-import these exported clips back into the timeline. This is a big pain in the a** if you have a lot of short clips, but it does work.
Apple techs were able to recreate this problem and told me that the new version (FCS3) doesn’t do this. I guess that is their way of saying not to expect an update in this version. So an alternative is to upgrade to FCS3, which is what we are thinking about, even though we are in mid-project, and upgrades can introduce other headaches. -
Just installed SL on an octo Xeon, 2.8GHz, 16GB, GeForce 8800 with FCS2, no capture card.
Installed OS on fresh 1 TB drive. All other drives were pulled until the install was finished.
Used Time Machine to install prefs and other files, but not applications.
Installed FCS2.
Checked for, and installed updates until there were no more. (twice)
Installed remaining non-Final Cut applications.
Re-calibrated the monitors.
I have been working a a feature length 1080i project, that is broken up into 9 sequences of approximately 10 minutes each and used this project to check FC.
Final Cut (6.0.6) opens and works normal, including FW log and capture.
All the other FCS2 applications open and work normal.
Exporting to Compressor works normal and sending that to DVD Studio Pro works normal too.
Opening existing Soundtrack projects is OK.
Sending a Multitrack project to Soundtrack is temperamental, and the return trip to a new Final Cut sequence very temperamental, but at least I eventually got it to work. Exporting to Final Cut wouldn’t work, unless Final Cut was already open.
So far most it seems like the Apple applications open a lot faster. FCS2 applications seem to open a little faster, but don’t run any faster.
All the non-Apple aps work fine, and may open a little faster.
I like the new Dock and Stacks behavior.
I’m going to put my old system drive back in, and revert back to Leopard for working on my project, but will probably switch over to SL, and FCS3 when its done since I’m collaborating with another person that is not going to upgrade. -
I wonder if Snow Leopard in combination with FCS3 will fix this?
It’s coming out today. -
Hi,
In the first clip you posted the range check is clearly on. The zebra, and the yellow triangle are the clues there.
Trash prefs and repair permissions, also try loading one of the other widow arrangements.
When was your last OS update? Saw some reports of weirdness after the last OS update.
Other than that, I don’t know. I couldn’t replicate the problem. -
Hi,
Looks like you might have the ‘range check’ turned on. Try turning that off and see if your safe area returns to normal. I have seen the ‘range check’ make the scopes and overlays behave weird before.
Could use more info. When did this start? On a new project? On start up?