<div class="gmail_quote">On Wed, Feb 24, 2010 at 9:52 PM, Orcan Ogetbil <span dir="ltr"><<a href="mailto:oget.fedora@gmail.com">oget.fedora@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I will leave it there for another 10 days or so. If there are no<br>
complaints I will push it to stable.</blockquote><div><br></div><div>Now that the latest Qt libs have been updated in F12, I tried out the rosegarden 'thorn' release by directly installing the following RPMs</div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px;"><div>
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 .</div><div><br></div><div>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 <a href="http://www.qchord.net/">one of my devices</a> 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.</div>
<div><br></div><div>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).</div>
<div><br></div><div>Other than the above issues, rosegarden 10.02.1-1.fc12 seems to be stable and work well. </div><div><br></div><div>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.</div>
<div><br></div><div>IMHO the new features and updates to rosegarden 10 are worth this small change in how one operates the software. I am therefore</div><div>giving <span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; "><a href="https://admin.fedoraproject.org/updates/rosegarden4-10.02.1-1.fc12" target="_blank" style="color: rgb(28, 81, 168); ">rosegarden4-10.02.1-1.fc12</a> positive karma in the hopes that it soon gets pushed to updates as a stable release.</span></div>
<div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; ">-- Niels</span></div><div>
<span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; "><a href="http://nielsmayer.com">http://nielsmayer.com</a></span></div></span></span></font></div></div>