v7.0pre25 - September 18 2023

[sockmonkey72]

v7.0pre25 - September 18 2023

• * Includes feature branch: support up to 32 main toolbars, 16 MIDI toolbars
• * Includes feature branch: MIDI CC vertical zoom/scroll
• * Includes feature branch: optionally hide collapsed tracks within a folder
• * Includes feature branch: export mouse modifiers as a script
• * Includes feature branch: target individual fixed lanes when pasting media items
• * Includes feature branch: support rendering raw PCM data
• * Includes feature branch: Development_Theme theme
• * Includes feature branch: JSFX plug-in defined compile-time configuration parameters
• * Includes feature branch: video YUV gamut selection
• * Includes feature branch: visual track spacers
• * Includes feature branch: 128 channels per track
• * Includes feature branch: updated Windows manifest for newer OS features
• * Includes feature branch: always running non-bypassed FX when the UI is visible
• * Includes feature branch: crossfade new recording with existing media items if configured
• * Includes feature branch: video from background projects
• * Includes feature branch: FX containers
• * Includes feature branch: improvements to aligning takes after recording
• * Includes feature branch: arrange view override mouse modifier sections
• * Includes feature branch: toolbar armed/special animations
• * Includes feature branch: pooled and unpooled ARA edits
• * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections
• * Includes feature branch: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: media item fixed lanes
• + CLAP: round MIDI velocity values returned from plugins [t=282782]
• + MIDI editor: intepret pitchwheel range as +/- semitones rather than low to high
• + MIDI editor: support snapping pitch lane to semitones
• + Media item lanes: do not change comp area source lane when clicking empty track space by default (preference in mouse modifiers settings)
• + ReaScript: add MIDIEditorFlagsForTrack(), to get/set pitchwheel range and snap settings
• + Toolbars: support up to 32 main toolbars, 16 MIDI toolbars
• + Tracks: add actions, menu items to move tracks to new or existing folder track
• # MIDI editor: fix overeager restriction when option disabled to allow CC curve shapes in certain lanes [p=2712200]
• # MIDI editor: separate preference for allowing CC shape in sustain lane
• # Media item lane: fix comping MIDI items

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

[deeb]

[*]+ ReaScript: add MIDIEditorFlagsForTrack(), to get/set pitchwheel range and snap settings


This seems like it would be extremely useful on envelope lanes too. Will try in CC to see what it can give us!

Thanks!

[smandrap]

Originally Posted by sockmonkey72

+ MIDI editor: intepret pitchwheel range as +/- semitones rather than low to high
+ MIDI editor: support snapping pitch lane to semitones

[Meo-Ada Mespotine]

Thanks for the toolbar additions.

[Svein]

I got a crash when clicking on an item while in comping mode. Click (not drag) on the bottom item in this session. Doesn't matter if it's Midi or Audio. I'm om Ventura Mac. Crash to desktop.

[_Stevie_]

Devs you are on fire, thanks!!!

[Sexan]

Btw has LV2 enumerate api landed yet?
Thank you for folder actions!

[schwa]

Originally Posted by Svein

I got a crash when clicking on an item while in comping mode. Click (not drag) on the bottom item in this session. Doesn't matter if it's Midi or Audio. I'm om Ventura Mac. Crash to desktop.

Hmm, can't reproduce. Can you share a screenshot of your fixed lane comp area left-click mouse modifier settings?

[Svein]

Originally Posted by schwa

Hmm, can't reproduce. Can you share a screenshot of your fixed lane comp area left-click mouse modifier settings?

It's not my main machine but here it is


VM Region Info: 0 is not in any region. Bytes before following region: 4309262336
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 100da2000-101776000 [ 9.8M] r-x/r-x SM=COW .../MacOS/REAPER

