From: <no...@ro...> - 2009-07-29 15:28:20
|
A page in your DokuWiki was added or changed. Here are the details: Date : 2009/07/29 15:27 Browser : Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4pre) Gecko/20090401 Ubuntu/9.04 (jaunty) Shiretoko/3.5b4pre IP-Address : 127.0.0.1,138.37.33.56 Hostname : localhost,research-dhcp56.elec.qmul.ac.uk Old Revision: http://rosegardenmusic.com/wiki/dev:device_management_and_replacing_auto-connect?rev=1248881072 New Revision: http://rosegardenmusic.com/wiki/dev:device_management_and_replacing_auto-connect Edit Summary: User : cannam @@ -1,4 +1,5 @@ + ===== Device Management (in Thorn), and Replacing the Unwanted Auto-Connect ===== Rosegarden 1.7.x has quite a strange device management system, in which devices (meaning: virtual things within the Rosegarden document, that can be connected to external MIDI hardware ports or software programs) are created "on demand" by Rosegarden itself, connected up automatically, and so on. Devices in 1.7.x exist in two places -- there is a device record within the document in the GUI process (base/Studio), and a mapped device record within the sequencer process. The sequencer's list is actually the authoritative one in 1.7.x, and at various pivotal moments it will contact the GUI and ask it to re-pull the list of devices from the sequencer (RosegardenGUIDoc::syncDevices()). So when, for example, the user adds a device from within the device manager dialog, the add-device command (in the GUI) both adds a device to the studio and pushes a device to the sequencer; the sequencer then requests a re-pull; and the document pulls back the list of devices, hopefully matching the list it already has. When a new device is created at the sequencer side (as happens automatically when a new ALSA client becomes visible, for example), the sequencer requests a re-pull and the document pulls back the list which now contains a device it did not already have. -- This mail was generated by DokuWiki at http://rosegardenmusic.com/wiki/ |