This discussion is archived
700 Views 5 Replies Latest reply: Jul 9, 2009 9:10 AM by avideditor
Currently Being ModeratedJul 9, 2009 8:35 AM (in response to Jane Evans)This sounds like a sync reference issue, but that would be unusual for a fire wire camera to have this problem. Make sure the camera is not in "EE" mode if it has one. If it has a video input, feed it something like the output of your FCP or black burst is more ideal.
I assume your capturing via fire wire though, so none of this is really applicable, but worth a try.
Are you capturing live from the camera, or off tape, using the camera as a deck?2 x 3.2 GHz Quad-Core Intel Xeon 8 GB 800 MHz, Mac OS X (10.5.7), Kona 3, XServe RAID, FCP Studio 2 v. 6.0.5
Currently Being ModeratedJul 9, 2009 8:44 AM (in response to avideditor)The camera was used to capture a number of tapes. Something was wrong with it, and the timecode has breaks in it. It got sent away and fixed, so now I am just using it as a deck. The video was done by someone else, and there are buttons on the camera that I have no idea of what they do.
When I use the Sony cassette deck, it is very sensitive to timecode breaks, but the picture itself is in perfect alignment. I would rather use the fixed camera body to input, but wondered if there was a button or slider that would correct the picture. Both inputs use firewire. I have not had a problem like this before, although I am still in the novice class of users!Intel iMac 24", MacBook, iMac G4, Mac OS X (10.5.7)
Currently Being ModeratedJul 9, 2009 8:55 AM (in response to Jane Evans)Can you see the vertical shift in the camera's viewfinder, with FCP disconnected physically from it? If you see the shift in the camera alone, the shift is likely dubbed onto the tapes that way when it was used as the dubbing deck. That was likely caused by a sync reference issue, where the two "decks" as it were didn't see the same black burst sync, or the deck you were dubbing from was in EE mode with no signal going to it, or it might have been in an edit mode of some kind.
If you don't see the shift on the camera alone, but do when FCP is hooked up to it... wow, I have no idea there.
Smells like sync reference to me.2 x 3.2 GHz Quad-Core Intel Xeon 8 GB 800 MHz, Mac OS X (10.5.7), Kona 3, XServe RAID, FCP Studio 2 v. 6.0.5
Currently Being ModeratedJul 9, 2009 9:02 AM (in response to avideditor)The lens part of the camera is not here, so no viewfinder. This splitting moves in and out, so I think it has something to do with the camera itself, not the tape. I guess I will just have to go back to the cassette which has none of this, but, as I said, has some timecode problems left by the original camera. Makes capturing a real pain. Thanks for trying to help...Intel iMac 24", MacBook, iMac G4, Mac OS X (10.5.7)
Currently Being ModeratedJul 9, 2009 9:10 AM (in response to Jane Evans)Well, I suggest capturing at your highest quality (no offline resolutions) and disable deck control, so you capture wild across the time code breaks by starting the deck and doing a capture now. You will not have source time code when your done, so back up the media, but this will allow you to ignore the time code problems the deck is throwing.
Or, try forcing the deck into LTC or VITC instead of auto. Try each setting first, see if one or the other behaves better. Often times there is only breaks in one of the time code tracks and not the other, but this depends on how the original tape was recorded.
Good luck.2 x 3.2 GHz Quad-Core Intel Xeon 8 GB 800 MHz, Mac OS X (10.5.7), Kona 3, XServe RAID, FCP Studio 2 v. 6.0.5