From: Guillaume L. <gla...@te...> - 2004-11-13 22:57:30
|
Here : http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91.tar.bz2 As usual, please report any problems. -- Guillaume. http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2004-11-14 09:57:58
|
On Saturday 13 Nov 2004 22:57, Guillaume Laurent wrote: > http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91.tar.bz2 0.9.91? What happened to releases 0.9.10 to 0.9.90? Surely 0.9.9.1 or some such? Anyway -- building it now. Chris |
From: Guillaume L. <gla...@te...> - 2004-11-14 10:07:08
|
On Sunday 14 November 2004 11:09, Chris Cannam wrote: > On Saturday 13 Nov 2004 22:57, Guillaume Laurent wrote: > > http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91.tar.bz2 > > 0.9.91? What happened to releases 0.9.10 to 0.9.90? Dunno, I just copied KDE's naming scheme :-) -- Guillaume. http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2004-11-14 10:27:37
|
On Sunday 14 Nov 2004 10:09, Chris Cannam wrote: > Anyway -- building it now. OK, looks good to me. Let's see how others find it. Chris |
From: Pedro Lopez-C. <pl...@te...> - 2004-11-14 13:07:46
|
On Saturday 13 November 2004 23:57, Guillaume Laurent wrote: > Here : > > http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91.tar.bz2 > > As usual, please report any problems. Builds, and works for me. BTW, here you can find a traditional song from Catalonia, imported from an arrangement I made a long time ago. Its name is "El cant dels ocells" (The song of the birds): http://perso.wanadoo.es/plcl/music/ocells.rg Problems I've found. First, the cello solo is recorded with my EWI3000 wind controller that sends breath intensity as aftertouch events. You can't edit the channel aftertouch events like a controller or velocity, with an event ruler. I will open a RFE for this feature. The sysex event sent at beginning makes my SC88 to recognize aftertouch events and translate it to volume amounts. Second, the track labelled as "portamento events" has controllers for the cello track. I want to keep these events alone in its own track, because sometimes i want to mute them. There are two possible RFE's regarding this: 1. Edit a track, and open an event ruler belonging to another track. 2. More MIDI filters, to ignore only some controller numbers. What do you think about it? Regards, Pedro |
From: Silvan <dmm...@us...> - 2004-11-14 22:16:34
|
On Sunday 14 November 2004 08:09 am, Pedro Lopez-Cabanillas wrote: > Second, the track labelled as "portamento events" has controllers for the > cello track. I want to keep these events alone in its own track, because > sometimes i want to mute them. There are two possible RFE's regarding this: > 1. Edit a track, and open an event ruler belonging to another track. > 2. More MIDI filters, to ignore only some controller numbers. > > What do you think about it? Can't you just edit them on their own track? (Assign them to the same device/instrument.) Am I missing something? (I didn't go get the file in question yet.) Being able to open a ruler for events on another track or maybe even use one track to send controllers to several different devices or whatever (ye olde conductor track) would be the Cakewalkesque thing to do for sure, but I think it's probably antithetical to the way RG is designed. Dunno, I don't have any deep thoughts at the moment. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Pedro Lopez-C. <pl...@te...> - 2004-11-14 22:48:10
|
On Sunday 14 November 2004 23:16, Silvan wrote: > Can't you just edit them on their own track? (Assign them to the same > device/instrument.) That is what i am doing now. The problem is that portamento is very related to the note events, so it is very important to see both at a time. What I do is to open two matrix views: one at top with the solo track and one at bottom with the portamento controllers. They keep in sync when playing, but you must synchronize it by hand for edition. Regards, Pedro |
From: Silvan <dmm...@us...> - 2004-11-14 22:53:02
|
On Sunday 14 November 2004 05:50 pm, Pedro Lopez-Cabanillas wrote: > On Sunday 14 November 2004 23:16, Silvan wrote: > > Can't you just edit them on their own track? (Assign them to the same > > device/instrument.) > > That is what i am doing now. The problem is that portamento is very related > to the note events, so it is very important to see both at a time. What I Yeah, I guess it would be. I wasn't thinking too clearly. (Hey, I'm still not. I'm tired. I spent all day yesterday at a Lego robotics competition with my son. I walked at least 40 miles and wore the soles off four pairs of shoes. Their team won the regional competition and are going to the state-wide finals though.) > do is to open two matrix views: one at top with the solo track and one at > bottom with the portamento controllers. They keep in sync when playing, but > you must synchronize it by hand for edition. I think there is a multi-segment matrix on the books, slated to be done sooner than later. Might this be just the ticket? -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Pedro Lopez-C. <pl...@te...> - 2004-11-15 22:19:24
|
On Sunday 14 November 2004 23:52, Silvan wrote: > On Sunday 14 November 2004 05:50 pm, Pedro Lopez-Cabanillas wrote: > > do is to open two matrix views: one at top with the solo track and one at > > bottom with the portamento controllers. They keep in sync when playing, > > but you must synchronize it by hand for edition. > > I think there is a multi-segment matrix on the books, slated to be done > sooner than later. Might this be just the ticket? Yes. I guess you mean this one: [ 931029 ] Matrix: Editing multiple tracks simultaneously like notation William proposed it thinking on notes, but it applies for other event types, too. Regards, Pedro |
From: Guillaume L. <gla...@te...> - 2004-11-17 19:50:47
|
New candidate tarball available : http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 In particular, could our worthy testers check if the matrix selector tool behaves properly while auto-scrolling ? (we know that autoscrolling confuses other tools, this will be corrected when the fix for the matrix selector is validated). Thanks, -- Guillaume. http://www.telegraph-road.org |
From: oota t. <ri...@us...> - 2004-11-17 22:34:05
|
On Wed, Nov 17, 2004 at 08:50:58PM +0100, Guillaume Laurent wrote: > New candidate tarball available : > > http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 I update translation currently. What time will the last deadline of release be? I am glad that deadline time is after Sunday because there is time to translate. oota |
From: Guillaume L. <gla...@te...> - 2004-11-17 22:44:29
|
On Wednesday 17 November 2004 23:33, oota toshiya wrote: > > What time will the last deadline of release be? > I am glad that deadline time is after > Sunday because there is time to translate. The deadline's not fixed, but I'd have hoped that we would do the release a bit before next sunday. Saturday would be good. -- Guillaume. http://www.telegraph-road.org |
From: Francois I. <isa...@sy...> - 2004-11-28 15:05:03
|
Guillaume Laurent wrote: >New candidate tarball available : > >http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 > >In particular, could our worthy testers check if the matrix selector tool >behaves properly while auto-scrolling ? (we know that autoscrolling confuses >other tools, this will be corrected when the fix for the matrix selector is >validated). > >Thanks, > > > The french translation is still incomplete, I can try to send a patch, but I'm not a professionnal translator. Are the french contributor active at this time ? Frank |
From: Helio C. de C. <he...@kd...> - 2004-11-17 20:52:11
|
Hey,=20 Please up the version number for 0.9.92 :-) Em Qua 17 Nov 2004 17:50, Guillaume Laurent escreveu: > New candidate tarball available : > > http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 > > In particular, could our worthy testers check if the matrix selector tool > behaves properly while auto-scrolling ? (we know that autoscrolling > confuses other tools, this will be corrected when the fix for the matrix > selector is validated). > > Thanks, =2D-=20 Helio Chissini de Castro KDE Project South America Primary Contact Curitiba - Brasil |
From: Chris C. <ca...@al...> - 2004-11-17 21:06:46
|
On Wednesday 17 Nov 2004 20:52, Helio Chissini de Castro wrote: > Please up the version number for 0.9.92 Huh? We haven't had 0.9.91 yet, just two release candidates. Man, how I wish Guillaume hadn't bizarrely decided to copy the KDE release numbering (at least, that's what he said he was doing). This tarball is really 0.9.9.1rc2 by any sane scheme. The next release that actually gets to SourceForge will be 0.9.9.1, except that it appears it's going to be 0.9.91. Either way, the rc tarballs can be called whatever we like, as nobody should be packaging them. Chris |
From: Guillaume L. <gla...@te...> - 2004-11-17 21:26:31
|
On Wednesday 17 November 2004 22:06, Chris Cannam wrote: > > Man, how I wish Guillaume hadn't bizarrely decided to copy the KDE release > numbering (at least, that's what he said he was doing). This tarball is > really 0.9.9.1rc2 by any sane scheme. The next release that actually gets > to SourceForge will be 0.9.9.1, except that it appears it's going to be > 0.9.91. Well, consider the amount of bugfixing that went into 0.9.9. Does this really feels like a .1 release ? We're getting fairly close to 1.0, I still feels 0.9.91 is a better version number. Just looks cooler. 0.9.9.1 looks whiny. -- Guillaume. http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2004-11-17 21:31:24
|
On Wednesday 17 Nov 2004 21:26, Guillaume Laurent wrote: > Well, consider the amount of bugfixing that went into 0.9.9. Does > this really feels like a .1 release ? We're getting fairly close to > 1.0, I still feels 0.9.91 is a better version number. That's a lousy excuse, or a lousy case of post-rationalisation. Call it 0.9.9.5 or 0.9.9.9 then. Or 1.0pre1rc2. Would anyone here actually object if we did this series of release candidates, just enough to establish there weren't any hugely embarrassing bugs, and then labelled the resulting release 1.0? Then we could have a party. Chris |
From: Guillaume L. <gla...@te...> - 2004-11-17 21:46:11
|
On Wednesday 17 November 2004 22:42, Chris Cannam wrote: > On Wednesday 17 Nov 2004 21:26, Guillaume Laurent wrote: > > Well, consider the amount of bugfixing that went into 0.9.9. Does > > this really feels like a .1 release ? We're getting fairly close to > > 1.0, I still feels 0.9.91 is a better version number. > > That's a lousy excuse, or a lousy case of post-rationalisation. > > Call it 0.9.9.5 or 0.9.9.9 then. Or 1.0pre1rc2. Helio discouraged us from using 1.0pre1, and, honestly, 4 subdigits look a bit too much for a version number. It's just confusing. > Would anyone here actually object if we did this series of release > candidates, just enough to establish there weren't any hugely > embarrassing bugs, and then labelled the resulting release 1.0? > > Then we could have a party. Nah, I only have a couple bugs left to fix (autoscrolling behaving properly with tools, and that problem with the matrix canvas being too small in some cases), but these might take a while. Please let's have this release first. -- Guillaume. http://www.telegraph-road.org |
From: Chris C. <ca...@al...> - 2004-11-17 21:48:57
|
On Wednesday 17 Nov 2004 21:46, Guillaume Laurent wrote: > On Wednesday 17 November 2004 22:42, Chris Cannam wrote: > > Would anyone here actually object if we did this series of release > > candidates, just enough to establish there weren't any hugely > > embarrassing bugs, and then labelled the resulting release 1.0? > > > > Then we could have a party. > > Nah, I only have a couple bugs left to fix (autoscrolling behaving > properly with tools, and that problem with the matrix canvas being > too small in some cases), but these might take a while. Please let's > have this release first. Oh well, it was an interesting if short-lived "what-if" experiment. I'll just have to have the party on my own. Chris |
From: Pedro Lopez-C. <pl...@te...> - 2004-11-17 22:17:53
|
On Wednesday 17, Chris Cannam wrote: > > > Then we could have a party. Next Monday, November 22, its the day of St. Cecilia for the Roman Catholic church. She is the patroness of musicians. It can be an excuse for a release date, or for a party. http://www.catholic.org/saints/saint.php?saint_id=34 Regards, Pedro |
From: Toni A. <ton...@bl...> - 2004-11-21 13:32:58
|
> http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 After installing RC2 on my gentoo box (it compiles without errors now :-), I have serious trouble with USB-MIDI: The first playback device seems to be broken (no MIDI output). With 0.9.9 there was no such problem. The problem is somwehat complex, and I don't know exactly what would be the expected behaviour in conjunction with qjackctl. But what I know is that after playing too much around, also the 2nd playback device has no sound no more, and a reboot of the box helps. Environment =========== Program versions ---------------- Distro: Gentoo stable Kernel: gentoo-dev-sources 2.6.9-r4 RG: http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 alsa-lib 1.0.6 jack-audio-connection-kit: 0.99.0 qjackctl 0.2.9 vkeybd 0.1.15 Relevant Hardware ----------------- 2 x MidiSport 2x4, showing up as device 80 and 88; Playback device 1 is on 80:2 Playback device channel 1, (with omni on), 80:1 is not connected. Steps to reproduce ================== A) Test environment without RG ------------------------------ start qjackctl via Alt&F2 start vkeybd via Alt&F2 qjackctl: Connect Virtual KeyBoard to Playback Device: 129:0 Virtual Keyboard |- 0: Virtual Keyboard --to-- 80: MidiSpoirt 2x4 - Rawmidi 2 |- 2: MidiSport 2x4 MIDI 3 Play with the mouse on vkebd and have some limited amount of fun ;-) -> Anything OK up to now. B) Bring in RG -------------- start rosegarden via Alt&F2 -> RG shows up as Writeable Client 130:Rosegarden |- 0:Rosegarden input -> don't touch it, bring vkeybd to front Play with the mouse on vkebd and have no fun at all :-( -> Although still connected as in A), no sound on the Playback device. close RG -> RG disappears from qjackctl as expected. Play with the mouse on vkebd and have no fun at all :-( -> Although still connected as in A), no sound on the Playback device. C) Verify reproducability until now ----------------------------------- close vkeybd close qjackctl back to square A) -> Steps A) to B) seem to be (sometimes?) reproducable. It seems not always to be needed to restart jack. D) Deeper inquiry: bring in a second playback device ---------------------------------------------------- qjackctl: Connect Virtual KeyBoard to Playback Device 2: 129:0 Virtual Keyboard |- 0: Virtual Keyboard --to-- 80: MidiSpoirt 2x4 - Rawmidi 2 |- 2: MidiSport 2x4 MIDI 2 Switch Device 2 to MIDI Channel 1 (for vkeybd) Play with the mouse on vkebd and have some limited amount of fun ;-) -> Device 2 is OK, Device 1 still muted. E) Play around with RG ---------------------------------------------------- The 1st Device can never be used with existing compositions (no MIDI, no matter whether I start RG with jack or without jack), the 2nd device works for playback. -> Exchanging the 2 devices in RG. -> The 2nd Device still works, it seems that the 1st device listed in qjackctl gets broken (no Idea which ordering is relevant here). The more I play around with RG, the more devices I seem to loose (I have 3 of them). Before sending this mail, I had no sound no more of device 2, saved the .rg file, rebooted, had still no sound out of device 1 as before, but device 2 worked again. --> ??? |
From: Silvan <dmm...@us...> - 2004-11-21 16:20:32
|
On Sunday 21 November 2004 08:32 am, Toni Arnold wrote: > > http://www.telegraph-road.org/rosegarden/rosegarden-4-0.9.91rc2.tar.bz2 > > After installing RC2 on my gentoo box (it compiles without errors now :-), > I have serious trouble with USB-MIDI: > The first playback device seems to be broken (no MIDI output). With 0.9.9 > there was no such problem. The problem is somwehat complex, and I don't > know exactly what would be the expected behaviour in conjunction with > qjackctl. But what I know is that after playing too much around, also the > 2nd playback device has no sound no more, and a reboot of the box helps. The expected behavior in conjunction with qjackctl is that if you use qjackctl to arrange MIDI connections, you can expect obnoxious things to happen with Rosegarden. I'm not sure to what extent you should *expect* trouble arranging things before starting Rosegarden, but you can *avoid* trouble, and can keep the set of problems we have to look at in sorting out any real or imagined bug by using Rosegarden exclusively to manage MIDI connections while you are using (or are about to be using) Rosegarden. Use qjackctl to manage audio connections, use Rosegarden to manage MIDI connections. We realize that is inconsistent, but that's the way it needs to be done at the moment. If you still have problems using only Rosegarden to manage MIDI connections, then we have something further to look at. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Toni A. <ton...@bl...> - 2004-11-21 19:33:15
|
> If you still have problems using only Rosegarden to manage MIDI > connections, then we have something further to look at. That's what I think is needed - or I'm having a really strange day today. The order of my steps in the last mail resulted out of the following history. Then I'll give some other order of steps to reproduce the problem which don't involve qjackctl in an early stage. Before I tried all that business with vkeybd, I was *absolutely sure* that the MIDI-cable was broken. Then I switched the MidiSport to hardware routing and I was *absolutely sure* that not the MIDI-cable was broken (as it worked), but that the MIDI interface itself had a problem. Thus I rebootet with win2k and verified that under windoze the piano made sound at the port it was expected to do so. Then I was not sure no more about nothing and began to try things out. To give another, precise order to reproduce that weird problem: [A] - reboot machine - start rosegarden via Alt&F2 With this default studio (partially): Manage Midi devices -> Play Devices: 80:2 MidiSport 2x4 MIDI 3 (write) <-- piano 80:1 MidiSport 2x4 MIDI 2 (duplex) <-- synth 88:2 MidiSport 2x4 MIDI 3 (write) ... Record Decices: 80:0 MidiSport 2x4 MIDI 1 (duplex) <-- piano ... piano is the instrument I'm interested in. - Press Record Button, play something Records track 1 piano (80:2 MidiSport 2x4 MIDI 3) -> notes visible within RG - Press the Play button RG plays, bar over the track number "1" is nicely animated. -> But no sound from the piano. (Possible reason: 80:2 MidiSport 2x4 MIDI 3 (write) physically not connected to the piano). - Change instrument for Track 1 to above synth - Press the Play button -> Synth is making noise from a track not intendet for it. => conclusion: 80:x MidiSport working for input and output -> Only possible reason causing the failure: "80:2 MidiSport 2x4 MIDI 3 (write) physically not connected to the piano." - Close RG [B] - start qjackctl via Alt&F2 - start vkeybd via Alt&F2 qjackctl: Connect Virtual KeyBoard to Playback Device: 129:0 Virtual Keyboard |- 0: Virtual Keyboard --to-- 80:2: MidiSport 2x4 MIDI 3 (above claimed piano) - klick some keys -> no sound. => double conclusion: The claim "80:2 MidiSport 2x4 MIDI 3 (write) physically not connected to the piano." has been proven to be true. -> Back to [B] again to be really sure. -> verified [C] - logout - login again (with the same account) - back to square [B] - klick some keys -> sound! sound! soooouuuuund!!!!!!!! => double conclusion has been proven to be false. Ok. Hold on. Close qjackctl, terminate jack server, logout, login. -> Back to square [A] (without rebooting) -> Anything is reproducable. |
From: Silvan <dmm...@us...> - 2004-11-23 02:58:37
|
On Sunday 21 November 2004 02:31 pm, Toni Arnold wrote: > That's what I think is needed - or I'm having a really strange day today. > The order of my steps in the last mail resulted out of the following > history. Then I'll give some other order of steps to reproduce the problem > which don't involve qjackctl in an early stage. OK, thanks for narrowing the focus of the problem. Now I have to say, unfortunately, I have no idea what to suggest next. I've never done any USB MIDI stuff, and can only imagine what might be going wrong. You'll have to wait until someone else notices this thread, I'm afraid. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Toni A. <ton...@bl...> - 2004-12-19 15:17:53
|
Still exactly the same problem with 1.0pre1. Am Sonntag, 21. November 2004 17.19 schrieb Silvan: > ... and can keep the set > of problems we have to look at in sorting out any real or imagined bug by > using Rosegarden exclusively to manage MIDI connections while you are using > (or are about to be using) Rosegarden. Am Dienstag, 23. November 2004 03.58 schrieb Silvan: > .... and can only imagine what might be going wrong. You'll > have to wait until someone else notices this thread, I'm afraid. I think that it is something like a bug - or at least a problem that should be solved on the RG side, as it was introduced with 0.9.91. Should I enter it into the bug tracker such that someone else notices? To repeat: When rosegarden starts up, the Kawai-ES-3 produces no sound no more (with qjackctl and vkeybd or via an external device directly routed through the midi-interface, bypassing the computer) until I logout and login into a new KDE session. I have the impression that the problem affects only that particular instrument. But I was able to narrow down the problem even more: If I unplug the cable connected to the Kawai's Midi-In connector before I start rosegarden and, after RG started up, plug in again, everything works as it should. But that cannot be the final solution :-( Another possiblity to solve the problem: If I turn the piano off for a second and then on again after RG started up, it produces sound again. But that cannot be the final solution either (but it will at least not damage the connector over time). One possible reason I thought could be the fact that for allmost any device definition xml-files (including the one I did for the Kawai-ES-3) has a default value of 0 for volume, but that seems not to be relevant (in the Instrument parameter panel, Volume seems to be always max, and turning the knob doesn't change anything.) Nevertheless, rosegarden seems to send some midi events to the attached Kawai that causes it to be muted. I can't look inside my piano, so I can't tell what it is. Any control values that I can see are normal (channel etc.). What I can tell is that the piano still reacts normally when some keys are hit, but it doesn't respond no more to midi note on events, regardless of where they come from. (Another story is: what does KDE send to it to wake it up again when I log out??) I don't know how to lock the console line by line, and with fast double-hitting the "Scroll Lock"-Key, I can only give the rough position in RG's startup output where the malicious event happens: PluginFactory::instance(ladspa): creating new LADSPAPluginFactory [/usr/lib/ladspa] ... ok rosegarden: RosegardenGUIDoc::openDocument(/home/tarnold/.kde3.3/share/apps/rosegarden/autoload.rg) rosegarden: RosegardenGUIDoc[0x88a5c18]::setModified(false) rosegarden: RosegardenProgressDialog::RosegardenProgressDialog type 2 - Datei wird gelesen... - modal : true ... ok rosegarden (sequencer): createMappedObject - type = 1, object id = 4 rosegarden (sequencer): createMappedObject - type = 1, object id = 5 ... ??? -------- somewhere here the piano gets muted --------- ??? ... rosegarden (sequencer): processMappedEvent(ev) - sending out single event at time 0.000000000R rosegarden (sequencer): processMappedEvent(ev) - sending out single event at time 0.000000000R The full output where the problem happens looks like this: rosegarden (sequencer): createMappedObject - type = 1, object id = 4 rosegarden (sequencer): createMappedObject - type = 1, object id = 5 rosegarden (sequencer): createMappedObject - type = 1, object id = 6 rosegarden (sequencer): createMappedObject - type = 1, object id = 7 rosegarden (sequencer): createMappedObject - type = 1, object id = 8 rosegarden (sequencer): createMappedObject - type = 1, object id = 9 rosegarden (sequencer): createMappedObject - type = 1, object id = 10 rosegarden (sequencer): createMappedObject - type = 1, object id = 11 rosegarden (sequencer): createMappedObject - type = 1, object id = 12 rosegarden (sequencer): createMappedObject - type = 1, object id = 13 rosegarden (sequencer): createMappedObject - type = 1, object id = 14 rosegarden (sequencer): createMappedObject - type = 1, object id = 15 rosegarden (sequencer): createMappedObject - type = 1, object id = 16 rosegarden (sequencer): createMappedObject - type = 1, object id = 17 rosegarden (sequencer): createMappedObject - type = 1, object id = 18 rosegarden: RosegardenGUIDoc::initialiseStudio - initialised studio including 16 audio faders rosegarden (sequencer): processMappedEvent(ev) - sending out single event at time 0.000000000R rosegarden: RosegardenGUIDoc[0x88a6030]::setModified(false) rosegarden (sequencer): processMappedEvent(ev) - sending out single event at time 0.000000000R ... ... many, many of this suspicious anonymous "single event"s ... rosegarden (sequencer): processMappedEvent(ev) - sending out single event at time 0.000000000R |