Incorrect segment size

roux · 31st October 2005, 18:29

Hi,

I'm dealing with a very strange problem. I have encoded the same segment first with HC and then with Procoder2 using RME. I wanted to compare which looked better at a noisy source and high compression rate.

The size of this segment is with HC 130MB and with Procoder only 40MB

I used excact the same settings (undot filter) only a different encoder.

At first i thougt it had something to do with RME but then i encoded the segment using dvd-rb only and the result was this time 69,59MB (also with the undot filter).

RME shows me the following info about this segment:

Code:

Total size: 82,86MB
Video size: 67,97MB
Audio/sub size: 14,89MB
Duration: Aprox. 00:02:37
Bitrate VBR 11127

Looking at the original segment size i would say the HC segment size (130MB) is to big and the procoder size (40MB) is correct. And the size which dvd-rb created is the same as the original...?

I also noticed the bitrate value is very high, maybe that's causing problems?

jdobbs · 31st October 2005, 20:29

Are you saying the bitrate reported in DVD-RB is reported differently? Ther reason I ask is because DVD-RB will compute the bitrate exactly the same way regardless of which encoder you choose... you'd have to be changing something between runs to get two different bitrates.

roux · 31st October 2005, 22:43

No dvd-rb gives me the same bitrate value's after the prepare phase of each run. Only the segment differs in size between the two runs.

I've run bitrateview on both segments created with RME:

Segment encoded with HC: Peak 7148, Avarage 6630
Segment encoded with Procoder: Peak 3306, Avarage 2038

How is this possible?

jdobbs · 31st October 2005, 23:11

You aren't running one pass encoding are you... that can make a huge swing in bitrates between segments.

roux · 31st October 2005, 23:39

No i don’t, i run at 2 passes but i think i have found the problem.

As i said the sizes of the same segment are very different, but this only happens with RME. In my first post i said the filesize with dvd-rb was 69,59MB using procoder. I forgot to run the test with HC in dvd-rb, after running the size was also 69,59MB.

So my conclusion is there’s something wrong with bitrate settings in RME. Here are the results just for clarification:

Code:

RME
Segment encoded with HC: Peak 7148, Avarage 6630, Size 130MB
Segment encoded with Procoder: Peak 3306, Avarage 2038, Size 40MB

REBUILDER
Segment encoded with HC: Peak 5840, Avarage 3546, Size 69,59MB
Segment encoded with Procoder: Peak 5597, Avarage 3546, Size 69,59MB

31st October 2005, 18:29	#1 \| Link
roux Registered User Join Date: Nov 2004 Posts: 93	Incorrect segment size Hi, I'm dealing with a very strange problem. I have encoded the same segment first with HC and then with Procoder2 using RME. I wanted to compare which looked better at a noisy source and high compression rate. The size of this segment is with HC 130MB and with Procoder only 40MB I used excact the same settings (undot filter) only a different encoder. At first i thougt it had something to do with RME but then i encoded the segment using dvd-rb only and the result was this time 69,59MB (also with the undot filter). RME shows me the following info about this segment: Code: Total size: 82,86MB Video size: 67,97MB Audio/sub size: 14,89MB Duration: Aprox. 00:02:37 Bitrate VBR 11127 Looking at the original segment size i would say the HC segment size (130MB) is to big and the procoder size (40MB) is correct. And the size which dvd-rb created is the same as the original...? I also noticed the bitrate value is very high, maybe that's causing problems?

31st October 2005, 20:29	#2 \| Link
jdobbs Moderator Join Date: Oct 2001 Posts: 20,976	Are you saying the bitrate reported in DVD-RB is reported differently? Ther reason I ask is because DVD-RB will compute the bitrate exactly the same way regardless of which encoder you choose... you'd have to be changing something between runs to get two different bitrates. __________________ Help with development of new apps: Donations. Website: www.jdobbs.net

31st October 2005, 23:11	#4 \| Link
jdobbs Moderator Join Date: Oct 2001 Posts: 20,976	You aren't running one pass encoding are you... that can make a huge swing in bitrates between segments. __________________ Help with development of new apps: Donations. Website: www.jdobbs.net

31st October 2005, 23:39	#5 \| Link
roux Registered User Join Date: Nov 2004 Posts: 93	No i don’t, i run at 2 passes but i think i have found the problem. As i said the sizes of the same segment are very different, but this only happens with RME. In my first post i said the filesize with dvd-rb was 69,59MB using procoder. I forgot to run the test with HC in dvd-rb, after running the size was also 69,59MB. So my conclusion is there’s something wrong with bitrate settings in RME. Here are the results just for clarification: Code: RME Segment encoded with HC: Peak 7148, Avarage 6630, Size 130MB Segment encoded with Procoder: Peak 3306, Avarage 2038, Size 40MB REBUILDER Segment encoded with HC: Peak 5840, Avarage 3546, Size 69,59MB Segment encoded with Procoder: Peak 5597, Avarage 3546, Size 69,59MB Last edited by roux; 31st October 2005 at 23:42.

31st October 2005, 22:43	#3 \| Link
roux Registered User Join Date: Nov 2004 Posts: 93	No dvd-rb gives me the same bitrate value's after the prepare phase of each run. Only the segment differs in size between the two runs. I've run bitrateview on both segments created with RME: Segment encoded with HC: Peak 7148, Avarage 6630 Segment encoded with Procoder: Peak 3306, Avarage 2038 How is this possible?