| |||||||||||||
Kino makes video editing simple (NewsForge)Kino makes video editing simple (NewsForge)Posted Aug 22, 2005 7:31 UTC (Mon) by LarsOlesen (guest, #31994)In reply to: Kino makes video editing simple (NewsForge) by man_ls Parent article: Kino makes video editing simple (NewsForge)
I have only used Kino so far but I am interested in shifting to Cinelerra. However I can't export my video material to quicktime from Kino, since Kino seg-faults each time I try.
Can anyone here advise me about what to do?
My system is:
(Log in to post comments)
Cinelerra makes video editing powerful Posted Aug 22, 2005 15:00 UTC (Mon) by man_ls (subscriber, #15091) [Link] I use Kino 0.7.5 on Debian Sarge; it behaves correctly when exporting to QuickTime: I use export to "DV File" then select "Quicktime DV". But usually I just capture with the same settings (Edit -> Preferences -> Capture -> Quicktime DV), so that all clips are automatically stored as Quicktime .mov files. I can't think of anything else, sorry.By the way, Cinelerra takes some time to get used to; be patient.
Kino makes video editing simple (NewsForge) Posted Aug 24, 2005 13:04 UTC (Wed) by forthy (guest, #1525) [Link] I don't use Kino (the GUI part), but the command line tool dvgrab only.You can set it to export quicktime .mov files. This works fine for me, and both mencoder and cinelerra can read the resulting .mov files. For quick&dirty removing of scenes, mencoder is the tool of choice for me. You simply rm the scenes you don't want to keep, and then mencode all the remaining scenes into one mpeg4 movie (non-linear file-system based video editing ;-). I don't like cinelerra; it's crashy, the GUI is non-intuitive, and often quirky. It is powerful, though (or at least it appears to be, being crashy, I lost patience to try too much). What I really would like to have is a render engine, which takes a command script, and a GUI which allows you to construct such a command script. The render engine should be capable to play such a script with at least two movies and several effects. I don't like monolithic applications; the non-linear video editor itself should not do the rendering, it should use a command-driven render tool. The editor should be able to browse through scenes, mark begin/end of effects, and so on - reliable, non-crashing. Probably it's simply that I'm not a GUI person for complex tasks. I don't typeset texts with a GUI editor, I use TeX. Why should I use a GUI for cutting movies? It's ok to have a GUI to select points within the scene - there you need the immediate visual feedback. Cutting has the same sort of high-level things to think about as typesetting; you have chapters, scenes, and intra-scene cuts. There's a lot more to it, but most of it can be said in words without a thousand pictures (the thousand pictures come out of the process, anyway).
|
|||||||||||||