Hi Lee, > If I drag-and-drop the first copy from the audio window again, it doesn't > make a copy, but it would be too tedious to do this for the whole track. How > can I automate this, without making so many copies? > > What I do is drag one copy into the arrange window. And then, via keycommand, call up the repeat object function and just type in the number of times I want aliases created for it, and then hit return. -- Eli Krantzberg Nightshift Orchestra Almat Productions

Hopefully simple question: I have a sys-ex fader whose min/max range needs to be set "on the fly", depending on the setting of another fader. I know how to do this (meta events 96 and 97) but the problem is that sometimes the range maximum of the fader needs to be 200, whereas the use of meta-events to set the faders maximum doesn't allow values over 127. I tried cheating by adding a "+ 73" transformer, hoping that 127 + 73 = 200, but that doesn't work :-). Is there any way to set a fader's maximum >127, using some external mechanism (i.e. _not_ setting a max of 200 by hand)? Ditto for the range minimum, which sometimes needs to be -12 (also outside the 0-127 scope). And if this can't be done (which I fear): how about putting _this_ on the wishlist??? After all, meta-events are only _pseudo_ midi-events, so I don't see why their range is limited to 0-127. I mean, having o.a. a tempo-fader that only goes from 50-177 is (to put it mildly) a bit ridiculous, isn't it? Oh, I also tried to use the 14-bit filter option, hoping this would give a 2-byte pitch-bend sort-of range, which would be more than sufficient, but alas... that didn't work either: the MSB uses the In-definitions controller number (i.e. 97) and the LSB uses the controller number 32 higher. The problem probably is that 97+32 falls outside the 0-127 range for controller numbers... Thanks for any insights in advance. cheers, Hendrik Jan -- Hendrik Jan Veenstra ( h@... )

>Is there any way to set a fader's maximum >127, using some external >mechanism (i.e. _not_ setting a max of 200 by hand)? Ditto for the >range minimum, which sometimes needs to be -12 (also outside the >0-127 scope). I don't know any way to do this and yes, it would be nice. Len

Thoughts from the mind of Len Sasso, 02-06-2000: > >Is there any way to set a fader's maximum >127, using some external >>mechanism (i.e. _not_ setting a max of 200 by hand)? Ditto for the >>range minimum, which sometimes needs to be -12 (also outside the >>0-127 scope). > >I don't know any way to do this and yes, it would be nice. Arrghhhh... if _you_ don't know how this can be done, then it surely must be impossible! Alas, alas, moan, moan, sigh, sigh, weep, weep... On a more serious note: "it would be nice"??? Isn't that understating things a bit? IMO it's bizarre that this can't be done. These last two days I made a partial editor for the Korg M1 (yup, a fully functional Combi editor -- any M1-owners out there?), and I really need faders with a range from -99 to +99 or 0 to +500 at times. But these same faders sometimes only require a range of 0 to 2, so giving all faders a constant "maximum range" (-99 to 500 or so) wouldn't be very user-friendly. S***, this is _really_ annoying... Well, thanks for your reply though. cheers, Hendrik Jan P.S. Yes, I'll upload the editor as soon as I'm sure it's bug-free -- and as soon as I've made up my mind on what to do about this fader-problem. -- Hendrik Jan Veenstra ( h@... )

>On a more serious note: "it would be nice"??? Isn't that >understating things a bit? IMO it's bizarre that this can't be done. >These last two days I made a partial editor for the Korg M1 (yup, a >fully functional Combi editor -- any M1-owners out there?), and I >really need faders with a range from -99 to +99 or 0 to +500 at >times. But these same faders sometimes only require a range of 0 to >2, so giving all faders a constant "maximum range" (-99 to 500 or so) >wouldn't be very user-friendly. S***, this is _really_ annoying... > >Well, thanks for your reply though. It just occurred to me that you might be able to work around this with Aliases and the Alias Assigner. But, if your patch is really complex, this may not be practical either. >P.S. Yes, I'll upload the editor as soon as I'm sure it's bug-free -- >and as soon as I've made up my mind on what to do about this >fader-problem. Great ;) Len

