Hi all,
is there any way to get a Win32 compiled version of the last build? I mean "FFmbc-0.6-rc3"... I'd like to use the target "xdcamhd422"...
Alternatively could I use previous build expanding commandline condensed in that target?
Last... Is there any easy way to compile your own windows version starting from tar.gz file?
Thank you all
+ Reply to Thread
Results 1 to 12 of 12
-
-
not sure how to compile it , but you could use the commandline for 0.5
http://www.itbroadcastanddigitalcinema.com/ffmpeg_howto.html#Encoding_XDCAM-HD-50_FCP
it's mov wrapped intended for fcp , but you should be able to just change the last part (-f mov output.mov) to (output.mp4) -
I removed "-f mov" and set "export.mxf"...
It returns error... like "Unable to parse option value "'1*QP2LAMBDA'" ....invalid for option 'lmin'
I removed the '...' around 1*QP...MDA -> now goes ok for MOV wrapper. No way for MXF.... "only 48Khz is implemented"...
So I added "-ar 48000" but it returns "track 1: could not find essence container ul, codec not currently supported in container"
...anything wrong with "-acodec pcm_s16be"?
EDIT: with "-an" everything ok... obviously without audio track...Last edited by elmuz; 26th Apr 2011 at 09:26.
-
why do you need xdcamhd ?
you could probably fudge some of the parameters (won't exactly match) , or use another format -
...we wanto to migrate to MXF. I suggested IMX for SD content, while XDCAM HD 422 for HD content. Adobe CS5 can handle them easily, but there are some little steps in workflow using ffmpeg-based script...
Would be probably enough looking for the right audio specifications...
I'd like to use parameter 'target' in ffmbc 0.6... -
don't rejoice yet... it might not be completely compatible
xdcamhd 422 (straight from the camera) uses big endian
so import some test footage and see if your NLE "sees" it properly
the ffmbc 0.6 is still in beta, so maybe it will be released soon (or maybe someone can compile it for you) -
There's a stripped-down download of 0.6 rc3 (last post in the thread below). It's only libav but that should be enough. This one accepts "-target xdcamhd422". Perhaps worth while to compare?
http://code.google.com/p/ffmbc/issues/detail?id=30 -
I tried both methods and they seem very good...
I just tested importing them in Premiere and it is ok...
Only one thing yet... on the wiki they say... Note: XDCAM transfer supports no less than 2 mono tracks channels. Use -newaudio and -map_audio_channel.
Is there anything wrong with only one stereo track (PCM, 2 channels, 48kHz, 24bit)? -
I looked at the specs of a camera and a deck ...
http://pro.sony.com/bbsc/ssr/cat-broadcastcameras/cat-xdcam/product-PDWF335L/
http://pro.sony.com/bbsc/ssr/micro-xdcam/cat-videorecorders/product-PDWF1600/
I see only support for separate mono tracks up to eight. The camera audio seems to be ony 16 bit, the deck also supports 24 bit.
I guess that's why they wrote "Use -newaudio and -map_audio_channel". You probably have to encode L and R into two separate mono streams?
Is there anything wrong with only one stereo track (PCM, 2 channels, 48kHz, 24bit)Last edited by Chris K; 26th Apr 2011 at 14:06. Reason: addition
-
I couldn't find that thing of mono tracks...
If Premiere accepts it and your goal is to finally render to something other than XDCAM, it shouldn't be a problem.
Very strange, any MXF/XDCAM HD 422 expert?
Similar Threads
-
Creating movie (mov) reference files with ffmpeg or ffmbc
By musicman in forum Video ConversionReplies: 3Last Post: 6th Jul 2012, 18:40 -
FFmbc 0.7 for Windows
By Chris K in forum Video ConversionReplies: 0Last Post: 30th Sep 2011, 14:28 -
FFmpeg / FFmbc ---> 8 Mono track to 1 Stereo
By elmuz in forum Video ConversionReplies: 2Last Post: 13th Jun 2011, 06:06