[Rwp] Last touched FX parameter unavailable. Why oh why?

[onlineeagle]

OK, perhaps that last touched option was always given an unavailable status. For what ever reason, I tried the learn opqion yesterday and it didn't recognise my fader move. But today it works. I think what happened was it stopped working for one tiny moment, and then I restarted the computer and spent two hours trying to diagnose the problem, even though it had already been fixed. That's why I took more notice of that last touched option, whereas normally I'd just go straight to midi learn without giving what that last touched thing says. I'm running the latest version of Reaper, as of 15 November, and latest Osara, and it's all working beautifully. Loving the focusable master track. In my opinion we can now get rid of the shift key strokes for exclusive master track behaviour, then we get some hotkeys back for other mapping. Thanks.  

Sent from my iPhone

> On 17 Nov 2015, at 00:40, James Teh <jamie at nvaccess.org> wrote:
> 
> As far as I can see, that "Last touched" item in the menu just tells you what parameter was last touched. You're not meant to be able to activate it. However, if you keep moving down, you should still see "Learn", which works on the last touched parameter.
> 
> Note that if it says "No recently touched parameters", then the "Learn" item isn't present.
> 
> Jamie
> 
>> On 17/11/2015 10:27 AM, onlineeagle wrote:
>> After having a massively successful day with Reaper, I was just about to go to bed, when I decided that I might as well finish the project I’m working on. After all, it would only consist of me automating the wet mix of the reverb effect on one track. It should take all of five minutes. And so hear I am, two hours later, typing this email.
>> 
>> Something has happened to Reaper in the last 24 hours. Yesterday I could assign a control surface fader to my last touched effect, by going to the fx window, going to the param button and hitting learn. But for some strange reason, this has stopped working. I add an effect, I press shift P to go to the parameters list. I then adjust one of the parameters and press enter to close the window. Then I press f to get to the effects dialogue, hit the param button, and then the despair sets in. It says that the last touched parameter is unavailable. I’ve tried this with multiple effects and it’s always the same, yet it was working perfectly the day before. I’ve managed to find a work around, by pressing shift L to go to the automation mode window, then using NVDA screen review to find the parameter learn button and doing it that way. Weirdly this works. What on earth is going on now?
>> 
>> Perhaps it’s something to do with updating Reaper today. Anyone with any ideas? Is this happening to anyone else?
>> 
>> Thanks again. I nearly managed a whole day without needing to ask a question on here.
>> 
>> 
>> Sent from my iPhone
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
> 
> -- 
> James Teh
> Executive Director, NV Access Limited
> Ph +61 7 3149 3306
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
> SIP: jamie at nvaccess.org
> 
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp