New issue 82 by bon...@gmail.com: Problem related to file extensions when
creating IMX50 and IMX30 files
http://code.google.com/p/ffmbc/issues/detail?id=82
Hi, we've found a problem related to file extensions when creating IMX50
and IMX30 files.
If we transcode to a file with a .mov file extension (as follows) it seems
to produce a valid IMX30 file.
ffmbc -i imx50.mov -target imx30 -ac 2 -map_audio_channel 0:1:0:0:1:0
-map_audio_channel 0:1:1:0:1:1 -f mov -y DMIEA-1001-imx30.mov
We check this by running mediainfo on the output file and check that its
Format_Commercial_IfAny is set to IMX 30
However, if we transcode as follows the output file has different video
codec information as output by MediaInfo.
ffmbc -i imx50.mov -target imx30 -ac 2 -map_audio_channel 0:1:0:0:1:0
-map_audio_channel 0:1:1:0:1:1 -f mov -y imx30.working
MediaiInfo shows that no Format_Commercial_IfAny field has been set.
Both files play back fine but we rely on the output of MediaInfo for our
workflow.
We can change our code to write to a .mov file extension but ideally we'd
like FFmbc to not care about the output file extension when we specify -f
mov.
This is with FFmbc version 0.7-rc5.
Thanks, Darren.
Comment #1 on issue 82 by baptiste...@gmail.com: Problem related to file
extensions when creating IMX50 and IMX30 files
http://code.google.com/p/ffmbc/issues/detail?id=82
Sorry, the target code is based on file extension currently.
Besides, you are creating a mov file here, why not use the correct file
extension ?
Yeah, we've fixed our code now.
Just figured I should raise a bug anyway in case it was an easy fix.
Thanks.