[RWP] automation

Indigo 33indigo at charter.net
Wed May 29 23:37:22 EDT 2013


I haven't tried the mouse or scroll wheel, since 3 control surfaces are 
plugged into the computer by USB; and I seem to have minimal energy of late.
I use each controller at different times and love what they do.
I don't remember the mode's name; but I'm 100 percent sure that any 
non-motorized control, fader or non endless knob, can be set to a mode 
that doesn't cause the current level to jump, but only begins to 
transmit midi data when the control's position reaches the current level.
I remember reading all that in the Edirol manual; back when I read that 
thoroughly.
Now, how you get that mode from a mouse scroll wheel, I don't know; 
maybe it's the default mode for those actions in Reaper.
Now that I think of it, that's the way the mod wheel on my keyboards 
work, I think.
I'll need to try it, but I'm pretty sure if I've left the no spring mod 
wheel rotated all the way back toward me, and I roll the wheel forward 
to change mod on a soft synth; the wheel begins to change  the synth's 
mod parameter only when it reaches about the center position, or is that 
not how yours works?
Once the mod wheel has picked up the synth's mod parameter, then it 
changes the parameter  throughout its movement in either direction.
Maybe that depends on a setting in the soft synth?
Indi



On 5/29/2013 10:57 PM, Jim Snowbarger wrote:
> Part of the problem I have with automation controls coming from things
> like controller knobs on your keyboard, or mouse scroll wheel, is that
> the physical control doesn't move as the existing automation on the
> track is moving.  So, when you make your first controller move, it can
> be a big jump from the current value, to where your control happens to
> be pointing at the moment.
> With a motorized fater on a surface, the control updates itself in real
> time, so you start from a known starting point.
>
> I have not tried it yet, but would hope that This should be less of an
> issue with mouse movement, since the action presumably finds the current
> level, and initializes the mouse at that level.
> Has anybody actually done that with a mouse?
> How natural is the dynamic feel of moving a wheel and getting a
> prescribed and predictable response.
>
> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Wednesday, May 29, 2013 11:27 AM
> Subject: Re: [RWP] automation
>
>
>> Man, how much hard work it is to find slow screen buttons to do what
>> any old control surface fader will do so much better.
>> Some of us don't realize we already have a fader or knob on our midi
>> keyboard that transmits midi data, as good as any control surface.
>> You know, we think we're lockout of using the mouse; but there's all
>> those mouse modifiers, like there's one that sets up the mouse only to
>> do vertical moves, and up raises track volume and down movement lowers
>> track volume.
>> Another mouse modifier action sets up pan with moving the mouse left
>> or right, with the pan following the mouse; or the mouse scroll wheel
>> can transmit midi CC's to automate anything.
>> These actions are specific to those automations, so using the mouse
>> after pressing that action's shortcut won't allow the mouse to screw
>> up anything else on the screen.
>> After you're finished automating with it, you then press another
>> shortcut to return the mouse to its ordinary function.
>> Indi
>>
>>
>> On 5/29/2013 11:51 AM, Scott Chesworth wrote:
>>> Alex, your workarounds never fail to simultaniously impress and crack
>>> me up man!
>>>
>>> If you're still able to hear your project above the maniacal laughter
>>> of any other musos in the room as they hear their song sounding like
>>> it's being played by an uberly stoned goth outfit from hell, this does
>>> actually work quite well.
>>>
>>> Scott
>>>
>>> On 5/29/13, Alex H. <linuxx64.bashsh at gmail.com> wrote:
>>>> On 5/28/13, Jim Snowbarger <Snowman at snowmanradio.com> wrote:
>>>>> Yep, I held it down, and my key repeat is very fast.
>>>>> The problem is that they change one key makes is 0.05 DB.  That is
>>>>> just
>>>>> insanely small.  nobody, not even you guys with good ears can hear
>>>>> that.
>>>>
>>>> Something I just tried, and it's a hackery hackington bad time, but
>>>> works, and assuming you wanna waste the time doing it. Slow proj tempo
>>>> to a crawl and then adjust pan/volume; once you bring tempo to the
>>>> original rate it'll actually move decently. Again, not very practical,
>>>> but still kinda doable I guess.
>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com
>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>>
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com




More information about the Rwp mailing list