Timecode changes when batch capturing

I am capturing betacam sp footage into FCP 5.1 on a dual G5 2.3 box, and using a Kona LSe card. Timecode is running through the 422. For the most part, things are going smoothly, but I am now running into an issue where when I batch capture my logged clips, the last 10 to 15 sec. is chopped off. I generally can just enter the time code again manually to fix the issue, but some of my clips are 8 to 10 min long (interviews), and my client is getting irritated that we are having to capture them again. I also tend to batch capture the majority of these long bites overnight for next morning's session, and they are now consistently coming in with the ends lopped off. FCP is actually changing the timecode on the clip, making me question whether or not I entered it correctly the first time. To prove that I'm not crazy, I monitored the capture on the first couple of clips, and sure enough, FCP decides that I don't need the last 15 sec of my clip, and changes the timecode accordingly during the capture.
What's going on? Is it the Kona card or its software? Thanks.

Well I recently had a similar problem that is really driving me crazy.
While capturing 720p 59.94 from the D5
In FCP when I log a clip at:
01:20:00:00 in
01:20:30:00 out
After Batch Capture is complete the clip shows up in the browser as:
01:19:55:05 in
01:20:25:05 out
FCP is effectively changing the logged timecode of the clip.
In all my experience with FCP I have never encountered this issue and I am completely puzzled. I've contacted AJA and they have said that they do not know of this issue and were puzzled also. The only thing about my current configuration that is not completely right is that I am not using a Tri-Level Sync at the moment. We get ours tomorrow. AJA suggests using the Tri-Level Sync with the Kona 3 card, but would that cause a glitch of this nature? I will try again tomorrow of course and update, but does having bad 720p reference effect how FCP logs and handles TC? To my knowledge it shouldn't and makes me think that there may be some sort of FCP error occurring. There is no reason why FCP should be changing my logged clip settings. Also, I tried a test where I made the clip that came in with the bad timecode offline, and then ran a Bath Capture again, and it changes the logged timecode even further. I've tried a variety of Device Control settings playing with frame offset etc with all having the exact same numeric result (see TC above).
Anyone who has any insight or similar experience your thoughts are greatly appreciated. Thanks for the help
Ted - Editor, NYC

