[Milivoj Ivkovic]

Many years later, maybe it’s still worth replying in case others stumble onto this post.

In .fcpxml files, the start, offset and duration numbers are real-time seconds (as hinted to by the “s” at the end). They are not related to framerate. You only need the framerate if you need to convert these times to a frame number or to standard timecode which uses frames.

An example from a title in a .fcpxml file:




[Milivoj Ivkovic]

Note that you can take advantage of the .csv (or json) outputs provided by ffprobe. They make parsing much easier.

For example, I use this to analyze the bitrate, saving the output into a .csv file for further parsing with Perl, Excel, a graphing tool or whatever:

ffprobe -select_streams V -show_entries frame=pict_type,pkt_size,pkt_pts_time -of csv "$INPUTFILE" > "$INPUTFILE.ffprobe.csv"

[Milivoj Ivkovic]

Has someone ever found the reasons for these weird choices in the standards? I’m curious too. Most cameras also offer recording with 1:89, probably for no other reason than it being “compatible” with that strange 2048/1080 ratio.

Is the real reason someone who made a calculation mistake, and when someone else noticed, it was already too late?

[Milivoj Ivkovic]

I just had this problem and it took me a while to find that it is some setting stored in the Timeline view settings. I don’t know how it came to that, but selecting another timeline view in the little menu at the bottom left restored the normal track order.

[Milivoj Ivkovic]

How do […] process the trans-code on all/more of my processor cores?

-threads X (where is X is the number of threads to use)

To use all available cores:
-threads 0

[Milivoj Ivkovic]

Maybe the mpeg video standard doesn’t accept 24 bit audio, which is what you had in your original. That would explain why it now works, since you also transcode the audio.

BTW, you had a “-t 360” option in your original line, for testing I guess. If you want to restrict the duration, put that option before the input file. To transcode only the first 60 seconds:

ffmbc -t 60 -i $INPUT …etc.

[Milivoj Ivkovic]

Looks like you suppressed the audio with “-an”.

You could try something like this:

ffmbc -i infile.mov -vcodec mpeg2video -b 12000k -acodec copy outfile.mpg

(I cannot test it right now, but hopefully that will be closer to what you are trying to do)

[Milivoj Ivkovic]

I would like to use FFmbc if it will be professional.

ffmbc is quite “professional”. It is it’s target audience after all. However, it is not “casual-user-friendly”. It’s main advantage – being a command-line program, thus scriptable – is a disadvantage for other uses.

You can probably find help on the correct options to use for your purpose in the wiki (https://code.google.com/p/ffmbc/w/list), in the ffmbc-discuss google group, or with a specific web search. Note that ffmpeg now also supports ProRes, and is more widely used than ffmbc. So search for both.

Maybe we can help here as well, if you let us know what result you want, and show us the output of ffmbc -i "$your_file"

[Milivoj Ivkovic]

This 7 year old post came up in my search for MediaLog for Mac, so maybe it is still worth replying to.

Avid makes this really difficult. The Medialog installer is included in the Symphony (and Media Composer?) installer, and cannot be downloaded separately.

So you need to first create an Avid account, so that you can download MC or Symphony. Then you can download the Symphony or MC .dmg. Open it, and you will find an “Install Symphony (or MC?).pkg” file. Right-click that .pkg file, and select “Show Package Contents”. Under Contents/Packages, you will find “AvidMediaLog.pkg”.

[Milivoj Ivkovic]

You certainly have solved your problem by now, but in case others come across this thread, I just did the following on Ubuntu 12.04 LTS:

Make sure you have the necessary tools installed:

sudo apt-get install build-essential yasm

After downloading the latest source of ffmbc, and unpacking it into ~/src/

cd ~/src/FFmbc-0.7-rc7

./configure --enable-gpl --enable-nonfree --enable-runtime-cpudetect
make
sudo make install


make gave out lots of warnings, but it seems to work fine anyway.