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 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
