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

theoreomonster at reaperaccess.com theoreomonster at reaperaccess.com
Tue Nov 17 18:46:20 EST 2015


I just picked up the x touch mini to test out over here. The x touch looks like the best bang going right now but i needed more buttons than faders for my workflow so mini fit the bill.  I can deal with non motorized since reaper has soft takeover built in. 

Also part of the reason PT stopped being my main DAW was the midi learn issues. I  just prefer OS X too much to switch back. lol. Though i do find a lot of the dialogs read better on OS X and i always had access to the master track. 

> On Nov 17, 2015, at 4:23 PM, onlineeagle <onlineeagle at gmail.com> wrote:
> 
> Hi Chris, the issue is solved. Hopefully my message to the list sent. Anyway, I just use my midi keyboard primarily. Une of my reasons for going over to Reaper from ProTools was that you can use any midi controler with it. I also have a Beringer BCF2000 which I use now and again. 
> 
> Sent from my iPhone
> 
>> On 17 Nov 2015, at 20:59, Chris Smart <csmart8 at cogeco.ca> wrote:
>> 
>> Unfortunately, I don't have an answer for you, but I do have a question. Which control surface are you using?
>> 
>> I'm waiting to see what people think of the Behringer X-Touch units, as I really do want to replace this BCF2000 with something more robust. If I could afford a real Mackie Control, I would just get one of those, but the budget doesn't stretch that far.
>> 
>> Chris
>> 
>> At 07:27 PM 11/16/2015, you 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
>> 
>> --- <http://www.shareasale.com/r.cfm?b=635671&u=1109457&m=54749&urllink=&afftrack=>Learn to meditate and train your brain with Muse, the first lab-grade EEG biofeedback headband for home use! 
>> 
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
> 
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp




More information about the RWP mailing list