From: Tom B. (Tehom) <te...@pa...> - 2013-05-15 00:32:57
|
I committed the "best of both worlds" merge on new branch controllers-BOBW. I am particularly interested in Tim Munro's comments on it. Some minor missing stuff: * Still not sure of the "right" way to update all the tr("Value (%):")'s. * I have made a new wiki page to document it, but can't seem to upload the images I have. Tom Breton (Tehom) |
From: Tim M. <or...@le...> - 2013-05-28 14:39:00
|
On 05/14/2013 05:32 PM, Tom Breton (Tehom) wrote: > I committed the "best of both worlds" merge on new branch > controllers-BOBW. > > I am particularly interested in Tim Munro's comments on it. Tom: I've finally found time to look over this new branch and report back. I like the added functionality, particularly the ability to define a ramp over only part of a selected range. In order to do that with my version, I would have to replace a note with a number of short-duration rests, select the ones I wanted, define the ramp, and then restore the original note. Related to functionality I found only a few minor annoyances: * When I highlight a note and insert a sequence of controllers, erasing that same sequence leaves the last controller still in place. I got around that in my own work by placing the last controller back one timing unit, so it would always fall within the boundary rather than on it. * The ability to select rests by themselves for establishing time frames would be convenient. This could be particularly useful when setting a controller back to zero on a rest following a ramped note. * If a ramp begins and ends at the same level (as when resetting a controller back to zero following a ramp that doesn't end at zero), there is no need to generate more than a single controller event. The extra event is just clutter. * The function "QSpinBox.setAccelerated(bool)" would be a useful addition to spinBoxes, as it permits using a small step size for precision, without requiring the user to wait forever for the thing to crank around. In the not-so-minor annoyance department, I found the user-interface dialog absolutely bewildering. It seemed to have little to do with expression controllers, and only after a great deal of trial and error was I able to work out what each item was supposed to do. However, once I figured it out, I found the new features quite powerful. From a programmer's point of view, the one-size-fits-all approach to the controller interface may be elegant, but from a user's perspective it is not. For the sake of clarity each controller should have its own specialized interface dialog that clearly presents only those options appropriate to that controller. Again, nice functionality but difficult to access. Respectfully, Tim Munro |
From: Tom B. (Tehom) <te...@pa...> - 2013-05-28 18:01:03
|
> On 05/14/2013 05:32 PM, Tom Breton (Tehom) wrote: >> I committed the "best of both worlds" merge on new branch >> controllers-BOBW. >> >> I am particularly interested in Tim Munro's comments on it. > I'm going to answer the biggest issue first: > In the not-so-minor annoyance department, I found the user-interface > dialog absolutely bewildering. It seemed to have little to do with > expression controllers, and only after a great deal of trial and error was > I able to work out what each item was supposed to do. However, once I > figured it out, I found the new features quite powerful. > > From a programmer's point of view, the one-size-fits-all approach to the > controller interface may be elegant, but from a user's perspective it is > not. For the sake of clarity each controller should have its own > specialized interface dialog that clearly presents only those options > appropriate to that controller. OK, clear interface design is not my strength and I welcome help. But all the options are available to all the controllers. For instance, you might apply vibrato to expression controllers; strings with expression vibrato + modulation vibrato is sometimes useful. So specializing on controllers vs pitchbends wouldn't help. Looking over the dialog, I see a number of places where the text assumes pitchbends or is just unclear. Let me run these possible renamings by you and everyone else: * "Pre-bend" -> "Before Ramp"/"Before Bend" * "Value (%):" -> "Start at value:"/"Start at value (%):" * "Duration (%):"" -> "Wait this long (%):" * Tooltip: "How long to wait before ramping, as a percentage of the total time" * "Bend Sequence" -> "Controller Sequence"/"Bend Sequence" * "Ramp duration (%):" -> "Ramp duration (%):"/"Bend duration (%):" * Tooltip: "How long the bend or ramp lasts, as a percentage of the remaining time" * "Preset" -> I don't know. I can see where a user might not guess what "preset" means, but what's a better word or short phrase to convey the meaning? * Tooltip for preset: "Use this saved or built-in setting. You can edit it. For saved (but not built-in) settings, that will become the new saved setting" > I've finally found time to look over this new branch and report back. > > I like the added functionality, particularly the ability to define a ramp > over only part of a selected range. In order to do that with my version, > I would have to replace a note with a number of short-duration rests, > select the ones I wanted, define the ramp, and then restore the original > note. I must humbly add that I only inherited that from others' work on PitchBendSequenceDialog. > Related to functionality I found only a few minor annoyances: > > * When I highlight a note and insert a sequence of controllers, erasing > that same sequence leaves the last controller still in place. I got > around that in my own work by placing the last controller back one > timing unit, so it would always fall within the boundary rather than > on it. OK, easily added. > * The ability to select rests by themselves for establishing time > frames > would be convenient. This could be particularly useful when setting > a > controller back to zero on a rest following a ramped note. OK. That's actually in the rc files, but I think I can change it around so it's active when there's any selection, not just a selection containing notes. > * If a ramp begins and ends at the same level (as when resetting a > controller back to zero following a ramp that doesn't end at zero), > there is no need to generate more than a single controller event. > The extra event is just clutter. Good thinking. I will test for that before placing the end event. > * The function "QSpinBox.setAccelerated(bool)" would be a useful > addition to spinBoxes, as it permits using a small step size for > precision, without requiring the user to wait forever for the thing > to > crank around. Good idea. I hadn't previously known about setAccelerated. I assume it makes up/down arrows hyperbolic instead of linear? We could probably use that on a lot of dialogs. Tom Breton (Tehom) |
From: Tom B. (Tehom) <te...@pa...> - 2013-05-28 20:32:17
|
While I was at it, I changed the vibrato waveform to be a (more correct) sine wave rather than the triangular wave we have been using. The amplitude and frequency scalings are unchanged. Tom Breton (Tehom) |
From: Tim M. <or...@le...> - 2013-05-30 10:38:51
|
On 05/28/2013 11:00 AM, Tom Breton (Tehom) wrote: > I'm going to answer the biggest issue first: > >> In the not-so-minor annoyance department, I found the user-interface >> dialog absolutely bewildering. It seemed to have little to do with >> expression controllers, and only after a great deal of trial and error >> was I able to work out what each item was supposed to do. However, >> once I figured it out, I found the new features quite powerful. >> >> From a programmer's point of view, the one-size-fits-all approach to >> the controller interface may be elegant, but from a user's perspective >> it is not. For the sake of clarity each controller should have its >> own specialized interface dialog that clearly presents only those >> options appropriate to that controller. > OK, clear interface design is not my strength and I welcome help. > > But all the options are available to all the controllers. For instance, > you might apply vibrato to expression controllers; strings with > expression vibrato + modulation vibrato is sometimes useful. So > specializing on controllers vs pitchbends wouldn't help. One of my basic concerns is whether or not it is appropriate to make all options available to all controllers. Is vibrato really appropriate for Pan (10), Chorus (93), Reverb (91), or Sustain (64)? Perhaps the appearance of vibrato options in the dialog could be made conditional, based on the controller chosen. A problem with the term "Vibrato" is that it refers to the frequency modulation of an audio tone. "Tremolo," on the other hand, usually implies amplitude modulation. Perhaps replacing "Vibrato" with "Vibrato / Tremolo" would make it clear that this option is not limited to frequency. "Vibrato wavelength" seems a bit murky. I think it would be clearer if, instead, the number of vibrato cycles in the selection could be specified. Or, better still, the vibrato frequency in hertz. The number of half cycles of vibrato could be calculated from the available time interval, the vibrato frequency, and the current tempo. > Looking over the dialog, I see a number of places where the text assumes > pitchbends or is just unclear. Let me run these possible renamings by > you and everyone else: > > * "Pre-bend" -> "Before Ramp"/"Before Bend" > > * "Value (%):" -> "Start at value:"/"Start at value (%):" > > * "Duration (%):"" -> "Wait this long (%):" > * Tooltip: "How long to wait before ramping, as a percentage of the > total time" > > * "Bend Sequence" -> "Controller Sequence"/"Bend Sequence" > > * "Ramp duration (%):" -> "Ramp duration (%):"/"Bend duration (%):" > * Tooltip: "How long the bend or ramp lasts, as a percentage of > the remaining time" Yes, I think these changes would greatly clarify the dialog. > * "Preset" -> I don't know. I can see where a user might not guess > what "preset" means, but what's a better word or short phrase to > convey the meaning? > * Tooltip for preset: "Use this saved or built-in setting. You > can edit it. For saved (but not built-in) settings, that will > become the new saved setting" I have no problem with "Preset," but I found "User 1, User 2, User 3, ..." a bit confusing. My first impression was that it was an attempt to set up user accounts within a controller dialog. Perhaps "User Setting 1, User Setting 2, User Setting 3, ..." would make clear what's going on here. >> * The function "QSpinBox.setAccelerated(bool)" would be a useful >> addition to spinBoxes, as it permits using a small step size for >> precision, without requiring the user to wait forever for the >> thing to crank around. > Good idea. I hadn't previously known about setAccelerated. I assume it > makes up/down arrows hyperbolic instead of linear? We could probably > use that on a lot of dialogs. When an arrow is held down, the spinBox performs normally for the first second or so, after which it kicks into a high-speed mode. > While I was at it, I changed the vibrato waveform to be a (more correct) > sine wave rather than the triangular wave we have been using. The > amplitude and frequency scalings are unchanged. Good idea. Tim Munro |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-05-30 17:23:16
|
On 05/30/2013 04:38 AM, Tim Munro wrote: > One of my basic concerns is whether or not it is appropriate to make all > options available to all controllers. Is vibrato really appropriate for > Pan (10), Chorus (93), Reverb (91), or Sustain (64)? Perhaps the > appearance of vibrato options in the dialog could be made conditional, > based on the controller chosen. > > A problem with the term "Vibrato" is that it refers to the frequency > modulation of an audio tone. "Tremolo," on the other hand, usually > implies amplitude modulation. Perhaps replacing "Vibrato" with > "Vibrato / Tremolo" would make it clear that this option is not limited > to frequency. > > "Vibrato wavelength" seems a bit murky. I think it would be clearer if, > instead, the number of vibrato cycles in the selection could be specified. > Or, better still, the vibrato frequency in hertz. The number of half > cycles of vibrato could be calculated from the available time interval, > the vibrato frequency, and the current tempo. Tim: I'm offering a few comments relative to your words above, based on my experience. Perhaps it will be useful - perhaps not. The "Sustain" controller is not useful for 'ramping' up or down. The sustain 'pedal' is either up (values 0 thru 63), or down (values 64 through 127). I don't see "Vibrato" among the controllers defined for General MIDI, though I do see "Tremolo Depth". Many synthesizers ignore many of the controls. The synthesizers I have used respond to either the modulation control (1) or channel pressure (after-touch, which is often assignable) to cause vibrato to occur, or control how much of it is used. I think the soundfont used has some degree of control on how vibrato works. One of the best software synthesizers around (Qsynth / Fluidsynth) makes use of the FluidR3_GM soundfont, which (I think) is quite good. But modulation (vibrato) with it, can often be a problem. For plucked string-type instruments, increasing the modulation control can produce an interesting change in the sound. But for melodic instruments (Flute, Cello, Oboe, etc), it can produce a sound that is (to me) very bad. The above behavior of Qsynth with the FluidR3_GM soundfont is (to me) so bad, that I have gone to great lengths to remove modulation (and channel pressure) controller values from sequences to be played with Qsynth. The same thing applies to the Soundblaster Live (emu10k1) hardware synthesizer using the FluidR3_GM soundfont, though to a lesser degree. That being said, the FluidR3_GM soundfont has a good amount of vibrato built-in for melodic instruments, so I usually don't need to use it. But if you do use it, a little goes a long ways... The modulation controller values I removed from sequences to be played by Qsynth, sounded very good on my Roland D20. -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2013-05-30 17:50:18
|
> One of my basic concerns is whether or not it is appropriate to make all > options available to all controllers. Is vibrato really appropriate for > Pan (10), Chorus (93), Reverb (91), or Sustain (64)? Perhaps the > appearance of vibrato options in the dialog could be made conditional, > based on the controller chosen. Hmmm. My take on it is that I don't want to deny options just because I can't think of a use for them right now. FWIW, I have used a vibrato-like effect with Pan (In "Much Brass", the mysterious section where horn chords are surrounded by percussion that pans slowly around). > A problem with the term "Vibrato" is that it refers to the frequency > modulation of an audio tone. "Tremolo," on the other hand, usually > implies amplitude modulation. Yes, I think so too. I didn't say "Tremolo" because that would be overly specific too: just expression and volume. > Perhaps replacing "Vibrato" with > "Vibrato / Tremolo" would make it clear that this option is not limited > to frequency. No good generic terms present themselves: * "Vibrato or Tremolo". But then controllers are saying that they might do vibrato, which is false, and it's still not a generic term. * Yamaha used to call that generic thing "Low Frequency Oscillation", but that might be even more confusing. * "Sinusoidal variation"? I am sure that whatever the right term is, it would be unwieldy to label each field "Sinusoidal variation start amplitude" etc. Even I would recoil at seeing that. Concatenating "Vibrato" etc onto "start amplitude" could make our translators' work harder. So part of the solution will probably be to group those 3 items in their own labelled box. With that, a sensible approach becomes clearer. The box label has more freedom to express an exact term, since it's not concatenated to anything. Its label could be: * For Pitchbend, "Vibrato" * For Expression and Volume, "Tremolo" * For anything else, "Low-frequency variation" unless someone can suggest a better term. > "Vibrato wavelength" seems a bit murky. I think it would be clearer if, > instead, the number of vibrato cycles in the selection could be specified. > Or, better still, the vibrato frequency in hertz. The number of half > cycles of vibrato could be calculated from the available time interval, > the vibrato frequency, and the current tempo. Heck, I didn't even know how it was actually calculated until I revamped this! Cycles per selection is easier to add, but as you probably saw, it still has the problem that using the "same" setting twice gives different results if one selection is longer than the other. I'm not sure hertz is the right unit. Perhaps cycles per quarter note? Perhaps both? I would very much like to hear from more people before I try this. The other stuff is just renaming and rearranging and has little potential to frustrate old users. EVERYBODY: If you use the pitchbend dialog, if the "Vibrato wavelength" field changed to "cycles per quarter note" or "hertz", would that be easier or harder for you to use? I really don't know. Perhaps everybody has been muddling thru with a tricky interface. I'll ask on the user list too. > Yes, I think these changes would greatly clarify the dialog. Great! > I have no problem with "Preset," but I found "User 1, User 2, User 3, ..." > a bit confusing. My first impression was that it was an attempt to set up > user accounts within a controller dialog. I never thought of that. That *is* confusing! Historically, you know, there was one lonely setting called "User" among the built-ins - the one and only thing that the user could preset. Now with my patches it's almost taken over. > Perhaps "User Setting 1, > User Setting 2, User Setting 3, ..." would make clear what's going on > here. OK. How about "Saved setting 1" etc? > When an arrow is held down, the spinBox performs normally for the first > second or so, after which it kicks into a high-speed mode. Thanks. Tom Breton (Tehom) |
From: Ted F. <te...@te...> - 2013-05-30 23:09:52
|
On 05/30/2013 01:50 PM, Tom Breton (Tehom) wrote: > * For Pitchbend, "Vibrato" > * For Expression and Volume, "Tremolo" > * For anything else, "Low-frequency variation" unless someone can suggest > a better term. "Modulation"? Or good ol' "LFO" as you mentioned before? I really haven't even looked at this, so no vote from me. Just brainstorming while reading. Ted. |
From: D. M. M. <ros...@gm...> - 2013-05-31 11:59:53
|
> * For Pitchbend, "Vibrato" > * For Expression and Volume, "Tremolo" > * For anything else, "Low-frequency variation" unless someone can suggest > a better term. "LFO" would probably be clear enough. All kinds of things in this sphere have an LFO control. > easier or harder for you to use? I really don't know. Perhaps everybody > has been muddling thru with a tricky interface. Haven't looked at it in ages. I'll try to weigh in. >> Perhaps "User Setting 1, >> User Setting 2, User Setting 3, ..." would make clear what's going on >> here. > > OK. How about "Saved setting 1" etc? User 1, User 2, etc. seems clear enough to me. It's impossible to be immediately intuitive to everybody, no matter how verbose your descriptions, and stuff that's verbose in English tends to explode horizontally in other languages. It's probably a pretty good rule of thumb to expect a complex English phrase to be at least half again as long in translation, and often longer than that. >> When an arrow is held down, the spinBox performs normally for the first >> second or so, after which it kicks into a high-speed mode. Haven't looked at this, but Rosegarden generally despises spin boxes and prefers to use combo boxes populated with numbers instead. They're MUCH faster to use. I used to think this was arbitrary and silly, but I saw the wisdom behind it and got to where I despise spin boxes too. They suck. Haven't looked in so long I have utterly no idea what the context is here though. I can't picture it at all. No time. -- D. Michael McIntyre |
From: Colin F. <col...@go...> - 2013-05-31 15:49:57
Attachments:
signature.asc
|
On 30/05/13 18:23, Aere Greenway wrote: > > The "Sustain" controller is not useful for 'ramping' up or down. The > sustain 'pedal' is either up (values 0 thru 63), or down (values 64 > through 127). Some (expensive) keyboard controllers actually do send the position of the sustain pedal as a value from 0 - 127, and some synths (e.g. Pianoteq) do make use of the intermediate values. Not that I have either Pianoteq or a nice keyboard, but I guess there might be some use in being able to ramp 'sustain' event values. Colin. |
From: Ted F. <te...@te...> - 2013-05-31 21:31:24
|
On 05/31/2013 11:49 AM, Colin Fletcher wrote: >> The "Sustain" controller is not useful for 'ramping' up or down. The >> sustain 'pedal' is either up (values 0 thru 63), or down (values 64 >> through 127). > > Some (expensive) keyboard controllers actually do send the position of > the sustain pedal as a value from 0 - 127, and some synths (e.g. > Pianoteq) do make use of the intermediate values. The Yamaha DPs have a half-pedal effect. Not sure if this comes in as variable sustain, but seems logical if it does. Won't know until I get one. Ted. |
From: Tom B. (Tehom) <te...@pa...> - 2013-05-31 17:27:57
|
>>> Perhaps "User Setting 1, >>> User Setting 2, User Setting 3, ..." would make clear what's going on >>> here. >> >> OK. How about "Saved setting 1" etc? > > User 1, User 2, etc. seems clear enough to me. I seemed clear to me too, but then when Tim mentioned that it looked like it wanted a login, I realized that I only "understood" it because I already knew what "User" meant and what it did. It's the Curse Of Knowledge - when you know something well, it's hard to put yourself in the place of those who don't know. Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2013-05-31 23:03:00
|
> I seemed clear to me too, but then when Tim mentioned that it looked like > it wanted a login, I realized that I only "understood" it because I > already knew what "User" meant and what it did. It's the Curse Of > Knowledge - when you know something well, it's hard to put yourself in the > place of those who don't know. I get that, but it's also standard terminology in this sphere. It's not Rosegarden's job to teach people what an LFO or a User setting is. Some expertise required to use expert features. Not that my opinion counts for much these days anyway. I'm barely here. -- D. Michael McIntyre |
From: Tim M. <or...@le...> - 2013-06-01 11:39:29
|
On 05/31/2013 04:02 PM, D. Michael McIntyre wrote: > I get that, but it's also standard terminology in this sphere. It's not > Rosegarden's job to teach people what an LFO or a User setting is. Some > expertise required to use expert features. I think "LFO" covers it, but I think "Low Frequency Oscillator" might be easier to translate. Tim Munro |
From: Holger M. <ho...@ma...> - 2013-06-01 17:32:06
|
On Sat, 1 Jun 2013, Tim Munro wrote: > On 05/31/2013 04:02 PM, D. Michael McIntyre wrote: > > I get that, but it's also standard terminology in this sphere. It's not > > Rosegarden's job to teach people what an LFO or a User setting is. Some > > expertise required to use expert features. > > I think "LFO" covers it, but I think "Low Frequency Oscillator" might be > easier to translate. I am not sure if that would help. Every Keyboarder knows what an LFO is. These 3 characters are printed on so many synthesizers' panels. A translation might sound a bit strange or even misleading. |
From: D. M. M. <ros...@gm...> - 2013-06-02 10:00:54
|
> I am not sure if that would help. Every Keyboarder knows what an LFO is. > These 3 characters are printed on so many synthesizers' panels. A > translation might sound a bit strange or even misleading. Right. No translation necessary is my thing. Anybody who has ever had any exposure to synths and the Latin alphabet has seen LFO before. I bet even the Japanese guy translates LFO as LFO. I get that the users are confused by what this or that is, but it really seems like we're overthinking things and going to a lot of trouble for translators who have to come up with a way to explain esoteric and complicated things in few words when the whole exercise is really pointless. Don't know what LFO does? Play with it, see what it does, and now you know the LFO thingie is what makes that other thingie happen to the sound, and when that thingie is what you want to hear, this is the thingie to use. Is anybody ever really shopping for a specific effect and thinking, "Dammit man, I've got to figure out a way to oscillate the low frequencies in this sound in order to create cold fusion in beer and bring about world happiness. Where the hell is the control that does this? My god man, I finally found it, damn you Rosegarden, damn you to hell for not printing 'create cold fusion in beer' on this control! You cost me hours! The planet nearly cracked in half while I was trying to figure it out!" Does anybody really understand what the hell the manual is talking about if you even read it? Does anybody except math genius sound processing dweebs actually give a flying rat's ass about the technical details of how the doohickey does the sound thingie? When I play with a synth, I just dick around with knobs until I get something neat to come out. Simple. Easy for translators too. Don't translate a bunch of crap nobody actually understands even if they read it. "Oh, the zion manipulfold of the transverse scrupulon is ejected into the velosphere by the tragsplisms." Great? What the hell does that mean? Let's play with the knobs and try to figure it out. -- D. Michael McIntyre |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2013-06-01 17:40:38
|
On 06/01/2013 11:31 AM, Holger Marzen wrote: > I am not sure if that would help. Every Keyboarder knows what an LFO is. > These 3 characters are printed on so many synthesizers' panels. A > translation might sound a bit strange or even misleading. Holger: Despite my decades of experience with synthesizers, I did not know what "LFO" referred to, and I do read the manuals. To me, the suggested translation would be a good idea. -- Sincerely, Aere |
From: <she...@gm...> - 2013-06-02 05:24:18
|
Or perhaps it should be expanded in the accompanying documentation? Could the online documentation or tooltips be helpful in this situation? Shelagh On 2 June 2013 03:40, Aere Greenway <Ae...@dv...> wrote: > On 06/01/2013 11:31 AM, Holger Marzen wrote: > > I am not sure if that would help. Every Keyboarder knows what an LFO is. > > These 3 characters are printed on so many synthesizers' panels. A > > translation might sound a bit strange or even misleading. > Holger: > > Despite my decades of experience with synthesizers, I did not know what > "LFO" referred to, and I do read the manuals. > > To me, the suggested translation would be a good idea. > > -- > Sincerely, > Aere > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel > |
From: Tom B. (Tehom) <te...@pa...> - 2013-06-03 01:13:01
|
Whew, I didn't realize quite what I invited. The following, while not completely satisfying to everybody, reflects what I've heard from everybody as well as I can balance the various concerns: * "hertz". Nobody liked "cycles per quarter note" but me, and that may have been just because my head was in the code and not in the interface. * "LFO". I was worried that a TLA would make translators' work needlessly more difficult, but if Michael says it works, that's good enough for me. * "Saved setting N". I believe it's clearer than "User" was, and despite being longer, it seems simple and straightforward. Tom Breton (Tehom) |
From: D. M. M. <ros...@gm...> - 2013-06-03 02:30:57
|
> * "Saved setting N". I believe it's clearer than "User" was, and > despite being longer, it seems simple and straightforward. String Length in chars "User N" 6 "Usuario N" 9 "Saved Setting N" 15 "Configuración personalizada N" 29 There isn't any simple way to say "setting" in Spanish, and translating "saved" directly would be too ambiguous here, so I went with "custom" and there's no way to say "custom" either, so I went with "personalized." I'm making a big deal out of something that isn't really all that significant, and I'm doing so because I find this over the top effort to save people from their own ignorance really amusing for some reason. I'm laughing the whole way through these long rants. This is all just so ludicrous and silly! -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2013-06-03 15:47:38
|
> I'm making a big deal out of something that isn't really all that > significant, and I'm doing so because I find this over the top effort to > save people from their own ignorance really amusing for some reason. Well, I felt bad when after I coded that functionality and made it available it wasn't recognized. So I made up my mind to fix that. Sure, the effort to fix that good and hard may be ludicrous and silly. If "Saved Setting N" is unacceptable, feel free to veto it. If not, I prefer it. Hope you have enjoyed a good laugh, Tom Breton (Tehom) |
From: Tom B. (Tehom) <te...@pa...> - 2013-06-04 20:34:15
|
OK, after much discussion and balancing of concerns, I have committed a new version of the merged controller functionality on controllers-BOBW. Tom Breton (Tehom) |
From: Tim M. <or...@le...> - 2013-06-05 10:55:30
|
On 06/04/2013 01:34 PM, Tom Breton (Tehom) wrote: > OK, after much discussion and balancing of concerns, I have committed a > new version of the merged controller functionality on controllers-BOBW. Thanks for all your work on this. I'll report back after I've checked it out. Tim Munro |
From: Tim M. <or...@le...> - 2013-06-05 14:56:17
|
On 06/05/2013 03:55 AM, Tim Munro wrote: > On 06/04/2013 01:34 PM, Tom Breton (Tehom) wrote: >> >OK, after much discussion and balancing of concerns, I have committed a >> >new version of the merged controller functionality on controllers-BOBW. > Thanks for all your work on this. I'll report back after I've checked it > out. Very nice. You've cleared up the ambiguity that was troubling me as well as some other minor issues. The way the presets work is now completely clear, and I particularly like the way the presets belonging to each controller are now separately saved in "~/.config/rosegardenmusic/Rosegarden.conf". A couple of very minor points: * Before a user sets anything, perhaps the ramp mode should default to "Linear" and the steps mode to "Use this many steps". That way the Vibrato / Tremolo / LFO would also be available by default. * Under the "Controllers" menu, the special item "Insert expression controller Sequence ..." is probably unnecessary, as the expression- controller dialog can be accessed the same as any other controller dialog by first selecting the appropriate ruler. * Slightly off the point, is there some sort of ruler available to show what is happening with pitch bend? I have never used pitch bend, so I admit I haven't looked very hard. Tim Munro |
From: Tom B. (Tehom) <te...@pa...> - 2013-06-05 16:41:59
|
> On 06/05/2013 03:55 AM, Tim Munro wrote: > [...] > Very nice. You've cleared up the ambiguity that was troubling me as well > as some other minor issues. > > The way the presets work is now completely clear, and I particularly like > the way the presets belonging to each controller are now separately saved > in "~/.config/rosegardenmusic/Rosegarden.conf". Thanks! > A couple of very minor points: OK, but I should admit up front, I'm a bit tired and I probably won't make non-bugfix changes. Now I'm dog-food-testing it. > * Before a user sets anything, perhaps the ramp mode should default to > "Linear" and the steps mode to "Use this many steps". That way the > Vibrato / Tremolo / LFO would also be available by default. Well, as you said, LFO isn't (commonly) used other than for pitchbend. I think this is a good middle ground: It's available but not the default, except for certain pitchbend presets. > * Under the "Controllers" menu, the special item "Insert expression > controller Sequence ..." is probably unnecessary, as the expression- > controller dialog can be accessed the same as any other controller > dialog by first selecting the appropriate ruler. 'Twas you who persuaded me to make a special menu item for expression! Now that it's coded up, I like it. :) > * Slightly off the point, is there some sort of ruler available to show > what is happening with pitch bend? I have never used pitch bend, so I > admit I haven't looked very hard. Yes. Its icon is to the left of the controllers ruler icon. It has a sort of curved arrow. Tom Breton |