From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-19 02:29:35
|
All: I just got some of my Lubuntu 12.04 systems upgraded to 12.10, and as part of that testing, tested Rosegarden. The version of Rosegarden that comes with Lubuntu 12.10 is Rosegarden 12.04. The first test I ran was to play one of my demo-pieces, and it seemed the piece was poorly balanced (the relative volume of the different instruments was poorly adjusted). On further investigation, I found that the settings of the knob-controls at the bottom of the Instrument Parameters pane, were different from what was loaded from the file (and worked properly in the earlier version). Apparently, the "Pan" controls were all set to center (64?), and the "Volume" controls were all set to 100, which is different from what was saved in the ".rg" file (and worked properly in the prior release). I do have the configuration parameter set to send the control values at the beginning of playback, but that was also the case with the earlier version, and the proper volume and pan values were used in playing the sequence. I found that (using Rosegarden 12.04) if I changed the most-wrong volume knob to what it was supposed to be, Rosegarden did not notice that the sequence data had been changed. But if I saved it, and re-loaded it, it did get the proper initial volume setting. It was disappointing that all of the "Pan" settings got reset to 64, since I had spent time getting the instrument-placement just right, and now all of that work gets discarded by the new version. I have a recent development version of Rosegarden, and checked if that version has the same problem, and unfortunately, it does. It also loses the initial volume and pan settings from what is loaded from the ".rg" file. -- Sincerely, Aere |
From: D. M. M. <ros...@gm...> - 2012-10-19 10:21:15
|
On 10/18/2012 10:29 PM, Aere Greenway wrote: > It was disappointing that all of the "Pan" settings got reset to 64... I copied your message text over and opened bug #1364. This issue sounds tantalizingly familiar, but I can't quite read the hint this is trying to show me. -- D. Michael McIntyre |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-19 16:30:40
|
Michael: I appreciate very much that you're looking into this. Since it seems to be able to save such settings, and re-load them from the file (all in the new level), I'm wondering if it's a problem in loading a sequence from an older-level file format, or perhaps the information is saved (now) at a later point in the file, so it gets acted-upon after the channels have been initialized (rather than before that happens). I was pleased to see that in the new level going out with Ubuntu 12.10, that there were demo-pieces that I had contributed (and contributed-to). That was a good feeling for me. Thanks again for all the work you have done for us over the years (in creating and maintaining Rosegarden). - Aere On Fri, 2012-10-19 at 06:21 -0400, D. Michael McIntyre wrote: > On 10/18/2012 10:29 PM, Aere Greenway wrote: > > > It was disappointing that all of the "Pan" settings got reset to 64... > > I copied your message text over and opened bug #1364. > > This issue sounds tantalizingly familiar, but I can't quite read the > hint this is trying to show me. -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-19 17:11:10
|
Aere: Thank you for the bug report. There are a few things I don't understand about it. > The first test I ran was to play one of my demo-pieces, and it seemed > the piece was poorly balanced (the relative volume of the different > instruments was poorly adjusted). > > On further investigation, I found that the settings of the knob-controls > at the bottom of the Instrument Parameters pane, were different from > what was loaded from the file (and worked properly in the earlier > version). > > Apparently, the "Pan" controls were all set to center (64?), and the > "Volume" controls were all set to 100, which is different from what was > saved in the ".rg" file (and worked properly in the prior release). I just checked and at least here, we're definitely reading saved pan settings. Not just defaults, stuff like pan = 57. So I wonder what's different in that situation. Being reset to defaults (rather than to 0) seems like a clue. That is something we're doing differently now in refreshForConnection / conformInstrumentControllers (my responsibility, including fixing it if it's at fault). But it doesn't reset settings in general, it only does anything if you change MIDI devices and a device parameter appears to be on a default setting (ie, it's zero and the new device default is not zero). But that doesn't seem to apply. You said you had saved pan settings (etc), presumably not all zero. And it would only happen if your demo file changed what device you're playing on (Eg, it output to a different sound card than what you were sending MIDI to before you loaded that savefile). So my theory seems to be a bust, but I have no other theory. > I do have the configuration parameter set to send the control values at > the beginning of playback, but that was also the case with the earlier > version, and the proper volume and pan values were used in playing the > sequence. OK, I'm not sure what to make of this. > I found that (using Rosegarden 12.04) if I changed the most-wrong volume > knob to what it was supposed to be, Rosegarden did not notice that the > sequence data had been changed. Do you mean that RG did not consider the document modified, so it didn't prompt to save on quit, etc? It always has. Which may be wrong, but hard to fix. > But if I saved it, and re-loaded it, it > did get the proper initial volume setting. > > It was disappointing that all of the "Pan" settings got reset to 64, > since I had spent time getting the instrument-placement just right, and > now all of that work gets discarded by the new version. That does sound annoying. Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2012-10-19 19:23:38
|
On 10/19/2012 01:11 PM, Tom Breton (Tehom) wrote: > But it doesn't reset settings in general, it only does anything if you > change MIDI devices and a device parameter appears to be on a default > setting (ie, it's zero and the new device default is not zero). > > But that doesn't seem to apply. You said you had saved pan settings > (etc), presumably not all zero. And it would only happen if your demo > file changed what device you're playing on (Eg, it output to a different > sound card than what you were sending MIDI to before you loaded that > savefile). I don't have time to get into it, but this makes me wonder what happens when you load an existing file and doctor it so it will play on your current setup a couple years later. Such doctoring is extremely common, and shouldn't cause all the controllers to reset to default values. I bet we don't make any attempt to preserve values though, and every different device definition you load could have different controllers. Let's say you had "Roland SC-33" loaded in the top slot, and you change it to "General MIDI" or something. It happens to have most of the same controllers, but does Rosegarden know and do anything about that? What *should* happen to pan and volume? Pan, volume, reverb and chorus are four legacy controllers that were originally treated differently too. No suggestions here, no looking at anything or experimentation, just idle pondering on my way out the door and nothing more. -- D. Michael McIntyre |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-19 19:46:53
|
Michael: I should have sent my reply to the whole group, instead of just to Tom. I didn't want to send my (attached) piece out to everybody, so I only replied to him, where he would need something to test the problem & fix with. My reply was: Tom: I have attached a Rosegarden ('.rg') file that was used successfully by the prior level of Rosegarden (11.11.42). The pan and volume settings for the tracks, as loaded and observed in the prior level of Rosegarden (11.11.42), are (as they should be): Track 2 (53. Choir Aahs), Pan=50, Volume=109 Track 3 (69. Oboe), Pan=80, Volume=110 Track 4 (74. Flute), Pan=80, Volume=104 Track 5 (99. FX 3 (crystal)), Pan=40, Volume=81 Track 6 (49. String Ensemble 1), Pan=64, Volume=127 Track 8 (1. Acoustic Grand Piano), Pan=64, Volume=117 Track 9 (49. String Ensemble 1), Pan=64, Volume=41 The pan and volume settings for the tracks, as loaded and observed in Rosegarden development version (12.12), are: Track 2: pan=64, volume=100 Track 3: pan=64, volume=100 Track 4: pan=64, volume=100 Track 5: pan=64, volume=100 Track 6: pan=64, volume=100 Track 8: pan=64, volume=100 Track 9: pan=64, volume=100 The thing that made me notice this problem, is that tracks 8 and 9 constitute what I call a "composite voice", in this case, to sound similar to the "Piano Strings" voice of the Yamaha S90-es synthesizer the piece was composed on. The piano part is normal volume, but the strings voice (a hint of strings in the background) is less than half-volume. The segments of the two tracks are the same. When I played the piece (doing verification testing on Lubuntu 12.10), I immediately noticed the string part (track 9) was way too loud. Please let me know if you need any further clarification, or information. - Aere On Fri, 2012-10-19 at 15:23 -0400, D. Michael McIntyre wrote: > On 10/19/2012 01:11 PM, Tom Breton (Tehom) wrote: > > > But it doesn't reset settings in general, it only does anything if you > > change MIDI devices and a device parameter appears to be on a default > > setting (ie, it's zero and the new device default is not zero). > > > > But that doesn't seem to apply. You said you had saved pan settings > > (etc), presumably not all zero. And it would only happen if your demo > > file changed what device you're playing on (Eg, it output to a different > > sound card than what you were sending MIDI to before you loaded that > > savefile). > > I don't have time to get into it, but this makes me wonder what happens > when you load an existing file and doctor it so it will play on your > current setup a couple years later. Such doctoring is extremely common, > and shouldn't cause all the controllers to reset to default values. > > I bet we don't make any attempt to preserve values though, and every > different device definition you load could have different controllers. > Let's say you had "Roland SC-33" loaded in the top slot, and you change > it to "General MIDI" or something. It happens to have most of the same > controllers, but does Rosegarden know and do anything about that? What > *should* happen to pan and volume? > > Pan, volume, reverb and chorus are four legacy controllers that were > originally treated differently too. > > No suggestions here, no looking at anything or experimentation, just > idle pondering on my way out the door and nothing more. -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-19 22:02:42
|
Aere: Thank you for the file. I can reproduce the problem here, but I have no idea what causes it. I re-saved it - restores OK onder 12.04 - and diffed the resulting files. There were about 192 diff regions to make sense of, so take this with a grain of salt, but with the help of ediff I think I scanned all the relevant ones. The one suspicious thing is that the old version file sets device default volume to 0, new version sets it to 100. That might trigger a "fix", but why should it affect the pan settings? I will experiment further and let you know if I find out anything. Tom Breton (Tehom) |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-19 22:06:43
|
> The one suspicious thing is that the old version file sets device default > volume to 0, new version sets it to 100. That might trigger a "fix", but > why should it affect the pan settings? > > I will experiment further and let you know if I find out anything. > > Tom Breton (Tehom) I experimented, and all I learned is that that's not it. In a copy, I manually edited those 0 defaults to 100's and loaded it. Nothing changed. So there goes my last hypothesis. Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2012-10-20 08:09:28
|
On 10/19/2012 06:02 PM, Tom Breton (Tehom) wrote: > I re-saved it - restores OK onder 12.04 Apparently he only sent the file to you, and/or there's a copy in the moderation queue. Either way, I can't get my hands on it directly. I doubt I will have some brilliant insight, but maybe. Incidentally, if a message goes into the queue, it goes there to die. Sorting out the moderation queue is like standing in a sewer waiting to try to catch a $5 bill floating down the stream once or twice a year. It's just not worth it. -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-20 17:42:32
|
> On 10/19/2012 06:02 PM, Tom Breton (Tehom) wrote: > >> I re-saved it - restores OK onder 12.04 > > Apparently he only sent the file to you, and/or there's a copy in the > moderation queue. Either way, I can't get my hands on it directly. He sent it to me privately. I'd suggest sending it to the whole list, but it's Aere's work so it's his call. Tom Breton (Tehom) |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-20 17:57:49
|
Tom: I (she) just sent it (privately) to Michael too. - Aere On Sat, 2012-10-20 at 13:42 -0400, Tom Breton (Tehom) wrote: > > On 10/19/2012 06:02 PM, Tom Breton (Tehom) wrote: > > > >> I re-saved it - restores OK onder 12.04 > > > > Apparently he only sent the file to you, and/or there's a copy in the > > moderation queue. Either way, I can't get my hands on it directly. > > He sent it to me privately. I'd suggest sending it to the whole list, but > it's Aere's work so it's his call. > > Tom Breton (Tehom) > > > > ------------------------------------------------------------------------------ > 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 > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: D. M. M. <ros...@gm...> - 2012-10-20 18:20:05
|
On 10/20/2012 01:57 PM, Aere Greenway wrote: > I (she) just sent it (privately) to Michael too. So noted. Oops. -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-22 02:41:01
|
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) |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-22 03:35:27
|
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 |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-22 04:04:20
|
Bad news: I had suspected my code in conformInstrumentControllers, but entirely disabling that doesn't make any difference. So once again I have no theory. > Tom: > > What did you do that can make it keep the original settings? You won't like it: I edited the savefile manually. Specifically, I ediffed it with the savefile that worked and replaced the "device" statement. Obviously that's no solution. > 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. I should emphasize, I don't think it's that Synth is bad and Timidity is good, I suspect it resets something when it mismatches the current connection. > 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 re-looked at that code, and I don't think it could. True, there are a lot of lines that differ by "fixed=", but I found the line that changes behavior and that's not it. I'm going to stop here, because I just had an idea what it might be. Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2012-10-22 05:35:46
|
On 10/22/2012 12:04 AM, Tom Breton (Tehom) wrote: > I should emphasize, I don't think it's that Synth is bad and Timidity is > good, I suspect it resets something when it mismatches the current > connection. First, I have not gotten a chance to piddle with her file for myself yet. It's still there on my list. Bearing in mind that this is pure blind speculation, let's think about this... On the one hand, controls like pan/volume/etc. are common, but they're not universal, and just because "General MIDI Device" had controller 943 defined as Chipotle, and "Some Random Other Device" also has controller 943 defined as Chipotle, I don't think Rosegarden makes any attempt to cross-map from one to the other when switching devices. As such, whenever there's a new device, don't we pretty much have to go back to defaults on everything? A potential solution for that is to implement cross-mapping when changing the device a track is pointing to. Look at what was in the old one, look at what's in the new one, if there's a match, carry those settings across. Anything that exists in both, set the new one to the old setting, use defaults in all other cases. Could conceivably be done, but I'm reasonably sure it isn't done currently. Beyond all of that, just because you saved a file that was rigged to play with one kind of hardware/whatever and loaded it on different hardware/whatever should not automatically change the device in the first place. Hrm. I'm getting off into too much stuff to think about without getting my hands on and poking around. I'm seriously going to try to do that before my night is over. I have the hint of something here, and might be able to ferret out this problem, either by pointing out that it's happening for a perfectly good reason, or pinpointing what's not happening that should be. I'll try to get back to this while all of these random ponderings are somewhat fresh in my mind. At this moment, the wife beckons, and I must needs pay some attention to her; she the Rosegarden Widow no longer. -- D. Michael McIntyre |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-22 05:49:24
|
Interesting, and probably good conjecture, possibly yielding a solution. Keep in mind, however, that saving the Pan and Volume settings has been working in Rosegarden for years. I personally have used it for years. This is the first time those settings haven't carried over to the new release. - Aere On Mon, 2012-10-22 at 01:35 -0400, D. Michael McIntyre wrote: > On 10/22/2012 12:04 AM, Tom Breton (Tehom) wrote: > > > I should emphasize, I don't think it's that Synth is bad and Timidity is > > good, I suspect it resets something when it mismatches the current > > connection. > > First, I have not gotten a chance to piddle with her file for myself > yet. It's still there on my list. > > Bearing in mind that this is pure blind speculation, let's think about > this... > > On the one hand, controls like pan/volume/etc. are common, but they're > not universal, and just because "General MIDI Device" had controller 943 > defined as Chipotle, and "Some Random Other Device" also has controller > 943 defined as Chipotle, I don't think Rosegarden makes any attempt to > cross-map from one to the other when switching devices. As such, > whenever there's a new device, don't we pretty much have to go back to > defaults on everything? > > A potential solution for that is to implement cross-mapping when > changing the device a track is pointing to. Look at what was in the old > one, look at what's in the new one, if there's a match, carry those > settings across. Anything that exists in both, set the new one to the > old setting, use defaults in all other cases. Could conceivably be > done, but I'm reasonably sure it isn't done currently. > > Beyond all of that, just because you saved a file that was rigged to > play with one kind of hardware/whatever and loaded it on different > hardware/whatever should not automatically change the device in the > first place. > > Hrm. > > I'm getting off into too much stuff to think about without getting my > hands on and poking around. I'm seriously going to try to do that > before my night is over. I have the hint of something here, and might > be able to ferret out this problem, either by pointing out that it's > happening for a perfectly good reason, or pinpointing what's not > happening that should be. > > I'll try to get back to this while all of these random ponderings are > somewhat fresh in my mind. At this moment, the wife beckons, and I must > needs pay some attention to her; she the Rosegarden Widow no longer. -- Sincerely, Aere Sincerely, Aere |
Re: [Rosegarden-devel] Fixed,
I think (Was: A clue (Was: Found A New Problem With Rosegarden
12.04))
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-10-22 17:32:10
|
Tom: Thank you very much for figuring this out, and fixing the problem. Good work! Let me know when the fix is in, so I can generate my own version of Rosegarden that will preserve the settings. I think if I once re-save these pieces with the new version (with the pan/volume settings preserved), the un-fixed release version will read them okay, so my users will not get the demo-pieces with incorrect pan/volume settings (which sound bad). The testing I have done so far suggests that if I were to laboriously re-edit the pan/volume settings to the correct values (using the released Rosegarden 12.04), and re-save them, that version of Rosegarden will successfully read (and preserve) the settings. Do you think my observations/suppositions are correct? - Aere On Mon, 2012-10-22 at 13:14 -0400, Tom Breton (Tehom) wrote: > I have apparently found and fixed the problem. > > Short summary: > > When we reset connection, we were inappropriately propagating controller > settings to instruments. The fix reads Aere's demo file perfectly, with > nuanced pans and volumes. > > What was happening: > > Not too long ago, I made MidiDevice react to connection resets. That > fixed certain bugs like expression being reset to 0. But the code it > called sometimes also reset some Instruments settings. My fault for > assuming. > > * Connection resets call Device::refreshForConnection, to MidiDevice:: > refreshForConnection. > * Which calls generateDefaultControllers. That figures out new defaults > for the device and calls addControlParameter to add them. > * But addControlParameter does more than that: If > isVisibleControlParameter(con) is true, it also propagates the controller > value to Instruments (calls addControlToInstrument). > > The fix: > > * addControlParameter (both signatures) has a new parameter, bool > propagateToInstruments. > * generateDefaultControllers passes false. I believe that's always > correct, since it's only called in MidiDevice ctors which then call > deviceToInstrControllerPush and in refreshForConnection. > * Other calls to addControlParameter pass true to keep their original > semantics. > * I have doubts about RoseXmlHandler, since it's just reading a > Controllable device at that point so why would it change instruments > settings? But I conservatively left it with the original semantics. > > I will (first get up to speed with the new Sourceforge and then) push this > fix. > > Tom Breton (Tehom) > > -- Sincerely, AereSincerely, Aere Sincerely, Aere |
Re: [Rosegarden-devel] Fixed,
I think (Was: A clue (Was: Found A New Problem With Rosegarden
12.04))
From: D. M. M. <ros...@gm...> - 2012-10-23 01:03:30
|
On 10/22/2012 01:14 PM, Tom Breton (Tehom) wrote: > I have apparently found and fixed the problem. The thing I love about you and Ted is that you usually figure something out and solve it before I even have a chance to dig into the problem for myself. You're both a true delight to have around. Aere, if I read the mailing list traffic correctly, the fix is in as of revision 13126. Try it out (make sure you have the new URL to reach late revisions) and see what you think! (Note to self, it would be nice if I could figure out a way to go back to having emails with diffs every time somebody commits something. That sure was handy. Now I just see a revision number and whatever the commit comment was. No diffs.) -- D. Michael McIntyre |
Re: [Rosegarden-devel] Fixed,
I think (Was: A clue (Was: Found A New Problem With Rosegarden
12.04))
From: Tom B. (Tehom) <te...@pa...> - 2012-10-23 02:05:15
|
> The thing I love about you and Ted is that you usually figure something > out and solve it before I even have a chance to dig into the problem for > myself. You're both a true delight to have around. Thank you! > Aere, if I read the mailing list traffic correctly, the fix is in as of > revision 13126. Try it out (make sure you have the new URL to reach > late revisions) and see what you think! Yes, 13126. > (Note to self, it would be nice if I could figure out a way to go back > to having emails with diffs every time somebody commits something. That > sure was handy. Now I just see a revision number and whatever the > commit comment was. No diffs.) So that's it. I was wondering where those had gone to. Tom Breton (Tehom) |
Re: [Rosegarden-devel] Fixed,
I think (Was: A clue (Was: Found A New Problem With Rosegarden
12.04))
From: D. M. M. <ros...@gm...> - 2012-10-23 02:36:05
|
On 10/22/2012 10:05 PM, Tom Breton (Tehom) wrote: > Yes, 13126. I just dinked around with a somewhat different problem on the user list. With channel set to fixed, you can put controllers in one segment and notes in the other, and have one affect the other. I think you pretty much took care of all of this in one fell swoop. Then again, I've signed off on stuff before that some user figured out how to break. There's no substitute for actually using Rosegarden to do stuff, and I'm afraid I haven't done that in a few years now. Maybe here shortly. My daughter wants to learn to play the trumpet, so I might have some scores to transpose and fiddle with to get my hands on this stuff for myself. -- D. Michael McIntyre |