Batch vs Manually Saving Video Files

I created a copy of the MP4 output profile and change the output codec to H.264/AVC and left the rest as default.

When I manually open up a Mpeg2 video file and save the video using the custom MP4 profile, the size is smaller then the original file size (since it's set to 70%). However if I add the video to batch manager and select the same output profile, the video size is a lot larger.

For example manually saved file size = 1,958,495 KB. Batch manager size - 4,546,829 KB

Is there something else that I'm missing or need to change?
 

hydra3333

Member
Eek, I rely heavily on non-interactive use of profiles and qsf ... looking forward to hearing the result for this one :)
 
I did an install of VRD pro 6 beta, which interfered with Pro 5 (what I've been using along with VRD 6 beta) and noticedc the same issue. I uninstalled all versions and reinstalled Pro 5 and see if if I have the same issue
 

Danr

Administrator
Staff member
Are you sure you're selecting the same profile in interactive vs. batch?

You can send us the log file(s) and we can see if there's any difference in the output profile.
 
Attached are Ver 6 log files. The First is just a manual File open, Save, select profile, process. The Batch_NoQS - is using batch manager, selecting the profile and Quick Stream Fix Not checked. The Final is the same as Batch - No QS, except QS Stream fix is checked.

When comparing file sizes, The Manual Save and Batch/No Quick Stream Fixed is the same. However if I enable QS Fix in Batch, the file size is 2.5x the size (1,999,149 KB vs 4,636,887 KB)
 

Attachments

Dan203

Senior Developer
Staff member
Attached are Ver 6 log files. The First is just a manual File open, Save, select profile, process. The Batch_NoQS - is using batch manager, selecting the profile and Quick Stream Fix Not checked. The Final is the same as Batch - No QS, except QS Stream fix is checked.

When comparing file sizes, The Manual Save and Batch/No Quick Stream Fixed is the same. However if I enable QS Fix in Batch, the file size is 2.5x the size (1,999,149 KB vs 4,636,887 KB)
That's too be expected. When you check QSF the automatic bitrate modes don't work. When we open a file in QSF mode we assume it's damaged, so we do not use our typical technique to determine the file duration. Without the duration we have no way of calculating the average bitrate of the file. As such Quality Factor and Target File Size do not work. Which means the profile falls back to the Bitrate Preset mode. If you don't manually set those bitrates then it uses the defaults which are set a little conservatively to ensure quality output.

If you want to use QSF and recode at the same time it's best to just set the profile to Force Recode and set the bitrates manually. Alternatively you can QSF to a file of like type first, which will be fast, then recode the fixed file using the regular mode without the QSF check.
 

hydra3333

Member
Ah.
Thank you.
Since my workflow QSF's everything, I'll need to check and change my workflow to
you can (a) QSF to a file of like type first, which will be fast, then (b) recode the fixed file using the regular mode without the QSF check.
 

Danr

Administrator
Staff member
Are you finding the behavior any different from Version 5 or Pro V5?
 
To be clear, I was testing the TV suite version of v6, along with using V5 pro (772a). If I checked the QSF boolean in batch on Pro 5, and using an H.264 Mp4 output, the new file would be smaller then the original file.

When I installed Pro Beta 6 (which won't run with Pro Beta 5, but Pro Beta 5 is still in the start menu), is when I noticed if I checked the QSF fix in batch, the output file size will be larger then the input.

I tried uninstalling all instances of Pro and installing Ver 5 pro back to see if it would go back to what I originally was seeing (smaller file size), but the output was still a larger file size

To make sure I wasn't going crazy, I installed TVS Ver 5 on another computer and using the same file, I checked the QSF in boolean and the output file was smaller.

Let me try running a test doing the following:

1) Convert Same File using H.264 MP4 profile
2) Convert in Batch
3) QSF boolean checked

Using TVS 5, Pro 6 Beta, TVS 6 Beta and getting the log file for each run
 
Top Bottom