On Monday 11 May 2009 18:49:28 jb wrote: > Yes. As previously commented, there is currently one producer by track for > audio and av clips. This is needed to bypass an issue in MLT causing sound > cracks if you try to mix the same producer with itself.
and this is not going to be fixed, i suppose :/ > Removing all kdenlive_producer and moving options to MLT's producer is > possible, however one issue is that MLT does not save producers that are > not used. So if you add a producer to your Kdenlive project but don't put > it in timeline, it will not be saved by MLT's xml output, you will have to > add it manually somewhere... is kdenlive using mlt's xml output? i thought it was produced internally... then there's no way to change the actual behaviour, unless dan changes mlt > I was also a bit worried that adding lots of properties (some of which can > be rather long) to the Kdenlive clips (for example text clips have an > "xmldata" field containing position and attributes for all the objects in > the title clip), could add some overhead to MLT, but Dan seems to say it's > ok... it's quite useless if we have the issue above, anyway: the meta.kdenlive properties could be written only in the first producer, and we could use the N_x id format kdenlive is already using > One small issue here too: I did not manage to save the MLT's tracks > attributes, which is why I added Kdenlive's <trackinfo>. Maybe that needs > some tweaks in MLT or maybe I just didn't try hard enough... gosh. is 'type="audio"' the only property we would need to add? -- Alberto Villa <villa.alberto at gmail.com>