v6.46+dev0120 - January 20 2022

[sockmonkey72]

v6.46+dev0120 - January 20 2022

• * Includes feature branch: improved zoomed-in peaks performance
• * Includes feature branch: FX chain oversampling
• * Includes feature branch: render internals simplification/cleanup
• * Includes feature branch: user-defined action overhaul
• * Includes feature branch: media explorer toolbar
• * Includes feature branch: media item fixed lanes
• + JSFX: channel_mapper uses menu instead of +/- buttons to set number of channels
• + MIDI editor: actions to navigate prev/next note move edit cursor
• + MIDI editor: improve non-synchronized playback behavior when changing project tempo
• + Peaks: improve zoomed-in peaks performance, especially on compressed media
• + ReaLimit: gray out threshold slider when constant gain is enabled
• + ReaLimit: rename "link" control to "constant gain"
• + ReaLimit: set default threshold and ceiling both to 0dB
• + Video: add project_timeoffs variable
• + Video: fix incorrect restart of peaks building when editing project during peaks build [t=262058]
• + Video: improve text overlay preset (can also display timecode, add fit bg to text parameter, change defaults)
• + WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts
• + macOS: disable input event throttling by default

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

[sockmonkey72]

Looks like the universal version isn't notarized again. Thanks Apple!

[Phazma]

Originally Posted by sockmonkey72

[*]+ Peaks: improve zoomed-in peaks performance, especially on compressed media

Thanks, this is great! Looks like also editing of compressed formats works better now.

I guess there is little Reaper can do to improve the sometimes (randomly occurring) incorrect display of peaks decoded by the video decoder?



All audios from the screenshot above are perfectly in phase btw, but the .m4a one sometimes (but not always) looks like it is off by 1 sample when zooming in. Also changing playback position during a null-test sometimes randomly causes the audio of such files not to null while nulling again after a few more position changes (or playing from start again).

[Phazma]

Originally Posted by sockmonkey72

[*]+ macOS: disable input event throttling by default

Could this... possibly... be a subtle hint indicating a paradigm shift and willingness of eventually implementing this? :O (pls finally pls)

[Edgemeal]

I render/dry run a full project, when done rendering I click Stats button > Open render statistics in browser and file length is now always '0:00:000'. Seems to work fine in releases (v6.46,.45,.41)

Win10_x64

[airon]

Originally Posted by sockmonkey72

+ WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts

Where is this going ?

"ntracks" going to carry some flags ?

[ovnis]

"+ WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts"

May we have more details, please?

[gapalil001]

Originally Posted by ovnis

"+ WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts"

May we have more details, please?

the same question here. as i know, there is no trackidx for master track. but i hope it's mean what upgrading queue finally reached WALTER. many times ago i noticed that tcp.trackidx is conflicts with tcp.foldercomp (or maybe was fixed, but i didn't know)

[nvk]

Does the peaks performance apply to video as well?

[Justin]

Originally Posted by sockmonkey72

Looks like the universal version isn't notarized again. Thanks Apple!

thanks, fixed!

[Justin]

Originally Posted by ovnis

"+ WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts"

May we have more details, please?

Layouts can arrange depending on the current total track count -- the next build will better display track indices for tracks >= 1000 (rather than cropping it off).

[Justin]

Originally Posted by nvk

Does the peaks performance apply to video as well?

Yep. There's a caching layer to avoid many redundant decodes of source material when zoomed in.

[akademie]

Originally Posted by sockmonkey72

v6.46+dev0120 - January 20 2022

• + JSFX: channel_mapper uses menu instead of +/- buttons to set number of channels

I don't get it?
What's new about this? It was like that couple of +dev releases ago already.
Or is it something I don't spot?
I compared with v6.43+dev1231 and it is the same there.
???

[Justin]

Originally Posted by akademie

I don't get it?
What's new about this? It was like that couple of +dev releases ago already.
Or is it something I don't spot?
I compared with v6.43+dev1231 and it is the same there.
???

the JSFX channel_mapper's GUI now matches that of the pin mapper

[creal]

Originally Posted by Justin

the JSFX channel_mapper's GUI now matches that of the pin mapper

Yes, it fully makes sense.

[White Tie]

Originally Posted by ovnis

"+ WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts"

May we have more details, please?

trackidx is a scalar variable that is the track's number. ntracks is a scalar variable for the total number of tracks in the project. I am going to use trackix>999 to improve the display of track numbers on the default theme for projects with 1000 or more tracks.

[mlprod]

Originally Posted by sockmonkey72

v6.46+dev0120 - January 20 2022
[*]+ macOS: disable input event throttling by default[/list]

Wow, nice! Been a bit frustrated since switching to Mac OS regarding this. Can some sort of sensitivity setting be user controlled?

[Phazma]

Originally Posted by mlprod

Wow, nice! Been a bit frustrated since switching to Mac OS regarding this. Can some sort of sensitivity setting be user controlled?

In Reaper you can just enable or disable throttling mouse-events under 'Preferences > General > Advanced UI/system tweaks..."

