fbcs.over-blog.com/
17 Janvier 2021
REAPER user Khatcha send me an email today with a tip to help those on Windows that found some of their VST plugins were tiny after the REAPER 6.0 upgrade. High five casion.
Pluginboutique is the place where the best music software companies come to sell their VST Plugins, Virtual Instruments, Synth Presets and Music Plugins to Producers, Musicians and DJs worldwide. Customers can browse Best Selling and Top Rated plugins and can download Free VST Plugins, Demos and Trial Versions before purchasing.

I'd like to give a useful tip concerning the version 6.xx on Windows only and it's about the issue with plugins scaling on 4K monitors (or probably less).
With this recent version of Reaper, all my plugins were drastically shrunk and it was impossible to work with such a small UI resolution.
I tried to find the problem with the Advanced UI/ System Tweaks on Reaper but that didn't help me.
I even tried to change some parameters in the Theme development options but it was unsuccessful.
I finally found the issue, I'll give to you so you can spread it better than me :
Of course, keep in mind that REAPER 6 is very new and these things are likely to change and improve in the coming months. Reporting your experience to the official forum with your system info, problem plugins, settings and workarounds is the only way things can improve for all.
The 6.02 update has some changes in this regard, Justin sent me a message on Twitter.
6.02 has a per-plug-in setting to allow the floating FX to be hidpi-unaware. Or you can go to preferences/general/advanced settings, and change the HiDPI Awareness mode to 'Unaware' (which makes the behavior match 5.x).
Justin FrankelIf you try this workaround, let us know in the comments if it worked for you as well.
http://www.twitter.com/reaperblog
http://www.facebook.com/thereaperblog
http://www.facebook.com/groups/reaperblogcommunity
http://www.patreon.com/thereaperblog https://ameblo.jp/0compsihy-o46/entry-12649619659.html.
Bridging and VST Plug-in Run Mode
If you are running the 64 bit version of REAPER and wish to use older 32 bit plug-ins you will need to use bridging. By default, REAPER will attempt to work out for any plug-in that you use whether this bridging is required (Options, Preferences, Plug-ins, Compatibility). However, for any plug-in you can override this setting by right-clicking over the plug-in in the FX browser and choosing from the context menu Run as, and selecting one of three options which allow you to specify just how a plug-in is to be bridged. These options are:
Separate process: all bridged plugins for which this option is selected will be put into a single process, external to the main Reaper process. This has the advantage of minimising the resulting CPU load, but also carries a significant disadvantage: if one plugin is buggy and crashes the bridge process, all the other bridged plugins will die too.
Dedicated process: this puts each bridged plugin into a separate bridge process of its own. This will prevent a buggy plug-in from crashing the entire bridge, but it has the downside of increasing the overall CPU load.
Native only: Descargar open shot. is the default; the plug-ins are run inside the main Reaper process. Bridging can serve another useful function. Postbox 6 1 8 – powerful and flexible email client. Even though it is primarily intended for use with 32 bit plug-ins, you can if you wish also bridge (most likely in a dedicated process) any 64 bit plug-in. This has the effect of firewalling REAPER against any adverse effects that could potentially arise from a buggy 64 bit plug-in.
A further choice, Embed bridge UI, determines whether the bridged plug-in GUI is displayed in the FX Chain wrapper window (or as a floating window) or is displayed in a completely separate (Windows / OSX) window. The choice is provided as some bridged plug-ins behave better in one context than in the other. Remember! You should not store 32 bit plug-ins in the same directory as 64-bit plug-ins.
