PDA

View Full Version : MeGUI: Filename after audio encode still has old/wrong bitrate (192kbps)


JakFrost
11th September 2008, 22:15
Just a question about asthetics of MeGUI 0.3.0.2008 and the filenames it creates after encoding jobs.

DGindex is the app that actually puts in the details and the bitrate about the file into the filename. That is a great feature. After DGindex demuxes the AC-3 audio track into the file below.

VTS_01_0 T80 2_0ch 192Kbps DELAY 0ms.ac3


Audio
Format : AC-3
Format/Info : Audio Coding 3
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : L R
Sampling rate : 48.0 KHz

Then you select it for encoding using "Nero AAC: NDAAC-HE+PS-64Kbps" you get the filename below.

VTS_01_0 T80 2_0ch 192Kbps DELAY 0ms.mp4


Audio
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Format settings, SBR : Yes
Format settings, PS : Yes
Codec ID : 40
Duration : 2mn 51s
Bit rate mode : Variable
Bit rate : 63.7 Kbps
Maximum bit rate : 71.2 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Resolution : 16 bits
Stream size : 1.30 MiB (99%)

So why doesn't the MeGUI change the filename to indicate that the new file is actually 64Kbps into a filename like the example below?

VTS_01_0 T80 2_0ch 64Kbps DELAY 0ms.mp4

Won't the wrong bitrate in the filename throw off MeGUI when it does the muxing into the final container format since the audio file selected has the wrong bitrate?

Also, wouldn't it be a nice asthetic change for MeGUI to change the bitrate in the filename to the correct one?

Avenger007
12th September 2008, 01:36
I'm guessing that keeping the file name the same is intentional (eg. DVDs can have different audio tracks so keeping the source name helps). The file name has nothing to do with muxing.
Most people who want high quality audio would use VBR mode (q=0.xx) instead.
Do you expect MeGUI to read the bitrate from the output file and then rename the file with the new bitrate?

Kurtnoise
12th September 2008, 08:56
this can be done by parsing the preset itself I think...:) reading the bitrate from the output won't be necessary in this case.

JakFrost
13th September 2008, 19:49
this can be done by parsing the preset itself I think...:) reading the bitrate from the output won't be necessary in this case.

Yes, that is exactly what I thought could be done, look at the preset and change the filename bitrate to the ABR/CBR bitrate chosen on the slider or for VBR just put in the q=0.? value.

The idea for this came when I was queuing up a few encodings of the same audio source to different audio profiles to proof-listen and would get errors when the filenames would conflict because I would forget to change the filename before I queued it up.