Hi all. Ubuntu Studio is looking for people to test and report on daily
builds and or Alphas for Hardy. We're interested in feedback on how
PulseAudio and JACK work together how Ardour is working and anything on
the -rt kernel.
I will note that the pulseaudio plugin will not be in Hardy because it
takes JACK being in the Main repo to build against. We're trying to get
JACK in Main for Hardy+1. But this adds a extra layer of latency so it
might not bother most people.
This looks like an opportunity to beef up audio side of things as well as
foster development of another powerful foss multimedia software.
See below for more info.
Ivica Ico Bukvic, D.M.A.
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-5034 (fax)
From: piksel-bounces(a)bek.no [mailto:firstname.lastname@example.org] On Behalf Of
Sent: Friday, January 18, 2008 7:05 PM
To: p1k53l workshop
Subject: [piksel] Fwd: [estudiolivre] I believe in cinelerra
---------- Forwarded message ----------
From: Leo germani <leogermani(a)gmail.com>
Date: Jan 18, 2008 7:53 PM
Subject: [estudiolivre] I believe in cinelerra
To: estudiolivre <estudiolivre(a)lists.riseup.net>, Felipe Fonseca
Develop cinelerra as a professional free/libre video editing tool.
Cinelerra is the most powerfull free software for video editting we
have nowadays. Although it has many resources and that it is far more
advanced than any other Open Source video software, its development is
very slow and has no sponsor.
Its main developer, Heroine Warrior, do not mantain a SVN or a mailing
list. The last official release was last july and there is no sign of
a upcoming version of cinelerra. They usually publish a new release
every six month or so but do it only for their own needs and do not
talk with the community much.
Few developers mantain a fork called "Community Version". All out of
volunteer work they mantain a SV a mailing list and an online wiki.
They also fix some bugs and add some features to the code.
This desorganized development results in a mess. There is no official
stable release and package for the distributions, and cinelerra is now
known as very hard to install and unstable software (although it got
really better last year).
Also, first contact with cinelerra is usually disappointing because of
a not well resolved interface and also because of big flaws it has on
With all that said, it happens that we have a software that is, at the
same time, powerfull enough to do any kind of editing, but weak enough
to have very basic issues of usability.
And the feeling all advanced users have is: We are pretty close to
have high standard software!
To learn more about the mess, take a look at this page:
Many of the actions described on this plan are already been done by
many people, but in a rather heroic way. If this people got motivated,
organized and _paid_, cinelerra would increase its quality
dramatically in a short period of time.
1. Get the community together
The community of developers today is very small and spread, and
cinelerra has no road map.
First thing to do is gather this people to discuss about the future of
cinelerra, identify the main flaws and its solution, make a plan to
organize the place and set up for new features.
Cinelerra needs a project leader, an interface designer, and more
people with defined roles that should be choosen on this meeting.
Developers of other softwares are also welcome. Cinelerra is, so far,
the only video free editing video editing software with professional
approach, but it could share a lot of things with other software, such
as effects, for example, that shoul be usable in any video software,
just like we have LADSPA for audio. There is already a video effect
standar called Frei0r that cinelerra does not support.
Cinelerra code is not very well documented, so few people have the
idea of how tuff is to deal with it. Second step is to see what must
be done so we can invite more people to colaborate with the code.
Documentation, refactoring, etc. It also has to work on the API so
other people can write plugins and effects.
In other words, lots of work that are a pain in the ass but has to be
done in order to advance properly. And passion has a limit. There must
be people getting money to work on that.
3. Make a plan
Based on the diagnostics and on researches with users and other video
editing tools, define how cinelerra will look and act in a not so
distant future. With that goal in mind, make a reasonable plan to make
3. Set up a core development team
No secret here. Few people dedicated to make it happen, including an
The core team can offer bounties for parts of the job they choose.
This will attracat more developers to the community.
5. Attract contributors
Mantain a nice looking website, a wiki, tools for easy translation of
the interface and of the online documentation, etc. are goos
strategies to attract people to contribute. Its also important to find
people to package the software for different distributions.
Lista de Discussão do Estúdio Livre
portal colaborativo -> http://www.estudiolivre.org/
sobre esta lista -> http://lists.riseup.net/www/info/estudiolivre
GNU User #286985
"As contradições mais agudas da vida humana
não foram feitas para serem solucionadas, mas vividas
com plena ciência de seu carater paradoxal."
piksel mailing list
Dear Linux Audio users,
A new jack release (0.109.0) is available:
* add jack_thread_wait API
* remove port_(un)lock functions
* add new time APIs
* add port aliases
* add new client registration callback
* add port connect callback
* ALSA: fix for use of snd_pcm_link
* ALSA: hardware jack-midi support
* ALSA: fix for enabling big-endian 16bit format discovery
* ALSA: hardware jack-midi support
* FreeBoB: fix deallocation segfault
* FireWire: add 'firewire' backend for use with FFADO
* OSS: add support for proper triggering in OSS driver when in full
* ALSA: fix illegal use of ALSA API
* OSS: disable software mixing and samplerate conversions on OSS 4.x
* CoreAudio: fix sample rate management
* add JACK_PROMISCUOUS_SERVER handling
* make /dev/shm the default tmpdir
* add -Z flag to cancel zombification on timeout
* add per-port update total latency
* increment default watchdog timeout to 10sec