[PlanetCCRMA] yum update

Niels Mayer nielsmayer at gmail.com
Sat Feb 27 16:41:33 PST 2010


On Wed, Feb 24, 2010 at 9:52 PM, Orcan Ogetbil <oget.fedora at gmail.com>wrote:
>
> I will leave it there for another 10 days or so. If there are no
> complaints I will push it to stable.


Now that the latest Qt libs have been updated in F12, I tried out the
rosegarden 'thorn'  release by directly installing the following RPMs
rosegarden4-10.02.1-1.fc12.x86_64.rpm
rosegarden4-feta-fonts-10.02.1-1.fc12.noarch.rpm
rosegarden4-parmesan-fonts-10.02.1-1.fc12.noarch.rpm
.

Initially it crashed very hard, in the process of doing so, it also took
with it all the flash players running in google chrome web browser. By
crashed hard I mean it locked up my console and I had to kill rosegarden
from a different computer. Investigating, it turned out that "studio->midi
through" was selected: there was a MIDI feedback loop from one of my
devices<http://www.qchord.net/>that had been triggered into play mode;
that was outputting it's usual
"rhythm" and causing the MIDI feedback loop. Apparently jack's realtime
support and too much MIDI "kept it real" by not letting any
console/mouse/keyboard events get through so I could kill it locally.

As far as I know, this didn't happen with the stock fedora Rosegarden
because the MIDI through stayed off, once I discovered the joys of the MIDI
feedback loop. The reason for midi-through turning on is that when you load
an external .rg file, you get whatever studio was defined in the file.
Therefore, each time I loaded a file, and started playing, i'd end up
invoking the midi feedback loop. To override this new behavior, I had to
perform an additional step each time I load an external .rg file. (I think
that's a misfeature: overriding studio out of .rg should be an option you
can specify prior to loading a .rg file).

Other than the above issues, rosegarden 10.02.1-1.fc12 seems to be stable
and work well.

One annoyance, is the new behavior of losing the default studio settings
each time you load a demo or a separately distributed .rg file. I've learned
to work-around this by doing "Studio->Import Default Studio" after loading
an external .rg file. And yes, there is a dialog box warning of this change
and "sorry for the inconvenience..." Instead of apologizing, there should be
a suggestion of doing the "Studio->Import Default Studio" to get your old
instrument definitions and connections setup again.

IMHO the new features and updates to rosegarden 10 are worth this small
change in how one operates the software. I am therefore
giving rosegarden4-10.02.1-1.fc12<https://admin.fedoraproject.org/updates/rosegarden4-10.02.1-1.fc12>
positive
karma in the hopes that it soon gets pushed to updates as a stable release.

-- Niels
http://nielsmayer.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ccrma-mail.stanford.edu/pipermail/planetccrma/attachments/20100227/11d82f45/attachment.html 


More information about the PlanetCCRMA mailing list