v7.33+dev0203 - February 3 2025

[smandrap]

v7.33+dev0203 - February 3 2025

• * Includes feature branch: themeable track gain reduction meters
• * Includes feature branch: improved VST2/VST3 migration
• * Includes feature branch: spectral edit api
• * Includes feature branch: support formatting suffix used when automatically incrementing rendered files
• * Includes feature branch: actions to save and restore envelope latches
• * Includes feature branch: support disabling ARA for specific plugins
• * Includes feature branch: region editing preview display changes
• * Includes feature branch: region/marker lanes
• * Includes feature branch: MIDI overhaul, aftertouch/MPE-CC-autofilter, tweaks
• * Includes feature branch: parallel render via master
• * Includes feature branch: multithreaded render postprocessing
• * Includes feature branch: optionally display recording pass, markers, regions, wildcards in Big Clock
• * Includes feature branch: render all selected items or razor edit areas as a single file
• * Includes feature branch: ripple edit when editing media item edges
• * Includes feature branch: MIDI item reconfiguration on effective timebase change
• * Includes feature branch: phase alignment dialog
• * Includes feature branch: per-lane ripple editing
• * Includes feature branch: graphical crossfade editor
• * Includes feature branch: playback support for rendered files
• * Includes feature branch: take FX tail-length utilization
• * Includes feature branch: trim leading/trailing silence when rendering
• * Includes feature branch: auto-bypass plug-ins with PDC when record armed
• + Project load: hide any FX UIs when displaying warnings after loading project to ensure that warning window is visible
• + Razor edits: improve behavior when pasting razor edits into a fixed lane track [p=2843440]
• # VST3: IPluginCompatibility/moduleinfo.json fuzzy-match their IDs, should hopefully fix various plug-in matches
• # VST3: fix program index restoration when loading VST2 state [p=2843655]

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[vsthem]

Have there been any hints as to when

MIDI item reconfiguration on effective timebase change

Might make it into a main release?

[smandrap]

Originally Posted by vsthem

Have there been any hints as to when

MIDI item reconfiguration on effective timebase change

Might make it into a main release?

I think it still has some issues and I hope they give it some more love soon

[EvilDragon]

The way I tested the migration fuzzy matching:

- went to vstplugins64.ini and removed the whole compat section, and K7/K8 lines
- rescanned plugins to pick this info back up
- opened my K1, K4, K5, K6 migration test projects

Results: still not working at all for K1, K4 and K5!

[ovnis]

Tested with a clean Reaper.

No migration from VST2 to VST3:

- Repro
- Kontakt 5
- Dune 3 (migration works perfectly with Cubase 14)(edited)
- GRT amp Stereo (waves) (migration works perfectly with Cubase 14)
- Doubler4 Stereo (waves) (migration works perfectly with Cubase 14)

Bad migration from VST2 to VST3 (preset is not recalled):

- All Valhalla plugs (migration works perfectly with Cubase 14)
- Serum (migration works perfectly with Cubase 14)
- FM8 (migration works perfectly with Cubase 14)
- Duck (migration works perfectly with Cubase 14)

You can download the Duck demo (VST2 and VST3) here: https://deviousmachines.com/duck-downloads/

Bad migration from VST2 to VST3 (edited):

- Kontakt 6 to Kontakt 7 (preset is recalled but it should be transfered to Kontakt 8 and not Kontakt 7)

Bad migration from VST3 to VST3:

- Kontakt 7 to Kontakt 8 (preset is recalled but no warning screen about the plug transfert. Inside the FX window, bad name : "Kontakt 7" remains or it should be displayed "Kontakt 8")

Edited 2 times

[EvilDragon]

I don't think it's reasonable to expect plugin names to change upon migration - this is keeping your plugin renames, and any manual plugin renames you could be doing after you've loaded a plugin.

[Funkybot]

No change here since yesterday with my U-he test project (did a Clear Cache and full Plugin Rescan):

