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.

Similar Messages

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

Aux timecode changes after entered in Modify Timecode window

I'm trying to manually add an aux timecode to some clips so I can edit them with multicam editing (two cameras DV, two DVCAM), the timecode itself isn't synced however I did have the cameras pointed at an external timecode generator for a few seconds so that I could get a constant, external time reference). Two of my clips accept the new timecode with no problems, however one of the other ones demands to add 8 frames to the timecode I enter, the other demands to add 14 frames.
I just realized that the DVCAM footage is Non-DropFrame timecode, but I'm adding a drop-frame timecode to it. That might explain it...

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

Clearing batch capture

How do I clear the Batch capture Queue?
Mac Pro Mac OS X (10.4.8) FCP 5.1

I usually just do a single clip with batch capture so when I abort, it's over. For those who have just tuned in, Jim goes thru his material and laboriously logs each shot he thinks he's going to use and then batch captures. I mark an out at the end of the tape, rewind, mark an in at the beginning with sufficient preroll, log the clip and batch capture the entire tape (of course with abort clip on dropped frames and make new clip on timecode break). After capturing if it's dv material, I do a start/stop detect. And then I do a thorough job of logging and labelling.

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.

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

Batch capture / Subclip question

Hey all,
I've logged tapes from DV marking in / out points and labeling the clips. I've selected "log clips" and then batch captured the clips. Sometimes, I've needed to batch capture 1 minute of footage from a 20 minute clip - and I don't want to recapture the whole 20 minute clip.
I've tried to make a subclip of the footage needed and just capture the subclip, but it wants to grab the whole 20 minute clip.
Ideas?
Thanks,
Kevin
PowerBook G4 15" Mac OS X (10.3.9) FCP HD 4.5

Subclips aren't captured, they are made from clips
ALREADY captured. If you needed shorter clips, you
need to log them that way before capturing ... or you
can make the 1 minute clip an "independent clip."
-DH
Thanks for the reply. I identified the clip in the sequence I wanted to recapture. It's a 20 second soundbite with a DV glitch in it. I highlighted the clip, selected "make independant clip", and nothing seemed to happen. With that clip highlighted, I tried to recapture the clip, but it still said the duration of the recapture would be the length of the full original clip. All I need to do is recapture a short piece of the original. Any ideas?
Thanks,
- KO

[svn:osmf:] 11312: Changes after code review.

Revision: 11312
Author:   [email protected]
Date:     2009-10-30 10:21:24 -0700 (Fri, 30 Oct 2009)
Log Message:
Changes after code review.
Modified Paths:
    osmf/trunk/apps/samples/framework/CuePointSample/src/CuePointSample.mxml
    osmf/trunk/framework/MediaFramework/org/osmf/metadata/TemporalFacet.as
    osmf/trunk/framework/MediaFramework/org/osmf/metadata/TemporalIdentifier.as
    osmf/trunk/framework/MediaFramework/org/osmf/video/VideoElement.as

[svn:osmf:] 13533: Changes after code review.

Revision: 13533
Revision: 13533
Author:   [email protected]
Date:     2010-01-15 14:20:10 -0800 (Fri, 15 Jan 2010)
Log Message:
Changes after code review.
Modified Paths:
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/SMILPluginInfo.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/loader/SMILLoader.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/media/SMILMediaGenerator.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/model/SMILDocument.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/model/SMILElement.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/model/SMILElementType.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/model/SMILMediaElement.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/parser/SMILParser.as
Removed Paths:
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/media/ISMILMediaGenerator.as
    osmf/trunk/plugins/SMILPlugin/org/osmf/smil/media/SMILProxyElement.as

Online help with Batch Capture

I'm trying to online a sequence in a tapeless workflow. I'm using Log & Transfer along with Batch Capture but Batch Capture keeps looking for a deck. How do I get it to look for my Hi-Res digital files?

Yeah...that's the problem.
You directly imported it and worked with it natively? What is this footage? From what camera?
The only way to offline/online with tapeless is to bring in the footage via Log and Transfer. Log and Transfer to ProRes Proxy...then you can Batch Capture to a higher data rate ProRes format.

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

