Log in

View Full Version : Super 8 backup glitch.


HandiA
17th January 2012, 06:14
When backing up Super 8, using full backup, BD25, with "quicker encode for extras", the main movie was compressed from 30gb to about 6gb. The picture was not clear, less than DVD quality. Also, the extra files were not much different in size from the original. In fact, the next 4 files in size were bigger on the backup than on the original.
Ran program again with the "quicker encode for extras" unchecked.
This time the main movie file came to about 13Gb with much better quality.

The option seemed to have a reverse effect unless I misunderstand the purpose of the option, which is to give more space to the main movie for better quality.

I don't know if this is a program bug.

Ch3vr0n
17th January 2012, 15:05
how much audio streams are present in the original and how many are you keeping?

SquallMX
17th January 2012, 17:26
When backing up Super 8, using full backup, BD25, with "quicker encode for extras", the main movie was compressed from 30gb to about 6gb. The picture was not clear, less than DVD quality. Also, the extra files were not much different in size from the original. In fact, the next 4 files in size were bigger on the backup than on the original.
Ran program again with the "quicker encode for extras" unchecked.
This time the main movie file came to about 13Gb with much better quality.

The option seemed to have a reverse effect unless I misunderstand the purpose of the option, which is to give more space to the main movie for better quality.

I don't know if this is a program bug.

Is not a bug per se, but by its nature "Quicker encode for Extras" (crf encoding) may occasionally create files bigger than the original ones, in the case of Super 8, most extras have a lot of fake grain, so they're perfect candidates for this issue.

jdobbs
17th January 2012, 17:32
The purpose of "quick encode for extras" is to save time. But a CRF encode's size is unpredictable. You can always change the CRF default used in quick encodes -- see HIDDENOPTS.TXT. My inclination is to get rid of that option -- it's benefit is marginal at best.

Sharc
20th January 2012, 20:48
The purpose of "quick encode for extras" is to save time. But a CRF encode's size is unpredictable. You can always change the CRF default used in quick encodes -- see HIDDENOPTS.TXT. My inclination is to get rid of that option -- it's benefit is marginal at best.
Please keep this option alive :o

jdobbs
21st January 2012, 01:18
Please keep this option alive :o Maybe I'll just make it a hidden options then. I get too many complaints about sizing from those who don't understand how CRF works.

Sharc
21st January 2012, 11:41
Maybe I'll just make it a hidden options then. I get too many complaints about sizing from those who don't understand how CRF works.
I even thought that the menus should be incuded in the "Quicker Encode for Extras" mode. I had few cases for "BD5 movie and menu" where 2-pass (or CRF predictive) shrunk the menus too much resulting in blocks and heavy GOP pulsing -- the equivalent rate factor was around 45 IIRC. Applying the "Quick" CRF would have produced bigger menu file sizes at only a slight expense of the movie bitrate, but with reasonable menu quality.
The case happened when the menu came with bloated audio and all the shrinking was applied to the video part of the menu.
But maybe this is getting too complicated ....