View Full Version : Time code and "logging"


Micky McCrea
December 22nd, 2005, 06:45 AM
Hi,

Is there a way to set the GL2 so that the time code does not return to zero if you record, stop and record. For some reason, the time code does not continue. Sometimes it resets to zero and I am sure that it is something that I am doing that causes it. I was visiting with an editor yesterday and he was explaining how to "log" for editing purposes.

Jim Montgomery
December 22nd, 2005, 07:23 AM
Try recording "nothing" for the length of the tape. It will write the timecode and when you record real material the timecode will already be there.

Graham Bernard
December 22nd, 2005, 12:00 PM
Micky? Have you set the time and date? Just checking with you. G

Jean-Francois Robichaud
December 22nd, 2005, 12:21 PM
Make sure to let the camera record for several extra seconds at the end of your shot. I you have to turn the camera off then back on, then just rewind a few seconds. That way, there should not be a timecode break. Anyway, no matter what you're filming, it's always better to let it run a few seconds more. Tape is cheap.

Micky McCrea
December 22nd, 2005, 03:57 PM
Yes, I have set the time and date. What I am wanting to do is create a written log that the editor can use when he gets the tape. For example:

292: Close up of boot stepping off ladder.
425: Wide shot of sunset.

If I understood the guy correctly, I use the numbers that indicate where on the tape this particular scene is located. This should expedite his editing work. Hope this makes sense to you.

Thanks,
Micky

Jim OMalley
December 22nd, 2005, 04:19 PM
Yes, logging of takes is a "best practice" in video editing so having reliable time code numbers is essential. Starting and stopping the camera in record mode should not result in broken time code. If that's happening, you might want to have the camera serviced. However, you'll get a break in time code if you remove the tape from the camera between takes, or if you rewind and review your takes after you record them. Are you doing either of those things?

Micky McCrea
December 22nd, 2005, 04:33 PM
Yes, logging of takes is a "best practice" in video editing so having reliable time code numbers is essential. Starting and stopping the camera in record mode should not result in broken time code. If that's happening, you might want to have the camera serviced. However, you'll get a break in time code if you remove the tape from the camera between takes, or if you rewind and review your takes after you record them. Are you doing either of those things?

Yes, we review the tapes after we record them. We are shooting video for a hunting DVD. We review the footage at the lodge after every hunt.