Thread 0 Crashed:: reaper Dispatch queue: com.apple.main-thread
0 REAPER 0x100fd5730 MediaTrack::Arrange_OnMouseLeftUp(long long, int, int, int) + 7008
1 REAPER 0x100f35f52 TrackList_OnMouseMessage(HWND__*, int, int, int, int) + 1186
2 REAPER 0x1013610d4 TrackListWindowProc(HWND__*, unsigned int, unsigned long, long) + 756
3 REAPER 0x1015b36cd CoolSBWndProc(HWND__*, unsigned int, unsigned long, long) + 2685
4 reaper_sws-x86_64.dylib 0x1098e701f ZoomWndProc(HWND__*, unsigned int, unsigned long, long) + 735
5 REAPER 0x1012e978c SWELL_SendMouseMessage(REAPERSwell_hwnd*, int, NSEvent*) + 668
6 AppKit 0x7ff80c2a33e6 _routeMouseUpEvent + 138
7 AppKit 0x7ff80ba437eb -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 424
8 AppKit 0x7ff80ba43427 -[NSWindow(NSEventRouting) sendEvent:] + 345
9 AppKit 0x7ff80ba41e01 -[NSApplication(NSEvent) sendEvent:] + 345
10 REAPER 0x101118afb -[REAPERapp sendEvent:] + 3515
11 AppKit 0x7ff80bcfc74e -[NSApplication _handleEvent:] + 65
12 AppKit 0x7ff80b8d17ad -[NSApplication run] + 623
13 AppKit 0x7ff80b8a59a1 NSApplicationMain + 817
14 dyld 0x7ff80841041f start + 1903

[Edgemeal]

+ Media item lanes: do not change comp area source lane when clicking empty track space by default (preference in mouse modifiers settings)

Thank You!

[Mercado_Negro]

+ Tracks: add actions, menu items to move tracks to new or existing folder track

This is great! Thank you!

It would be nice if the available folders also appeared in the sub-menu "Move tracks to folder". At the moment it is only available in the main track menu and as an action.

Also, I think tracks should move to folders as last tracks.

And for the icing on the cake, when creating a new folder for selected tracks REAPER should immediately prompt for a name for this new folder.

[schwa]

The option at the bottom of that page, "do not change comp source lane...", is that enabled or disabled? If enabled, does anything change if you disable it?

[gofer]

Thanks for keeping up MIDI improvements.

This is not a bug, but Pitch snap doesn't work quite as I hoped it would. In this Licecap I have selected a bunch of events where a note vibrato ended up to be sharp. I try to correct by grabbing an event that I want to be on pitch.



What I was hoping for was that the event I click on would snap and all other selected events move the same amount, so the vibrato stays alive, just a tad lower altogether.

I do see what the thinking behind the current behaviour is. And maybe it is exactly what other users asking for snap expected and probably useful for some other task. It's just obviously not useful for editing recorded MPE MIDI. I should probably just keep it off and enjoy dragging the events to the ballpark, which works plenty good.

Guidelines at integer pitches would be of tremendous help both spotting and fixing this kind of stuff.

[Svein]

Originally Posted by schwa

The option at the bottom of that page, "do not change comp source lane...", is that enabled or disabled? If enabled, does anything change if you disable it?

Crash with both enable and disabled

[Edgemeal]

Originally Posted by schwa

The option at the bottom of that page, "do not change comp source lane...", is that enabled or disabled? If enabled, does anything change if you disable it?

Enabled by default, when disabled it returns to previous behavior, seems to work fine.
Win10_x64

[schwa]

Originally Posted by Edgemeal

Enabled by default, when disabled it returns to previous behavior, seems to work fine.
Win10_x64

Sorry, to be clear, you are seeing the same crash with this option enabled?

[ferropop]

Originally Posted by gofer

Thanks for keeping up MIDI improvements.




What I was hoping for was that the event I click on would snap and all other selected events move the same amount, so the vibrato stays alive, just a tad lower altogether.

This is why people opt to not even use CCs in the MIDI Editor. Look how easy this is if using ReaControlMIDI and doing this in arrange with Razor Edits:



Just a datapoint devs, there's much inconsistency between Arrange and MIDI Editor CC workflows, causing us to jump between these disconnected panes to do operations that should exist in the other -- both ways.

Razor Edits in MIDI Editor would put this important tool where it belongs equally-if-not-more than in Arrange. <3

[Svein]

Originally Posted by schwa

Sorry, to be clear, you are seeing the same crash with this option enabled?

Yes

[Edgemeal]

Originally Posted by schwa

Sorry, to be clear, you are seeing the same crash with this option enabled?

No crashing here, just doing simple on/off testing, seems fine.
EDIT I also did plenty of item clicking, etc, still no crashes, must be a MAC thing.

Win10-_x64

[MonkeyBars]

Originally Posted by gofer

What I was hoping for was that the event I click on would snap and all other selected events move the same amount

+1 imo snap should only apply to the node being dragged. The rest should maintain their relative value

