MIDI/OSC Learn Popup version 6, using radio buttons instead of check boxes? (FIXED)

[kodebode2]

Edit 12th Feb 2022 : I have tested the fix in version 6.47 on Windows 10, all 64 bit, and consider this issue resolved.

Thanks to all related contributors

---------------------------------------------------------

In version 4 and version 5, the MIDI/OSC Learn Pop Up dialogue box is similar to this with all options using check boxes.



Then in version 6, for some strange reason which I cannot figure out, it changes to this :



As a result of this really strange change, I am unable to use MIDI to modify any parameters, unless I have a plugin visible or selected. I like version 6 cos it displays better in my higher resolution display, in comparison to version 4, where the text of elements on the screen, such as menu's is a bit blotchy, and more difficult to read.

For the life of me I cannot fathom, why version 6 would impose such changes, and there is nothing in the change notes on the Reaper web site, explaining the change.

Also the Reaper Guide still has the following image, so the Reaper Guide - version 6.41c (on page 210) is therefore also not in sync with the Reaper executable 6.41 64 bit (on Windows 10).

Image below is from the Reaper Guide 6.41c



Could someone kindly look into this issue please - Its really breaking workflow that I have been using in Reaper for about 4 years.... I may have to go back to version 5, cos this strange change is definitely a bug in my humble opinion.

[akademie]

Hi kodebode,
actually there is a bug in the Learn dialog as I reported month ago here:
REAPER Bug Reports > MIDI/OSC Learn bugs (default states)

And here is the another thread about this problem:
learn%20function%20change

[kodebode2]

Akademie, that was really quick, Thanks.

I almost thought I was going a bit wacky cos its so rare in my experience to have such bugs in Reaper, where things that were working ok, regress/stop working, as intended.

I do not wish to go all the way back to version 5, so I'll track back to see if one of the earlier version 6 releases omits this bug.

I am not one who needs the latest greatest Reaper features, - truth be told, I was happy enough with version 4, and probably would be ok with it if it were not for the improved high resolution support which I can see in version 6.

Thanks, will check back in a few months to see if the bug has been fixed..

Merry Xmas.

[toyoto]

I hope we'll get check box again !!
Kind regards

[schwa]

This was inadvertently changed in version 6.37 and will be fixed in 6.47 which would be released today. I'm sorry we missed the original report!

[kodebode2]

Originally Posted by schwa

This was inadvertently changed in version 6.37 and will be fixed in 6.47 which would be released today. I'm sorry we missed the original report!

A massive thank you from me and also to all the others, especially akademie, who highlighted the issue on various threads, and provided a temporary workaround.

I really appreciate this response on the part of the Reaper Development and Support team. As a paid up user (I had to after a few years of using it for free, cos it really is such a great tool), Reaper has become a tool I use every day, for over 12 hours a day. I listen to all of my Youtube, Spotify, Tidal, via Reaper, so I can analyze audio in real time, do Loudness Measurements, and learn using analysis tools to discover the tricks used in commercial audio and also use the monitoring section in Reaper to correct headphones and speakers.

The MIDI automation features in Reaper, especially because the default plugin Bypass provided by Reaper, is also MIDI automatable, is such an important tool for me, cos it allows me to compare plugin chains, by swapping chains in and out without having to go anywhere near a mouse, e.g. switch my monitoring between headphones and speakers.

Thanks ever so much and I look forward to testing the fix.

In 10 years or more of using Reaper this has been the only significant bug, that has bugged me enough to discuss it on the forum, actually I cannot remember anything else that I considered a Reaper specific bug.

Which is a great testament to Reaper the tool and the community which makes this possible.

Long live the Republic of Reaper !

And to Schwa - thanks also for your JSFX tools and the native plugins you have provided for free, so many years ago, which liberated many of us to the new world of almost unlimited creativity with audio.

Thank you, Thank You.