v6.0+dev1204 - December 4 2019

[Otto Tune]

v6.0+dev1204 - December 4 2019

• + ARA: inform plugins that audio source content has changed after external edits [t=227813]
• + Automation items: add sine shape, tilt parameter
• + MIDI editor: add basic CC LFO dialog
• + MIDI editor: fix macOS Metal Retina rendering glitch when nav lane is visible and resized
• + MIDI editor: refresh open editors after changing default MIDI note colormap
• + MIDI editor: remove support for per-media-item note colormaps
• + MIDI editor: support HiDPI/Retina images for track list
• + MIDI editor: support HiDPI/Retina transport button images
• + MIDI inline editor: support HiDPI/Retina theme images
• + MIDI: optionally display program names and text events in arrange view
• + Media explorer: support HiDPI/Retina transport button images
• + Mouse modifiers: add modifiers to adjust loop section start/end
• + ReaScript IDE: add checkbox to disable state watchlist
• + ReaScript IDE: do not run watch window continuously after script has stopped running
• + ReaScript IDE: reduce watch update frequency
• + ReaScript: remove support for deprecated MIDI support file types
• + ReaSurround: improve multimonitor HiDPI issues on Windows
• + ReaVerb: enable ZL/LL by default for better low-latency performance
• + Stretch markers: preserve beat-based positions of stretch markers when item timebase is beats (position, length, rate)
• + Takes: implode items into takes only if at least half of the item overlaps [p=2207040]
• + VST3: add support for plugins that output MIDI CC data, via LegacyMIDICCOutEvent
• # MIDI editor: add sine shape to LFO dialog
• # MIDI editor: better interpolation of LFO start/end
• # MIDI editor: fix unintentionally disabled menu items (effectively reverts c548c617)
• # MIDI editor: increase width of CC LFO dialog on HiDPI displays [t=168589]

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

[pepe44]

+ ReaVerb: enable ZL/LL by default for better low-latency performance

Great Thanks

[EvilDragon]

CC LFO is BACK! And with presets and more features! Very nice!


By the way I think it may need to have a "Commit" option just like Quantize dialog, because currently if you quickly flip between "Time selection" and "Entire item" then back to "Time selection", it destroys your existing CC data completely. Not nice.

Also it should work across all editable items in "Entire item" mode. Maybe rename that mode to "All editable items", then?


Regarding program names in arrange on MIDI items, the font is truncated at the bottom...?

[Yanick]

will the LFO have a clip?

[Yanick]

Cool LFO tool! I would also like a tool for tilt the selected Velocity / CC
And some other parameters that are in the LFO tool

[ashcat_lt]

Any chance we could get the option to add, subtract, multiply the LFO with existing CC data? Would be cool if we had that same functionality for AIs too.

[Alez156]

Originally Posted by EvilDragon

CC LFO is BACK! And with presets and more features! Very nice!


By the way I think it may need to have a "Commit" option just like Quantize dialog, because currently if you quickly flip between "Time selection" and "Entire item" then back to "Time selection", it destroys your existing CC data completely. Not nice.

Also it should work across all editable items in "Entire item" mode. Maybe rename that mode to "All editable items", then?


Regarding program names in arrange on MIDI items, the font is truncated at the bottom...?

I am with you here. I was trying to find a commit option. And as soon as I switched to entire item the whole thing gets destroyed. Not fun

[_Stevie_]

MIDI: optionally display program names and text events in arrange view

This is insane, guys! Thank you so much! That makes Reaper the only DAW with that feature!

[mawi]

Moving item content in a looped item without moving loop start and end would also be great.

[Tod]

I thought my eyes were changing because it was becoming difficult for me to read the text in the midi CC lanes.

But going back to an earlier version it became apparent that it wasn't my eyes it was the change in the font, as you can see in this picture. The top picture is the way it appears in
Reaper, and as you can see in the bottom exaggerated picture, the font is different and harder to see.

[Icchan]

There's so many gazillion modifiers and ways to grab or click certain area of item these days, that it would be the most amazing feature if by hovering on top of an item area and pressing down a some of attached key modifiers a tooltip would jump above the cursor that tells you exactly what action you're going to perform if you click or drag now...
A huge help for usability. ;D

[schwa]

Originally Posted by Alez156

I am with you here. I was trying to find a commit option. And as soon as I switched to entire item the whole thing gets destroyed. Not fun

I'm not quite following this. Can you give an example of when switching the entire range/time selection dropdown immediately overwrites CC data?

[Alez156]

Originally Posted by schwa

I'm not quite following this. Can you give an example of when switching the entire range/time selection dropdown immediately overwrites CC data?

As soon as I open the LFO window, it just overwrites all my previous CC data. And even switching from entire item to time selection, the damage is done.
It is destructive right away which makes it difficult to use and you have to undo every time

[ovnis]

And even switching from entire item to time selection

CC envelope item could fix this issue.

[Zeno]

Originally Posted by Alez156

