Hi all. I am writing a basic video editor based on MLT. At the moment,
I use an mlt_playlist, which lets me append video files, break them in
clips, and connect different filters to different clips. So far so
good, I appreciate
the clean C interface of MLT: congratulations. But
now I'm facing a
Thank you for your reply.
>> I thought I could use
>> a "multi"
consumer, but ...
>
> That will not work. MLT does not have a general
tee-like component.
> I have never tried to do what you are doing, but
I think you are going to
> have to compose and run distinct graphs: one
that is unfilter
Hi all,
I succeeded in creating a preview of the unfiltered frames, as
suggested by Dan: I wrote a filter, first in the chain, which extracts
the image.
Now I have another problem: I would like to process frames
to inspect the audio levels. I thought I can use the audiolevel filter
and ask it
> The filter will not process the audio until you call
mlt_frame_get_audio()
Thank you for the answer. I tried to follow the
sources of mlt and shotcut, but without success... I will try your
suggestion.
>Why not listen to theĀ "consumer-frame-render" event from
the consumer and request the l
Hello all.
I wrote an mlt-based video editor that is working quite
well. Now,
I am trying to write a program to extract thumbnails from a
video clip,
but nothing works as expected... and it is strange because
I am
using the same code snippets of the previous (video editor)
program.
I am getti
Hi all,
I am writing a video editor using mlt. The editor basically
edits a playlist, inserts filters, and does preview via a swallowed SDL
window. When requested, the editor generates an XML file to be fed to
melt(1). So far so good.
In order to crop clips, I used until now the
stock "crop"
ilter then provides only the parameters to the
>one previously added by loader. There is also a qtcrop filter that
fills
>the area outside of a shape with a color including alpha.
>
>
>On Sun, Jan 31, 2021 at 1:39 PM linux...@tin.it
wrote:
>
>> Hi all,
>>
>>
Hi again,
I only want to signal that I discovered something strange:
my crop filter has 6 properties: left-right-top-bottom, plus "width"
and "height". They work correctly in the editor but, when exporting in
XML, "width" and "height" are omitted from the XML file. Of course this
fact polluted