Jim OMalley
December 22nd, 2005, 04:36 PM
Do you review the takes in the field, on the camera, before you go back to the lodge? If so, that could be your problem. Going from "record" mode to "play" mode and back to "record" mode will cause you to have a time code break. (Note that I'm saying "takes" not "tapes.")

Micky McCrea
December 22nd, 2005, 05:00 PM
Do you review the takes in the field, on the camera, before you go back to the lodge? If so, that could be your problem. Going from "record" mode to "play" mode and back to "record" mode will cause you to have a time code break. (Note that I'm saying "takes" not "tapes.")

Usually, that is not not the case. Maybe this is not going to be a problem on all of the tapes. We have 3-4 folks running cameras and I bought 50 tapes. I told them to always put in a fresh tape when they go back in the field. They were trying to "use up" the tape at first. But, one individual recorded over some good footage. After that, I think everyone has only used the tape for one session in the field. When they come back to the lodge, they do review the tape before removing it, locking it and storing it.

Jim OMalley
December 22nd, 2005, 05:07 PM
But, one individual recorded over some good footage.

Well, in at least that one case you definitely had a break in your time code. More than likely, that's the kind of thing that's been causing your time code problem (especially since you've had multiple shooters on this project.)

Graham Bernard
December 22nd, 2005, 05:18 PM
"Stops" and then roll "forwards" create timecode breaks. Reviewing and then NOT stealing some frames of the previous capture will do it too. I just shoot. Stop. Shoot. Stop. Never ever had a timecode break using this method. Looking over my shoulder I got something in excess of 500 miniDV tapes.

Are you reviewing and then putting the same tapes back in the field?

Of course the other way - if already mentioned, apologies - is to bulk stripe all your tapes ALL of them! Then I guess you wont have breaks! But I aint doing it for you . . . ugh!

Grazie

Micky McCrea
December 22nd, 2005, 06:11 PM
"Stops" and then roll "forwards" create timecode breaks. Reviewing and then NOT stealing some frames of the previous capture will do it too. I just shoot. Stop. Shoot. Stop. Never ever had a timecode break using this method. Looking over my shoulder I got something in excess of 500 miniDV tapes.

Are you reviewing and then putting the same tapes back in the field?

Of course the other way - if already mentioned, apologies - is to bulk stripe all your tapes ALL of them! Then I guess you wont have breaks! But I aint doing it for you . . . ugh!

Grazie

Once reviewed, the tapes are locked and stored. What does "bulk stripe" mean?

Graham Bernard
December 23rd, 2005, 01:14 AM
Micky? I did a search for you on the subject.

Please note this from our own Chris Hurd on the subject:

"Considering that the camera's Rec Search + and - buttons will always insure that you have unbroken time code, I just can't see any reason to pre-stripe tapes for the XL2. In my opinion it's not worth the time required nor the wear on the tape transport mechanism and recording heads. The simple, quick employment of the Rec Search buttons means you'll never have a problem with broken time code on the XL2."

Here is the thread which contains Chris' post on - if you do a search on "stripe" or "striping tape" you will find others.

Here's the thread:
http://www.dvinfo.net/conf/showthread.php?t=49169&highlight=stripe

Grazie

Graham Bernard
December 23rd, 2005, 01:20 AM
The other thing that we need to consider is that are you referring to TC breaks OR nonconsecutive OR out of sequence TC?

Striping tape - ugh - will lay down 0>60 mins BUT any "gaps" that are unfortunately created will have this underlying BLACK out of sequence TC. Do you understand?

Grazie

Micky McCrea
December 23rd, 2005, 02:50 PM
Thanks for the replys. Based on what I understand from some of your comments, I think the problem must be that sometimes they tapes are rewound and played back in the field.

I will check that out.

Thanks again.
Micky

Graham Bernard
December 24th, 2005, 01:41 AM
Micky, " . .. I think the problem must be that sometimes they tapes are rewound and played back in the field." AND not picking some of the PENULTIMATE frames as a means to "latch" onto previous timecode. Playing stuff in the field works for me - but, I do this very VERY rarely - so this is NOT the problem. The technical problem is that timecode is NOT being made continuous. That is the "technical" problem.

IMHO, the problem is "WHY" this is being done at all? Why do your operatives feel it is necessary to do this? Are they worried they haven't got what you want? Or are they purely interested to "see" what they have shot? Is there pressure on them to ensure shots? I have suffered with all this myself. I've kinda taught myself to leave well alone - mostly! LOL!

However, I WILL do this within a controlled and controllable situation and maybe where it is needed = INTERVIEWS! Lit interviews where I can do retakes. But here again, I monitor both audio: CANS! and video: MONITOR! and get a very good realtime version of what is happening.

I guess what I'm inviting you to look at is the management of the expectations you have of those you are making responsible for getting the "shots". This is tough call. Only you and you alone will know what to do. Again, breaks in timecode has a "technical" solution.

Grazie

Micky McCrea
December 24th, 2005, 11:19 AM
Grazie,

I think that any play back in the field is attributed to the "hunter" coming out in the camera operator. Especially when bowhunting. It is so tempting to replay and try to determine where the arrow impacted. As if it would change anything.

If I understand you correctly, the time code will run continuous after replay if we start recording over a portion of tape that was previously recoded.

Thanks for the help. I think this gets me to the root of the problem. We are in a learning curve right now. Our project is to produce a hunting DVD. The editor pointed out many things for us to do to "help" him when he gets the tape. Fortunately for us we have many chances to get enough quality footage. Hopefully, we get more efficient and proficient as we go along.

Thanks again,
Micky

Graham Bernard
December 24th, 2005, 12:30 PM
" . .If I understand you correctly, the time code will run continuous after replay if we start recording over a portion of tape that was previously recoded." . . .you will get the "old" timecoded portions left behind, from striping, between the NEW events. You will NOT get the continued timecode from the NEW shoot. Just so long as you know/realise this?

Grazie

Jim OMalley
December 24th, 2005, 12:37 PM
Grazie,

If I understand you correctly, the time code will run continuous after replay if we start recording over a portion of tape that was previously recoded.


Grazie -- I think "recoded" is a typo. He may have meant "recorded." And in that case, yes Micky, the timecode will pick up from the previous shot as long as you begin recording over some of the previous footage.

Micky McCrea
December 24th, 2005, 01:58 PM
Grazie -- I think "recoded" is a typo. He may have meant "recorded." And in that case, yes Micky, the timecode will pick up from the previous shot as long as you begin recording over some of the previous footage.

You are correct, that was a typo.

Thanks,
Micky