From: Lorenzo S. <lor...@gm...> - 2012-10-18 09:10:27
|
This is on 12.12 I'm not sure what is causing this but I can't seem to set MIDI channels ('Instrument' in rosegarden lingo) properly. If I set the Channel mode from 'auto' (unfortunately the default) and change a channel this is not used correctly. Additionally the auto mode seems to re-activate itself even when 'fixed' was selected after changing the channel ('instrument'). Try this wit ha a midi monitor connected to rosegarden (e.g. GMIDImonitor) and you'll see what I mean: create a small segment put some random notes in, put it in repeat mode start playing and changing the channels and setting channel to fixed. I can't seem to find a reasonable logic in what's going on :| Is all this a known bug? On a side note: the Channel auto thing seems to have broken all my .rg file previous to its introduction. Does this mean that it has backward broken .rg files? Honestly I'm not sure what the auto mode really is and what it's for. Has it something to do with track # -> channel #? I may sound old school but I like to have full control of my midi channels on a sequencer. Lorenzo. |
From: D. M. M. <ros...@gm...> - 2012-10-18 11:00:58
|
On 10/18/2012 05:10 AM, Lorenzo Sutton wrote: > Honestly I'm not sure what the auto mode really is and what it's for. > Has it something to do with track # -> channel #? I may sound old school > but I like to have full control of my midi channels on a sequencer. I'm afraid I don't have time just at the moment to look into what's going on. I'll get back to it one day soon, I promise. In the meantime, I can offer a brief explanation of what this is all about. It came about through a sort of round about process. Tom Breton noticed certain oddities concerning MIDI channels and ornaments, or something to that effect, and it all snowballed into some huge theoretical discussion over some weeks from there. Basically a segment is a little box that contains stuff, and for that paradigm to work as well as Tom thought it should, it would need to be possible for each segment to grab its own MIDI channel. Let's say you have two segments, each of which is using pitch bend controllers to manipulate notes in very specific ways. This works great when each segment sits by itself on a separate track, but if you put the two on the same track, overlapping in time, now the controllers conflict with each other. That's because these controllers act on a whole channel level, and they can't be constrained inside one of Rosegarden's logical constructs. So what if Rosegarden could allocate channels on the fly on an as needed basis? Let's say Instrument #3 needs to play events from two different segments that happen to conflict with each other. What if the Instrument could use channel 3 to play some of the notes, and then grab some unused channel, let's say it happens to be 13, to play the remaining notes? That was the question, more or less. It was just stupidly complicated beyond imagining, and when I gave Tom the green light to go ahead and carry out this ridiculously twisted and nightmarishly complicated scheme, I never remotely dreamed the crazy hacker would actually get the damn thing working well enough to suit me. I beat the crap out of it and sent it back to the drawing board a dozen times, and in the end, he solved all the problems I could find with it. I'll be surprised if there isn't some way for you to work with the new paradigm yourself, and achieve the results you're after. If not, I fully support raising the bar even higher and ironing all of this out somehow. We'll get there, Lorenzo. Thanks for your patience, and I'll get back to the meat of your problems as soon as I happen upon a day when I have a bit more free time. -- D. Michael McIntyre |
From: <jp...@it...> - 2012-10-18 13:29:07
|
Quoting Lorenzo Sutton <lor...@gm...>: > This is on 12.12 > > I'm not sure what is causing this but I can't seem to set MIDI channels > ('Instrument' in rosegarden lingo) properly. If I set the Channel mode > from 'auto' (unfortunately the default) and change a channel this is not > used correctly. > Additionally the auto mode seems to re-activate itself even when 'fixed' > was selected after changing the channel ('instrument'). I've found that you sometimes have to switch back and forth from fixed to auto and back, but it seems to be a fairly rare occurrence. It occurs to me that it might be doing something like setting the drop-down but not actually using the setting itself under some specific circumstances. I haven't yet sat down to investigate it. > On a side note: the Channel auto thing seems to have broken all my .rg > file previous to its introduction. Does this mean that it has backward > broken .rg files? Mine all seem to work, but obviously I have to go through and set them all to 'fixed' because most of the synthesizers are monotimbral or otherwise use a fixed channel allocation scheme (different organ manuals etc). > Honestly I'm not sure what the auto mode really is and what it's for. > Has it something to do with track # -> channel #? I may sound old school > but I like to have full control of my midi channels on a sequencer. I think it uses a round-robin channel allocation scheme, where it uses the first free channel. That's handy on a GM synthesizer, but on everything else - basically all the expensive ones - it will make a mess. > > Lorenzo. > |
From: Lorenzo S. <lor...@gm...> - 2012-10-18 14:16:31
|
Thanks Michael and jmp for your explanations... I just fired up my (simple) rg and noticed this, I'm in the middle of a long project to be finished tomorrow (actually finishing off the boring presentation thing right now), but thought I'd write to give a heads up, will happily give some feedback and debug support if needed from next week. At a quick look it seems the problem is also there if you are playing back, so maybe it's something more trivial like jpm suggests. Thanks again for the quick replies Lorenzo. On 18/10/12 15:02, jp...@it... wrote: > Quoting Lorenzo Sutton <lor...@gm...>: > >> This is on 12.12 >> >> I'm not sure what is causing this but I can't seem to set MIDI channels >> ('Instrument' in rosegarden lingo) properly. If I set the Channel mode >> from 'auto' (unfortunately the default) and change a channel this is not >> used correctly. >> Additionally the auto mode seems to re-activate itself even when 'fixed' >> was selected after changing the channel ('instrument'). > > I've found that you sometimes have to switch back and forth from fixed > to auto and back, but it seems to be a fairly rare occurrence. It > occurs to me that it might be doing something like setting the > drop-down but not actually using the setting itself under some > specific circumstances. I haven't yet sat down to investigate it. > >> On a side note: the Channel auto thing seems to have broken all my .rg >> file previous to its introduction. Does this mean that it has backward >> broken .rg files? > > Mine all seem to work, but obviously I have to go through and set them > all to 'fixed' because most of the synthesizers are monotimbral or > otherwise use a fixed channel allocation scheme (different organ > manuals etc). > >> Honestly I'm not sure what the auto mode really is and what it's for. >> Has it something to do with track # -> channel #? I may sound old school >> but I like to have full control of my midi channels on a sequencer. > > I think it uses a round-robin channel allocation scheme, where it uses > the first free channel. That's handy on a GM synthesizer, but on > everything else - basically all the expensive ones - it will make a > mess. > >> >> Lorenzo. >> > > ------------------------------------------------------------------------------ > 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-user mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user > |
From: Michael J. W. <mw...@al...> - 2012-10-18 15:06:05
|
I'd like to add that, at least in 12.04, an "all controllers reset" as well as any visible controllers in the Instrument Parameters box are sent at the start of each segment. I have some compositions that use separate overlapping segments in the same track for control data and notes, and the result is that in recent versions of Rosegarden the volume and panning get reset to their default values every time a new segment starts, sometimes during the middle of another segment on the same track. I tried to work around this by removing all the controllers from the Instrument Parameters pane via the Manage MIDI Devices dialog. But it seems like if the Volume and Pan controllers are hidden in this way then they are silently added back when the .rg file is saved, Rosegarden is closed, and then Rosegarden is launched again and the file re-opened. If I import a saved .rgd file with all controllers hidden every time I open the project then it seems to behave the way I want it to; that is, individual controller default values are no longer sent. The "all controllers reset" message is still always sent, however. Maybe in "fixed" mode the default values and all controllers reset should not be sent at the start of each segment, but just at the start of playback? This would maintain legacy behavior for people using fixed mode, although it may have implications for drum tracks which I think currently default to fixed. It makes sense to send the controllers for each segment in "auto" mode, because the new MIDI channel is probably not initialized for that track yet. I understand that I may not be using segments the way they are intended to be used, but I appreciated the ability to do this in previous versions! Thank you, and sorry to go off on a tangent (also apologies if this has already been fixed; my distro hasn't packaged 12.12 yet). -Michael J. Wilson |
From: D. M. M. <ros...@gm...> - 2012-10-23 02:31:41
|
On 10/18/2012 10:43 AM, Michael J. Wilson wrote: > I understand that I may not be using segments the way they are intended > to be used, but I appreciated the ability to do this in previous versions! I'm not looking at a data dump in KMidiMon or anything, just doing a quick and dirty test. As I understand your problem, you want controllers in segment B overlapping with segment A on the same track. Track has channel set to "fixed" instead of auto. Idea is the controllers in segment B affect the notes in segment A. Test case: 1. New doc with track 1 set to "fixed" per default 2. Draw segment A 3. Draw segment B, overlapping about halfway 4. Put some random notes in segment A 5. Set top level Instrument Parameters volume to 0 6. Put some volume controllers in segment B, volume rising slowly from 0 7. Hit play Result is I hear nothing (top level volume in effect) until segment B kicks in, then the notes ascend in volume. Conclusion: If a default volume of 100 were being sent, the volume would jump, then fall off and creep back up. I'm hearing it start low and rise, per the controllers. I think the fix Tom just committed addresses your problem as well, Michael. Subversion revision 13126. > Thank you, and sorry to go off on a tangent (also apologies if this has > already been fixed; my distro hasn't packaged 12.12 yet). Nobody has packaged 12.12. It's not December 2012 yet, and it hasn't been released yet. We're working on it now. This is a good time to get set up to build the development source and try it out. The more testing we get before the release, the better. Otherwise we're going to keep on the same sort of cycle we're in now, where we're fixing a list of quite nasty bugs that have been out there in the wild for more than a year. Good luck. -- D. Michael McIntyre |
From: Michael J. W. <mw...@al...> - 2012-10-23 03:45:35
|
On 10/22/2012 07:31 PM, D. Michael McIntyre wrote: > Test case: > > 1. New doc with track 1 set to "fixed" per default > 2. Draw segment A > 3. Draw segment B, overlapping about halfway > 4. Put some random notes in segment A > 5. Set top level Instrument Parameters volume to 0 > 6. Put some volume controllers in segment B, volume rising slowly from 0 > 7. Hit play > > Result is I hear nothing (top level volume in effect) until segment B > kicks in, then the notes ascend in volume. > > Conclusion: If a default volume of 100 were being sent, the volume > would jump, then fall off and creep back up. I'm hearing it start low > and rise, per the controllers. As I understand it, this test wouldn't show the problem I'm experiencing. The following modification will show it: 1. New doc with track 1 set to "fixed" per default 2. Draw segment A 3. Draw segment B, overlapping about halfway 4. Put some random notes in segment A 5. Set top level Instrument Parameters volume to 100 6. Put a single volume controller in segment A at 50, somewhere before the start of segment B 7. Put any CC in segment B besides volume (it seems like if there are no events in segment B it is skipped) 8. Hit play Expected outcome: Volume starts loud (100), then gets softer (50) and does not change again. Actual outcome (12.04): Volume starts loud (100), then gets softer (50), then gets loud again (100) at the start of segment B. The reason the test you described wouldn't show the issue is because the top-level value and the first value in segment B are the same. There are actually two issues: 1) The top-level value is sent at the start of every segment if the controller is not hidden, instead of just the start of playback (this may make sense in auto mode but I don't think it makes sense in fixed mode). 2) If the volume or pan controllers are hidden, then the .rg file saved and reloaded, they are re-enabled somehow. I haven't looked into this as much. For my purposes, fixing 1) would make 2) not important to fix. I was only hiding these controllers to try to work around 1). > Nobody has packaged 12.12. It's not December 2012 yet, and it hasn't > been released yet. We're working on it now. Ah, now I understand the version numbering. > This is a good time to get set up to build the development source and > try it out. This is definitely on my list of things to do. I am in the middle of a big move so it will probably be a couple of weeks before I get a chance to play with the development version. I will report back here when I do. I know you are extremely busy and I appreciate you taking the time to look into this. -Michael J. Wilson |
From: D. M. M. <ros...@gm...> - 2012-10-23 03:55:25
|
On 10/22/2012 11:45 PM, Michael J. Wilson wrote: > The reason the test you described wouldn't show the issue is because the > top-level value and the first value in segment B are the same. Quick note: That's true according to the description I wrote, but in practice I was just being lazy in my writing. I said I started from 0 for the sake of showing that I went from low to high steadily, but in fact I really started somewhere above 0 with the first controller in the segment. If that's your acid test, I'll wait for you to try the development version before I spend more time fiddling with this. I see your point that my test wasn't completely reasonable, but I still think the changes Tom just made will more than likely take care of your issue anyway. In the meantime, I noticed when I entered the values for the volume controller it appeared I could only use values from like -3 to -120 or something, and it should in fact be 0 to 127 if memory serves. Something else is broken by the look of things. -- D. Michael McIntyre |
From: D. M. M. <ros...@gm...> - 2012-10-21 14:30:17
|
On 10/18/2012 05:10 AM, Lorenzo Sutton wrote: > Try this wit ha a midi monitor connected to rosegarden (e.g. > GMIDImonitor) and you'll see what I mean: create a small segment put > some random notes in, put it in repeat mode start playing and changing > the channels and setting channel to fixed. I can't seem to find a > reasonable logic in what's going on :| Segment 1 bar long with 4 notes in it. Check. Hook up to KMidiMon. Check. "Repeat mode" is an imprecise description, so I'm not sure how to duplicate that. Attempt 1: Interpret "repeat mode" as "set the segment to repeat." Hit play. Watch a jillion iterations of everything going on channel 1. Fail to repeat bug. Attempt 2: Interpret "repeat mode" as "set a loop and put the transport in loop mode." Hit play. Watch a jillion iterations of everything going on channel 1. Fail to repeat bug. All of this started from scratch with a default autoload.rg from current SVN, so all the instruments had channels set to fixed from the beginning. Attempt 3: Change instrument #1 to "auto." Repeat attempts 1 and 2 with identical results. Everything still on channel 1. Attempt 4: Save file in this state. Restart. Repeat attempts 1 and 2 with identical results. Everything still on channel 1. Attempt 5: Start messing with instrument #2. Same results ad infinitum. > On a side note: the Channel auto thing seems to have broken all my .rg > file previous to its introduction. Does this mean that it has backward > broken .rg files? If I remember correctly, the way it's supposed to work is that since old .rg files contain no fixed/auto information, we have to pick one and set it to something, and we're supposed to be setting it to fixed. I'm being kind of terse here because I'm finally getting to this on my way to bed, but please don't take my terseness for a bad attitude on my part. I'm totally sincere about wanting to make sure there are no problems here. What I'm seeing right now is a distinct lack of weird or unexpected behavior. I suspect if there's any bad behavior to see, it's going to take a more complex test case than one segment with a few notes in it. If I see anything weird here, some of the controller traffic looks like it could be suspect. I'm not trying to think about that one yet. -- D. Michael McIntyre |
From: Lorenzo S. <lor...@gm...> - 2012-10-25 12:39:45
|
Hi Michael, I'll try to summarize and be a little more detailed. I did some tests again with the latest SVN build. - Connect "General MIDI Device" to gmidimonitor (but any midi monitor will do) - Create a 2 bar segment with notes - Check the "repeat" segment ( this is totally irrelevant to the channel problem - it's just useful to set up lots of playback quickly, sorry if it generated confusion ) - Play - Instrument is set to #1 and channel is correctly 1 - Select a different instrument (channel) from the Instrument dropdown _while playing_ _This_ seems to be the problem. Until you stop and re-start play the channel is unchanged. I also noticed that now Channel is set to fixed by default for a new file (but I think this actually is irrelevant to the problem) So all that noise seems to sum up to: Instrument/channel won't be updated during playback. Hope it's clearer now. Should I add a bug report? Lorenzo. On 21/10/12 16:30, D. Michael McIntyre wrote: > On 10/18/2012 05:10 AM, Lorenzo Sutton wrote: > >> Try this wit ha a midi monitor connected to rosegarden (e.g. >> GMIDImonitor) and you'll see what I mean: create a small segment put >> some random notes in, put it in repeat mode start playing and changing >> the channels and setting channel to fixed. I can't seem to find a >> reasonable logic in what's going on :| > Segment 1 bar long with 4 notes in it. Check. > > Hook up to KMidiMon. Check. > > "Repeat mode" is an imprecise description, so I'm not sure how to > duplicate that. > > Attempt 1: Interpret "repeat mode" as "set the segment to repeat." Hit > play. > > Watch a jillion iterations of everything going on channel 1. Fail to > repeat bug. > > Attempt 2: Interpret "repeat mode" as "set a loop and put the transport > in loop mode." Hit play. > > Watch a jillion iterations of everything going on channel 1. Fail to > repeat bug. > > All of this started from scratch with a default autoload.rg from current > SVN, so all the instruments had channels set to fixed from the beginning. > > Attempt 3: Change instrument #1 to "auto." Repeat attempts 1 and 2 > with identical results. Everything still on channel 1. > > Attempt 4: Save file in this state. Restart. Repeat attempts 1 and 2 > with identical results. Everything still on channel 1. > > Attempt 5: Start messing with instrument #2. Same results ad infinitum. > >> On a side note: the Channel auto thing seems to have broken all my .rg >> file previous to its introduction. Does this mean that it has backward >> broken .rg files? > If I remember correctly, the way it's supposed to work is that since old > .rg files contain no fixed/auto information, we have to pick one and set > it to something, and we're supposed to be setting it to fixed. > > I'm being kind of terse here because I'm finally getting to this on my > way to bed, but please don't take my terseness for a bad attitude on my > part. I'm totally sincere about wanting to make sure there are no > problems here. > > What I'm seeing right now is a distinct lack of weird or unexpected > behavior. I suspect if there's any bad behavior to see, it's going to > take a more complex test case than one segment with a few notes in it. > > If I see anything weird here, some of the controller traffic looks like > it could be suspect. I'm not trying to think about that one yet. |
From: Al T. <alt...@gm...> - 2012-10-26 00:36:35
|
On 10/25/2012 09:54 AM, S. Christian Collins wrote: > I don't know that I've ever tried to change MIDI instrument/channel > during playback using any music software. Is this something that other > programs do? I've always auditioned my instrument changes live with a > MIDI keyboard with playback stopped. Changing instruments (Patches) during playback is pretty common, and something I do fairly regularly. Changing channels, however, is usually a Very Bad Thing, that almost always results in hung notes, and unpredictable CC behavior, and most often requires a MIDI reset to straighten out. -- --- My bands, CD projects, music, news, and pictures: http://www.lateralforce.com My blog, with commentary on a variety of things, including audio, mixing, equipment, etc, is at: http://audioandmore.wordpress.com Staat heißt das kälteste aller kalten Ungeheuer. Kalt lügt es auch; und diese Lüge kriecht aus seinem Munde: 'Ich, der Staat, bin das Volk.' - [Friedrich Nietzsche] |
From: Abrolag <ab...@us...> - 2012-10-26 16:55:35
|
On Thu, 25 Oct 2012 20:36:27 -0400 Al Thompson <alt...@gm...> wrote: > On 10/25/2012 09:54 AM, S. Christian Collins wrote: > > I don't know that I've ever tried to change MIDI instrument/channel > > during playback using any music software. Is this something that other > > programs do? I've always auditioned my instrument changes live with a > > MIDI keyboard with playback stopped. > > Changing instruments (Patches) during playback is pretty common, and > something I do fairly regularly. Changing channels, however, is usually > a Very Bad Thing, that almost always results in hung notes, and > unpredictable CC behavior, and most often requires a MIDI reset to > straighten out. Ah yes. Ignore my previous comment :o I was thinking of patch and program changes, not channel changes! -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: D. M. M. <ros...@gm...> - 2012-10-26 09:25:17
|
On 10/25/2012 05:16 PM, Tom Breton (Tehom) wrote: > But what's puzzling me most is that I can't reproduce it in the current > working version. I did what I thought the steps were, but I must have > missed something. First up, let's all get on the same page. I read Lorenzo's message again and as far as I can tell we're all still talking about playback, _not_ recording. If you found some weird recording thing, it's not what we're talking about. 1. Draw a segment on track 1 and put some junk in it, set it to repeat This is our noise making source. It repeats just so you have less junk to draw to slap the test together, and you could substitute a really long segment filled with lots and lots of junk (or even real music if you prefer!) 2. While it's playing, change the instrument on track 1 from #1 to #2, which also changes the channel from 1 to 2 in the process. Rosegarden 11.whatever I tested with this morning actually made the channel changes instantly. Al Thompson did a good job of summing up why I never noticed we used to do that: changing channels during playback is often a good way to experience mayhem. Now, apparently, we don't do that anymore. Change the instrument to #2 now and nothing happens until you interrupt and restart playback. Since the behavior changed, and it's apparently behavior at least one user has come to expect, it's officially a regression. Since two out of three users surveyed think changing channels while playback is rolling is a goofy thing to do anyway, it doesn't look much like it's worth taking on Batman to me. I don't have a strong opinion on any of this, and will go with the flow. -- D. Michael McIntyre |
From: S. C. C. <s_c...@ho...> - 2012-10-26 15:28:34
|
My question: do MIDI program change messages at least work during playback? This is something that should be supported by any MIDI sequencer. -~Chris On 10/26/2012 04:25 AM, D. Michael McIntyre wrote: > On 10/25/2012 05:16 PM, Tom Breton (Tehom) wrote: > >> But what's puzzling me most is that I can't reproduce it in the current >> working version. I did what I thought the steps were, but I must have >> missed something. > First up, let's all get on the same page. I read Lorenzo's message > again and as far as I can tell we're all still talking about playback, > _not_ recording. If you found some weird recording thing, it's not what > we're talking about. > > 1. Draw a segment on track 1 and put some junk in it, set it to repeat > > This is our noise making source. It repeats just so you have less junk > to draw to slap the test together, and you could substitute a really > long segment filled with lots and lots of junk (or even real music if > you prefer!) > > 2. While it's playing, change the instrument on track 1 from #1 to #2, > which also changes the channel from 1 to 2 in the process. > > Rosegarden 11.whatever I tested with this morning actually made the > channel changes instantly. > > Al Thompson did a good job of summing up why I never noticed we used to > do that: changing channels during playback is often a good way to > experience mayhem. > > Now, apparently, we don't do that anymore. Change the instrument to #2 > now and nothing happens until you interrupt and restart playback. Since > the behavior changed, and it's apparently behavior at least one user has > come to expect, it's officially a regression. > > Since two out of three users surveyed think changing channels while > playback is rolling is a goofy thing to do anyway, it doesn't look much > like it's worth taking on Batman to me. > > I don't have a strong opinion on any of this, and will go with the flow. |
From: Abrolag <ab...@us...> - 2012-10-26 16:53:26
|
On Fri, 26 Oct 2012 10:28:20 -0500 "S. Christian Collins" <s_c...@ho...> wrote: > My question: do MIDI program change messages at least work during > playback? This is something that should be supported by any MIDI sequencer. > > -~Chris Indeed! That is something that's being worked on for Yoshimi. The development branch had that and at the time Rosegarden did what it should do. Haven't checked it recently though. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-26 18:42:45
|
> My question: do MIDI program change messages at least work during > playback? This is something that should be supported by any MIDI > sequencer. > > -~Chris > You're asking about program change messages that set the instrument to something different than what the track dialog at the left is showing? If I understand your question, that will work if you set fixed channel and uncheck "Bank" and "Program" in "Instrument Parameters". Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2012-10-26 19:36:05
|
On 10/26/2012 11:28 AM, S. Christian Collins wrote: > My question: do MIDI program change messages at least work during > playback? This is something that should be supported by any MIDI sequencer. This was all working reasonably the last time I looked. I haven't looked recently. -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-26 16:08:13
|
> On 10/25/2012 05:16 PM, Tom Breton (Tehom) wrote: > >> But what's puzzling me most is that I can't reproduce it in the current >> working version. I did what I thought the steps were, but I must have >> missed something. > > First up, let's all get on the same page. I read Lorenzo's message > again and as far as I can tell we're all still talking about playback, > _not_ recording. If you found some weird recording thing, it's not what > we're talking about. Oh, I see. Yes, I had found something different. Thank you for setting me straight! > 1. Draw a segment on track 1 and put some junk in it, set it to repeat > > This is our noise making source. It repeats just so you have less junk > to draw to slap the test together, and you could substitute a really > long segment filled with lots and lots of junk (or even real music if > you prefer!) > > 2. While it's playing, change the instrument on track 1 from #1 to #2, > which also changes the channel from 1 to 2 in the process. Yes, that works to reproduce it. I'm going to have a look at it. I suspect it won't be that hard to fix. (Famous last words again) Tom Breton (Tehom) |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-26 17:59:00
|
> I'm going to have a look at it. I suspect it won't be that hard to fix. > (Famous last words again) OK, I've fixed it. TrackButtons now reacts to changing the instrument by calling new function SequenceManager::segmentInstrumentChanged on each segment on the affected track. A bit quick-and-dirty: segmentInstrumentChanged just remaps the segment. There's a much faster way to do it but it'd be more complex and it's not clear that it needs to be that fast. Tom Breton (Tehom) |
From: Lorenzo S. <lor...@gm...> - 2012-10-26 18:47:00
|
Well didn't think it would start such conceited exchanges. I must admit I often do weird non-standard stuff such as connecting Rosegarden to Pd (through alsa-midi) and trying out stuff. Morale: I guess I can live with the no channel changes during playback and can see the drawbacks Al underlines, while see the need as most seem to agree with for Program changes. Sorry for the noise (this started 2 days before my conservatoire thesis discussion last week and I was probably in somewhat of a "panic" state). Anyway happy to see the rg community is active and alive! :) Lorenzo. On 26/10/12 19:58, Tom Breton (Tehom) wrote: > >> I'm going to have a look at it. I suspect it won't be that hard to fix. >> (Famous last words again) > > OK, I've fixed it. > > TrackButtons now reacts to changing the instrument by calling new function > SequenceManager::segmentInstrumentChanged on each segment on the affected > track. > > A bit quick-and-dirty: segmentInstrumentChanged just remaps the segment. > There's a much faster way to do it but it'd be more complex and it's not > clear that it needs to be that fast. > > Tom Breton (Tehom) > > > > ------------------------------------------------------------------------------ > The Windows 8 Center > In partnership with Sourceforge > Your idea - your app - 30 days. Get started! > http://windows8center.sourceforge.net/ > what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ > _______________________________________________ > Rosegarden-user mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user > |
From: D. M. M. <ros...@gm...> - 2012-10-27 11:55:27
|
On 10/26/2012 02:46 PM, Lorenzo Sutton wrote: > Well didn't think it would start such conceited exchanges. Hope you don't think I was being conceited. If I come off that way, it's just because I'm constantly in a huge hurry, and I'm being terse. Anyway, looks like Tom restored the existing behavior for you. Check it out! -- D. Michael McIntyre |
From: Abrolag <ab...@us...> - 2012-10-27 12:27:59
|
On Sat, 27 Oct 2012 07:55:20 -0400 "D. Michael McIntyre" <ros...@gm...> wrote: > On 10/26/2012 02:46 PM, Lorenzo Sutton wrote: > > Well didn't think it would start such conceited exchanges. > > Hope you don't think I was being conceited. If I come off that way, > it's just because I'm constantly in a huge hurry, and I'm being terse. > > Anyway, looks like Tom restored the existing behavior for you. Check it > out! Actually, I think Lorenzo meant concerted :) -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: S. C. C. <s_c...@ho...> - 2012-10-27 15:39:50
|
On 10/27/2012 07:27 AM, Abrolag wrote > Actually, I think Lorenzo meant concerted :) I was wondering about that, LOL! Certainly nobody was coming across as conceited to me. -~Chris |
From: Tom B. (Tehom) <te...@pa...> - 2012-10-27 15:50:19
|
> On Sat, 27 Oct 2012 07:55:20 -0400 > "D. Michael McIntyre" <ros...@gm...> wrote: > >> On 10/26/2012 02:46 PM, Lorenzo Sutton wrote: >> > Well didn't think it would start such conceited exchanges. >> >> Hope you don't think I was being conceited. If I come off that way, >> it's just because I'm constantly in a huge hurry, and I'm being terse. >> >> Anyway, looks like Tom restored the existing behavior for you. Check it >> out! > > Actually, I think Lorenzo meant concerted :) Heh, thanks for clearing that up. Tom Breton (Tehom) |
From: Lorenzo S. <lor...@gm...> - 2012-10-28 07:58:38
|
On 27/10/12 14:27, Abrolag wrote: > On Sat, 27 Oct 2012 07:55:20 -0400 > "D. Michael McIntyre" <ros...@gm...> wrote: > >> On 10/26/2012 02:46 PM, Lorenzo Sutton wrote: >>> Well didn't think it would start such conceited exchanges. >> >> Hope you don't think I was being conceited. If I come off that way, >> it's just because I'm constantly in a huge hurry, and I'm being terse. I certainly feel like that most times, that's why fingers are sometimes faster than the brain... > > Actually, I think Lorenzo meant concerted :) Wops indeed... sorry about that, as I said fingers sometimes go faster than brain :| ... It was meant as a positive remark about the quick community reaction that's why I also ended my email with: "Anyway happy to see the rg community is active and alive! " Lorenzo. |