Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Tom Schenk <tschenk@te...> - 2007-11-11 19:05:29
Before I dig too deeply into the script code, I was wondering if anyone
else has experienced problems converting MKV files with the 0.36 beta.
As far as I can tell at this point, it is mainly with files where the
MKV container contains multiple audio tracks and a video track with no
sound. The two audio tracks are processed ok, but when the script goes
to process the video track, it doesn't recognize that there is no audio
and it creates a mangled transcode command line that fails because there
are missing audio parameters. Here is an example of what I am talking
Running: transcode -H0 -i
"/opt/encoding/Classmates_1/Classmates_01-v1.avi" -x mplayer="-mc
0",mplayer -f 29.970 -g 720x480 -n 0x1 -e ,16, -y ffmpeg -F mpeg2 -Z
352x240 --export_asr 2 -j -18,-12,-18,-12 -D0 -N 0x2000 -E 48000,16,2
-b 384 -m "/opt/encoding/Classmates_1/Classmates_01-v1.ac3" -o
"/opt/encoding/Classmates_1/Classmates_01-v1" -w 2500 ...
Error: Video encoding failed for
"/opt/encoding/Classmates_1/Classmates_01-v1.m2v", file not successfully
As you can see, it is trying to seperate the video and audio from the
AVI file, but if you notice, the -e argument is ,16,. It is missing two
values, which is why it fails. Since the AVI container doesn't have an
audio track, the script fails to get the other two parameters, but
doesn't realize it and creates the malformed transcode command.
What puzzles me is that the script works for most MKV files, but on
some, especially those encoded in H264 format, it bombs.
Has anyone else seen this problem and have a workaround or any
suggestions on how to make the script realize that there is no audio
track in the avi file extracted from the MKV file? If not, I will look
into the code myself and see if I can fix it. I am thinking that if I
checked the SRC_AUDIO_RATE and SRC_AUDIO_CHANS and both are zero length
strings, then make sure that transcode command line generated doesn't
even try to extract audio from the avi file, but I'm not sure how
difficult that would be.
On a totally seperate note, has anyone ever considered rewriting these
scripts in Perl or Python?