If you disable throttling you will be able to do the inertial scrolling that is typical for mac (slow swipe scrolls a little bit and stops, fast swipe scrolls far and keeps scrolling for a while). This has been possible for over a year now and the only change is that it is now enabled by default for new installations. In my experience it is pretty well in line with other mac apps and you can tweak the scrolling speed on your mac overall under "System Preferences > Accessibility > Mouse & Trackpad > Mouse Options..." if scrolling with inertia is active.

What still isn't possible however is smooth/interpolated scrolling, meaning that like in your browser or other mac apps there are no scrolling-steps but the content on your screen moves pixel-by-pixel. When you scroll slowly in Reaper it still looks very choppy and there is no way around it unless the devs implement it as a new feature/preference.

[akademie]

Originally Posted by Justin

the JSFX channel_mapper's GUI now matches that of the pin mapper

Oh yeah, I got it, it's the specific "channel mapper" JSFX effect. I thought it was in/out pin assignment for the JSFX effects as in general
Thanks and sorry for silly question

[AZpercussion]

There are no check marks anymore, at least on Windows 8.1

[thommazk]

Since we're having some MIDI Editor fixes, can you take a look at this bug I found?
https://forum.cockos.com/showthread.php?t=261839

[Mercado_Negro]

Is REAPER now using a specific oversampling algorithm regardless of the playback resample mode chosen? I just made a test using different resample modes (sinc512, sinc64, r8brain, etc) and the rendered files they all null with each other.

[akademie]

Originally Posted by AZpercussion

There are no check marks anymore, at least on Windows 8.1

Confirming!
Windows 7 (32-bit) here.

[schwa]

Oops, thanks!

[Lannister]

Getting random crashes with EastWest Opus VST3 while putting a template together. Not sure if it's REAPER or Opus. Two simultanious crash events in Windows Event Viewer.

This one,

Faulting application name: reaper.exe, version: 73.201.157.154, time stamp: 0x61e97e3c
Faulting module name: reaper.exe, version: 73.201.157.154, time stamp: 0x61e97e3c
Exception code: 0xc0000005
Fault offset: 0x00000000000219b2
Faulting process ID: 0xfa8
Faulting application start time: 0x01d80e5c790436f6
Faulting application path: C:\Users"Lannister"\Audio\REAPER\reaper.exe
Faulting module path: C:\Users"Lannister"\Audio\REAPER\reaper.exe
Report ID: 8f50ece7-8488-467c-b1c4-702d74b5d138
Faulting package full name:
Faulting package-relative application ID:


and this one,

.NET Runtime

Application: reaper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00000001400219B2
Stack:

[PhelixK]

• + WALTER: add trackidx (0 is master, 1 is first track, <0 is unknown/invalid), ntracks (<0 if invalid) for track contexts

This is very welcome!
–also possible to show a warning when approaching critical mass, lol

• + ReaLimit: rename "link" control to "constant gain"
  

This label is better.

– how about (real) equal loudness listening mode, is it too heavy on CPU?


.

[mlprod]

Originally Posted by Phazma

In Reaper you can just enable or disable throttling mouse-events under 'Preferences > General > Advanced UI/system tweaks..."

If you disable throttling you will be able to do the inertial scrolling that is typical for mac (slow swipe scrolls a little bit and stops, fast swipe scrolls far and keeps scrolling for a while). This has been possible for over a year now and the only change is that it is now enabled by default for new installations. In my experience it is pretty well in line with other mac apps and you can tweak the scrolling speed on your mac overall under "System Preferences > Accessibility > Mouse & Trackpad > Mouse Options..." if scrolling with inertia is active.

What still isn't possible however is smooth/interpolated scrolling, meaning that like in your browser or other mac apps there are no scrolling-steps but the content on your screen moves pixel-by-pixel. When you scroll slowly in Reaper it still looks very choppy and there is no way around it unless the devs implement it as a new feature/preference.

Look at that, I had totally missed these options. Thanks!

[mccrabney]

razer editing in these fixed lanes has been a blast, and objects are moving from mixed track types in a clean and consistent way.

one issue i've run into: does anyone else accidentally trip "Item: Select all items in track," intending to select all items on the lane in which you're working?

would it be feasible to see that action [edit: cloned and modified to become] "Item: Select all items in track/lane" ?

a lane-aware version of that action would be preferable to a dedicated/discrete "select all items in lane" action. i forget that i'm working in a fixed lane and not just a "normal" track - the workflow is essentially identical. this is a good thing, and it wouldn't be the case anymore if we have to switch to a different set of deep muscle-memory actions for lanes vs for tracks.

[Phazma]

Originally Posted by mlprod

Look at that, I had totally missed these options. Thanks!

Tbh it's easy to miss them as they are hidden away in the advanced settings window with warnings of caution all over the place so I bet many users won't feel comfortable tweaking settings in that window.

I don't understand in the first place why the settings in that window are considered advanced and should be used with caution.. all of them are easily reversible and have never caused me trouble, unlike some other settings which are much more accessible and can potentially break Reaper in wrong combinations.

IMO it would make sense to create a "User Interface" subsection under 'Prefereces > General' to make these settings more accessible.

[nofish]

Originally Posted by sockmonkey72