Batch Capture - Frame rate changes after first clip

Hey everybody,
Working in CS4 on a Mac, and trying to simply batch capture about 35 clips after all have been logged accurately.
I'm using the DVX100A, and shot in 24Pa. So I have set up my sequence settings to DV 23.98 Fps, and 16:9 Progressive.
Upon batch capturing (making sure the capture settings are the same) the first clip is captured at 23.98 and works fine, then every one after that 'captures' at 29.97. I say 'captures' because it says it is captured but when I try and play it in the source monitor Premiere crashes or freezes.
Has anyone else experienced this issue? Thanks for any input regarding this issue.

Then I changed Recording Setup to 480i/30p...My thoughts were that this would be slowed down a little.
That is an incorrect thought. DV tape runs at 29.97fps always. Even 24p...that runs at 29.97 but has the film like cadence. If you want to shoot slow motion, you need to shoot 720p. That is a 60 frame format. You can shoot 720p24 to get 23.98, then there is a trick to get the camera to shoot 60fps and record it as 24fps. The Barry Green book that comes with the camera explains that. And that is SMOOTH slow motion.
Now the camera ships with a 16GB P2 card. One comes in the box, along with the Barry Green book. Did you not get that? Where did you buy the camera?
Shane

Audio Not Syncing After Offline Conversion/Batch Capture from OfflineRT-DV

WORKFLOW:
1. Shooting HDV on a Sony HDR-V1U (DF/NDF Timecode setting is AUTO on the camera)
2. Using the camera to downconvert to DV as I import into FCP 7 (final product will be NTSC DVD).
3. I first capture and log using the OfflineRT NTSC (Photo JPEG) preset
4. I make my Edits, and then use Media Manager to create new project and create offline media referenced by duplicated items. (Set sequences to: DV NTSC 48 kHz)
5. The clips I need are then batch captured using Capture Preset: DV NTSC 48 kHz
PROBLEMS:
A. As I'm initiating my batch capture in step #5 above, the following warning is generated:
WARNING: You are about to capture Drop Frame media from a device currently detecting or configured for Non-Drop Frame media. If you proceed, you may experience changes in logged in and out points, problems relinking media, or removal of master clip relationships.
B. When I playback my sequence, the in/out points are off by several seconds. (like the media within the clip slid ahead several seconds--to fix it, I would have to slide each clip back)
QUESTIONS:
Q1: How can I properly execute my workflow while avoiding the WARNING above and the problem with the in/out points?
NOTE: The OfflineRT clips in the original project (#3 above) are shown as DF (semicolon in timecode), but the duplicated clips in the DV project (#4 above) are NDF (colon in timecode). I have already tried changing my capture preset to Firewire NTSC NDF, recapturing the clips, and the result is the same.
Q2: Should the capture preset be the same or different when logging the first (OfflineRT) and second (DV NTSC 48kHz) times?

Wish I had a simple answer for you, stay tuned, some folks who actually use those cameras will drop by sooner or later.
TrevorRawson wrote:
After importing through log and capture I continue to get a pop up when it's done saying that the audio and video frame rates do not line up.
I'll bet you're shooting with a Canon.
TrevorRawson wrote:
I am using a Canon xl2 and a Panasonic DVX100A,
Ah-HA!
TrevorRawson wrote:I'm shooting in 24p Advanced with a 2:3:3:2 pull down. The capture settings are set up for FCP's default DV NTSC 24p with Advanced Pulldown, same with my sequence settings. This is my first time shooting in 24pa so I'm a little lost at what to do. Does anyone know the correct settings I should be using?
so neither camera captures properly? that's odd. We know the Canon is going to give you trouble but the Pani should work.
Try searching the forum for your camera models, see what comes up. Many different cameras shoot their own versions of various image,frame, and pulldown formats.
bogiesan

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?

Logged Timecode Changes after Batch Capture

Similar Messages

Maybe you are looking for