v6.15+dev1108 - November 8 2020

[vitalker]

v6.15+dev1108 - November 8 2020

• * Includes branch: separate process VST/VST3 scanning
• * Includes feature branch: per-chain PDC mode and overhaul/optimization
• * Includes feature branch: media explorer and metadata improvements
• * Includes feature branch: razor editing
• + NINJAM: lower network latency in voice chat mode
• + Razor edit: add action to create area from cursor to mouse
• + Razor edit: add arrange view right-drag modifier to create razor edit area from cursor
• + Tooltips: fix reset of topmost pins on Windows when showing tooltip [t=243837]
• # Master mixer meter: fix resize flicker when muted
• # Media explorer: improve media label/tempo info positioning
• # Media explorer: prevent volume fader from being moved out of window when narrow [p=2357793]
• # VST: add undocumented vst_scan ini setting to allow disabling separate-process scanning
• # VST: fix new plug-in marking when scanning out of process

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

[Phazma]

Dear devs, I know this is not related to razor edit, but seeing that you are adding right mouse drag options for the arrange view, would you please consider adding a modifier option for deleting items when right dragging over the arrange (ideally with some possibility to override the item right click context - like the similar option in the editor)?

[JamesPeters]

There's a bug, related to per-chain PDC mode and overhaul/optimization for this DEV build and the prior one 1026 (the behavior exists in both builds). Tested using Reaper for Linux (x86_64):

The famous ReEQ (JS plugin) v1.0.11 reveals a minor bug...either in itself, Reaper, or both? In HQ mode, ReEQ requires 16 samples latency, but it's not reporting correctly.

Latency in HQ mode is initially reported when I switch from eco to HQ, with playback stopped. (16/64 samples, since I use a 64 sample size buffer in ALSA.) But as soon as I start playback that reported latency disappears (not showing as reported to Reaper) from the fx browser window and the Reaper performance meter.

When I try the other PDC modes, they also have the 16 samples latency disappear (not showing as reported to Reaper) when I hit play.

I tested ReEQ in eco mode and in HQ mode to see if they added 16 samples (looking at the recorded output and comparing sample positions) and the HQ mode does add 16 samples.

For comparison, I tried the same thing with other plugins including VST that have latency, and other JS plugins which have latency. None of the other plugins I have exhibit this behavior. If they report latency, it remains reported during playback and also when playback is stopped.

In Reaper for Linux 6.15 (official non-DEV build) this doesn't happen. PDC is reported correctly.

(edit) Confirmed this is fixed in Prerelease v6.15+dev1109.

[Mercado_Negro]

A blacklist for plugins that crashed when opening REAPER would be very useful because the user don't have to clear cache and rescan again when a new version of the plugin is installed.

[Paul1982]

Hello, some issue with the UI. Before, buttons were OK:


But now, they are stretched:

[Vagelis]

Originally Posted by vitalker

v6.15+dev1108 - November 8 2020

[*]+ Razor edit: add action to create area from cursor to mouse[*]+ Razor edit: add arrange view right-drag modifier to create razor edit area from cursor

This is very nice addition thank you devs!

Now i wish if we could also extend the RE edges to mouse position with a single click but not from the cursor.

[Justin]

Originally Posted by Mercado_Negro

A blacklist for plugins that crashed when opening REAPER would be very useful because the user don't have to clear cache and rescan again when a new version of the plugin is installed.

If a plug-in is hidden due to crash on scan, installing a different version of the plug-in (assuming the last-modified time of the file changes) will not require clear-cache, it will be scanned again. But a list of failed-loaded plugins might be useful, anyway

[Skorobagatko]

Originally Posted by Vagelis

This is very nice addition thank you devs!

Now i wish if we could also extend the RE edges to mouse position with a single click but not from the cursor.

+1 for this

[Mercado_Negro]

Originally Posted by Justin

If a plug-in is hidden due to crash on scan, installing a different version of the plug-in (assuming the last-modified time of the file changes) will not require clear-cache, it will be scanned again. But a list of failed-loaded plugins might be useful, anyway

This is failing lately, Justin. REAPER used to do that all the time but now it's very rare (it's not seeing new versions).

A list of failed-loaded plugins would be a fast way to make them active again if the user decides so.

[Arthur McArthur]

Since work has resumed on the new media explorer I'd like to re-raise two regressions from the old media explorer behaviour that are a constant bother when browsing samples:

Dragging a sample and releasing it returns the view to the top of the folder and stops preview of the item. This is very easy to do accidentally when you are quickly browsing:

https://i.imgur.com/5HFIGw2.gif


Using the mousewheel to quickly scroll away from the selected sound while it is playing snaps back the view of the media explorer to the selected item :

https://i.imgur.com/lUVSkun.gif

[mschnell]

Originally Posted by vitalker

• * Includes feature branch: per-chain PDC mode and overhaul/optimization

AFAIK, the suggested improvement is not to add the latencies rounded up to block size, but rounding to block size after adding.

Will the PDC calculation of parallel pin routed VSTs be cared of (in the released version the PDCs are added for the track delay instead of using the max PDC.)

