Frame accurate H264 editing

relaxvideo wrote on 3/10/2016, 8:00 AM
I have an MP4 file which was created by Dvdfab.
My problem is that i like to cut scenes and make a shorter version of this video.
But at cuts i often have bad frames in rendered file. Seems like Vegas can only cut at I frames correctly and GOP size in the mp4 file is too long.
Is this true? How can i solve this?

I understand, i cannot have smart rendering, i only want frame accurate re-rendered file.

Comments

wwaag wrote on 3/10/2016, 9:43 AM
For jobs like this, Vegas is not your best choice. Try something like VideoRedo TV Suite or TMPGEnc's MPEG Smart Renderer. You can do frame accurate cuts plus they both smart-render. Lots faster and no loss of quality due to re-render. Having said that, there is no reason that Vegas will not do frame accurate cuts AFAIK and there is no limitation that cuts must be on an I frame. Don't know about GOP size. Most likely, it's an issue with the file that is produced by Dvdfab. Both VideoReDo and Smart Renderer have free trials.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

relaxvideo wrote on 3/10/2016, 9:49 AM
thanks, but i like to stay on vegas,
because files are full sbs 3d files (huge resolution), sometimes i have to make some levels, color correction (but only one side), etc..

#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas22 latest

PeterDuke wrote on 3/10/2016, 8:36 PM
VideoReDo is more than a smart trimmer; it also tidies up things that may cause the video to not play well on some players.

Don't close your eyes to the benefits of more than one tool. Good tools have their good and bad points and selecting the best one for the task gives the best end product.
musicvid10 wrote on 3/10/2016, 9:48 PM
@wwaag
@PeterDuke

+2

The $26 upgrade supposedly expires tomorrow.



relaxvideo wrote on 3/11/2016, 12:10 AM
Peterduke:
are you saying that i should open my video in VideoReDo and save (without recompress), and then i can use correctly in Vegas?

#1 Ryzen 5-1600, 16GB DDR4, Nvidia 1660 Super, M2-SSD, Acer freesync monitor

#2 i7-2600, 32GB, Nvidia 1660Ti, SSD for system, M2-SSD for work, 2x4TB hdd, LG 3D monitor +3DTV +3D projectors

Win10 x64, Vegas22 latest

NickHope wrote on 3/11/2016, 12:56 AM
Vegas makes a pig's ear of decoding some long-GOP formats, typically with extra frames or repeated frames outside of the initial and final I-frames. You can sometimes cater for this by using the Trim Captured Clips script after the rendered files are put back on the Vegas timeline. You can also compensate by rendering the file slightly longer then trimming.

I wish SCS would update their decoders to fix these errors.

VideoRedo didn't work with my UHD GH4 footage.
PeterDuke wrote on 3/11/2016, 6:02 PM
relaxvideo

I can't say for sure since I have not tried your video. I suggest you try it out. I think there is a 15 min video length limit if you don't request a trial key. After that there is only the trial period time limit.
PeterDuke wrote on 3/11/2016, 8:10 PM
Nick

I already noticed that, and took it up with VideoReDo support. By default, VRD is limited to 3840x2160 output. To smart edit 4096x2160 you have to set two things.

1. Click on the Tools menu. Shift click on Options. Under item 55, set "Allow UHD 4096 output" to True.

2. Edit your video. Click on Save Video > Profile Options. In the Video section, set max. resolution to 4096x2160.

Step one is sticky but step 2 is not.

I requested that the default maximum might be 4096, so maybe in the fullness of time (as Sir Humphrey used to say) this will be fixed.
NickHope wrote on 3/11/2016, 10:25 PM
Thanks Peter but my problems were with 3840x2160 GH4 MP4/LPCM footage. In my first test, it crashed during the render. I did then manage to render 2 files, but they do not decode properly in VP13. Much of them appear as green thumbnails on the timeline, they don't play back properly, and the end is not quantized.
PeterDuke wrote on 3/12/2016, 8:12 PM
The GH4 samples I have I downloaded from the internet. They were short and may have been cut with some utility. Eight players plus File Explorer, Vegas and Mediainfo all thought they were 2 to 3 times longer than they really were. VideoReDo alone knew the correct length.

After re-doing (hence the name) in VidoReDo, the file sizes were slightly smaller, since the time code stream and the time code within the video stream were removed (according to Mediainfo). The players now played them properly, but Vegas would no longer accept them on the timeline.