1. RePro-1*
2. RePro-5*
3. FilterscapeVA
4. FilterscapeQ6
5. ACE
6. Zebra2
7. ZeraHZ
8. Bazille
9. Presswerk
10. Diva
11. Satin
12. Hive
13. ColourCopy
14. Twangstrom

*Didn't work.

The others all migrated successfully.

RPP for the new Test Project is here:
https://www.dropbox.com/scl/fi/772c1...=22ufetfk&dl=0

Latest reaper-vstplugins64.ini here:
https://www.dropbox.com/scl/fi/7wy9y...=xsvx11w9&dl=0

Windows.

[Justin]

Originally Posted by ovnis

Tested with a clean Reaper.

No migration from VST2 to VST3:

- Kontakt 5
- GRT amp Stereo (waves) (migration works perfectly with Cubase 14)
- Doubler4 Stereo (waves) (migration works perfectly with Cubase 14)

Bad migration from VST2 to VST3 (preset is not recalled):

- All Valhalla plugs (migration works perfectly with Cubase 14)
- Serum (migration works perfectly with Cubase 14)
- FM8 (migration works perfectly with Cubase 14)
- Duck (migration works perfectly with Cubase 14)

You can download the Duck demo (VST2 and VST3) here: https://deviousmachines.com/duck-downloads/

Bad migration from VST2 to VST3 (edited):

- Kontakt 6 to Kontakt 7 (preset is recalled but it should be transfered to Kontakt 8 and not Kontakt 7)

Bad migration from VST3 to VST3:

- Kontakt 7 to Kontakt 8 (preset is recalled but no warning screen about the plug transfert. Inside the FX window, bad name : "Kontakt 7" remains or it should be displayed "Kontakt 8")

Edited

ah looks like a lot of plugins don't support the tryVst2StateLoad() format, trying something relating to that

[sockmonkey72]

Originally Posted by vsthem

Have there been any hints as to when

MIDI item reconfiguration on effective timebase change

Might make it into a main release?

Speaking of work in this area, it would be really friendly to provide an option to re-PPQ imported MIDI data (when importing files -> MIDI items) to the REAPER default. I'd prefer to not need to deal with a mishmash of PPQs from various provenances when writing scripts, for example.

IIRC there's also no easy way to extract a PPQ from a MIDI take. You need to do something like this:

  local qn1 = reaper.MIDI_GetProjQNFromPPQPos(take, 0)
  local qn2 = qn1 + 1
  return math.floor(reaper.MIDI_GetPPQPosFromProjQN(take, qn2) - reaper.MIDI_GetPPQPosFromProjQN(take, qn1))

(probably the conversion back from QN -> ppqpos is unnecessary, it should be 0). Anyway, sorry for the OT.

[Justin]

Originally Posted by Funkybot

No change here since yesterday with my U-he test project (did a Clear Cache and full Plugin Rescan):

1. RePro-1*
2. RePro-5*