Thoughts from the mind of Len Sasso, 03-06-2000: ><snip> > >times. But these same faders sometimes only require a range of 0 to >>2, so giving all faders a constant "maximum range" (-99 to 500 or so) >>wouldn't be very user-friendly. S***, this is _really_ annoying... >> >>Well, thanks for your reply though. > >It just occurred to me that you might be able to work around this >with Aliases and the Alias Assigner. But, if your patch is really >complex, this may not be practical either. Ah, a new route to explore! Thanks for the hint! As for impractical: the patch now contains some 140 sys-ex faders, 150 controller faders, 230 transformers, 50 'bang'-faders, and a dozen monitor-objects -- so worrying about things being practical is a bit too late :-). But all this _does_ give you a fully automatable (is that a word?) editor that's driven by plain-vanilla controllers only. So now at least I have an easy way to have e.g. note-velocity (or pitch, or whatever) determine the panning-position of a sound, or to have the pitchbend wheel control the amount of detuning, or to have the modulation wheel control one particular volume in a multi-timbral setup. Or all at the same time :-) In the past (Atari days) I used to spend days typing in sys-ex messages by hand to achieve similar effects, so up till now I'm rather happy -- apart from the slight problems I still have to overcome. And all that with just two days of work. Mwah... Enough of this self-satisfied talk... Back to the problem at hand: just this afternoon I found at least a way to generate negative numbers, as long as the total range doesn't exceed 127. Let me briefly explain what's behind all this (let me just mumble to myself -- maybe you'll generate more useful ideas while reading :-). I have a bunch of sys-ex faders -- in-definition is some controller and out-definition is sys-ex. These are off-screen, and are controlled by control-panel faders which send out the appropriate controller to control the sys-ex faders (how often can you put "control" in one sentence, without losing control? :-). This way recording and playing back fader-settings is simply a matter of recording/playing controllers instead of entire sys-ex messages. Some sys-ex faders are able to send out values between e.g. -200 and 200. But then the controller-fader has to be able to send out these values as well, obviously. And that's where the problems start, since controllers are limited to a 0-127 range. Part of the solution is to use mapped transformers that do not control a sys-ex _fader_ but a sys-ex-mapping _transformer_ instead -- clever mapping of the 0-127 range makes it possible to set MSB and LSB in a sys-ex message, so that instead of e.g. 0-100 the values -50 - 50 are sent. The use of controller-faders with the 14-bit filter should give an opening towards a solution for >127 ranges (probably requires a lot more clever mapping of controller numbers and values -- haven't gotten round to that yet, but I'm pretty sure it's do-able). All this still leaves the problem of setting fader ranges on the fly when these ranges exceed the 0-127 range. I feel a sort of solution is lurking somewhere in the foregoing, but I'm not quite sure yet. The "solution" will probably be a kludge, like having a 0-100 fader generate sys-ex messages with a 0-500 range, in which only multiples of 5 are sent (i.e. multiply the fader output by 5). Not elegant, since some values are unreachable, but I'd rather have a fader that at least covers the whole range and skips some values, than having a fader that stops at 100. A 14-bit fader _would_ be able to send the whole range, but then you run into the old problem again: how do you tell the fader to be "14-bit, 0-500" on the fly, especially when earlier in the session it was a non-filtered fader with a 0-2 range? Ahw, my head hurts... Gotta get a good night's sleep over this... > >P.S. Yes, I'll upload the editor as soon as I'm sure it's bug-free -- > >and as soon as I've made up my mind on what to do about this > >fader-problem. > >Great ;) Well, what did you expect? This is my chance to place myself in the "hall of fame and eternal gratitude" -- at least as far as the single other M1-owner on this list is concerned :-). Thanks again for the suggestion and for thinking along. I'll read up on Aliasses and Alias Assigners - probably tonight :-). cheers, Hendrik Jan -- Hendrik Jan Veenstra ( h@... )