Originally Posted by ferropop

Just a datapoint devs, there's much inconsistency between Arrange and MIDI Editor CC workflows, causing us to jump between these disconnected panes to do operations that should exist in the other -- both ways.

Razor Edits in MIDI Editor would put this important tool where it belongs equally-if-not-more than in Arrange. <3

+1 Unfortunate that the envelope and CC handling appears not to be modular and easy to apply between ME and Arrange. Would be great to have consistency

[gofer]

Originally Posted by ferropop

This is why people opt to not even use CCs in the MIDI Editor. Look how easy this is if using ReaControlMIDI and doing this in arrange with Razor Edits:



Just a datapoint devs, there's much inconsistency between Arrange and MIDI Editor CC workflows, causing us to jump between these disconnected panes to do operations that should exist in the other -- both ways.

Razor Edits in MIDI Editor would put this important tool where it belongs equally-if-not-more than in Arrange. <3

Of course I want to have that at some point For now I am just wearing rose tinted glasses because I can finally edit the pitch data at all. Compressing/tilting/LFO and all the other magic razor edit brings clearly is where it all should go next.
Sadly Juliansadders nifty multitool doesn't play nicely with the MPE pitch range and the new zooming feature.

[deeb]

Originally Posted by MonkeyBars

+1 imo snap should only apply to the node being dragged. The rest should maintain their relative value



+1 Unfortunate that the envelope and CC handling appears not to be modular and easy to apply between ME and Arrange. Would be great to have consistency

There is good things in both that are not present in the other. ME just got a new one snap values.
Regarding razor edit I personally think being not available to be used with markers is the biggest pita at this moment. RE in ME is obviously nice to have tho but is not such a deal breaker. As someone said: cubase just announced RE (area selection) for ME/cc in their new version, and they have re in project for around 15 years.

[ferropop]

Originally Posted by gofer

Of course I want to have that at some point For now I am just wearing rose tinted glasses because I can finally edit the pitch data at all. Compressing/tilting/LFO and all the other magic razor edit brings clearly is where it all should go next.
Sadly Juliansadders nifty multitool doesn't play nicely with the MPE pitch range and the new zooming feature.

Yup I went directly to MultiTool, it's just not stable or dependable enough as the main tool for this.

[gofer]

Do you have thoughts about the snap behaviour?
I don't see where multitool is unstable or undependable, I use it all the time for 127 range CC. It just doesn't have the resolution necessary for MPE pitchbend and isn't ready for zoom/scroll.

[Phazma]

Originally Posted by sockmonkey72

[*]+ MIDI editor: intepret pitchwheel range as +/- semitones rather than low to high[*]+ MIDI editor: support snapping pitch lane to semitones

This is great, thanks devs! Any chance we can also get a snapping feature for track envelopes with a user-settable range for each envelope?

That would not just be useful for doing pitchbends with ReaControlMIDI but any automated FX parameter can then be set to a useful range to snap to. For example a gain plugin with +/- 24dB range can be subdivided into 24 snapping steps to be adjusted in precise 1dB steps (or in 0.5dB steps if the range is set to 48).

Also it would be easier to match one point's value to an earlier/later one without having to copy/paste values between points. And resetting it to the center value would also be easily possible by just dragging.

[smandrap]

Originally Posted by sockmonkey72

+ Toolbars: support up to 32 main toolbars, 16 MIDI toolbars

Speaking of "more of this", could you please also take care of this FR?

[deeb]

Originally Posted by Phazma

This is great, thanks devs! Any chance we can also get a snapping feature for track envelopes with a user-settable range for each envelope?

This will be wonderful when it comes. Range should be more complex and we should be able to do things like: 1-27 , 40, 80, 100-120, 127. I guess ccs would also benefit with this. In the right timing !

[creal]

Hello,

https://forum.cockos.com/showthread.php?t=279033

https://forum.cockos.com/showthread.php?t=278403

Thank you.

NB: sorry but I will bump this thread until the bugs are solved. I already asked several times but nothing has changed.

[Loulou92]

More toolbars. My saviors...
Thank you so so so sooooooo much ! You are the best !!!!
Cockos for life.

[IrishRover79]

hi, there seems to be an issue with lanes and grouping when the following conditions are met:

-tracks are grouping for media editing/razor editing
-one track has no fixed lanes
-all other tracks do have fixed lanes
-you want to select the item on the track with no fixed lanes, e.g for dynamic split purposes, and have the operation apply to the grouped items

