v6.19+dev0109 - January 9 2021

[Edgemeal]

v6.19+dev0109 - January 9 2021
* Includes branch: IDE autocomplete
* Internal Register() API cleanups
* Includes branch: 2nd pass render
* Includes feature branch: per-chain PDC mode and overhaul/optimization
* Includes feature branch: razor editing
+ Automation items: fix potential crash when splitting automation item under mouse cursor [t=247651]
+ Envelopes: fix automation items potentially left behind when moving media items across tracks
+ FX browser: improve selection behavior when renaming FX
+ Media explorer: add track number column (not displayed by default)
+ Media explorer: restore selection after renaming file [p=2389201]
+ ReaScript: Lua gmem_attach() returns previous global memory segment name [t=240447]
+ ReaScript: add preference for IDE watch window update interval
+ VST: improved plug-in scanning status messages
+ VST: option to not scan for new/updated plug-ins on startup
+ VST: preferences lists skipped plug-ins and allows manual re-scan
+ Video: do not show intermediate frames when seeking playback long distances
+ Video: do not show intermediate frames when stopped and repositioning cursor, unless rapidly repositioning cursor
# VST: remove redundant splash messages when VST scan window is open
# Video: typo fix [t=247675]

Full changelog / Latest pre-releases

[musicbynumbers]

+ Video: do not show intermediate frames when seeking playback long distances

Thanks for going the extra mile there Justin!

Will give that a try and see how it goes.

[Nixon]

+ Media explorer: add track number column (not displayed by default)

Thanks Devs

Also thanks for keeping Track number metadata in batch processing.

[musicbynumbers]

The video seems to work well for me when there's only one video in the project with various formats all seeking well in scrubbing or big wide gap seeks too.

But..

If you have two or more videos in the same project than some weird things happen.

When seeking (by clicking the ruler to move the playhead). The video window can take nearly 2 seconds to show the actual frame I've clicked on. (I think more so if each video has different frame rates)

It will first show either the frame where the loop points start or if there are no loop points, I think it will show the first frame of the video at 0 seconds in the project.

This takes around 1.5 to 2 seconds depending I think on how many videos there are.

If there's a way to stop this, that would be amazing.

This might be related to a setting though so would be nice if someone else can test this

EDIT:

On further testing..

if all the videos are the same format/frame rate etc then there's only 2 things that cause the frame to be delayed and wrong for a sec

1. If loop is on
2. The first time you jump from one video to a different/new one (but it's then fine if you stay within that video

If all the videos are different then it happens in any situations.

[Justin]

musicbynumbers at this point I think the only video-related feedback we'll look at at this point is how it relates to 6.19 (e.g. if there are behaviors that are noticeably worse than 6.19, I'd like to hear that).

[musicbynumbers]

Originally Posted by Justin

musicbynumbers at this point I think the only video-related feedback we'll look at at this point is how it relates to 6.19 (e.g. if there are behaviors that are noticeably worse than 6.19, I'd like to hear that).

Ah, no worries then.

That behaviour I described is the last thing I can see wrong with video seeking (and maybe related to some of the big jump seeking issues others are seeing) but I'm super happy with the rest of it so will leave it to others to feedback on it now. all good

[Phazma]

Originally Posted by Justin

musicbynumbers at this point I think the only video-related feedback we'll look at at this point is how it relates to 6.19 (e.g. if there are behaviors that are noticeably worse than 6.19, I'd like to hear that).

In this pre-release the video window behaves way better than 6.19 in every regard. I am sure some more advanced people can do more thorough tests but to me it seems perfect now! Also can't reproduce the issues musicbynumbers is having.

Thanks a lot for taking the time to tackle all of these video related issues and nitpicks!

[J Reverb]

+ ReaScript: Lua gmem_attach() returns previous global memory segment name Really cool !
+ ReaScript: add preference for IDE watch window update interval
This is so so so good ! thank you now my eyes and my brain doesn't hurt no more lol

[planetnine]

Originally Posted by Nixon

+ Media explorer: add track number column (not displayed by default)

Thanks Devs

Also thanks for keeping Track number metadata in batch processing.

I’ve wondered why Project Bay doesn’t have a track number column, this would be useful...

>

[cfillion]

Calling the OpenMediaExplorer API function hangs REAPER no matter the parameter values. It works in v6.19.

reaper.OpenMediaExplorer('', false)

