[Kdenlive-devel] copy/paste

[Till Theato]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/15/2012 11:29 PM, Vincent PINON wrote:
> Sorry for not being clear :-/ Let's say we prepare a 1h movie,
> splitted in 10mn chapters, each in one kdenlive project file
> (already >100 clips for each chapter). A topic that was integrated
> in chapter 1 (say 4mn of interview, illustration, actions all
> mixed) would actually fit really well in chapter 3, but with
> alternating responses from an other edited interview (5 other mn
> with precisely adjusted transitions etc) forming a new 9mn sequence
> all mixed-up, but keeping many audio alignments, cross fades or 
> whatever. Copying 4mn of timeline from chapter 1, pasting into
> chapter 2 (other kdenlive project), changing many things... If the
> new edits prove good, maybe images from chapter 1 will be deleted 
> (maybe few  non-redundant images will be kept), but no need to 
> synchronize at all the timelines : it is a totally new edition
> trial.
> 
> (Technical detail : the clips can have been imported in advance in 
> chapter 2...)
> 
> At last, in the main project, chapters timelines might be dropped
> as a whole. The result is a main timeline with access to
> sub-timelines, but that can exchange data and move parts from one
> to another (called "pistes gigognes" in french, sorry I can't
> remember the translation in the reverse way!)

Hey,

what we've already considered in the past and what I'm also trying to
make easy to add to the refactored code are multiple timelines per
project, which can be dragged into each other.
Would this approach help? Once this basic functionality is implemented
it should also be straight forward to export a single (or multiple)
timeline as pure mlt xml (or as kdenlive project) and make it possible
to add and edit it again in another project, although for the workflow
you described this shouldn't be necessary anymore.

If I understood you correctly you could then edit each chapter in it's
own timeline while staying in the same project, drag groups of clips
between the different timelines (without having to import clips again)
or align the chapter timelines as a whole on a single "main" timeline.

As said, this is nothing I will do in the phase of refactoring but it
shouldn't be too hard (hopefully) to add it afterwards. What do you think?


And btw, great to hear the developer team is growing. Welcome to
Kdenlive :)


regards

Till

> 
> Le 15/06/2012 22:51, Simon A. Eugster a écrit :
>> On 15.06.2012 19:39, Vincent PINON wrote:
>>> [life] I convinced my wife (videast) to switch to kdenlive more
>>> than one year back [/life] up to now she has edited only rather
>>> short movies (~5-10mn), and never missed anything without
>>> finding an acceptable workaround. But for few weeks she started
>>> working on a longer, complex documentary, with many sequences
>>> to mix, searching for constructions that make the more sense,
>>> rythm etc. From her previous habits, she splitted her work into
>>> chapters and sequences, but after some trials she finds that
>>> some parts would eventually be really relevant *mixed* with
>>> others. So it would be beneficial to keep some constructions,
>>> grouped elements etc, but with
>> Clear so far.
>> 
>>> total freedom to merge and interleave with other pre-assembled
>>> shots.
>> Other pre-assembled shots. What are those? An extract of the
>> whole timeline (maybe excluding sound)? Just one video?
>> 
>>> For now she accepts to restart from a copy of the longest basis
>>> and redo the work for the new imported parts, but she wouldn't
>>> recommend this process to colleagues that would be interested
>>> by this free alternative (without great motivations and
>>> convictions)...
>> ewww ... jep.
>> 
>>> That's why I am interested to work on what I feel is missing,
>>> as from my local point of view it would be greatly beneficial
>>> for the project, and I believe I could handle it (with some
>>> some wise advice from time to time ;-))
>> The reason why I'm not convinced yet is Copy/Paste. You update
>> the original, you have to adjust the copy (copIES) too. That I
>> find totally unnecessary work which I want to avoid as far as
>> possible. So I hope we can find a better method that ideally
>> could also be used for different use cases :)
>> 
>> Simon
>> 
>> 
>>> Le 15/06/2012 18:02, Pascal Fleury a écrit :
>>>> Especially as a project can be imported as a clip in another
>>>> project.
>>>> 
>>>> --paf
>>>> 
>>>> Le 15 juin 2012 13:35, "Simon A. Eugster"
>>>> <simon.eu at gmail.com <mailto:simon.eu at gmail.com>> a écrit :
>>>> 
>>>> Hey Vincent,
>>>> 
>>>> before implementing this, what would be a use case for
>>>> copy/paste?
>>>> 
>>>> I.e., Is it really something we need, or could the problem
>>>> perhaps be solved differently? The reason for asking this is
>>>> that I never missed this feature so far, and there are other
>>>> places to work on too :)
>>>> 
>>>> Simon
>>>> 
>>>> On 15.06.2012 11:44, Vincent PINON wrote:
>>>>> Hi devs,
>>>>> 
>>>>> I started to study how to add clipboard support, to be able
>>>>> to reuse timeline sections from one project to another
>>>>> (assuming for the beginning that clips are present in both
>>>>> projects?)
>>>>> 
>>>>> I wanted to discuss with you about the interchange format
>>>>> to use
>>>> (mime
>>>>> data) : shouldn't it be a a full kdenlive document by
>>>>> itself? (like drawings in clipboard can be saved as
>>>>> autonomous metafiles...) Then the paste feature would be a
>>>>> kind of "project merge", which implementation is not
>>>>> complete, according to a changelog
>>>> search... (1st
>>>>> step to complete then)
>>>>> 
>>>>> Or would you suggest another approach?
>>>>> 
>>>>> BR,
>>>>> 
>>>>> Vincent.
>>>>> 
>>>>> 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAk/brWEACgkQzwEyz7QP6nTKBQCfXZzSyCrgJp4lzH/728+B/CEn
BEkAn1R/yZONMc0seq6rSp86bOv6RTiK
=1VW3
-----END PGP SIGNATURE-----