please keep mailing list in your replies.
On Tue, Sep 11, 2012 at 10:43 AM, Janne Liljeblad
<[email protected]> wrote:
>> Does it happen if you use 2 different NTSC widescreen DV files?
>
> Yes, I made a copy of the same file on disk withdifferent name, and
> behaviour remained unchanged.
>
>> Also, as I told you recently, a Python mlt.Producer constructed from
>> an existing mlt.Producer is not a separate producer; it is merely an
>> additional reference to the same underlying producer.
>
> I always create a new mlt.Producer with path and profile, does this
> not make a new Producer even if the paths are same?
>
> def create_file_producer_clip(self, path, new_clip_name=None):
> producer = mlt.Producer(self.profile, path) # this runs 0.5s+
> on some clips
yes, that works because that constructor uses the factory.
p.s. if you know the clip is valid, you can tell it to use the
avformat-novalidate service to make it load faster.
> producer.path = path
> producer.filters = []
> ---
>
> Also, this is not the problem here because producers to different
> files still do the wrong thing.
ok, I will have to try to reproduce it with xml and melt.
> The self.profile above is the same I provide the consumer with, could
> this be wrong? It is the same profile is used when I create playback
> consumers by doing:
no, that is the correct practice
> def create_sdl_consumer(self):
> """
> Creates consumer with sdl output to a gtk+ widget.
> """
> self.consumer = mlt.Consumer(self.profile, "sdl")
> self.consumer.set("real_time", 1)
> self.consumer.set("rescale", 1)
>
> Should I use different suitable profiles for different clips when I
> create them, or is using the same as the one used for consumer the
> correct way to do it?
one profile per composition/project. The consumer "adopts" the
profile. In all released versions thus far, if the consumer will be
seeing a different profile, you would have to destroy the consumer and
recreate it. However, in git version, you only need to stop the
consumer and restart it to make it adopt a different or altered
profile.
> I clone clips with the following method, using path from existing
> clip, using the above method:
>
> def _create_clip_clone(clip):
> if clip.media_type != appconsts.PATTERN_PRODUCER:
> new_clip = current_sequence().create_file_producer_clip(clip.path)
> else:
> new_clip =
> current_sequence().create_pattern_producer(clip.create_data)
> new_clip.name = clip.name
> return new_clip
>
> I also init consumers and tractors correctly when new projects are
> opened, because it does not matter what is the default profile used to
> create the default project.
>
> If default profile is "NTSC widescreen" it does not work, and when I
> create a "DV PAL" project it does work.
>
> If there are any tests, images or code information you need that would
> enable you to help me here, I'll be more then happy to provide you
> with them. This is huge bug that I've been completely blind to.
If you export the XML (add this function to your app if it does not
yet exist!) does it reproduce with melt?
> I'll also read mlt_producer.c and mlt_transition.c code, to try to get
> idea whats going wrong.
--
+-DRD-+
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mlt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mlt-devel