[*]+ Peaks: improve zoomed-in peaks performance, especially on compressed media

Could it be a chance to also imrove peaks display accuracy?

https://forum.cockos.com/showthread.php?t=173221
https://forum.cockos.com/showthread....05#post2019605

(Bringing it up because here it was stated that the way it is currently is due to performance reasons, if I gahther it correcly).

[Phazma]

@nofish is this related to peaks sometimes appearing/disappearing at different zoom levels like in this gif?



Happens also often when cutting an item exactly on grid that the transient of the next/previous beat appears at certain zoom levels and disappears at others.

[mlprod]

Originally Posted by Phazma

Tbh it's easy to miss them as they are hidden away in the advanced settings window with warnings of caution all over the place so I bet many users won't feel comfortable tweaking settings in that window.

I don't understand in the first place why the settings in that window are considered advanced and should be used with caution.. all of them are easily reversible and have never caused me trouble, unlike some other settings which are much more accessible and can potentially break Reaper in wrong combinations.

IMO it would make sense to create a "User Interface" subsection under 'Prefereces > General' to make these settings more accessible.

Been in that window a lot tweaking things and still missed them somehow, but I agree they should be more accesible.

[srdmusic]

+ macOS: disable input event throttling by default

What is input event throttling?

[Phazma]

Originally Posted by srdmusic

What is input event throttling?

I explained it above in post #18:

Originally Posted by Phazma

If you disable throttling you will be able to do the inertial scrolling that is typical for mac (slow swipe scrolls a little bit and stops, fast swipe scrolls far and keeps scrolling for a while).

[Justin]

Originally Posted by Phazma

@nofish is this related to peaks sometimes appearing/disappearing at different zoom levels like in this gif?



Happens also often when cutting an item exactly on grid that the transient of the next/previous beat appears at certain zoom levels and disappears at others.

That is not peaks disappearing, that's effectively aliasing noise from the envelope + peaks being downsampled to such a low resolution... (live with it)

[srdmusic]

Originally Posted by Phazma

I explained it above in post #18:

Thanks

[stillshaded]

I’m getting very strange behavior in the midi editor. After performing any action the view will center on some seemingly random spot in the project. I can’t see any connection. I just keep having to scroll back over to where I am editing. Reverted back to the latest official release and I didn’t have the problem anymore.

[bolgwrad]

Originally Posted by mccrabney

razer editing in these fixed lanes has been a blast, and objects are moving from mixed track types in a clean and consistent way.

one issue i've run into: does anyone else accidentally trip "Item: Select all items in track," intending to select all items on the lane in which you're working?

would it be feasible to see that action [edit: cloned and modified to become] "Item: Select all items in track/lane" ?

a lane-aware version of that action would be preferable to a dedicated/discrete "select all items in lane" action. i forget that i'm working in a fixed lane and not just a "normal" track - the workflow is essentially identical. this is a good thing, and it wouldn't be the case anymore if we have to switch to a different set of deep muscle-memory actions for lanes vs for tracks.

Yes, fixed lanes and razor edits are second nature to me now. What would be good is to be able to double-click the lane number icon to select all the lane items.

[srdmusic]

I Justin,

A while ago a posted about the new r8brain free resample mode crashing while rendering.

I believe I have narrowed down the problem.

This seems to only happen when I am down sampling from 48k to 44.1k with two prints WAV and MP3.

It also only seems to happen is session where I have the plugin Output Thermal installed.

Thermal is know to crash Reaper when reloading a session with Thermal install on a track. Output is aware of this problem but has not come out with a fix. So as a work around I load thermal as a separate process outside Reaper and then reaper won't crash.

I have a feeling that there is some conflict between r8brain down sampling a plugin that is run as a separate process. Or there is some conflict between Thermal in general/ Reaper.

Thanks in advance for checking this out.

PC Specs

Windows 10 1909
32 Core Threadripper AMD
256GB Ram
Reaper 6.46+DEV0120

Also tested

Windows 10 20H2
Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz 3.07 GHz (2 processors)
128GB Ram
Reaper 6.46+DEV0120

[Justin]

Originally Posted by srdmusic

I Justin,

A while ago a posted about the new r8brain free resample mode crashing while rendering.

I believe I have narrowed down the problem.

This seems to only happen when I am down sampling from 48k to 44.1k with two prints WAV and MP3.

It also only seems to happen is session where I have the plugin Output Thermal installed.

Thermal is know to crash Reaper when reloading a session with Thermal install on a track. Output is aware of this problem but has not come out with a fix. So as a work around I load thermal as a separate process outside Reaper and then reaper won't crash.

I have a feeling that there is some conflict between r8brain down sampling a plugin that is run as a separate process. Or there is some conflict between Thermal in general/ Reaper.

Thanks in advance for checking this out.

PC Specs

Windows 10 1909
32 Core Threadripper AMD
256GB Ram
Reaper 6.46+DEV0120

Also tested

Windows 10 20H2
Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz 3.07 GHz (2 processors)
128GB Ram
Reaper 6.46+DEV0120

If you want to post a crash dump, would be happy to take a look to see if there are any hints (email a link to a zip to support at cockos dot com).