Dear friends,

I found some AVCHD raw footage on the internet for testing Kdenlive:

http://file.meyersproduction.com/hg10/00009.MTS.zip

http://file.meyersproduction.com/hg10/00011.MTS.zip

http://file.meyersproduction.com/hg10/00019.MTS.zip

Any downloading links for testing latest MLT/kdenlive developments?

In reply to Dan, I have a bi-core AM2 computer.

I may buy a Phantom quad-code processor.

Kind regards,

Jean-Michel

I tested:

inigo 00019.MTS

Decoding works fine but is not multi-threaded.

I can see the activity of my AM64x2 stuck to 50%.

Kind regards,

Jean-Michel

When building the ffmpeg that MLT is using, did you --enable-pthreads? If you are using --avformat-svn, you need to supply this additional option to --avformat-svn-extra.

Finally, did you enable multi-threading for the MLT module either through the threads property or MLT_AVFORMAT_THREADS environment variable? It is not on by default.

ffmpeg does not yet support interlaced AVCHD. The above causes ffplay to issue "[h264...] PAFF interlacing is not implemented." That is why I asked if you know of any progressive AVCHD with which to test.

Your ffmpeg is out of date :) or you should enable h264 decoding.

--enable-libx264

I can use inigo to watch00009.MTS and 00019.MTS, slowly, but it works on my computer.

This is a test video shooting a fountain.

I am sure that ffmpeg now supports PAFF interlaced AVCHD.

This was a main development months ago.

export MLT_AVFORMAT_THREADS=2 ; inigo 00019.MTS

still consumes 50% of my AMDx2

I see no difference with MLT_AVFORMAT_THREADS=1

I compiled today's ffmpeg ... it rocks.

It contains optimizations, now inigo plays very smoothly.

inigo does not seem to reach more than 100% of one CPU core.

libx264 is used only for encoding



I stand corrected. I tested on one of the above with on my work computer with a dated ffplay. I just updated, and it does work.

Also, I was generalizing with the claim "interlaced AVCHD" because while the above clips work, AFAIK, it is still incomplete with some clips reporting:

"[h264 @ 0xbf3220]Interlaced pictures + spatial direct mode is not implemented"

I though spacial direct mode was used for digital HD channels, not camcorders.

Did you find some camcorder footage with spacial direct mode?

Yes, it was from a camcorder, being played with ffplay from sometime December on yet another computer. Then, I updated ffmpeg on that system, and those messages went away. Now, I just get some other occasional messages that less alarming especially since the picture looks rather good.

Is inigo playing the AVCHD for you nearly as smooth as ffplay? It's not for me. What is your inigo command line?

An example of mine:

inigo -profile atsc_1080i_60 00009.MTS threads=2 -consumer sdl rescale=none

For a pure clip playback scenario the rescale=none on the consumer is good to make it use the XVideo hardware scaler instead of the MLT software scaler. However, in a project with mixed resolutions, transitions, and compositing, you don't want to use that option.

I tried several options but was not able to play clips from inigo:

inigo 00009.MTS -profile atsc_1080i_60 threads=2 -consumer sdl rescale=none
Usage: inigo [ -profile name ]
             [ -serialise [ filename.inigo ] ]
             [ -group [ name=value ]* ]
             [ -consumer id[:arg] [ name=value ]* [ silent=1 ] [ progress=1 ] ]
             [ -filter filter[:arg] [ name=value ]* ]
             [ -attach filter[:arg] [ name=value ]* ]
             [ -mix length [ -mixer transition ]* ]
             [ -transition id[:arg] [ name=value ]* ]
             [ -blank frames ]
             [ -track ]
             [ -split relative-frame ]
             [ -join clips ]
             [ -repeat times ]
             [ producer [ name=value ]* ]+

More than likely the avformat module was not linked to a dependent lib. Also, a common pitfall with avformat is to forget to supply --avformat-swscaler to mlt/configure when building against an ffmpeg that was configured with --enable-swscaler

my command line was :

I checked and ffmpeg was not compiled with --enable-swscaler.

I am recompiling ffmpeg and will report back.

You seem to be mixing mlt and ffmpeg configure options directly, which is non-sense. I realize there is some commonality between their options, and it is an easy mistake.

--enable-theora --enable-libogg --enable-pp --enable-shared-pp are all ffmpeg options, and mlt will ignore them as it does not understand them. You can safely remove them from future runs of mlt/configure.

Your configure command is linking the avformat module to a shared installation of ffmpeg. Last night, I updated the avformat configure script to use pkg-config, which will pull in all the right libs automatically. The only thing it can not do is know whether ffmpeg was built with --enable-swscaler as that info is not supplied with pkg-config. Can you please update mlt from svn to make sure you have the updated configure script? Then, run 'ffmpeg -version' to see what options it is built with, and look for --enable-swscaler. If it's there, then leave your mlt configure option --enable-swscaler. Otherwise, remove it.

Dan

by the way, what do you think are the "standard" configure options for mlt ? In the wiki I've found these:

./configure --prefix=/usr --enable-gpl --disable-mmx --avformat-swscale --enable-motion-est

As I'm now updating the script to automatically (more or less ;) )install kdenlive, I'll appreciate if you can give a clue on what options are the most suitable for most of the users.

Thanks in advance.

Regards.

JM

I followed guidelines, still does not work.

Any idea to check MLT?