Kudos to whoever pushed the LADSPA SWH plugins to Extras! Thank you!
Now, here's my thoughts: this is a set of LADSPA plugins. It works
strictly in conjunction with the package named "ladspa" - indeed, it is
an extension to it.
Therefore, I believe that the name of the plugins package should include
the string "ladspa" somewhere. Examples:
Or perhaps even more logical:
This name shows clearly the fact that it's actually part of the LADSPA
suite. Moreover, the highest, least specific, denominator (ladspa) comes
first, the second highest (plugins) comes next, while the most specific
denominator (swh) comes last. Kind of like the YYYYMMDD scheme.
My proposal is to settle to a clear rule to name these packages and
apply it consistently to all LADSPA plugins. There are quite a few that
can still go to Extras:
And this one too:
Hey Fernando, I just yum installed qjackctl out of FC5 Extras.
Excellent! Thanks! It took me a couple of packages to get familiar and
comfortable with everything. I hope you'll find the same is true for
I'd like to see a 'Powered by Fedora' sticker on one of these, or
something like it, someday...
"Start-up Trinity Audio Group (TAG) is using Linux and open source audio
applications in a small, portable, inexpensive digital audio workstation
(DAW) claimed capable of professional-quality recording and mixing. The
Trinity DAW is based on an Intel PXA270 processor, and targets field
recordists, podcasters, and producers. It will ship in October. "
> Summary: Review Request: rosegarden4
> ------- Additional Comments From green(a)redhat.com 2006-07-19 18:51 EST -------
> (In reply to comment #13)
> > Patched and built on devel and FC5! FC4 is missing liblrdf, liblo and dssi though.
> Great news!
> I wasn't planning on putting those packages in FC4, as I don't have an FC4
> machine to test with. Is this still something you would really like?
(moving out of the closed bug. Heh.)
Doesn't really matter to me personally, I keep current. This is
something that should be coordinated amongst the SIG though. I think it
would be best to have all or no audio apps available on FC4, rather than
having some packages available and some not.
So what does everyone think? Should we make an effort to support FC4 or
should we just concentrate on FC5 and beyond? Will FC4 even work, i.e.
does it have a PAM and kernel that lets us enable real time support for
jack? Would building for FC4 be helpful to Planet CCRMA, or just cause
Hey - Callum's PlanetCCRMA based rosegarden4 package was just introduced
to Extras (FC5 & devel). It took a long time to get here, but I believe
this is the first full useful application to migrate to Extras from
PlanetCCRMA. Most everything else was supporting technology. Cool
Hiya... some of my (Planet CCRMA) users are still having problems when
trying to install older kernels with yum. Does anyone know how to tell
yum to pretty please install a kernel even if it is version-older than
the newest already installed?
I have a set of packages (planetccrma-core-*) that "Requires:" the
proper kernel, alsa, rtirq script, etc, etc. Yum refuses to install an
I thought that doing this in /etc/yum.conf would fix it:
But it does not...
---- Forwarded message:
On Sun, 2006-07-16 at 10:46 -0700, Fernando Lopez-Lezcano wrote:
> Last suggestion was to clean up the internal yum state - but I never
> feedback on whether it worked or not. See "man yum" and go to the
> options" section. I would try "yum clean metadata" first (this will
> reload all the metadata from the servers which could take a while on
> slow links). Please let us know if any of this helps...
I tried a yum clean all, and even that didn't seem to work. It seem
whatever setting causes the kernels to be treated differently than other
packages isn't either being checked, or isn't present on the files.
Let me know if you require more information.
Watch as the music industry continues to create opportunities for an open
A question from one of the comments in the article:
"Eventually the media companies are going to push too hard. Many big
companies like to ride the line, and it seems legally that with the
current political influence they have the media companies can keep on
moving that line so they don't cross it. The question is, where has the
consumer market set that line?"
My guess: the line is set the *millisecond* there's an alternative that
is in any way viable.
Greg DeKoenigsberg || Fedora Project || fedoraproject.org
Be an Ambassador || http://fedoraproject.org/wiki/Ambassadors
In the bugzilla for my hexter review you mentioned that we should make
a icon/menu entry for hexter (as symlinked to jack-dssi-host) because it
silently fails when jackd isn't running. I agree that this is a
problem. The (hopefully temporary) solution I'm proposing is that we
either mod jack-dssi-host to complain with a dialog box, or we wrap
jack-dssi-host in a script that tests for jackd and pops up a dialog box
complaint if required.
I think having hexter, whysynth, etc in the menu system is worth this
little extra bit of work. Are you (or anybody else) opposed to this
solution? Are either of my proposals better than the other?
(I say "hopefully temporary" because I'm hopeful that one day the jack
api will always be available in the desktop - at least that's what has
suggested in monty's fudcon video).
We're coming up to FC6 test 2. It's nice the basic infrastructure is
getting into FE, like dssi and jack-audio-connection-kit, but what would
be really cool is if some non-trivial apps like ardour, rosegarden and
hydrogen could get accepted into FE prior to the FC6 release. They have
all been submitted to Extras by myself and others, but I don't know how
to make the review process go any faster. Suggestions?