Batch Capture Log Template

Does anyone know of an app or spreadsheet template that will make it easier to create a capture log--so I don't have type in the repeated colons and semi-colons and will possibly go to the next cell once the required TC numbers have been entered?
thanks

Drop frame and non-drop frame both have the same number of frames. No frames are "dropped". What is "dropped" are some frame numbers.
Think of timecode as frame addresses.
If video ran at 30 frames per second, in an hour 60 * 60 * 30 frames would go by (108,000 frames) and the timecode at the end of that time would be 1 hour, or 01:00:00 or 3,600 complete seconds of 30 frame counting timecode.
However, frames go by at a slightly slower rate (slower by 1 part in 1000, or 1/10th of 1 percent) of 29.97 frames per second. So in an hour of time on the wall clock, only 60 * 60 * 29.97 frames go by, or 107,892 frames. The timecode at that time would be 59:56:12 or 3596.4 complete seconds of 30 frame counting timecode.
This is all well and good, except the clock on the wall says 1 hour, and the clock counting timecode addresses says 59min56secs12frames. If you're running a TV station, this is confusing.
So in order to make the timecode on the tape deck match the clock on the wall, the difference needs to be fixed, so that at 1 hour the timecode reads 1:00:00 even though the frame rate is 29.97.
The difference between the theoretical 30 and the real 29.97 is 108 frames in an hour. To make up that difference in Drop Frame timecode, two frames of the counting (addresses) are skipped each minute on the minute. So at 00:59:29 the next frame is called 01:00:02, skipping two frames of numbering.
This is done on every minute, except the even 10 minutes. So for 54 minutes out of the hour, two frames of counting are skipped. For 6 minutes out of the hour, no frames are skipped. 2 frames times 54 minutes is 108 frames, or the difference we needed.
No frames were "dropped", only some frame numbering addresses were skipped to help the clock on the wall match the clock on the video tape deck or computer.
Drop frame and non-drop frame timecode both play the same number of frames in an hour of real time.
The difference is that non-drop frame timecode has consecutive frame numbering addresses, and drop-frame timecode does not have consecutive frame numbering addresses, as it has dropped 108 frames of the count over the course of an hour, when it skipped 2 frames of count 54 times.