As soon as I open the LFO window, it just overwrites all my previous CC data. And even switching from entire item to time selection, the damage is done.
It is destructive right away which makes it difficult to use and you have to undo every time

WOW! CC LFO? Is that an external script? Where do I get it?

[dupont]

Originally Posted by Alez156

As soon as I open the LFO window, it just overwrites all my previous CC data. And even switching from entire item to time selection, the damage is done.
It is destructive right away which makes it difficult to use and you have to undo every time

Yes, a commit option should be added.

[Triode]

[/QUOTE]

Sorry off-topic

What theme is that?! Is it Logic Next? - with that input/record double button? I'd like to know

Excuse me, back to main discusssion

[Peevy]

Another great update, it just keeps coming!


I take it this is just placeholder graphics:







until WT finishes the graphics for the midi/media explorer.

[vitalker]

Originally Posted by Otto Tune

+ Mouse modifiers: add modifiers to adjust loop section start/end

Can't find it.

Originally Posted by Otto Tune

+ MIDI editor: remove support for per-media-item note colormaps

Still seeing it.

[EvilDragon]

Originally Posted by vitalker

Can't find it.

Still seeing it.

Media item edge, left drag context.

If you have custom menus, note colormap actions won't be removed from them. But the actions themselves are not there anymore in the a ction list.

[vitalker]

Originally Posted by EvilDragon

Media item edge, left drag context.

If you have custom menus, note colormap actions won't be removed from them. But the actions themselves are not there anymore in the a ction list.

Oh cool, thanks! I thought it was about project loop edges.

No custom menus for sure, this version is clean.

[D Rocks]

you guys never sleep or drink too much coffee..
Thanks Justin/Schwa

[EvilDragon]

What I really wanna see is 6.1, really. schwa said it's gonna be lit. I wanna see just how much

[Vagelis]

Originally Posted by Otto Tune

[b]v6.0+dev1204 - December 4 2019
Mouse modifiers: add modifiers to adjust loop section start/end

And so it is!! Thanks a million you guys are the best!!! This feature will enhance the editing in reaper a lot, it’s like the painting feature in FL but way better!
While you ‘re at it would it be possible for another modifier that would allow us to change only the looped item positions inside the item and not the item length? This could be useful if we want to loop in a specific area without changing the item length if there’s another item next to it.
Thanks again and for the automation item updates!

[schwa]

I actually really like this little feature. In this example, the recorded hit is less than one beat, but using the modifier you can loop it on the beat, and then also change the looped length without stretching.



Unfortunately the feature will be a bit hidden, because the default mouse modifiers for media item edge are aready allocated for all standard key combinations.

[Joe90]

LFO editor in midi CC lanes is very cool! Cheers.

Regarding these HiDPI improvements - I just wanted to re-raise a couple of minor issues I'm seeing here (running Win10, one 4k screen and one 1080p, OS scaling at 150% for the 4k screen, 100% for the 1080, using multimonitor aware mode in Reaper) -

The mouse cursor is not being scaled, it's way too small. This is frustrating when trying to grab item edge points or anything else fiddly.



Tooltips are oversized on the second (1080p) monitor, seems like they are being scaled up even on the 1080 screen.



Melodyne UI is not scaling up when used within Reaper via ARA, it's not a melodyne issue as it scales in other DAW's.

Cheers!

[Breeder]

Originally Posted by Otto Tune

[*]+ MIDI editor: add basic CC LFO dialog

These actions, which usually work on all MIDI editor windows I've tried them, don't work with LFO dialog for some reason:

SWS/BR: Move active floating window to mouse cursor (horizontal: middle, vertical: top)

[Vagelis]

Originally Posted by Otto Tune

[b]v6.0+dev1204 - December 4 2019
Mouse modifiers: add modifiers to adjust loop section start/end

Oooo my god!!! Is this what I think it is??! I’ve made a request some days ago, going to try now, then i’m The happiest guy on earth!!

[Edison]

[QUOTE=Otto Tune;2210707]v6.0+dev1204 - December 4 2019

[*]+ Mouse modifiers: add modifiers to adjust loop section start/end

Hi, Otto!

The blue window texts are only translated in the 'Actions' in the Mouse Modifiers not yet enabled for translation. See pic.

Thanks

[juliansader]

Originally Posted by Otto Tune

[*]+ Takes: implode items into takes only if at least half of the item overlaps [p=2207040]

It is good that imploding is receiving some updates. I think that many of the complaints regarding takes and splitting can be addressed by a smarter imploding action: Users can record in free item positioning without splitting, edit the items as desired, and then implode them into a multi-take comp. Or they can receive new recordings by email, and simply implode the new files into existing comps.

Imploding still does not work well, unfortunately, particularly if empty items are involved, or if the items are not precisely aligned.

Imploding and exploding should mirror each other. At present, empty takes explode into gaps that cannot be imploded again. This image shows items before exploding, after exploding, and after re-imploding in v6.0:




