Andrew Saliga
Forum Replies Created
-
Oh, I also took your advice Rafael and cleaned the heads. No luck.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Quick followup…
This timecode has still been a nightmare. I just don’t see it being actual TC breaks, since these are film transfers done by &Transfer. Could older tape have issues? Some of this is from the early ’90s.
Jeremy– I tried that creating that text file. No luck.
Chad– I like your theory, but I FCP won’t let me capture without interruption with these breaks. I do have the option checked to warn after capture, but this isn’t a great solution. I have 60+ one hour tapes that I don’t want to babysit 🙁
Sam– I wonder if this is a performance issue. The digitizing station I’m using has 2 Dual-Core Intel Xeons at 2.66GHz. I’m capturing to a SAN via fibre. Each core is hovering from 80-90%.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Thanks for the input everyone. I’ve just been able to take another look at the deck this afternoon.
I went through all the deck settings again and also made sure “Warn after capture” was selected. So far so good. However, I realized I am capturing a different tape than I did on Thursday. If I encounter any issues, I’ll start looking into the RS422 polling issues.
Very useful info everyone. I appreciate you helping out an HDCAM newbie.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Jeremy– I’m using a Kona 3. All Kona and FCP settings should be correct as I’ve been capturing without any issues. I’ll try creating that text file in the morning. I’ve never even heard of a fix like that.
Chad– The clips are being captured from a batch list. Timecode format is matches that of the tape. I can’t get FCP to continue capturing though, it will randomly stop and seek timecode. I’m with you on thinking along the lines of the RS-422. I tried a different cable, but am still not 100% convinced. Tomorrow I’m going to try to capture from the DigiBeta deck in an attempt to rule out the cable.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Thanks John. I’ll give that a shot.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
No worries. I’ll see what happens. It seems in trying to “fix” this problem I’ve done something that prevents me from editing to tape…
Thanks for all your help guys.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Making sure I’m following you and it’s not a typo Dave. You say you have encountered that situation?
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Yes, not surprised about QT, but I’ve had several people (specifically on the COW compression forums) suggest not trusting FCP because it’s always wrong and to use MediaInfo.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
I guess I hadn’t considered that as an option. Have you seen this behavior before or have any idea as to why it’s reading the metadata incorrectly?
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com -
Ran the AJA uninstaller.
Rebooted.
Reinstalled latest AJA Kona 3 Drivers.
Rebooted.Test capture #1 ProRes422HQ 1080i29.97.
FCP says it’s 29.97.
QT Pro says 29.67.
MediaInfo says 29.665.Trashed FCP prefs.
Rebooted.
Emptied trash.Test capture #2 ProRes422HQ 1080i29.97.
FCP says it’s 29.97.
QT Pro says 29.62.
MediaInfo says 29.627.All capture and edit to tape (via Beta and BetaSP) worked prior to the holiday break.
Andrew Saliga
I/O Specialist/Assistant Editor
Steelehouse Productions
http://www.steelehouse.com