PDA

View Full Version : Audio Volume too low - Ignoring % Setting


MrZebra
03-04-2007, 10:39 PM
Hi, I just found out that Videora now has newer version out so I downloaded it and started playing with it.

The Video Quality has really improved a lot, it's amazing how at 640x480/352 I get really great results even with the bitrate still at 768kbps.

My only problem seems to be with the audio, as everyone probably knows, DVDs are notorious for having really low audio volume so to make them usable on an iPod, you have to increase the volume. Using Videora 0.91, I was encoding most of my movies using a boost factor between 200% and 300% (Depends on movies, some movies mainly concerts had loud enough audio that I have to use 100 for those)

Looks like the Volume % option appear to be ignored in v2.05, I turned on the debug console and I can see the -vol 250 param being passed and I see no error/warning messages pertaining to the fact that I used an invalid value (Maybe there is a limit?)

Any workaround to this bug? Volume boost worked fine in 0.91.

MrZebra
03-05-2007, 06:12 AM
I figured it out on my own!

I still had v0.91 installed so I ran the video through it using one of my 250% boosted profile with console enabled and saw the param passed was -vol 640. So it looks like ffmpeg is expecting the volume param not in % but in "Byte Percent" where 256 = 100%. Which explains why -vol 250 did nothing since -vol 256 = 100%.

So I changed my 250% profile in v2.05 to put 640 in the Volume % field, ran an encode and perfect, my volume was boosted at 250% like I wanted.

So there you go, maybe this should get fix in the next release, either state in the Audio Properties that the Volume field is in pertwofiftysix instead of percent or just multiply that value by 2.56 so that the resulting files get boosted by the factor the user asks for.

Red Kawa
03-05-2007, 08:26 AM
Thanks for reporting this issue. You are correct, we should be multipling the value by 2.56 before putting it on the command line. This is bug which we will fix in the next release.

Red Kawa
03-05-2007, 04:33 PM
This bug has been fixed in version 2.06.