osara
osara copied to clipboard
jcsteh
Determining parameter range when using REAPER's Parameter Modulation/MIDI Link dialog
Hi, I'd like to get feedback on the min and max values when I'm using the midi link feature in the parameter modulation / midi link dialogue. For example, I may have a volume plugin and I want to use the scale and offset values in this dialogue so my mod wheel only varies the volume parameter between -6 and 0db. Sighted help suggests that there is no text in this dialogue giving the parameter value but sighted users can have the original plugin UI open and see the affect that moving the mod wheel is having. So they can tweak the offset and strength values to set the min and max range fairly easily. I did write a script to announce the current value of the last touched parameter but it isn't possible to run a script from within the parameter modulation / midi link dialogue. I was hoping that I would be able to put my mod wheel in the lowest position, read the value and adjust offset and strength to match my desired min value. Then repeat with the mod wheel in the most up position. Could OSARA announce the current value of the parameter being adjusted?
I'm not super familiar with the workflow, reproduction steps would be helpful. IN the meantime, does enabling surface feedback do anything to help with this?
Hi. Here goes with a description of the workflow..
I recorded a mono audio track and then added the js Volume Pan smoother v5 plugin to the track
My aim is to control the pan with my mod wheel but I only want the panning to happen from full left to centre. The mod wheel when fully down should represent full left and mod wheel at full up should represent pan in the centre.
Ensure the track is armed, monitored and the input set to the midi controller so that cc messages are sent to it.
Using the param button for this plugin I go to FX parameter list > parameter modulation / midi link > pan
Tab to the link from midi or FX parameter checkbox and tick it
Tab to the phase reset button and hit space, down to MIDI, down to cc, and select mod wheel.
You can play the audio now and move the mod wheel and hear the change in pan. The behaviour out of the bag in this case seems to be the exact opposite of what I want which is a range from centre to full right.
Looking at the weird envelope baseline overrides checkbox percentage change thingy I use the up and down arrows to change this from 50% to 0% which seems to put me in a better position.
Then I play around with the offset and scale edit box values to achieve what I want. It turns out an offset of 0 and a scale of 50 does the trick just about.
I can determine this a lot by listening but it isn’t numerically a precise approach but gets you in the ball park.
The current accurate way to check the parameter value at each extreme of the mod wheel is to set your baseline override percentage, offset and scale values, then go pack to the TCP and hit P on the track with the mod wheel set to either full down or full up and look in the value for pan. Or as this is a js plugin we could also tab to the pan parameter in the UI to see how it varies as the mod wheel is moved.
If you need to change the offset and scale values you need to go back into the plugin, to the param button, through the menus and back to the midi link dialogue.
This back and forth between the midi link dialogue and the inspection of the parameter value could be speeded up and made more precise with some method of spoken feedback of the parameter value as the midi controller is moved.
The example of pan is quite easy to hear but imagine you wanted to set the mod wheel to only change the volume from -6 to 0db. You really need the numerical value feedback to achieve this. Sighted users would just look at the UI of the plugin to see how its value changed as the mod wheel was moved and as offset and scale were adjusted.
Hope that explains the workflow.
From: ScottChesworth @.> Sent: 21 January 2023 12:55 To: jcsteh/osara @.> Cc: CastleStarter @.>; Author @.> Subject: Re: [jcsteh/osara] Determining parameter range when using REAPER's Parameter Modulation/MIDI Link dialog (Issue #842)
I'm not super familiar with the workflow, reproduction steps would be helpful. IN the meantime, does enabling surface feedback do anything to help with this?
— Reply to this email directly, view it on GitHub https://github.com/jcsteh/osara/issues/842#issuecomment-1399246570 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOFDPSNRMZXPON6HXRKKGDWTPMDZANCNFSM6AAAAAAUCK7D4E . You are receiving this because you authored the thread.Message ID: @.***>
Dunno how feasible it is to implement this, but how about if we could load the OSARA Parameters dialog direct from the Modulation dialog, like we already can from the FX window. That way you'd be able to set some values, hit Alt+P, check the slider, Escape lands back in the Modulation dialog, tweak, Alt+P to check, Escape etc. It's not as convenient as having both UIs on screen at once I know, but seems quicker than what you're currently doing. Would that help? Does anyone have a better idea?
The reascript api supports interrogating the value of the last touched parameter. Could there be a way to run code to do this and speak the value from the midi link dialogue with a keystroke or when the controller stops moving for a second?
Although of course the parameter being adjusted may not be the last touched one. Perhaps it could be determined programmatically since the midi link dialogue has it in the title bar.
But otherwise yes, your suggestion would be quicker but still feels cumbersome.
Regards, Chris
From: ScottChesworth @.> Sent: 21 January 2023 16:30 To: jcsteh/osara @.> Cc: CastleStarter @.>; Author @.> Subject: Re: [jcsteh/osara] Determining parameter range when using REAPER's Parameter Modulation/MIDI Link dialog (Issue #842)
Dunno how feasible it is to implement this, but how about if we could load the OSARA Parameters dialog direct from the Modulation dialog, like we already can from the FX window. That way you'd be able to set some values, hit Alt+P, check the slider, Escape lands back in the Modulation dialog, tweak, Alt+P to check, Escape etc. It's not as convenient as having both UIs on screen at once I know, but seems quicker than what you're currently doing. Would that help? Does anyone have a better idea?
— Reply to this email directly, view it on GitHub https://github.com/jcsteh/osara/issues/842#issuecomment-1399283793 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOFDPRXKNNDOQ2MFQAVUHLWTQFJRANCNFSM6AAAAAAUCK7D4E . You are receiving this because you authored the thread.Message ID: @.***>
Oh hang on. Stop all the clocks. I forgot to test OSARA feedback from control surfaces. I don’t have this ticked usually. And it does the trick. Or at least, it does on my example about panning. I’ll go experiment some more. But hey wow, this is great.
From: ScottChesworth @.> Sent: 21 January 2023 16:30 To: jcsteh/osara @.> Cc: CastleStarter @.>; Author @.> Subject: Re: [jcsteh/osara] Determining parameter range when using REAPER's Parameter Modulation/MIDI Link dialog (Issue #842)
Dunno how feasible it is to implement this, but how about if we could load the OSARA Parameters dialog direct from the Modulation dialog, like we already can from the FX window. That way you'd be able to set some values, hit Alt+P, check the slider, Escape lands back in the Modulation dialog, tweak, Alt+P to check, Escape etc. It's not as convenient as having both UIs on screen at once I know, but seems quicker than what you're currently doing. Would that help? Does anyone have a better idea?
— Reply to this email directly, view it on GitHub https://github.com/jcsteh/osara/issues/842#issuecomment-1399283793 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOFDPRXKNNDOQ2MFQAVUHLWTQFJRANCNFSM6AAAAAAUCK7D4E . You are receiving this because you authored the thread.Message ID: @.***>
Oh, no, sorry, got over excited there. Control surface feedback doesn’t work from the midi link dialogue.
From: ScottChesworth @.> Sent: 21 January 2023 16:30 To: jcsteh/osara @.> Cc: CastleStarter @.>; Author @.> Subject: Re: [jcsteh/osara] Determining parameter range when using REAPER's Parameter Modulation/MIDI Link dialog (Issue #842)
Dunno how feasible it is to implement this, but how about if we could load the OSARA Parameters dialog direct from the Modulation dialog, like we already can from the FX window. That way you'd be able to set some values, hit Alt+P, check the slider, Escape lands back in the Modulation dialog, tweak, Alt+P to check, Escape etc. It's not as convenient as having both UIs on screen at once I know, but seems quicker than what you're currently doing. Would that help? Does anyone have a better idea?
— Reply to this email directly, view it on GitHub https://github.com/jcsteh/osara/issues/842#issuecomment-1399283793 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQOFDPRXKNNDOQ2MFQAVUHLWTQFJRANCNFSM6AAAAAAUCK7D4E . You are receiving this because you authored the thread.Message ID: @.***>