Why a black frame at the end of MOV files?

jmrobbins42 wrote on 7/3/2011, 10:23 AM

When I import any MOV file from my camera into MEP17, it places a black frame at the end. No other

editor I have does this. I thought that it was my camera but after test found it was not. It causes the extra step

of having to trim each file I import.

 

Any ideas or has anyone else seen this?

Comments

jmrobbins42 wrote on 7/4/2011, 8:51 AM

I see on some other forums that this is not a new thing. I take it that it was in earlier versions also. My question

is with so many of the new cameras producing MOV file output, how can this problem be ignored? My camera

is a Canon and outputs 1920x1080 24P.

johnebaker wrote on 7/4/2011, 12:08 PM

Hi

This problem usually occurs when you are not creating a new frametable on import, check that you have the following setting checked

John

Last changed by johnebaker on 7/4/2011, 12:08 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

jmrobbins42 wrote on 7/4/2011, 1:07 PM

Thanks for the sugestion.

 I set it and re-booted but I still get the extra frame. I don't have any MOV files with other frame rates. I wonder if it has anything to do with it. The input video is HD @ 24Frames Progressive, my project output is set for AVCHD . I am very pleased with MEP17 and it's AVCHD disc output. It's the only editor Ihave seen that allows 2 pass encoding and various bit rates. The AVID Studio I had purchased gave just a few pre-sets and crashed constantly. The disc authoring is better than most also.

johnebaker wrote on 7/4/2011, 4:03 PM

Is it always 1 extra frame?  I think it may be that MEP thinks the frame rate is 25 fps and is adding one black frame to the 24 from the camera. 

What is the camera and can it record at other frame rates?

Use GSpot or MediaInfo to analyse one of the original files to see what information MEP is getting. 

Also is MEP upto date with the latest patch?

John

Last changed by johnebaker on 7/4/2011, 4:03 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

jmrobbins42 wrote on 7/4/2011, 7:48 PM

Yes, it's always 1 frame added. The file is correctly identified by MEP17 as 24frames. The 25 fps makes sense. Yes, the

camera (Canon ELPH 300 HS) has a mode which I will try. Program

reports latest version and is set for NTSC specs.

jmrobbins42 wrote on 7/5/2011, 11:17 AM

John, I tried importing a and NO black frame. I think we can conclude that it errors

on 24FPS and thinks it is PAL 25FPS. It correctly ID's the rate but must ignore it.

jmrobbins42 wrote on 7/9/2011, 9:12 AM

I sent this problem and a clip to Tech Support several days ago but haven't heard from them. I

hope it can be resolved.

jmrobbins42 wrote on 7/16/2011, 9:22 AM

Tech Support said change the settings. The file settings are 1920x1080x23.97 for movie, and 1920x1080x29.97

for project. Sorry, it is always producing 1 extra frame at the end. I guess this will be a problem always since Tech

Support doesn't see it.