On Mon, Jan 5, 2015 at 2:37 PM, jb <j...@kdenlive.org> wrote:
> Hello Dan,
>
> In the Kdenlive refactoring process, I want to change the file format we
> use,
> so that we only use MLT to store our extra data.
>
> For example, in the project bin, to keep track of a clip's folder, or when
> a
> clip is using a proxy, we need to keep track of its original url.
>
> So I want to store these extra infos inside MLT's producer, tracks and
> tractor. I think I read somewhere that you proposed that external programs
> use
> "meta." properties to store that data. I think it is a good idea to somehow
> isolate this from usual MLT data.
>
The meta prefix was intended as a form of extensible metadata (media and
descriptive). However, properties beginning with "meta." on the producer
are automatically copied to the frame object, which has some overhead.
>
> What naming scheme do you recommand ?Is "meta.kdenlive.xyz" ok or do you
> have
> other suggestions ?
>
>
Any unique prefix is sufficient. For Shotcut, I use "shotcut:" and I
suggest to use "kdenlive:". At some point, we might want to define a common
taxonomy to facilitate project exchange. I believe some properties will be
app-specific and others not so much. I will make a to-do item to document
all of Shotcut's special properties.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel
