Missing space (frames) between "Master" and "Sub" clips? at DVinfo.net

Jamon Lewis · April 9th, 2007, 10:15 PM

I have a CitDisk HDV 80 gig drive.There's a 2GB (or something) limit and a new clip is made, but the clips after the original are missing frames (about 3-4 or maybe more frames between clips) and don't piece together smoothly.Any insight, anyone. I know this isn't how this thing was designed to work..

Lauri Kettunen · April 10th, 2007, 08:10 AM

Have not noticed this problem with my CitiDisk, but not sure that I've ever checked the sequental files so closely. However, one thing which comes into mind is the edit software. Are you sure the frames are really missing or is it the software which is not able to show the first frames?

The reason to ask is, at some point I did try to import the m2t files (generated by XL H1) directly to Premiere, and observed that Premiere was not able to show the first frame(s). [BTW, the same happened also with the files generated by the Firestore device.] My standard approach is to convert the m2t files immediately to Cineform avi-files, and doing so I've never experienced problems with the first frames.

Jamon Lewis · April 10th, 2007, 08:34 AM

Thanks for the reply. I Use Final Cut Pro. I went to MPEG Stream Clip and played the actual M2T file and it seems to be the same as the Quicktime file that i converted and used in FCP (to the best of my knowledge)... simply put what happens is when i line the clips up, end to beginning in the sequence of the event, there is a jump as if there are a few frames lost as a result of starting a new clip. The master and subsequent clip should go together seamlessly correct?

John Mitchell · April 26th, 2007, 01:56 AM

Try shooting a stopwatch to see if you can get a more exact handle on the problem. With NTSC every frame will equal .033 second roughly (much easier in PAL :). If you have an NLE which can generate burnt in code (or a deck with an LCD counter) you could try recording the screen to get an exact frame counter.

April 9th, 2007, 10:15 PM	#1
Jamon Lewis Regular Crew Join Date: Jul 2006 Location: NY NY USA Posts: 95	Missing space (frames) between "Master" and "Sub" clips? I have a CitDisk HDV 80 gig drive.There's a 2GB (or something) limit and a new clip is made, but the clips after the original are missing frames (about 3-4 or maybe more frames between clips) and don't piece together smoothly.Any insight, anyone. I know this isn't how this thing was designed to work..

April 10th, 2007, 08:10 AM	#2
Lauri Kettunen Major Player Join Date: Aug 2004 Location: Kangasala, Finland Posts: 445	Have not noticed this problem with my CitiDisk, but not sure that I've ever checked the sequental files so closely. However, one thing which comes into mind is the edit software. Are you sure the frames are really missing or is it the software which is not able to show the first frames? The reason to ask is, at some point I did try to import the m2t files (generated by XL H1) directly to Premiere, and observed that Premiere was not able to show the first frame(s). [BTW, the same happened also with the files generated by the Firestore device.] My standard approach is to convert the m2t files immediately to Cineform avi-files, and doing so I've never experienced problems with the first frames.

April 10th, 2007, 08:34 AM	#3
Jamon Lewis Regular Crew Join Date: Jul 2006 Location: NY NY USA Posts: 95	Thanks for the reply. I Use Final Cut Pro. I went to MPEG Stream Clip and played the actual M2T file and it seems to be the same as the Quicktime file that i converted and used in FCP (to the best of my knowledge)... simply put what happens is when i line the clips up, end to beginning in the sequence of the event, there is a jump as if there are a few frames lost as a result of starting a new clip. The master and subsequent clip should go together seamlessly correct?

April 26th, 2007, 01:56 AM	#4
John Mitchell Contributor Join Date: Jul 2005 Location: Sydney Australia Posts: 873	Try shooting a stopwatch to see if you can get a more exact handle on the problem. With NTSC every frame will equal .033 second roughly (much easier in PAL :). If you have an NLE which can generate burnt in code (or a deck with an LCD counter) you could try recording the screen to get an exact frame counter.