Rui's note on qjackctl prompted me to look at http://www.rncbc.org and then
http://www.rncbc.org/drupal/node/191 which lead to
http://qmidictl.sourceforge.net/ and http://qmidinet.sourceforge.net/ ...
Both of these apps look awesome. Any chance these can be made available
through PlanetCCRMA or even better, through fedora which already carries
up-to-date versions of qtractor.
Also, one issue I've found w/ controllers in general is that there is a need
for a simple scripting language, or a comprehensive set of "built-in special
functions" to handle "state" and "computation" in midi controllers. Do
qmidictl or qmidinet have any solutions for this?
One quick example I ran into recently. I've setup a very useful remote
control to a TC Electronics Finalizer. One of the features it has is a
MIDI-controlled "fader" (e.g. for doing smooth fadeouts/fadeins). I've got
that mapped to a 100MM slider on a behringer controller and it's SWEET. But
also, it's linear. What I need is to map the midi controllers 0-127 to a
logarithmic curve so as to match human loudness perception. This doesn't
seem possible in qmidiroute... (?) What tools would allow this, or any other
"computed" mapping to be done? (see also see
Is there an easy way to add scripting languages to Qt apps? (something like
'Guile' would be nice).
PS: thanks to http://www.rncbc.org/drupal/node/183 , I will also be taking a
look at qtractor-0.4.5-1.fc12.x86_64 which i've installed, but not yet
explored ( rosegarden4-10.02.1-1.fc12.x86_64 works well for me so far).
On Tue, Mar 9, 2010 at 3:34 AM, Luis Garrido wrote:
>> The main reason that I am writing is to ask you about your take on our
>> update strategy in Fedora. Currently, there is a heated discussion in
>> Fedora-devel mailing list about update policies. It might happen that
>> our updates policy might change to a more conservative one.
> I thought Fedora filled RedHat's niche for "keeping up with the new
> features even if stability suffers a bit" distributions. What is "more
> conservative", exactly?
There are mixed opinions. Some say security and bugfixes but no
enhancement updates. Some even go up to pushing security fixes only.
Here is a proposal that will be discussed in tomorrow's steering
No conclusion has been reached for the time being.
> A mature-ish Fedora (i.e., one version below the the current one but
> still on maintenance, between 6- and 12-months old) is usually a good
> trade-off. You will always have to deal with some problematic stuff or
> another, putting down small fires, but that's the blood in the
> bleeding edge, people should be aware of that when they choose this
> kind of distro. If you value rock-solid stability over new features go
> RHEL or CentOS (which I do for my servers.)
:) These were the main arguments that some more "adventurous" package
maintainers like me came up with.
I just wanted to hear you folks' opinions, as that's what matters for me most.
On Mon, 2010-03-08 at 22:39 -0800, Niels Mayer wrote:
> For example, there should be a well supported option for "prosumer"
> and "pro" audio/video use of Linux using Jack and netjack as a
> replacement for pulseaudio. These would need to be supported across
> the board by other apps in fedora/gnome/kde s.t. users wouldn't need
> to manually set gstreamer properties in gconf, or do other gyrations I
> described earlier
> in: http://comments.gmane.org/gmane.comp.audio.planetccrma.general/9485 . One suggestion for using Jack as a replacement to pulseaudio was made here: http://pdavila.homelinux.org:8080/blog/?p=369 ...
This comes up every once in a while in the jack* lists (and/or lac). So
far no one (AFAIK) has gone beyond saying that it is the way it should
be and that that would solve all problems. When somebody actually starts
working the way down that path he/she will realize that it is not that
simple (this is not to say that it should not be done or could not be
Currently Jack2 (fc12+) plays nice with Pulseaudio and can get the sound
card on startup and release it when exiting. And the Pulseaudio
connection to Jack did work on limited tests I did.
So you can start Jack, load the appropriate Pulseaudio plugin and
redirect all PA streams to play through Jack. I experimented with that
briefly when writing the perl script I used for Jack/PA interaction in
fc11 when the PA vs. Jack interaction was still buggy. It was possible
to start Jack and get an application that was playing on PA to keep
playing transparently through Jack.
So, the building blocks are already there, I think.
Still, there are many reasons why it is not possible or desirable to
make Jack a "system service" that starts when the computer boots. It is
not designed to do that (security is one of the main problems).
> Such an option would also make Fedora even more "the distro to have"
> for doing prosumer and pro music and video on Linux, especially with
> Fedora's strong support for infrastructure like qjackctl and patchage,
> audio tools like rosegarden or ardour, and video tools including
> qjadeo , kino, kdenlive etc.
On Tue, Mar 9, 2010 at 1:39 AM, Niels Mayer wrote:
> Orcan -- Please continue doing what you're doing!
> I think what would help is your continuing to announce new packages, and our
> willingness to invest enough time to properly test functionality in new
Yes I admit I have not been so good with announcements of new update
candidates. I will try harder.
Hi folks, I just submitted rosegarden-10.02 to stable in Fedora since
nobody yelled at me, and those who commented didn't complain.
The main reason that I am writing is to ask you about your take on our
update strategy in Fedora. Currently, there is a heated discussion in
Fedora-devel mailing list about update policies. It might happen that
our updates policy might change to a more conservative one.
Are you happy with the current situation? What I do is, I typically
push an update to updates-testing, leave it there for 2 weeks minimum
(sometimes more). If no complaints, push it to stable updates repo. Do
you think that we are pushing updates too frequently? I like to keep
all of us up to date. We get a decently low number of bug reports. Do
you have a stability problem with this policy? I can stop doing
non-critical updates in stable Fedora releases if there is an issue.
I just wanted to hear your opinion.