Similar Messages

  • Logged Timecode Changes after Batch Capture

    I'm working with the Kona 3 and the Panasonic D5 (HD3700B)
    I'm having a problem with FCP changing my logged clip TC after Batch Capture in 720p 59.94. This problem only occurs in 720p mode, 1080i is just fine.
    While capturing 720p 59.94 from the D5
    In FCP when I log a clip at:
    01:20:00:00 in
    01:20:30:00 out
    After Batch Capture is complete the clip shows up in the browser as:
    01:19:55:05 in
    01:20:25:05 out
    FCP is effectively changing the logged timecode of the clip. I'm capturing with burned in TC and the Burned in TC is Frame accurate, but why is FCP changing the clip's TC?
    In all my experience with FCP I have never encountered this issue and I am completely puzzled. I've contacted AJA and they have said that they do not know of this issue and were puzzled also. I am using a Tri-Level Sync and everything seems to be getting proper reference.
    There is no reason why FCP should be changing my logged clip settings. (right?) Also, I tried a test where I made the clip that came in with the bad timecode offline, and then ran a Batch Capture again, and it changes the logged timecode even further. I've tried a variety of Device Control settings playing with frame offset etc with all having the exact same numeric result (see TC above).
    Anyone who has any insight or similar experience your thoughts are greatly appreciated. Thanks for the help
    Ted - Editor, NYC

    The BITC matches the original Logged TC (even though the logged TC changes after capture)
    Logged TC (Media Start/End in FCP)
    01:20:00:00, 01:20:30:00
    Captured TC (Media Start/End in FCP)
    01:19:25:05, 01:20:25:05
    Burned in TC Captured (Viewable on Video File)
    01:20:00:00, 01:20:00:00
    I'm very curious about what yourlooking at on the deck manual. Page 145??? I don't see a page 145. It's been my understanding that the Monitor HD-SDI does produce the 720p 59.94 signal, and that's what all my monitors and Kona say that their getting.
    Also, could you clarify your last sentence.
    *"Forgive my guessing but this deck looks like it really wants to work in 1080 and 720 is kind of there to step up from 8 bit DVCPro HD."*
    I dont think that its a 23.98 issue and our source tape is not 23.98, even still if it was, it shouldn't effect the logged TC.... but I'll try it in the morning, could'nt hurt.
    Update: A person over the phone at Apple "didn't" (did) say over the phone that upgrading to 5.1 (universal) would improve 720p capabilities.
    So the next step will be giving more money to Apple for Universal and installing the new Kona drivers released yesterday.....and then let the testing fun begin again.
    Thanks so much for your help, please let me know where to find that info in the D5 (3700B) manual. Cheers.

  • Timecode error in batch capture

    I've searched this problem but still haven't found an answer. When I batch capture, I get a "Timecode error" and on about half the clips I logged I have to cancel out of the capture. some work,some don't. It's not a problem with the pre-roll at the beginning of the tape; I left plenty of room when I set the in/out, and the first clip is now captured anyway so it can't be the start of the tape. But every time I try to capture the rest of the clips, I get this error with some if not most of them. I've changed the setting to NDF and it doesn't seem to make a difference. I'm only capturing in the middle of the tape now, so the beginning and end have lots of space. Please someone tell me how to stop this! I just upgraded to Pro and it's my first attempt at batch capture, so I'm pretty disappointed that it's such a waste of time.
    Thanks, smart people!

    Great, now you made Studio go and have some fun on the weekend.
    X is right eliminate things one at a time.
    You didn't let us know what drive you are capturing to.
    If capturing from the camera doesn't work, it may be that you are experiencing the "multiple FW devices on one FW bus issue" in which case you might try looping the camera or deck through the drive, works for some, but more likely you will need to install another FW bus via the card slot on the laptop.
    By the way, this really doesn't sound like a drop/non drop issue, but look at the timecode display of the footage on tape. If the last 2 numbers are preceded by a semicolon,,, it's drop frame.
    Now, I believe someone mentioned the US Open!
    rh

  • "No Video" error when Batch Capturing

    I am getting a new error that I have not seen before when using Batch Capture in FCP. It cues the tape, starts the pre-roll and then spits out an error message that there is "no video". Of course, there is video.
    The same thing does not happen when capturing one clip at a time nor does it happen if you capture live (hitting Capture "Now" in L&C window).
    Any thoughts?

    I also don't want to keep paying $23 a month for software that is not 100%.
    Software as complex as Premiere Pro will never be 100% bug free.
    I'm also inclined to believe this is more of a system issue than a PP issue.  I don't recall other reports of this nature, and it works fine on my own system.
    The only other thing I can think of to suggest is another FireWire port, possibly by adding a FireWire card to the system.  I've read that the chip makes a difference, so research over in the Hardware forum.

  • When Batch Capturing, Final Cut doesnt notice Media Out points

    I have logged about 20 clips with all of the in and out points set and correct. I have put them in a logging bin and choose batch capture and it begins the process just like usual. However now it wont stop when it comes to the out point of each clip the camera will just keep running until i cancel the batch capture. What could be wrong? any help would be great. thanks

    You need more than one hard drive. Capturing to your system disk is not a good idea and will bite you.
    The in/out ignoring issue could be a problematic QT install or a problem with the firewire protocol.
    1. Make sure you are using the correct Firewire (Basic or std) for your camera/VTR first.
    2. Make sure there is no interference between external hard drives on the firewire bus and your camera
    3. Use the Apple QT7 reinstaller
    Cheers,
    x

  • Audio Timecode changes when match framing

    I'm working in Premiere CC v7.2.2. While working with synced audio, I've noticed that when matching back from audio in my sequence, the timecode displayed in my source monitor is off by a matter of minutes. Each .wav file I'm using has about 10 tracks of audio. This is slowing our workflow considerably and could cause problems for us down the line. Has anyone else experienced this issue? Any help would be appreciated!

    kmbarry23_,
    Thank you for snapping photos to clarify this problem.
    Richard, by default, the "audio time units" or samples is unchecked in the Program Monitor, and the affected timecode to the right of the Program Monitor's wrench/spanner refer to the last frame of media in the sequence, not the timecode of the clip nor audio file your playhead is parked on. The problem is that the dual system audio Overlay timecode as kmbarry23_ has revealed is always displayed in "audio time units" or samples. The only preference in Overlay settings is "source timecode," so there is nothing to change.
    The camera timecode overlay displays correctly, so you have to match frame on your clip, make a marker, and then match frame on your audio, type in the camera timecode, make a marker, and line to two up in the sequence; not too shabby, but it defeats the efficiency and usefulness of overlays. Coupled with the Indeterminate Media Timebase preferences under "Media" always defaulting to 29.97 and the random glitch of drop frame defaulting in the source monitor, it could be confusing how Premiere was really reading the field recorder's timecode.
    Perhaps not all editors are experiencing this phenomenon depending on whatever field recorder was used, but I am still experiencing this problem in CC 2014 (last two week's big update) with jam-synced Ambient timecode from a Sound Devices 744t into a Sony F55 as well as a Red Epic.
    Yes, Pluraleyes is very popular, but not without its own set of glitches. I'd prefer to use Overlay settings in Premiere for syncing when the effort of jam-synced timecode was administered. I'll submit a bug report.

  • Can't find Clip that is choking Batch Capture

    I'm getting a Timecode error saying Final Cut has reached the end of the tape when it tries to capture a particular clip. I can't delete the clip because it's not showing up in my browser window! In other words, it doesn't exist. Is there such a thing as invisible files in Final Cut Pro?
    K

    The thing that's got me the most confused is when I go over to my batch capture list to see what the timecode indicates, the clip that it's having probelms with isn't listed. It doesn't exist. How do I fix a clip's timecode parameters if I can't find the clip listed anywhere. The only time I can see the name of the file (clip) is when batch capture is happening and the program lists the clip it's trying to capture. The name of the clip ends with a number. The last clp closest to it has the number CU 5-1. The program is trying to capture CU 5-2...but there is no CU 5-2!
    What's going on?
    K

  • Batch Capture (Re-Capture) with Free Run TC

    I'm batch capturing footage from 5 years ago for a client that wants another copy of their video. 1 tape was shot REC RUN timecode and it batch captured without issue. However, the 2nd tape is FREE RUN timecode and the capture utility bounces all over the place trying to find the in point. 50 clips, 0 successful captures.
    Have adjusted handles, etc....no dice. I actually had re-captured this tape in CS4 a few years back and it worked fine, might have lost one clip total. Now in CS5, nada.
    Let me know if anyone has an idea what I can do to make PPro park the playback right on the in point without trying to preroll, because nothing I've tried so far has worked.
    For all I know it's a specific issue with CS5...dunno....I turned my back on MiniDV tape a while back and have not tried it since.
    Using CS5, PC, Panasonic camcorder is the capture device.
    Thanks!

    Ann Bens wrote:
    Why not capture the whole tape with scene detection.
    Then chuck out the clips you do not want.
    Ultimately this is what I intend to do if I can't find a resolution for this issue by the time I start working on the project again tomorrow. It should work, re-linking clips doesn't involve preroll or handles so I don't expect any problems going that route. I do expect to capture about twice as much footage as I actually need, as you indicated, so that will be a small hassle but that seems to be the workaround for the moment.
    Thanks for the responses....if anyone else has something they'd like to add (or if anyone is aware of this kind of thing being a recognized bug) feel free to weigh in here. I might file a bug report...it seems to be that the preroll settings are not being recognized, or something along those lines.
    Oh, I should also have noted that this is a fresh (er...4 week old) install of CS5 on a fresh (ahem...also 4 week old) install of Win7 x64. So there's not an application conflict...this is just an Adobe computer for all intents and purposes.

  • Batch Capture Changes Media Start, End, and Duration

    Hello all... For some reason, when I batch capture from an imported batch list in FCP 4.5, the program changes the media start, end, and duration just slightly once the capture has completed. Does anyone know why this might be occurring?

    OK... I don't believe it has to do with drop frame or non-drop frame issues, and here's why... I ran a series of tests.
    The footage was originally shot with two cameras, an A Cam and a B Cam, which were Jam Synced together. The original A Cam tapes were log and captured normally. But for the B Cam tapes, we exported a batch list to excel, performed a rename function where _B was added to all file names and reel names, and brought the data back into FCP by importing a Batch List at 29.97.
    For the tests, I experimented with only one clip. First, I noted the timecode for the media start and media end when the file was uncaptured. Next, I placed the A Cam Tape in the deck and did a batch capture on the one clip. The program changed the media start and end times upon hitting ok. Here were the results of the first test:
    LOGGED: MS (05:50:39:26) ME (05:51:41:01)
    CAPTURED A CAM: MS (05:50:39:17) ME (05:51:41:07)
    Then, I undid the capture so that the timecode would revert back to the precaptured state. I placed the B Cam tape in the deck and ran the capture again, on the same clip, in Batch Capture mode. The program changes the media start and end yet again, but this time, changed it in a different way:
    LOGGED: MS (05:50:39:26) ME (05:51:41:01)
    CAPTURED B CAM 1st Attempt: MS (05:50:39:16) ME (05:51:41:06)
    So then I undid the capture again to revert back to the logged settings, and put the EXACT same tape in the deck, and ran the batch capture in exactly the same way. This time however, FCP didn't change anything. It logged the clip correctly. I tried it yet again, in the same way, and it did it perfectly again:
    LOGGED: MS (05:50:39:26) ME (05:51:41:01)
    CAPTURED B CAM 2nd Attempt: MS (05:50:39:26) ME (05:51:41:01)
    CAPTURED B CAM 3rd Attempt: MS (05:50:39:26) ME (05:51:41:01)
    So I ask again... what is up with FCP 4.5?

  • Batch Capture Randomly Changes In and Out Points

    I'm editing a documentary on Final Cut Pro 5.0.
    Using a SONY DSR-11 firewire deck.
    I logged sets of clips and then batch captured them. I DIDN'T select add handles in the batch capture tool. Some clips, as they're captured, change their in and out points. Sometimes by two frames early, sometimes by two frames late, and sometimes not at all. Several clips even stopped captured with an out point twenty seconds earlier than what I'd logged. The result is that I have clips with media start and media end points that are not in what I wanted. There seems to be no rhyme or reason whatsoever to this.
    Any ideas what's going on?
    Many Thanks if you do!
    Micah
    G4   Mac OS X (10.4.6)   Dual 1.25 Processors

    Check to see if your tapes have NDF time code.
    If you play a tape with NDF TC using Log & Capture, the current time display will defaut to DF until the tape palys forward long enough for the current time field to update. It is posible to log NDF tapes as DF, in which case the timecode values can be incorrectly re-converted if recapturing.
    Also, If you initiate a batch capture from the browser, FCP will default to DF, and not be able to update the TC format to NDF duriing the batch. The workaround here has been to cue up NDF tapes with L&C, and start the batch capture while L&C is still open and showing NDF TC.
    However, upon upgrading to FCP5 last year, I found that even observing all these precautions and steps, FCP would still shorten the out point of my captured clips on NDF tapes. I was capturing a feature film that came from the UK, and so the starting time on the master was 10 hours instead of 1 hour. When the DF/NDF error occurred and shortened the out point of my 2-hour clip, it did it by several minutes instead of several seconds, because of the starting TC on the tape. In that case, I wound up adding several minutes to my out point and recapturing the end over again.
    I haven't experienced this issue lately, but it comes up every now and then.

  • Unable to locate timecode in batch capture

    Hi there, I have been working on this problem for a while and would really appreciate some help.
    I have a documentary project I have been working on for some time and have completed the EDL. I am now trying to batch capture the footage again in full res and am having problems with a couple of the tapes.
    First the specs:
    The video was shot on a Sony HDR-HC1 in HDV(1080) mode.
    I am using this camera to capture the footage.
    I am trying to recapture the footage in a sequence with the easy setting on HDV1080i50.
    I had originally captured the footage in SD on an older version of final cut pro (I am now working with FCP6) and didn't realise that my 16:9 footage was actually all 4:3 letterboxed. To fix this problem I used the media manager to export and then in the new project batch capture all the footage again from the tape. The project uses 18 tapes, 16 of which were batch digitised with only minor troubleshooting required. However 2 of the tapes are proving to be very problematic. It seems that whatever clip I select on the tape it gives me a message saying "unable to locate timecode".
    I have tried setting the tape to the exact location of the clip before selecting the batch capture, but the computer always seems to look for a spot which is 2-3 mins out of sync with the clip. For example, if the in point is 00:10:00:00 the computer will roll the tape to around the 00:12:00:00 mark and start jogging around there for about 30 seconds until eventually giving me the "unable to locate timecode" message. Looking in the information in the bins, the in and out points are accurate, its just that when I try to capture, the computer rolls the tape to the wrong position.
    If anyone knows a workaround for this that will help me avoid having to edit the footage all over again I will be extremely grateful.
    Thanks
    Liam

    HI I have the same problem, the capture window says: Waiting for time code, the device must set in vcr mode and then This operation could not be complete as there is no video, the F!#!%$$ problem is very illogical ,at this mooring I do batch capture without a problem but since the second tape this problem starting, I update to FCP 6.0.4 and,. @@#%#@%#$ the first tape capture but the second not capture and the problem starting againd, note that IMOVIE capture the tape and work very well, iI replace fire wire, camera VCR and , I trayu with Canon, Sony, JVC and the problem persist , I have quicktime 7.4.5, FCO 6.0.4, note that I have two Macs with the same problem in both macs IMOVIE work like a PRO edition Software but FCP is very bad, I have with this problem a long time, I formated Mac, reinstall FCS2 many timers and the problem persist. IS not a problem whit easy setup or wherever , I download the FireWire SDK from Apple and test all connection with the applications of sdk and in all case , the camera and the fire wire are OK, the problem is with quicktime and FCP, If any one is working OK with FCP and DV NTSC devices and JVC PRO HD devices, please tell us HOW DO. I'm working with FCP since 2000 and in this month FCP makes me very UNHAPPY.

  • Help!  Batch Capture Changes My Logged Clips' Media Start & Media End

    I'd be very grateful for any help on this.
    I log a tape with about 40 clips ranging from 30 seconds to 4 minutes. I select the clips and start a batch capture. Everything appears to be capturing normally and I receive no error messages or dropped frame warnings - after my last clip is captured I get a "Successfully Captured" message.
    However, as soon as I click "Finished," all of my clip media start's, media end's, and durations in the log window arbitrarily change to weird times. All my media start points are 26 frames too early (I've tripple-checked that "Add Handles" is indeed deactivated), and the media end points make no sense at all.
    A clip that was once 44 seconds long is now only 12 seconds long, the media end point moved a whopping 34:03 too early. Another clip will become 2 seconds longer, the media start point still shifted back 26 frames, but with the media end now 31 frames too late. Checking the original files on my drive confirms that only these weird, unusable segments are what has been captured.
    What complicates things is that I just discovered today that if I capture locally to my internal hard disk, the clips capture normally (the times remain unchanged). But if I set my capture scratch to my external hard drive (a LaCie F800 2-TB RAID-5 using Firewire-800), that's when the clips start changing themselves. I ran disk utility and found no errors on the drive, and have never had a problem with it or any part of my configuration until the last month or so... the only changes to my system being the regular use of Software Update.
    On top of that, my colleague is experiencing a similar problem with batch capture changing his clip times, even though he is using a different computer (single-processor G5), a different video deck (Sony DHR-1000), and a different storage medium (Apple Xserve RAID).
    So my question is: What is happening! The only thing I can think of is that perhaps some update has a bug - but I can't find anyone with a similar problem online.
    Any help on this would be extremely appreciated! Thank you in advance for your advice.
    Dual 2.3GHz PowerPC G5 Mac OS X (10.4.4) Deck: JVC CU-VH1 / Storage: LaCie F800 2-TB RAID-5
    Dual 2.3GHz PowerPC G5 Mac OS X (10.4.4)

    Here's an update on this. Both my colleague and I have confirmed that if we capture to an internal or external drive that is not a RAID FCPro batch captures just fine.
    But, if the drive we are capturing to is a RAID (in my case a LaCie Biggest F800 and his case an Apple Xserve), then we get dropped frame reports and/or clip in's and out's changing after the batch capture is complete.
    We even tried reformatting one of the xServe's and rebuilding it as non-journaled, it didn't solve the problem.
    It seems impossible that we're the only ones to be experiencing this problem... does anybody have any help or suggestions!?

  • Help with Batch Capturing, Timecode Issues?

    Hi Final Cut Pro Pro's. I've just come over from Avid.
    I have a problem with capturing - I have a lot of tapes to capture and there is no way I will make deadline doing it by individual capture - I need to batch capture. My tape shows no timecode breaks and I have already spent hours logging all the various clips. It shows it has registered all of the media start/end timecodes, but when I click on batch capture, it says
    BATCH CAPTURE: TIMECODE ERROR: UNABLE TO LOCATE THE SPECIFIED TIMECODE. YOU MAY HAVE SPECIFIED A TIMECODE WITH INSUFFICIENT ROOM FOR A PRE/POST ROLL OPERATION.
    I don't understand as there is clearly a functioning timecode? This is going to break my balls if I have to go through this individually, no time! Anyone? Any ideas?
    Thank you.

    I'm capturing from the camera directly, a Sony DSR-250...
    It turns out that yes, if you have marked the in/out point too close to the head or the tail of the tape, or even if you have marked it okay and are currently at the start/end of tape when pressing on batch capture it cannot send the command to the device. If you move forward or backward accordingly by five or six seconds it doesn't come up anymore.
    Thanks for all the responses, I'm going to make deadline now. Apple forums are my hot hot S€X.

  • Batch Capture : Timecode Error?

    So I am attempting to capture my first video onto FCP from my Canon XL. I have about 5 minutes of video and I have logged the info for each clip. They are all in my "Bin 1" and it is set as a "logging bin." The first logged clip that i want it to capture i have marked the "In Point" at 00:00:00;00 and the "Out Point" at around 00:01:09;24. The rest of my 11 clips just go in order (i.e. 2nd clip: In = 00:01:09;25 etc...). After doing all of this I click on "Batch" under the "Capture" option, a big black screen pops up over my FCP with the capture info underneath the black screen in a gray strip. My camera then rewinds to the beginning and STOPS. I then have to sit and wait for anythin to happen, my camera still saying "STOP," and then a message pops up reading the following:
    Batch Capture: Timecode Error: Unable to locate the specified timecode. You may have specified a timecode with insufficient room for a pre/post roll operation.
    I have no idea what this means and I am beginning to get impatient with capturing my video. In the Log and Capture window, the tab that says Logging, i did not mess with the "Markers." I don't know if this matters.
    Any help would be GREATLY appreciated so that I can start editing my project with this wonderful software otherwise.
    God bless,
    |-(|:^D
    `

    In standard trim, FCP needs at least 5 seconds preroll before capturing. The preroll is so the tape can get up to speed, the heads read timecode accurately and so on. You have discovered what happens when you give it no oppertunity to sort itself out.
    The simple answer for your current situation is to set your first in point 10 seconds after the start of the time code. Be sure to make sure your last clip's OUT point is 10 seconds or more before the end of time code or you can have problems at that end of the capture as well.
    The long term answer is next time let the camera run for a minute or two before you start recording anything you will want to keep. The same is true for the end of the tape - let it run for another half minute or so.
    Cheers,
    x

  • Failed Batch Capture - Broken Timecode

    Hello,
    I'm attempting to capture some old footage from a project I had done in Premiere about a year ago.
    There is clip in particular I'm trying to capture where the timecode was broken - premiere attempts to capture the first 8 minutes of my clip and then stops and gives me an error stating that the timecode was broken.
    Is there anyway to force premiere to capture this clip all the way through and ignore the broken timecode point?
    It's not a big deal to capture the clip "manually" but the problem is that I had split up and edited this clip so much, I'd rather batch capture it so that it will automatically appear on my sequence and I won't have to re-edit the whole thing.
    Thanks!
    FOO

    I also have a Canopus card (in a system with Premiere 6.5) and broken timecode ("timecode hell" as I call it) was really only an issue when the tape pre-rolled over the break point during batch capture.
    Do you still have the old Canopus .avi? You could use their util for CDVC <-> DVSD conversions:
    http://download.videohelp.com/download/Canopus_DV_File_Converter.exe

Maybe you are looking for