|
|
Subscribe / Log in / New account

Cinelerra stability

Cinelerra stability

Posted Dec 8, 2009 16:26 UTC (Tue) by cantsin (guest, #4420)
In reply to: Cinelerra stability by MattPerry
Parent article: The CinelerraCV Project (Linux Journal)

That's why my original comment suggested to remove functionality that is
not reliable. If Cinelerra would ditch the Record/Capture module, limit
import and rendering to Quicktime with a small number of editing-safe
codecs, prompt a default warning message on systems with insufficient
CPU/RAM resources, and have safe default preferences (such as the use of
OSS instead of ALSA for audio output), it would avoid shock and awe for
most first-time users.


to post comments

Cinelerra stability

Posted Dec 9, 2009 8:10 UTC (Wed) by drag (guest, #31333) [Link] (1 responses)

Well the safe bet would be to fix Alsa and drop OSS. OSS support is so depreciated at this point that pretty soon even the most basic support of it is going to be missing completely in many Linux systems.

--------------

That's the thing, right? Alsa support is a requirement, not optional. Not unless you want to re-do most of the audio to use Gstreamer or SDL or something like that so you don't have to give a shit about Alsa vs OSS anymore.

AVI files themselves are nothing special.. it's just a container format that commonly has mpeg4 and mp3 audio. If Cinelerra can't handle importing that then there is something massively wrong in this day and age. There is some sort of fundamental design flaw going on there. Hell just off the top of my head spawning a helper script to use ffmpeg to dump raw YUV video into a fifo that directs to a internal buffer should not be that difficult and will probably be easily made to work 95 times out of a 100.

Cinelerra is useful to some people because it has features that nobody else has and capabilities that nobody else comes close to. Stripping out features to make it 'newbie friendly' is going to negate the entire purpose of it. It's a professional-style tool. It is like suggesting that GCC should just strip out warning and errors so that it can be more friendly to new C programmers. It's not a desktop or a browser and has to be useful for a general case. It has to be useful for a specific case.

This program has been around for years and years. Long ass time. It looks as if it has hit some sort of wall in terms of progress. I am sure the CinelerraCVS folks are working hard, but to progress to the next level they are simply going to have to do what the Blender folks have done. That is they need to sit down, get some funding, and work with people using it in a real environment with real video and audio in a real project. There is a insurmountable difference between arguing about features and UI in a mailing list versus standing behind professionals taking notes and suggestions as they struggle to use your software.

It's the difference between something like this:
Blender 2.37 screenshot
versus:
blender 2.5 beta screenshot

Ditto for Gimp and Krita or any other tool that wants to be more then just a useful tool to play around with.

Cinelerra stability

Posted Dec 9, 2009 9:21 UTC (Wed) by halla (subscriber, #14185) [Link]

Well, Krita is busy raising funds just now: see the Krita fund raiser, though we were clearly not ambitious enough: we managed to raise the 3000 euros needed to have one of us work on Krita full-time for three months in three days instead of the three months we thought we would need.

And we have got a plan, some real users who work with us to go through the issues they have with Krita and who tell us what is missing and what is crappy, so I am really confident that the next major release of Krita, around August or September 2010 will be a very significant improvement.

Especially if people don't stop donating, but go on so we can have Lukas for another month, fixing bugs full-time in the running up to the release!


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds