View Single Post
Old 9th September 2017, 15:21   #5779  |  Link
j8ee
Registered User
 
j8ee's Avatar
 
Join Date: Aug 2002
Location: Sweden
Posts: 65
There's an issue with the generated .avs file for audio when indexing a video with 6 channel aac audio. In the scripts it says

# detected channels: 2 channels
# detected channel positions: 3/2/0.1

regardless of ffmsindex or l-smash being used. MeGUI throw warnings when encoding:

--[Warning] [2017-09-08 17:00:32] Channel count mismatch! The input file is reporting 2 channels and the AviSynth script is reporting 6 channels
--[Warning] [2017-09-08 17:00:32] Ignoring downmix because of the channel count mismatch

and the resulting encode ends up being multi-channel. Trying to encode an mp3 fails with the error message "Unsupported number of channels: 6"

Manually changing the .avs files to

# detected channels: 6 channels

makes everything work fine.

Using MeGUI 2768 development server

(By the way, is there an easy way of verifying that video/audio files actually are multi-channel without having any matching hardware for playback? A longer-than-normal google session only came up with tools and ways for checking playback and hardware, nothing for verifying the files.

Maybe not on topic, but I'm also curious of the big difference in bitrate for the resulting audio file, depending of the l-smash or ffms indexer being used, and other decoding methods. With the l-smash indexer the encoded 2-channel audio had 51 kbps, and with ffms it had 40 kbps. Just encoding the extracted aac file directly in MeGUI resulted in a 2-channel file with 66 kbps, and encoding in foobar2000 with it's downmix filter produced a file with 42 kbps. Encoding settings being the same of course. Is this all good and perfectly normal, especially the difference between l-smash and ffms indexers?)

Last edited by j8ee; 9th September 2017 at 15:30.
j8ee is offline   Reply With Quote