Tom: What did you do that can make it keep the original settings?
I loaded the file (but the way it was saved originally was using Qsynth), as you observed. So using Manage MIDI Devices, I set General MIDI Device to Timidity port 0, remembering that it seems to remember the settings between pieces. Then I loaded another of the pieces, and it did indeed remember Timidity Port 0, but all of the Pan and Volume settings were still gone. I tried re-loading the original piece now (with Timidity Port 0 set), and on loading it showed the device as Timidity Port 0, but still, all of the Pan and Volume settings (from the original) were lost, replaced by somewhat standard values. If I had a work-around, I could load them (preserving the original settings), then re-save them with the new level, and it seems to load okay once I have saved them with the new level. I do remember sometime back, when I would create a new track, I would record into it, seeing the note-marks in the segment, then play it back, hearing nothing. This puzzled me until I noticed that the volume setting of all newly-created tracks were set to zero for some reason, so I changed it, and the track played fine. Could your seeing different results with Timidity have something to do with the Preferences setting "Always use default studio when loading files"? In mine, I do not check that. If I selected that option, might it work as you described? I don't want to use that option, because I worry it would change sequences that used a very different setup. Could it have something to do with the "Channel" setting of "Auto" or "Fixed"? The old level didn't have that selection, so it wouldn't have saved it. Perhaps not seeing that expected specification might cause it to reset values to something 'sane'. I noticed in the bank-definition XML files, that the device information specified what controls were used. I have seen older ones that didn't have the "Expression" control, and other devices that did. I worry that this problem can be very insidious, where a user loads their old pieces, quickly plays a few of them to see if they played, concluding the new level is working. But if they do a "Save" on it (possibly because they changed the MIDI device used) they would lose the "Pan" settings, and the finely-tuned volume settings, not knowing they lost them. Maybe months later, they would see the Pan settings gone, and wonder how they lost them, and why the volume levels don't seem to be balanced quite right any more. - Aere On Sun, 2012-10-21 at 22:40 -0400, Tom Breton (Tehom) wrote: > I haven't solved the problem, but I have found out what makes the > difference in the savefile: The "connection" field of the XML "device" > statement. > > That's probably specific to what sound card etc one has. Here, the > original value "129:0 Synth input port (2067:0) (write)" shows the bug, > while "128:0 TiMidity port 0 (write)" does not (and is something my setup > writes to savefile) > > I don't think that's because "Synth input" is bad; I suspect that when it > doesn't match hardware settings it causes resetting the device connection > when the file is loaded. Which isn't itself wrong, but somehow that > resets Instrument controllers, though it *should* only reset insane Device > defaults (like the expression=0 bug that it fixed) > > Tom Breton (Tehom) > > -- Sincerely, AereSincerely, Aere Sincerely, Aere ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