Spindump:

  Thread 0x1ed30            DispatchQueue 1           Thread name "reaper"      1001 samples (1-1001)     priority 46 (base 46)     cpu time 9.977s (35.7G cycles, 53.9G instructions, 0.66c/i)
  1001  start + 52 (REAPER + 7732) [0x109ba4e34]
    1001  NSApplicationMain + 777 (AppKit + 10952) [0x7fff2fba5ac8]
      1001  -[NSApplication run] + 755 (AppKit + 79296) [0x7fff2fbb65c0]
        1001  -[REAPERapp sendEvent:] + 3739 (REAPER + 3822571) [0x109f483eb]
          1001  -[NSApplication(NSEvent) sendEvent:] + 331 (AppKit + 151115) [0x7fff2fbc7e4b]
            1001  -[NSWindow(NSEventRouting) sendEvent:] + 478 (AppKit + 1594983) [0x7fff2fd28667]
              1001  -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 1899 (AppKit + 1597466) [0x7fff2fd2901a]
                1001  -[REAPERSwell_listview mouseUp:] + 249 (REAPER + 5889401) [0x10a140d79]
                  1001  -[NSTableView mouseDown:] + 7098 (AppKit + 3972650) [0x7fff2ff6ce2a]
                    1001  -[NSTableView _sendAction:to:row:column:] + 121 (AppKit + 3979663) [0x7fff2ff6e98f]
                      1001  -[NSControl sendAction:to:] + 86 (AppKit + 3631506) [0x7fff2ff19992]
                        1001  -[NSApplication(NSResponder) sendAction:to:from:] + 312 (AppKit + 3196484) [0x7fff2feaf644]
                          1001  -[REAPERSwell_hwnd swellOnControlDoubleClick:] + 527 (REAPER + 5762783) [0x10a121edf]
                            1001  SwellDialogDefaultWindowProc(HWND__*, unsigned int, unsigned long, long) + 438 (REAPER + 5770454) [0x10a123cd6]
                              1001  ActionWnd::wndProc(HWND__*, unsigned int, unsigned long, long) + 170 (REAPER + 7446378) [0x10a2bcf6a]
                                1001  ActionsProc(HWND__*, unsigned int, unsigned long, long) + 11367 (REAPER + 7425383) [0x10a2b7d67]
                                  1001  SwellDialogDefaultWindowProc(HWND__*, unsigned int, unsigned long, long) + 438 (REAPER + 5770454) [0x10a123cd6]
                                    1001  ActionWnd::wndProc(HWND__*, unsigned int, unsigned long, long) + 170 (REAPER + 7446378) [0x10a2bcf6a]
                                      1001  ActionsProc(HWND__*, unsigned int, unsigned long, long) + 8898 (REAPER + 7422914) [0x10a2b73c2]
                                        1001  kbd_onAction(KbdAccel*, int, int, int, bool, KbdSectionInfo*, HWND__*) + 1768 (REAPER + 3789432) [0x109f40278]
                                          1001  ProcessCustomCommand(KbdSectionInfo*, int, int, int, int, HWND__*) + 477 (REAPER + 7383453) [0x10a2ad99d]
                                            1001  RunReaScript(char const*, int, KbdSectionInfo*, int, bool, int) + 1705 (REAPER + 8146105) [0x10a367cb9]
                                              1001  LuaAPI::InterpretScript(char const*, char const*) + 385 (REAPER + 7804225) [0x10a314541]
                                                1001  lua_pcallk + 152 (REAPER + 8015704) [0x10a347f58]
                                                  1001  luaD_pcall + 64 (REAPER + 3764976) [0x109f3a2f0]
                                                    1001  luaD_rawrunprotected + 107 (REAPER + 3765659) [0x109f3a59b]
                                                      1001  luaD_callnoyield + 70 (REAPER + 3757990) [0x109f387a6]
                                                        1001  luaV_execute + 1982 (REAPER + 4949246) [0x10a05b4fe]
                                                          1001  luaD_precall + 2132 (REAPER + 3755428) [0x109f37da4]
                                                            641   OpenMediaExplorer(char const*, bool) + 8 (REAPER + 7112376) [0x10a26b6b8] (running)
                                                            348   OpenMediaExplorer(char const*, bool) + 5 (REAPER + 7112373) [0x10a26b6b5] (running)
                                                            7     OpenMediaExplorer(char const*, bool) + 0 (REAPER + 7112368) [0x10a26b6b0] (running)
                                                            3     OpenMediaExplorer(char const*, bool) + 2 (REAPER + 7112370) [0x10a26b6b2] (running)
                                                            1     OpenMediaExplorer(char const*, bool) + 8 (REAPER + 7112376) [0x10a26b6b8]
                                                             *1     ??? (kernel + 1734656) [0xffffff80003a7800] (runnable)
                                                            1     OpenMediaExplorer(char const*, bool) + 5 (REAPER + 7112373) [0x10a26b6b5]
                                                             *1     ??? (kernel + 1734656) [0xffffff80003a7800] (runnable)