Similar Messages

  • Batch capture logged clips makes subclips that are invisible in sequence

    Any ideas?
    I log a series of clips (the icon is the square master clip icon). They are offline until I batch capture. However, once I batch capture, they become subclips(jaggy-edge subclip icon). They can play in the viewer and they are viewable in Quicktime. However, once I put them in the sequence, they are only black, even after rendering. HOWEVER, if I do a capture now off of the SAME tape w/ the SAME settings it will play just fine (after render) in the SAME sequence.
    Anyone else experiencing this? Thanks in advance
    Vicky
    Power Mac G5   Mac OS X (10.4.2)   FCP 5.01

    Okay, finally able to do a couple of tests. I started a new project w/ settings for capturing good ol' NTSC DV, logged some footage and then batch captured (ntsc footage) -- no problem at all. The clips were clips, not subclips. Then I went into a project for DVCPro HD 720 30p, and pulled some clips from my original low res project into the HD project. Made those offline, then batch captured those at the full HD resolution. Not a problem there either. Then I went back into the original low res project, made a clip offline, recaptured it at full HD res, no problem. Soo.... I think there is some connection between what I've been capturing at my "low res HD" setting and the problem of turning the logged clips into subclips upon capture.
    All that said...I think I'm ok. At least I know now when I do need to capture it all in full HD res, I'll be able to, and it will relink into my project correctly as visible clips.
    Also, how can you mark somthing "helpful' if it has already been marked "solved"...it is not undoable, correct?
    Dual 2.7 GHz PowerPC G5   Mac OS X (10.4.5)   2 GB RAM

  • 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!?

  • Capturing Batch Input Log without keeping BDC session

    Hi all -
    Would like to capture the Batch Input log and keep it persistent in some manner (for example using an application log) without keeping the corresponding BDC session.  The reason for this is that any manual corrections to data interfaces through BDC sessions MUST be logged indefinitely for audit purposes.  The actual BDC sessions are HUGE and therefore precludes saving the entire BDC session.  My thoughts are user-exit'ing in BDC session either as a Batch Input Log is being created or when a Session is being deleted (NOTE: running ECC 6.0 which has new enhancement concept permitting extremely flexible user-exit'ing so exit points are NOT an issue and repair/core mode not required).  Anyone see any flaws with this approach or can recommend perhaps a simpler or standard approach so that Batch Input Logs are retained indefinitely whereas the Session is deleted?
    Many thanks,
    Pat

    Hi Pat,
    Why dont you try archiving?
    For archiving, archive object BDCLOGPROD can be used. if archived, then you can read the archived logs using program RSBDC_ARCHREAD (also accessible from SARA->Read).
    See some notes if it is helpful:
    147354, 18319, 24438, 18307
    Also have a look at the Data Management Guide available at service.sap.com/data-archiving.
    Hope this helps,
    Naveen

  • 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.

  • Logging/batch capture

    After logging 3 tapes I discovered that early on, somehow my capture settings have been switched from Audio and Video to just Audio. Now I have about 50 clips that are logged incorrectly. Someone please tell me there's a way to change these without having to re-log all of these.
    Thanks!

    I figured it out. It's a bit tedious, but not nearly as bad as re-logging.
    One by one, take each logged clip as if you were going to batch capture. So right click and select "batch capture". Then once the clip is loaded in the Capture window, abort the capture. Then change the settings back to Audio and Video and you can either select "Capture In/Out" or "Log Clip". Problem solved!

  • Batch capture opening rather than log and transfer

    What causes batch capture to open rather than log and transfer? Attempting to media manage and reimport clips but only batch capture will open? Thanks, Michael

    Hey there camera400,
    were there any solutions you found? I'm having exactly the same issue at the moment....
    I'm following the "RED FCS White Paper" dated November 11, 2008 from the RED support page-
    Doing "Workflow 2: Work offline Using ProRes; Finish Using RED Quicktime Media" - (my offline was ProRes (hq)).
    Based on this workflow, I get all way through step 5.3 of Workflow 2 -- creating offline project and setting Log & Transfer settings.
    The Paper suggests that when I right-click the new offline sequence, select "Batch Capture" from the shortcut menu, the Log & Transfer window will appear, allowing me to reinjest RED footage.
    However, it opens Batch Capture instead...
    Any insights appreciated.

  • Batch capture settings do not match project settings

    Batch capture audio settings do not conform to project settings-
    PROJECT SETTINGS ON CREATION OF NEW PROJECT:
    For editing with IEEE1394 (FireWire/i.LINK) DV equipment.
    Standard NTSC video (4:3 interlaced).
    48kHz (16 bit) audio.
    Drop-Frame Timecode numbering.
    General
    Editing mode: DV NTSC
    Timebase: 29.97fps
    Video Settings
    Frame size: 720h 480v (0.9091)
    Frame rate: 29.97 frames/second
    Pixel Aspect Ratio: D1/DV NTSC (0.9091)
    Fields: Lower Field First
    Audio Settings
    Sample rate: 48000 samples/second
    Default Sequence
    Total video tracks: 3
    Master track type: Stereo
    Mono tracks: 0
    Please note audio setting for project 48kHz (16 bit) audio.
    When I set for batch capture by creating off-line clips using the "Log Clip" option the off-line clip shows audio as
    32KHZ 16-bit  everyting else is correct as project settings.
    Just prior to creating the off-line batch capture clip I had sucessfully captured from the same device using the same tape shot with the above settings including 48khz 16-bit audio by using standard " Capture" by setting in & out then clicking Capture>In/Out.
    I've looked at capture settings etc...unable to determine to change audio settings etc or why the audio settings under batch capture do not conform to project settings...
    Any ideas?
    Tnx,
    mick

    Thanks for your reply, Harm....
    Well now...having negated all the possibilities you listed, I decided to do a an actual batch capture with clips which I previously logged which reported audio at 32kHz instead of the project setting of 48kHz:
    1. two clips  were selected from the same device/tape ( both selected from the logging util which erroneously reported audio at 32kHz) for the batch
    2. both clips captured "flawlessly"
    3. both clips after the batch capture then reported audio as being 48kHz
    Btw, I also did a batch capture from the same device/tape in Pr 6.x...and it reported and captured at 48khz...I must say, I must prefer the legacy version of Pr 6 for batch capture which creates a log .pbl file which can then be easily exported as a csv to and .xls etc..IMO, much more useful...and useable..
    Mi dos pesos(.002US)
    So it would appear there is some kind of bug in the Pr cs4 batch capture util that is erroneously reporting audio settings?
    Should this go to the devel as a possible bug?
    Tnx,
    mick

  • Any way to re-capture logged clips to anamorphic setting?

    Hello-
    I have an FCP project with containing clips with a 16:9 aspect ratio captured with 4:3 aspect ratio setting. I'd like to recapture all of the logged clips using the anamorphic capture setting. However, all the capture information is embedded in the clips, so, even if I set the capture preference to anamorphic, the clips still come through as 4:3 when I attempt to re-batch capture.
    Is there anyway to globally change the capture setting to anamorphic with clips that have already been captured at 4:3?
    Thanks....

    If you are talking about DV, there is absolutely no need to recapture. The difference between 4:3 and 16:9 DV is really in how FCP interpretes the pixels- they are both 720x480.
    Go to the Browser and you can add a check mark in the ANAMORPHIC column. Voila, you now have anamorphic clips without recapturing.
    x
    edit: I'm slow slow slow. To elaborate on what Tallguy said, if you need to fix the aspect ratio of the clips you've already placed in a 16:9 timeline, select all the clips in the timeline, right (control) click and from the popup menu select: Remove Attributes>Video Attributes>Distort.

  • Batch capture problem

    I'm trying to batch capture my clips, so i logged them all but when i select them all and choose batch capture an error comes up after a while and says "end of tape reached". The only footage i have on my tape goes from the beginning of the tape to about three minutes in. Can someone please help me here.
    thanks,
    Paul

    Don't know if you are still looking for a solution to this but...
    You most likely set your in point very near the first code on the tape. FCP needs to roll back a few seconds, before the in point, in order to ensure the deck gets up to speed before the capture begins. If it rolls back and can find not code before your in point, things get confused and FCP will not do the capture. This is also why, when shooting, you should always roll at least 5 seconds before the action starts.
    Try moving the in point forward at least seconds.

  • Batch Capture Error: Timecode Error: End of Tape Reached

    I have been having issues doing batch capture with my JVC VS30U. I logged all my clips on the fly and did the entire tape, so the OUT point of one clip is the same as the IN point of the next clip. When I attempt to batch capture it gives this error between every clip.
    I have to hit retry, sometimes more than once, in order for the deck to properly cue and FCP to start the digitize. I don't know if this is a weird pre-roll issue, or something else, but it completely defeats the purpose of a batch if I have to sit here and hit retry after each clip.
    There are no TC breaks, and obviously its not really the end of the tape. I've read where people have similar problems, but didn't find a solution. Have already trashed prefs, but to no avail. Using FCP 5.0.4 with OS 10.4.3 and said JVC deck via firewire.
    Any ideas? Thanks in advance!

    I don't know the deck but a simple test would be to move a couple of i/o points so they are not adjacent. Or test with a single, longer clip and break it up into subclips.
    Tell us what you've tried so we don't waster your time and ours with fruitless suggestions.
    Errors displayed by FCP are usually irrelevant and rarely helpful.
    bogiesan

  • HDV batch capture is making new clips...

    thanks for watching...
    i have imported batch lists into FCP with name, media start, media end, reel and log note just as the FCP manual instructs. they import fine and i have them all in their own bins.
    i batch captured a few tapes to day and i noticed that FCP is making new clips at times. for instance i'll have a clip "dogs" in the original batch list. after the batch capture there will be "dogs" and "dogs -1" the starting time code of "dogs" and the ending timecode of "dogs -1" are the original start and end of the clip. so, FCP has spit this clip in two for some reason. why is that?
    i thought it might have to do with the setting "make new clip on Start/stop" thats listed in the clip settings tab of the log/capture window. so i made sure this was unclicked and then tried another batch , also making sure to uncheck "use original clip settings" in the batch window. but, the problem still persists.
    i have 30 tapes to digitize and i'd prefer the clips matched the batch lists. any ideas i can try to solve this problem?
    take care,
    max

    Is it a new media drive?
    how is your media drive formatted? highlight the drive on the desktop and press command(apple)+i to get info...
    Where it says 'Format' it should read Mac OS Extended... does yours say FAT 32 by any chance?
    FAT32 is a different format that can be read by PCs and Macs... it can only store file sizes of 2Gb, so has the knock-on effect of causing FCP to break captures into smaller chunks.
    If your drive is FAT32 you need to re-format it using Disc Utility. When you do this, you will lose everything on that drive, so back it up if possible.
    If your drive is formatted correctly, post back with your media set-up, ie - what drives you use, how is your capture scratch configured etc.

  • 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 capturing entire tape...recomended???

    Is it a good idea to attempt to batch capture a tape in its entirety? I am having problems doing this...I do a lot of events that last often over 2 hours. Instead of capturing footage in clips, I just capture the entire tape. When I'm done with the project, I simply make the clips offline.
    I'm in the process of reviving a project now, and one tape in it's entirety(55 min approx), captured OK, but I am having problems with another tape. I am getting a broken timecode error, when I don't see how this is possible...because I let the tape freely run. Also, under the logging info, the media ends before the tape ends, which means that is space left on the end of the tape without any timecode. Yet when I batch capture, it still goes to the end of the tape.....isn't a batch capture suppose to go by the clips media in and media out points?
    All help is greatly appreciated.

    I do this often. There are two shools of thought on this method -
    Capturing entire tapes allows one to scroll through non-linearly and make subclips. The advantage to subclips is that they are serachable and you can add comments. The downside to this method is that the files are large, and you may be capturing much more metarila than you need. I often do this when working on docs with very high shooting ratios. The most recent one had 190 tapes for a 1-hour program, which led us to use offline RT for our cutting format and then recapture for online.
    Logging and capturing single clips fives you the advantage of starting out capturing only what you know you might use, you can input the logging info at the start, and will have several small clips that may be easier to manage. Since at some point you'll have to familiarize youself with the matreial anyway, you might as well do it at the logging stage.
    Several factors can contribute to perceived TC breaks - reusing tapes, camera stops, shooting format (HDV, for instance, will show a TC break each time the camera stops). If you are capturing whole tapes, you might do well to let FCP create new clips on TC breaks and just let it roll. Make sure the TC format matches between your tape and settings (DF vs. NDF)
    Regarding rolling off the end of the tape during capture, you might be very close to the end with the clip you are capturing. You might try lowering the post-roll value in the device control preset in your A/V settings.
    Hope this helps -
    Max Average

  • Batch Capturing in HD

    Hello,
    Digitizing HD footage has given me some real problems. I've used the "Log and Capture" feature and it worked to an extent, though because you're unable to name the "reel" for the this footage you are left in the lurch if the media becomes disconnected. I've been trying to log clips and batch capture the old fashioned way, but it still creates new clips within my "In" and "Out" cues. This is would be acceptable, except about 7 seconds are cut off at the start of each clip. If anyone knows a way to disable the creating new clips function, that would be EXTREMELY helpful.
    I've tried adjusting the setting in the user preferences and it's done me no good. Even after i changed "Make new Clips" to "Warn afterwards." That preference only causes the batch capture to crash. Again, if anyone can help that would be huge.
    Thanks again.
    Brendan

    The HDV capture setting has a start/stop detect. (It makes a new clip each time you started and stopped the camera.) Not sure why you lose seven seconds at the beginning of each clip, I thought that only happened when timecode breaks and dropped frames were detected. But anyway, rule of thumb when you can, always start the camera rolling BEFORE you need it to. Get at least 10sec at the beginning of each clip and roll out for at least 10sec when you are done. Ample handles to cover just such an issue.
    Of course this doesn't help your current project, so let me go get an A1U and see what is going on. I'll try to post back soon, but someone may just beat me to it.

Maybe you are looking for