What's new in v1.2.2

No new features in this one. Seven things that were wrong are now right, and four of them could damage or lose something you had set up yourself.

Installing VFxM adds one button to REAPER’s main toolbar, which means writing to reaper-menu.ini. It now copies that file first, verbatim, into REAPER/Virtue/Backups/, along with a plain-English HOW_TO_RESTORE_YOUR_TOOLBAR.txt naming the file to copy back.

If an earlier version left you with a toolbar containing only the Virtue button, installing this one rebuilds it from your own backup rather than from REAPER’s factory defaults — the buttons you had, in the order you had them.

See Your toolbar backups for where the files are and how to restore one by hand.

A separate bug in the same file, and this one could take a toolbar you had built yourself.

REAPER reads item_0, item_1, item_2 and so on, and stops at the first index that is missing. The uninstaller deleted its own line outright — so if you had dragged the Virtue button towards the front of your strip, everything after it stopped being drawn. Reinstalling did not bring it back either, because the new button was appended past the gap.

The slot is now blanked instead of deleted, leaving one unused separator and nothing else. Installing also closes a gap it finds in a toolbar that was already damaged this way.

Plug-ins you removed stop reappearing

REAPER keeps a separate plug-in cache for each processor architecture and rewrites only the one it is running as. On an Apple Silicon Mac the Intel file sits untouched from whenever that machine last ran an Intel build.

VFxM read all of them and merged the results, so a live list was blended with one that had stopped being maintained, and plug-ins uninstalled long ago kept appearing. REAPER’s own Clear cache/re-scan could never fix it, because REAPER rebuilds only the file it maintains — doing the right thing in the right order genuinely did not work.

VFxM now reads the same cache REAPER does. Nothing needs clearing or rescanning after updating.

A crashing plug-in is not tried twice

When a plug-in crashes REAPER during a thumbnail scan, VFxM records it so the scan can resume past it. That record was being written to one location and read back from another, so the empty-looking list let Resume Crashed Scan open the same plug-in and crash again.

Both halves now use the same file, and Resume Crashed Scan does what its name says. Your existing blocklist carries over.

The search cleared itself ten seconds after you clicked away — while you were still reading the results of what you had searched for — and there was no way to change it or switch it off.

It is now a setting in Settings → Interface:


On or off	Clear the search box when it is left alone
Delay	0 to 30 seconds, default 20
At 0	clears the moment focus leaves the box

Hidden panels stay hidden

Rebuilding the dock layout on a version bump forced all five panels visible, so an update handed back the Notes or Filters panel you had deliberately closed. Visibility is a preference, not part of the layout: it is now set only on a genuine first run, or when you press Reset Layout and ask for exactly that.

The scanner’s files move into the Virtue folder

Three working files belonging to the thumbnail scanner — the blocklist, the queue and the in-progress marker — were written loose at the top of REAPER’s resource folder, which is the one thing VFxM is not supposed to do to somebody else’s directory. They move into Virtue/ when you update, so a blocklist you built by crashing your way through a scan comes with them.

Upgrading

Install over the top. Favourites, banks, thumbnails, notes, categories, your licence, your window layout and your hidden panels all carry across.