I know a lot more had been said already in this thread by people who know a lot more than myself about the whole area.
But when I read your message more closely something jumped out at me that I thought was at least worth picking up on.
You mention a comparison with Ardour. One feature that I like about Ardour, and is also used in Sony Vegas for video editing is the way they handle transitions. In both cases a transition is handled by simply taking two clip sections (on the same track) and dragging them over one another. The length of the overlap is the length of the transition, and overlapping automatically generates two default berzier curves, one for the clip fading in, one for the clip fading out. (Interestingly, Vegas has its heritage in audio editing too, just like Cinelerra -> Broadcast 2000 ->....).
Now I have to say that Vegas has probably the sweetest interface I have come across in *any* software package, and is the one application that I would go out and specifically buy a Windows box for. I am not saying we have to be like Vegas, but it is a paradigm that I think just fits so nicely: to cross-dissolve, you just overlay two tracks. I have not looked into it, so I have no idea how difficult it would be to implement, but I at least raise it for your consideration.
I admire you all and the work you do (Heroine and Cin-CV)
Ciao,
marks
On 7/18/06, Leo germani <[EMAIL PROTECTED]> wrote:
Hi all,
I am happy to announce that we are about to effectivelly contribute to cinelerra. This could happen through the Pontos de Cultura project of the ministery of culture of Brasil, who have hired Estudiolivre.org.
Rafael (slackware packages maintener) is soon starting to work on cinelerra code. Our aim is to fix the faders and automation lines.
We beleive they are great features (the faders for audio and video, and the possibility of automating camera and projector...) but the way they are today they are not very usable.
Of course we want to do this together with the community. So, first, Im gonna ask your opinions on whats the best way to deal with these issues. Later, I'll ask you to help Rafael, who is going to go deep in the code.
We have two plans so far, depending on how complex the thing gets:
Plan A:
Build Ardour-like automation tracks: it means you would have, on the left panel, the option to show or hide the automation tracks of your choice, wich would be subTracks of the track you are working in. On this track all you see is the automation line of the selected automation (fade, CameraX, etc...). You would be able to see one or as many automation tracks as you like at a time.
I think this is the best way cause also opens the door for, later on, someone add all the effects to this. For example, the PluginKey frames could migrate to the automatinoLine style. So I could automate, lets say, the HUE parameter of the Color Balance effect. It would substitute the yellow keys in the future in a much better way.
(Please let me know if my english is too confusing, maybe I can draw some snapshots)
Since we dont know how hard is to do this we have a second option:
Plan B:
just adding a selection box on the left panel for the user to select wich automation he/she wants to see/edit. It would be possible to see only one at a time. And the scale would be automatically adjusted for the selected automation.
Much simpler.. but does the job...
Please share your opinions!
cheers
Leo,,
--
Mark Stavar
Swan Dancer Productions
Email: [EMAIL PROTECTED]
Mobile: 0410 638 671
http://www.the-writers-retreat.com/
