When I start rosegarden, and particularly when I load a sequence, the program seems to scan an excessive number of potential MIDI devices. These are accompanied by many messages of the type RosegardenGUIDoc::syncDevices(). It takes about a minute to perform this scan with my setup. I have a Audigy card with a few ports, and a Midi Express XT (mtpav driver) that makes a whole bunch of ports, which is why this scan takes so long. Is this set of scans necessary? What does it do? It seems like a "sync device" wouldn't even be necessary until a working syncronization feature was implemented. Even then, it would only use one device.
A related problem occurs when I manipulate the "studio". When I make a change to it, I have to wait for another device scan, although it is not as long as when I load the sequence. The studio mechanism also forgets when I remove a device, so when I reload the sequence after trimming my "studio" to the ports that I am actually using, all the unused deleted ports reappear. This phenomenon is probably related to the scan, I would guess. I think the second point is probably an actual bug. On the other hand, the scan itself might be OK for small setups. However, for large MIDI setups (even if only a portion is used in a sequence) the scan is inconvenient. How important is the scan? If it were disabled, how would it affect rosegarden functionality? John ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