Very odd, those are working here using the exact same setup (and I've checked your .ini and it has the same settings as mine!). You 100% certain it was +dev0203?

[Funkybot]

Originally Posted by Justin

Very odd, those are working here using the exact same setup (and I've checked your .ini and it has the same settings as mine!). You 100% certain it was +dev0203?

100% sure.


And when I add the VST2 back in, it's this revision, which is the latest:

[_Stevie_]

Not sure if it's only me, but Kontakt 8 doesn't get an xvst3 entry, which essentially means, when I remove K7, it doesn't pick up K8. Did a rescan, but situation remains the same.

[EvilDragon]

Hmmmm, can't confirm here. K8 promptly replaces K6 and K7 in my case.

Are you sure you removed K8 from vstplugins64.ini before rescan?

[_Stevie_]

I didn't remove it, but I did a complete rescan. I'll give it another try. (btw, macOS here)

[Justin]

Originally Posted by Funkybot

100% sure.


And when I add the VST2 back in, it's this revision, which is the latest:

hmm the VST2 is still in the ini file, which may be why it is still trying to use it instead of migrating to the vst3?

Repro_1.dll=00BC99DB7272D301,1968332593,Repro-1 (u-he)!!!VSTi
Repro_5.dll=00BC99DB7272D301,1968332597,Repro-5 (u-he)!!!VSTi

[Funkybot]

Originally Posted by Justin

hmm the VST2 is still in the ini file, which may be why it is still trying to use it instead of migrating to the vst3?

Weird, I did `Clear Cache and Rescan VST Paths for all plugins`. Assuming that's the right one. I wonder if there's an older version in a different plugin folder. Will go hunting...

[ovnis]

Repro migration doesn't work, too. But it works with Cubase (last demo version).

[Justin]

Originally Posted by Funkybot

Weird, I did `Clear Cache and Rescan VST Paths for all plugins`. Assuming that's the right one. I wonder if there's an older version in a different plugin folder. Will go hunting...

Also, make sure you don't have "Allow multiple plug-ins with the same VST3 UID (not recommended)" checked.

[Funkybot]

Originally Posted by Justin

Also, make sure you don't have "Allow multiple plug-ins with the same VST3 UID (not recommended)" checked.

Still not working unfortunately. I definitely do not have "Allow multiple plug-ins with the same VST3 UID (not recommended)" checked. Never did. But confirmed.

Steps taken:

I did another `Clear Cache and Rescan VST Paths for all plugins' scan. This time, U-he VST2's hidden off entirely. Even got rid of some junk VST plugin folders in case there was an install somewhere else (there wasn't - but didn't need these anyway). Reloaded the same project and got the same errors with RePro-1 and RePro-5.

Latest version of the reaper-vstplugins64.ini:
https://www.dropbox.com/scl/fi/7wy9y...=x33okuv5&dl=0

Adding my reaper.ini here in case it helps:
https://www.dropbox.com/scl/fi/kibu5...=cxjgr9w0&dl=0

And the test project here:
https://www.dropbox.com/scl/fi/772c1...=m7qz25d8&dl=0

[ovnis]

Update: v7.33+dev0203a


GOOD :

- All Valhalla plugs
- Serum
- Duck
- Massive
- Massive X
- Transient Master
- FM8
- Pro-Q3

No migration from VST2 to VST3 :

- DUNE 3
- Repro
- GRT amp Stereo
- Doubler4 Stereo
- Kontakt 5


Edited

[Justin]

what version of Repro are y’all using?

[ovnis]

The same as Funkybot: 1.v1.1.3.16797

[Funkybot]

Originally Posted by ovnis

The same as Funkybot: 1.v1.1.3.16797

Yep. Thanks.

[ovnis]

I couldn't manage to transfer Satain (u-he) VST2 to VST3 at all. I opened my project with Satain VST2, then saved my project. I deleted Satain VST2, and then the migration to VST3 went smoothly.


Maybe the old project I opened had been created with a version of Satan that was older than the one I had already installed several months ago?


It seems to be the same issue with Valhalla plugs.

[Tale]

• # VST3: IPluginCompatibility/moduleinfo.json fuzzy-match their IDs, should hopefully fix various plug-in matches
• # VST3: fix program index restoration when loading VST2 state [p=2843655]

I've just tested VST2 to VST3 migration for For Martinic Kee Bass again (in v7.33+dev0203a on Windows 10), and it seems to work well now, w00h00!

I will test some of or other plugins later, but I suspect all of them will work.

[EvilDragon]

Originally Posted by Justin

Also, make sure you don't have "Allow multiple plug-ins with the same VST3 UID (not recommended)" checked.

Disabled it, no change as far as Kontakt migrations are concerned...

[anomar]

Razor edits: improve behavior when pasting razor edits into a fixed lane track [p=2843440]

I think it is not yet fixed with razor copy/paste.

[schwa]

Originally Posted by anomar

Razor edits: improve behavior when pasting razor edits into a fixed lane track [p=2843440]

I think it is not yet fixed with razor copy/paste.

Can you be more specific please?

[Daodan]

Originally Posted by schwa

Can you be more specific please?

Same behavior as before

[d. gauss]

Slightly off topic, but very much related:

Speaking of migration, is there a way to view the settings of an AU plugin on a windows machine? Not looking for migration, per se, just a visual txt would do, so i could enter the values manually. (i.e. have some old projects that were done on a mac, but now i'm on windoze, but have same plugins)

[EvilDragon]

That is not possible, plugin data is serialized in a binary format.

[STOP]

I don't see v7.33+dev0203a listed anywhere.

v7.33+dev0203a - February 3 2025

• * Includes feature branch: themeable track gain reduction meters
• * Includes feature branch: improved VST2/VST3 migration
• * Includes feature branch: spectral edit api
• * Includes feature branch: support formatting suffix used when automatically incrementing rendered files
• * Includes feature branch: actions to save and restore envelope latches
• * Includes feature branch: support disabling ARA for specific plugins
• * Includes feature branch: region editing preview display changes
• * Includes feature branch: region/marker lanes
• * Includes feature branch: MIDI overhaul, aftertouch/MPE-CC-autofilter, tweaks
• * Includes feature branch: parallel render via master
• * Includes feature branch: multithreaded render postprocessing
• * Includes feature branch: optionally display recording pass, markers, regions, wildcards in Big Clock
• * Includes feature branch: render all selected items or razor edit areas as a single file
• * Includes feature branch: ripple edit when editing media item edges
• * Includes feature branch: MIDI item reconfiguration on effective timebase change
• * Includes feature branch: phase alignment dialog
• * Includes feature branch: per-lane ripple editing
• * Includes feature branch: graphical crossfade editor
• * Includes feature branch: playback support for rendered files
• * Includes feature branch: take FX tail-length utilization
• * Includes feature branch: trim leading/trailing silence when rendering
• * Includes feature branch: auto-bypass plug-ins with PDC when record armed
• # VST3: when loading migrated vst2 chunk state, try raw state data before tryVst2StateLoad-compatible state date

This thread is for pre-release features discussion. Use the Feature Requests forum for other requests.

Changelog - Pre-Releases

Generated by X-Raym's REAPER ChangeLog to BBCode

[anomar]

Quote - Can you be more specific please?

Hi Schwa!
1) Make a Razor Selection on Source track
2) Copy the selection with Ctrl+C
3) Go To destination track (fixed lane)
4) Paste with Ctrl+V
Result: a empty line is added

Reapeat steps 1 to 4
Result: a lot of empty lines are added!

I made a licecap I think clarify this issue.

(I saw that @Daodan post ahead of me.)

Thanks.

[_Stevie_]

Originally Posted by _Stevie_

Not sure if it's only me, but Kontakt 8 doesn't get an xvst3 entry, which essentially means, when I remove K7, it doesn't pick up K8. Did a rescan, but situation remains the same.

So, I'm still not able to migrate to K8. Does anyone else have that issue on Mac?
On Windows, this seems to work.

[EvilDragon]

Still no changes over here when attempting to migrate K1/4/5 projects...

[Funkybot]

Checked 2.03a with RePro just to be sure and alas no change.

[ovnis]

dev0204


All waves work well, now.
Repro works.

Dune 3, which previously failed to migrate to VST3, loses all its settings after migration.

demo:
https://www.synapse-audio.com/dune3.html

[playtimer]

Originally Posted by ovnis

dev0204


All waves work well, now.

Can you please confirm is this from earlier Waves (V14, V13...) to V15?

All VST2 Waves plugins from these earlier versions in your older projects succesfully migrated to Waves V15 VST3?

If so, that is just great

[_Stevie_]

Yes, that's working here. VST2 V14 plugins from Windows loading V15 VST3 on Mac. So pretty amazing!

[playtimer]

Originally Posted by _Stevie_

Yes, that's working here. VST2 V14 plugins from Windows loading V15 VST3 on Mac. So pretty amazing!

That is sweet!

Thanks for testing and confirming, mate!