When imploding a full-length item onto an item with splits, the same splits should be applied to the full-length item. At present, some weird stuff happens:
Before:


How the imploded items should look:


How it looks in v6.0:



When items aren't perfectly aligned, they can either be padded with silence or with empty takes before imploding, but their relative alignment must always be maintained. This image shows items before imploding, after imploding in v6.0, and how the items should be imploded (in case empty takes are used):

[musicbynumbers]

+ Mouse modifiers: add modifiers to adjust loop section start/end

This is great thanks!

Probably been asked for but..

Could we have a mouse modifier to "Slip" the contents of the looped area around too?

Thanks!

[RCJacH]

I just noticed today that the mouse modifier for changing CC curves does not work on unselected CC events in 14-bit CC lanes. I think when no cc event is selected, mouse modifier for changing cc curve adjust the latest point rather than the point/curve under mouse.

[juliansader]

Originally Posted by Otto Tune

[*]+ Stretch markers: preserve beat-based positions of stretch markers when item timebase is beats (position, length, rate)

Should this actually refer to timebase = auto-stretch?

Copy/pasting of items with timebase = auto-stretch to positions with different tempos now seems to work well, even if the items contain user-inserted stretch markers -- but only if the tempos are all square.

When tempo changes are linear, timebase=auto-stretch doesn't apply slopes to the user-inserted stretch markers, so items have a hodgepodge of sloped and flat stretch segments.

The slope lines of auto-generated stretch markers are sometimes still not easily visible unless the arrange view is zoomed in very close (using new default theme).

[schwa]

Originally Posted by juliansader

Should this actually refer to timebase = auto-stretch?

This is a general fix for either timebase. Previously the beat-based positions of stretch markers were not preserved when copy/pasting.

Originally Posted by juliansader

When tempo changes are linear, timebase=auto-stretch doesn't apply slopes to the user-inserted stretch markers, so items have a hodgepodge of sloped and flat stretch segments.

It's not obvious what the right behavior is in that case. If the user has applied a stretch marker slope manually, should the auto-stretch timebase override it?

[juliansader]

Originally Posted by schwa

It's not obvious what the right behavior is in that case. If the user has applied a stretch marker slope manually, should the auto-stretch timebase override it?

If a user wishes to preserve slopes, the old timebase = Beats (P,L&R) may be more appropriate.

If the new auto-stretch timebase doesn't apply slopes, audio will not properly align with MIDI and the grid.

As an example:

In this image the audio to the left is manually stretched, as in many projects before auto-stretch. If auto-stretch is applied, and the items are copied to the right (below the sloped tempo changes), the auto and MIDI become misaligned, because only flat SMs are applied. The bottom item is how I would recommend the timebase to work, with sloped SMs.

(This image also shows that the slopes of some of the auto-SMs are not visible.)




P.S. It would also be useful if, when switching from timebase=auto-stretch to another timebase, the auto-generated SMs are preserved, so that timing doesn't change. Perhaps REAPER can pop up a dialog box to ask whether the auto-SM should be preserved, similar to how REAPER asks whether to maintain timing when switching *to* auto-stretch

[juliansader]

Plain copy/paste, without any manual SMs, still appears to be buggy:

In this image, I glued the audio to remove manual SMs (top left) then applied auto-stretch with "maintain timing" (bottom left), and then either Ctrl-dragged or copy/pasted to the right:


(I used dev1206.)

[operator]

Originally Posted by Otto Tune

v6.0+dev1204 - December 4 2019
[*]+ Mouse modifiers: add modifiers to adjust loop section start/end
[/url]

MAybe someone could help me... I`m using the newest version of Reaper... but i can`t find the modifier for loop start/end... did this option/function changed?

it doesn`t show up in my modifier context menu... (see attachment)

[Vagelis]

Originally Posted by operator

MAybe someone could help me... I`m using the newest version of Reaper... but i can`t find the modifier for loop start/end... did this option/function changed?

it doesn`t show up in my modifier context menu... (see attachment)

It's not yet included in the latest prerelease-release of Reaper. But i hope it will come back again soon

[operator]

Originally Posted by Vagelis

It's not yet included in the latest prerelease-release of Reaper. But i hope it will come back again soon

THANKS A LOT for the quick answer. I thought I was going insane when i couldn`t find it.

Is the following feature also taken out again? :

v6.01+dev1209: + Mouse modifiers: support editing loop source length by dragging loop divider notch when media item edge mouse modifier is set to edit loop source


I hope it will make it`s comeback too.... these are a must in my opinion. :-)

[Vagelis]

Originally Posted by operator

THANKS A LOT for the quick answer. I thought I was going insane when i couldn`t find it.

Is the following feature also taken out again? :

v6.01+dev1209: + Mouse modifiers: support editing loop source length by dragging loop divider notch when media item edge mouse modifier is set to edit loop source


I hope it will make it`s comeback too.... these are a must in my opinion. :-)

Yeap also this one, the devs have been working on other features as well, so i believe after they finish them at some point, we will see them again.