From: Chris C. <ca...@al...> - 2003-06-05 08:28:56
|
Larry Troxler wrote: > On Wednesday 04 June 2003 05:28, Chris Cannam wrote: > >> I don't think the record device is saved to or restored from .rg >> files yet. You would have to set it explicitly after startup. > > I don't understand. As far as the GUI, the setting is indeed saved. I was sort-of right and sort-of wrong here. The setting is not saved in the .rg file; instead it's saved as part of the general settings for the application. In other words, it's saved when you exit or select Save Settings from the settings menu. It has nothing to do with autoload.rg though. But the upshot is that yes, it's saved. >> This is possibly down to a disparity between the way the sequencer >> reports setting the record device on startup and setting it on user >> request. The former is logged to the audit stream (which is what >> you see in the detailed status log), the latter is (by an >> oversight) only logged to stderr. > > I don't understand what you're saying there, in particular, the part > about "setting it on user request". Sorry, what I meant was this: Rosegarden-4 is in two parts, the GUI process and the sequencer process. When you start up the GUI (which is the rosegarden executable), it starts a sequencer process behind the scenes (the rosegardensequencer executable) and that process does some initialisation before synchronising itself with the GUI. That initialisation includes setting a default record device, which is where you see the "Record client set to (64,0" message. However, as part of the sync with the GUI that happens after initialisation, the GUI tells the sequencer process which record device _you_ had selected. (Similarly when you change the record device later while the program's running.) And the sequencer's response to this information is what's only being reported to stderr and not to the audit log. In order to see the sequencer's stderr output, you run the rosegardensequencer executable first (with no arguments) and leave it running in one terminal window while starting rosegarden in another. This way, rosegarden (the GUI) will use the sequencer process you already started instead of starting its own. (This procedure is actually detailed in the FAQ.) > But as it turns out, I see the same "Record client set to (64,0)" in > the output from "rosegardensequencer". Yes, you'll always get that at startup -- but if then start the GUI and keep reading, you should see one or more messages starting AlsaDriver::setRecordDevice - that report the success or failure of any attempt to reset the device to the one you really wanted when the GUI starts up. > So I'm not sure if > rosegaredensequencer is hardwired to read from autoload.rg or not. autoload.rg and the configuration settings that I mentioned earlier are only used by the GUI -- so you need to start the GUI afterwards so it can tell the sequencer what to do. Hope this helps, Chris |