On Mon, Apr 7, 2014 at 11:20 AM, Hungerburg <pc...@myzel.net> wrote: > Cinelerra would not read MTS files of a friends camera correctly and I > felt like learning, so I gave shotcut a try. It does not work like > cinelerra at all; but it works a little like kino NLE, which I remember > warmly. Maybe I should have watched the tutorials first, some things are > not obvious, some conceptual background is required to get up to speed. > > I will keep my copy of Shotcut and very likely update in the future, it > seems to be good for projects that I do. The most I miss a title > generator: That took me quite some time -- a title, that fades out.
We still have yet to expose the inbuilt HTML editor to the Open Other dialog. Right now, it is only available when using the Overlay HTML filter, which I dunno if you saw. But, as you noticed there is nothing inbuilt to fade overall title opacity. > 1) I did not want to create an extra playlist item to determine length: > I saw that jquery was in the html created from the template, so I tried > to use that, but it seems to be unavailable in the qmelt batch renderer > (qrc:// resources). As a workaround I put another copy of jquery.js in > the project folder and included from the html source. Eww, yeah, that is a major oversight. Thanks for bringing it to attention. > 2) The load event does not fire, when the clip starts to play, or when > the frame is displayed, where the filter starts -- in my case, that is > the same. As a workaround, I load the file from the menu and start the > render without a playback. I do not understand your workaround. > 3) The clock in the jquery script (see below) uses render time, not > playback time. As a workaround I used two-plus times the times (maybe I > should drop the sharpener filter...): You need to use the webvfx javascript extension to use playback time. See about the renderRequested signal here: http://rectalogic.github.io/webvfx/effects_authoring.html > > window.addEventListener("load", function() { > $("#intro").delay(20000).fadeOut(15000); > }, false); > > Also, during the experiment, I tried to make the html another provider > in its own track, which showed an additional problem: the "make > transparent" tick in the properties widget would not stick, it would > fall back to off on revisiting the pane. Seems like a bug in the gui. I Yes, I know there are some problems with changing file properties when you select a shot on the timeline. I think if you had selected transparent in properties before adding to the timeline, it should have worked. I will investigate this bug in the next couple of days. > put "transparent" into the .mlt file and made the track "compose", so it > would show right on first play. > > I also tried to get the fade by adding a filter to that track, but there > is only "fade to black" and not "fade to transparent" in the filter That capability is dependent upon a general purpose filter parameter keyframing timeline. Sure, we could add something along the lines of fade to/from black in the meantime, and I might choose to do that in the short term, but no promises. > list. That way, the timing would be playback time, not render time, I guess. > Now thats my report for now. > > Kind regards > > -- > peter ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