Will the a delay for JSFXes in the "dry" path be added (regarding the PDC) ? In the released version this does happen for VSTs but not for JSFXes.

-Michael

[ivansc]

Originally Posted by Justin

If a plug-in is hidden due to crash on scan, installing a different version of the plug-in (assuming the last-modified time of the file changes) will not require clear-cache, it will be scanned again. But a list of failed-loaded plugins might be useful, anyway

Absolutely. Cakewalk had this in Sonar for years & it is still in the current Bandlab version... I miss it in Reaper & would love to see this added.

[Justin]

Originally Posted by JamesPeters

There's a bug, related to per-chain PDC mode and overhaul/optimization for this DEV build and the prior one 1026 (the behavior exists in both builds). Tested using Reaper for Linux (x86_64):

The famous ReEQ (JS plugin) v1.0.11 reveals a minor bug...either in itself, Reaper, or both? (I posted this on the ReEQ thread as well.) In HQ mode, ReEQ requires 16 samples latency, but it's not reporting correctly.

Latency in HQ mode is initially reported when I switch from eco to HQ, with playback stopped. (16/64 samples, since I use a 64 sample size buffer in ALSA.) But as soon as I start playback that reported latency disappears (not showing as reported to Reaper) from the fx browser window and the Reaper performance meter.

When I try the other PDC modes, they also have the 16 samples latency disappear (not showing as reported to Reaper) when I hit play.

I tested ReEQ in eco mode and in HQ mode to see if they added 16 samples (looking at the recorded output and comparing sample positions) and the HQ mode does add 16 samples.

For comparison, I tried the same thing with other plugins including VST that have latency, and other JS plugins which have latency. None of the other plugins I have exhibit this behavior. If they report latency, it remains reported during playback and also when playback is stopped.

In Reaper for Linux 6.15 (official non-DEV build) this doesn't happen. PDC is reported correctly.

Thanks, fixing!

[Justin]

Originally Posted by Mercado_Negro

This is failing lately, Justin. REAPER used to do that all the time but now it's very rare (it's not seeing new versions).

A list of failed-loaded plugins would be a fast way to make them active again if the user decides so.

Hmm any idea in what instance it is failing? Does the modified-time change?

[FeedTheCat]

Originally Posted by vitalker

v6.15+dev1108 - November 8 2020

• # Media explorer: improve media label/tempo info positioning
• # Media explorer: prevent volume fader from being moved out of window when narrow [p=2357793]

It's perfect now, thx

[Mercado_Negro]

Originally Posted by Justin

Hmm any idea in what instance it is failing? Does the modified-time change?

I'll try tomorrow a few plug-ins I've updated in the past days.

[BirdBird]

Originally Posted by Arthur McArthur

Since work has resumed on the new media explorer I'd like to re-raise two regressions from the old media explorer behaviour that are a constant bother when browsing samples:

Dragging a sample and releasing it returns the view to the top of the folder and stops preview of the item. This is very easy to do accidentally when you are quickly browsing:

https://i.imgur.com/5HFIGw2.gif


Using the mousewheel to quickly scroll away from the selected sound while it is playing snaps back the view of the media explorer to the selected item :

https://i.imgur.com/lUVSkun.gif

+1
These also bother me everytime I use the media explorer.
(I believe the second behaviour isn't new, it was always present.)

[BirdBird]

Originally Posted by vitalker

[*]+ Razor edit: add action to create area from cursor to mouse

This currently cannot be used with left click mouse-modifiers as they also move the edit cursor. (Which was one of the requests)
This has been a long going issue with actions assigned to left-click modifiers from the action list moving the edit cursor.

There should be an option in the modifier menu that disables this behaviour.
In its current state the description of behaviour of the modifier does not match what it does, it also prevents the usage of variety of actions through mouse modifiers.

[musicbynumbers]

I get these too and would love to see them fixed

Originally Posted by Arthur McArthur

Since work has resumed on the new media explorer I'd like to re-raise two regressions from the old media explorer behaviour that are a constant bother when browsing samples:

Dragging a sample and releasing it returns the view to the top of the folder and stops preview of the item. This is very easy to do accidentally when you are quickly browsing:

https://i.imgur.com/5HFIGw2.gif


Using the mousewheel to quickly scroll away from the selected sound while it is playing snaps back the view of the media explorer to the selected item :

https://i.imgur.com/lUVSkun.gif

[Reflected]

I don't know since when we can't open a track's fx window if it doesn't have any fx yet. :/

in the past if I clicked on track fx, the fx window of this track opened even if it didn't have any fx yet.


Can you please add this as option at least?

thanks

[Mercado_Negro]

Hi Justin. I just updated my MacBook Pro to Catalina and found a problem with REAPER and my Waves plugins while scanning. REAPER crashed (well, it didn't crash because it was scanning on a separate process) while scanning one of the Waves .vst3 files. It happens when a window pops up asking for some samples I didn't install and I try to click on "cancel" on that window. I've tried a lot of things but I can't make it work and now I'm missing lots of my Waves plugins (VST3).