Hi there!

Welcome Achim.

Very interesting. We are looking forward to your videos.

Hello and welcome.
A curiosity on the part of an incompetent: what does ScrumMaster consist of?
I am also waiting for your videos 🙂

A ScrumMaster is part of a team producing software. There are developers (responsible for delivering high quality software), a product owner (responsible that the product is successfull) and a ScrumMaster (responsible the processes (given and chosen) the team has to follow).

I too, look forward to see your videos!

No flame intended: I heard kdenlive is not very stable how was using it for 9 years?

Since you know kdenlive very well, could you outline its advantages over cinelerra? Maybe they can be used as source for ideas of feature requests to improve cinelerra:)

Yeah, good idea... Using kdenlive since version 0.5 made me a "save often person". After 2-3 edits I saved the project. That was fine as kdenlive used to stall less and less over the years. I think it was GPU acceleraton that brought me back to cinelerra. GPU acceleraton made kdenlive quite unstable again and in addition to that it was not predictable if (GPU) effects would work in the next release. So compatibility became an issue. For me as an Archlinux user working with kdenlive felt like playing a lottery.

Features that made kdenlive better than cinelerra-cv 9 years ago:
* kdenlive has been much more intuitively to use - as a long term user I have no idea what a beginner would say today, as the number of features increased significantly over the years.
* Resolve between clips with predictable and easy to edit results by applying a resolve transition between two overlaying tracks
* Video and stereo audio in one track by default - This reduced the number of tracks and reduced mistakes by unarming and arming tracks.
* The more modern design
* far better support of codecs and export formats (everything that ffmpeg supported)

Features I like in cinlerra-gg today:
* Excellent support of GPU rendering by using the render pipe - greatest feature in the world for me!
* Excellent support of codecs - build in ffmpeg presets or render pipe
* design improvements
* speed on startup and editing
* build in rendering engines are so fast (e.g. RGB for pipe export, flac or wav export)
* very stable GPU acceleration for preview
* excellent keyframe features, speed effect with keyframes (maybe I missed that in kdenlive...)
* usage with keyboard (was possible in kdenlive but I never used it, dunno why)
* not a single crash in 2018 - WOW!!

All in all, when coming back to cinelerra (this time cingg) I missed the "all in one tracks" (video and stereo audio in a video track, or stereo audio on an audio track). And I am still struggling with the resolve feature but found workflows to get the same accurate results as in kdenlive.

Wow thanks for the exhaustive report!

Interesting comparison of Cin-GG and Kdenlive.  I have looked on the internet for Kdenlive with Resolve Transition and find nothing.  What is "applying a resolve transition between two overlaying tracks"?  I know you have found a workaround but if there is a demo for Kdenlive out there or documentation about it, I am curious if it would be something easier to add to cin-gg.  But I do not believe "all in one tracks" would ever get added.

Also, thanks for the definition of "scrum master" as I had never heard of that!

Yay, the transition is called Dissolve, just saw it's the same as in cin-gg - sorry for wasting your time...

kdenlive: https://www.youtube.com/watch?v=kDc0qTV2Xww

Shotcut provides dissolve in one track like this:  https://youtu.be/NUDCcq6WcJU?t=109

So, as you have to deal with a lot of tracks in cin-gg I would prefer some dissolve transition editable in one line.

In Kdenlive this effect is created with two tracks, in Cin-GG you can create the same effect with just one track, similar to what Shotcut does. You insert two clips directly to each other in a track and then insert the transition dissolve, that's it.
You don't need as many tracks as with Kdenlive. Cin-GG does it like Shotcut, but for the audio track the cross-fade has to be inserted separately. Maybe a small extension can be built in, which is optional, that when inserting Dissolve the cross-fade can also be inserted automatically on the audio track, that would certainly make the work a bit easier. If you want to make such a suggestion, then I would ask you to open a ticket in MantisBT.

Sam

@cinadmin
Yes, I know how to add a dissolve in cingg. But imagine you need to have a dissolve to end at a certain frame F of the second clip. In kdenlive you simply trim the second clip to that frame, put that short clip under the end of the first (right end under right end), add dissolve and then drag the right end of the second clip to the length you need.

In cinelerra I have to measure the distance from frame F to the cut between the two clips by selecting the section. Then do some mathematics (distance shown in secs:frames in my settings) and adjust the dissolve to the correct time.

It would be perfect if one could simply drag the right end of the dissolve transition to the frame F as if dissolve would be an effect. Then we have easy to edit accurate dissolves in one line. 🙂 As a second shot: If the dissolve could be adjusted in secs:frames instead of pure secs it would also be easier. 

Now I understand the problem. I have to agree with you, that unfortunately doesn't work. I just noticed while testing that the extended trim features don't work when the transition is inserted. Only the left clip is shown. If you hold down the Shift key and drag the cutting edge between two clips, both clips are displayed in the compositor, but it doesn't work if a transition is inserted.

I think your idea is very good, maybe we could combine your suggestion with the extended display of both clips in the compositor, if technically feasible. I have attached a screenshot. I would support the idea if you open a ticket. You are welcome to add my screenshots if you like my idea with the compositor.

https://ibb.co/kH1RsVj
https://ibb.co/VWvtQ8y

Sam