I added a wiki page with commandlines to encode IMX 50 or 30
in either MXF or MOV.
http://code.google.com/p/ffmbc/wiki/IMXD10Encoding
It also explains how to add more audio channels since MXF typically only
accepts 4 or 8 channels.
--
Baptiste COUDURIER
Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
FFmpeg maintainer http://www.ffmpeg.org
Thank you!
Always good to have usage examples.
J.Reykdal
> Guys,
>
> I added a wiki page with commandlines to encode IMX 50 or 30
> in either MXF or MOV.
>
> http://code.google.com/p/ffmbc/wiki/IMXD10Encoding
>
> It also explains how to add more audio channels since MXF typically only
> accepts 4 or 8 channels.
Baptiste,
Small correction on the text in the wiki:
The XDcam transfer tool does accept any amount of channels.
And the exporter app (that wants QT on input) will add as many channels as
the codec requests.
However, i'm not sure about other equipment, and i know for sure
broadcasters over here will not accept anything less than 4 channels.
(Typically with 3/4 being empty...)
What i don't get is the audio mapping in your example.
You suggest one can map a stereo input to dual mono, but that seems not to
work...
Bouke
Nope, it won't play the sound if channels are < 4. It will accept it,
but you won't here any sound when playing it.
> [...]
>
> What i don't get is the audio mapping in your example.
> You suggest one can map a stereo input to dual mono, but that seems not to
> work...
Humm, yes it's not clear enough, you must map the channels of the input
as well.
I updated the wiki page.
Btw any help is welcome on the wiki.
> On 2/18/11 2:13 AM, Bouke (VideoToolShed) wrote:
>>
>> ----- Original Message -----
>> From: "Baptiste Coudurier" <baptiste....@gmail.com>
>> To: <ffmbc-...@googlegroups.com>
>> Cc: <ffmb...@googlegroups.com>
>> Sent: Thursday, February 17, 2011 11:36 PM
>> Subject: [ffmbc-discuss] How to encode IMX/D-10 using FFmbc
>>
>>
>>> Guys,
>>>
>>> I added a wiki page with commandlines to encode IMX 50 or 30
>>> in either MXF or MOV.
>>>
>>> http://code.google.com/p/ffmbc/wiki/IMXD10Encoding
>>>
>>> It also explains how to add more audio channels since MXF typically only
>>> accepts 4 or 8 channels.
>>
>> Baptiste,
>> Small correction on the text in the wiki:
>> The XDcam transfer tool does accept any amount of channels.
>
> Nope, it won't play the sound if channels are < 4. It will accept it,
> but you won't here any sound when playing it.
My bad, just tested, this is true for SD.
HD however plays here with just 2 channels. (on Mac)
>> [...]
>>
>> What i don't get is the audio mapping in your example.
>> You suggest one can map a stereo input to dual mono, but that seems not
>> to
>> work...
>
> Humm, yes it's not clear enough, you must map the channels of the input
> as well.
I'll toy with it a bit more when i have time, first jolly good fun with
Canon MXF...
Bouke
I updated the wiki to reflect new rc2 feature.
It is now much more easier to encode imx:
ffmbc -i < file > -target imx30 < file.mxf | file.mov >
ffmbc -i < file > -target imx50 < file.mxf | file.mov >
Well, i would help if i could, but i'm not into this stuff so deep...
And that brings me to another question, could you expand the Wiki with XDcam
HD?
Have had good luck with 50 Mbits @ 25 fps, but no idea how to do it for
23.976 nor 29.97.
(Bufsize probably should be different, perhaps other stuff as well)
And, is there a way to set the TC to NDF? How about Reelname? (FFmbc reads
it, so i would think there 'should' be a way to set it.
Something else (not a feature request, but you might be interested), FCP
flags the TC tracks in QT with user data to distinguish Normal, Aux1 and
Aux2.
(but besides FCP and a few things i've made, no other app uses it...)
Bouke
NDF, just use -timecode "00:00:00:00" for DF use "00:00:00;00"
Notice the ';'
-metadata reel_name="...."
--J.Reykdal