In this situation, the grouping always seems to be on lane 1 - even when only lane 2 is visible.

Is this perhaps because the grouping operates at the level of lanes and the track with no fixed lanes is viewed as being on 'lane 1'?

I think it would make more sense if the grouping respected the visible lanes.

[daxliniere]

[*]+ Tracks: add actions, menu items to move tracks to new or existing folder track

I've had a custom action for this from day 1 of using REAPER, but glad to see it make the mainstream. I use this 20 times a day!

I believe I'm seeing a bug, though, as after I've done it once, then named the folder track, that named folder track doesn't show up in the list of folders when I look in the menu again. Like I said, I have my own custom action for this, but seems like a bug.

BTW, It would be nice to get a complementary action to 'dissolve' folders, preserving children. ("un-folder")

[Justin]

Originally Posted by Svein

It's not my main machine but here it is


VM Region Info: 0 is not in any region. Bytes before following region: 4309262336
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 100da2000-101776000 [ 9.8M] r-x/r-x SM=COW .../MacOS/REAPER

Thread 0 Crashed:: reaper Dispatch queue: com.apple.main-thread
0 REAPER 0x100fd5730 MediaTrack::Arrange_OnMouseLeftUp(long long, int, int, int) + 7008
1 REAPER 0x100f35f52 TrackList_OnMouseMessage(HWND__*, int, int, int, int) + 1186
2 REAPER 0x1013610d4 TrackListWindowProc(HWND__*, unsigned int, unsigned long, long) + 756
3 REAPER 0x1015b36cd CoolSBWndProc(HWND__*, unsigned int, unsigned long, long) + 2685
4 reaper_sws-x86_64.dylib 0x1098e701f ZoomWndProc(HWND__*, unsigned int, unsigned long, long) + 735
5 REAPER 0x1012e978c SWELL_SendMouseMessage(REAPERSwell_hwnd*, int, NSEvent*) + 668
6 AppKit 0x7ff80c2a33e6 _routeMouseUpEvent + 138
7 AppKit 0x7ff80ba437eb -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 424
8 AppKit 0x7ff80ba43427 -[NSWindow(NSEventRouting) sendEvent:] + 345
9 AppKit 0x7ff80ba41e01 -[NSApplication(NSEvent) sendEvent:] + 345
10 REAPER 0x101118afb -[REAPERapp sendEvent:] + 3515
11 AppKit 0x7ff80bcfc74e -[NSApplication _handleEvent:] + 65
12 AppKit 0x7ff80b8d17ad -[NSApplication run] + 623
13 AppKit 0x7ff80b8a59a1 NSApplicationMain + 817
14 dyld 0x7ff80841041f start + 1903

(edit: thanks -- this crash log should be enough!)

[ijijn]

Originally Posted by sockmonkey72

v7.0pre25 - September 18 2023

+ CLAP: round MIDI velocity values returned from plugins [t=282782]

Fantastic, that got it. Thank you!

[foxAsteria]

Originally Posted by sockmonkey72

up to 32 main toolbars, 16 MIDI toolbars

Thanks so much!

[dangguidan]

I guess picky netizens will demand that the grid change with the range of bending .

[Pink Wool]

* Includes feature branch: updated Windows manifest for newer OS features


Sorry, what's this? Can anyone shed some light?

[eungang]

[*]+ Toolbars: support up to 32 main toolbars, 16 MIDI toolbars

Great addition, but unable to get any of the new toolbars to run yet. Bug most likely, or ignorant user error on my part.

[Tod]

+ Toolbars: support up to 32 main toolbars, 16 MIDI toolbars

This is great, I've waited a long time for this.

Originally Posted by eungang

Great addition, but unable to get any of the new toolbars to run yet. Bug most likely, or ignorant user error on my part.

Maybe some problems, but they'll get fixed.

[Suzuki]

Originally Posted by sockmonkey72

[*] * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections

While you're at it, could you also add multiple MIDI keyboard sections? It would be very handy to switch action sets depending on what you do, for example inserting notes mode, editing cc mode, and editing notation etc.

[elcalen]

I previously reported about weirdness when stopping a TCP drag on top of the panel being dragged; previously unfoldered track's folder depth would change so it's now in the folder above. A similar thing seems to happen when it's the last track in a folder; the folder depth changes even though it clearly shouldn't.