[Funkybot]

If we're not done with the Media Explorer...

1. This dialog box really needs a cancel button IMO. EDIT: I should add, hitting the "x" to close the dialog box [with no effect] does nothing. The window stays open. So fixing that bug may negate the need for a cancel button.


2. When dealing with rx2 files, I can't seem to find any way to bulk-edit tags in the Media Explorer. Here I'm trying to manually enter BPM information for these files.

Example 1: Right Click "Edit Metadata Tags -> BPM" has no effect on rx2 files. No edit window appears. Works on .wav files.

Example 2: I'm trying to set the highlighted loops to all show 84 BPM in the BPM column. I'd like to be able to highlight multiple files, double click (or maybe modifier+click), have the selection get retained, enter the BPM for one, then have that BPM apply to all.

[schwa]

Originally Posted by Funkybot

Example 1: Right Click "Edit Metadata Tags -> BPM" has no effect on rx2 files. No edit window appears. Works on .wav files.

You can write values in the media explorer that will persist for REX files, but they can't be written back to the file because it's a closed format.

[nikki5000]

I've set the mouse modifier for media bottom half to Razor Editing.

Is it possible to switch to Razor Edit cursor while hovering over the media bottom half?
At the moment the cursor only switches after click/dragging.

When clicking the media bottom half the item doesn't get selected.
Left Click Modifier is set to "select items & move edit cursor".

"Duplicate Items" works on razor edit areas, "toggle take reverse" doesn't work.

edit: thank you for the updates. Razor Editing is awesome!
Sorry for the newbie questions! ^^

[Funkybot]

Originally Posted by schwa

You can write values in the media explorer that will persist for REX files, but they can't be written back to the file because it's a closed format.

Yeah, that makes sense. Just looking for some way to write values in the media explorer to multiple items at a time rather than one-by-one.

[AtmanActive]

+ VST: option to not scan for new/updated plug-ins on startup

@Justin: this is great! Thank you. What could be useful in this usage scenario is an action "Re-Scan VST Folders", so we can expose it as a button on our main toolbar, as opposed to having to click Options/Preferences/VST/Re-Scan each time we would like Reaper to do so. Just thinking about saving 4 clicks for 1 click. Since I believe that for some people (me included), this is the way forward: "don't scan on every startup, but do scan when I tell you to". A thing of mileage.

[Phazma]

Originally Posted by AtmanActive

+ VST: option to not scan for new/updated plug-ins on startup

@Justin: this is great! Thank you. What could be useful in this usage scenario is an action "Re-Scan VST Folders", so we can expose it as a button on our main toolbar, as opposed to having to click Options/Preferences/VST/Re-Scan each time we would like Reaper to do so. Just thinking about saving 4 clicks for 1 click. Since I believe that for some people (me included), this is the way forward: "don't scan on every startup, but do scan when I tell you to". A thing of mileage.

Great idea!

[Funkybot]

Originally Posted by AtmanActive

+ VST: option to not scan for new/updated plug-ins on startup

@Justin: this is great! Thank you. What could be useful in this usage scenario is an action "Re-Scan VST Folders", so we can expose it as a button on our main toolbar, as opposed to having to click Options/Preferences/VST/Re-Scan each time we would like Reaper to do so. Just thinking about saving 4 clicks for 1 click. Since I believe that for some people (me included), this is the way forward: "don't scan on every startup, but do scan when I tell you to". A thing of mileage.

Just an FYI - you can already right click in the FX Browser and Scan For New Plugins from there. Much faster than going to the preferences.

[daxliniere]

Originally Posted by Edgemeal

+ VST: improved plug-in scanning status messages
+ VST: option to not scan for new/updated plug-ins on startup
+ VST: preferences lists skipped plug-ins and allows manual re-scan

Hey everyone, happy new year!

Since there's been some action around plugin scanning, is it possible to implement a function to trim the existing VSTPLUGINS.INI (plus x86+x64, VSTrenames, etc) files to remove plugins that no longer exist?

As a beta tester, my VSTPLUGINS and VSTPLUGINS64 INI files are over 4100 lines combined(!)

I asked once before and someone suggested just deleting those files and letting REAPER rebuild them. This would be a huge problem as I have a lot of renames, specific settings for certain plugins, etc, that I would have to know, remember, and set again.

Thanks for considering it!

Cheers,
Dax.

[daxliniere]

A little suggestion for IDE key commands, in my favourite text editor, CTRL+D will duplicate whatever line you are on. If you have several lines selected, they will all be duplicated.
Saves a bunch of time.

[nofish]

@dax
At least the renames are stored separately in reaper-vstrenames(64).ini, so I'd think they should be kept intact when rebuilding vstplugins(64).ini (but maybe Justin/schwa can confirm or not).

[daxliniere]

Hey NoFish

Yes, my renames files are pretty huge, too. I'm sure that more than 70% of the lines in all of these files are superfluous.

[Arthur McArthur]

Could we get an option for "Insert sample player on new track" that doesn't float the FX window? The default settings on RS5K are fine 95% of the time and it's irritating when adding a bunch of samples that you have to subsequently close all the windows.

[daxliniere]

Originally Posted by Arthur McArthur

Could we get an option for "Insert sample player on new track" that doesn't float the FX window? The default settings on RS5K are fine 95% of the time and it's irritating when adding a bunch of samples that you have to subsequently close all the windows.

Hi Arthur,
Not sure if you would be happy with this solution, but REAPER has a cool function (SHIFT+ESC) which closes all open windows. Sometimes you have to run it twice in a row, but it's very useful and I use it all the time.

Hope that helps!
Dax.

[Arthur McArthur]

Originally Posted by daxliniere

Hi Arthur,
Not sure if you would be happy with this solution, but REAPER has a cool function (SHIFT+ESC) which closes all open windows. Sometimes you have to run it twice in a row, but it's very useful and I use it all the time.

Hope that helps!
Dax.

Yeah I have script doing the same thing mapped to my escape key. But having to do that every time I insert a sample (20-40 times each project) is a workflow killer.

[AtmanActive]

Originally Posted by Funkybot

Just an FYI - you can already right click in the FX Browser and Scan For New Plugins from there. Much faster than going to the preferences.

Thank you Funkybot.

But, I don't even use that one anymore. I'm adding my plug-ins to a track by right-clicking on the track's FX button and selecting an FX directly from the menu that pops up. That saves me a lot of clicks.

[daxliniere]

Originally Posted by AtmanActive

Thank you Funkybot.

But, I don't even use that one anymore. I'm adding my plug-ins to a track by right-clicking on the track's FX button and selecting an FX directly from the menu that pops up. That saves me a lot of clicks.

You can also click F5.

[Tale]

+ VST: option to not scan for new/updated plug-ins on startup

I had to manually enable "Scan new/updated plug-ins on startup" to get the old behavior, is that correct? Not a problem for me personally, but if this option is off by default, then this would likely make it harder for a new user to get plug-ins up and running.

EDIT: This was on Win64. I just quickly tested on macOS, and there option was already on by default.

[Justin]

Originally Posted by Tale

I had to manually enable "Scan new/updated plug-ins on startup" to get the old behavior, is that correct? Not a problem for me personally, but if this option is off by default, then this would likely make it harder for a new user to get plug-ins up and running.

EDIT: This was on Win64. I just quickly tested on macOS, and there option was already on by default.

Hmm it should have been on by default, maybe there was some ini setting that used to use that same bit? Maybe I'll give it a new fresh ini location...

[Funkybot]

Windows user here and it was on at startup here so definitely not global.

[Tale]

Originally Posted by Justin

Hmm it should have been on by default, maybe there was some ini setting that used to use that same bit? Maybe I'll give it a new fresh ini location...

FWIW, I have also installed +dev0109 on my Win10 computer at work, and there the option was also off. Note that I've installed countless prereleases on both machines, so yeah, it could well just be because of that. Then again, I've probably installed just as many on my Mac.

[Meo-Ada Mespotine]

+ ReaScript: add preference for IDE watch window update interval

YEEEEESSSS!!!

ThankYouThankYouThankYouThankYouThankYouThankYouTh ankYouThankYouThankYouThankYouThankYouThankYouThan kYouThankYouThankYouThankYouThankYouThankYouThankY ouThankYouThankYouThankYouThankYouThankYouThankYou ThankYouThankYouThankYouThankYouThankYou




Edit:

ReaScript: Lua gmem_attach() returns previous global memory segment name

Omg, that's also great