v6.73+dev0117 - January 17 2023

[bolgwrad]

v6.73+dev0117 - January 17 2023
* Includes feature branch: mouse modifier small ID action binding fix
* Includes feature branch: fixed lane comping
* Includes feature branch: shortcut import/export improvements and multiple main keyboard sections
* Includes feature branch: improve samplerate change behavior when loading projects
* Includes feature branch: VST3 re-map of parameter IDs due to restartComponent
* Includes feature branch: AU parameter list change notification support
* Includes feature branch: MIDI editor screenset improvements
* Includes feature branch: routing matrix/track wiring input activity indicators
* Includes feature branch: preview item selection for grouped tracks
* Includes feature branch: VST3 per-channel silence reporting compatibility option
* Includes feature branch: better .RfxChain media explorer and clipboard integration
* Includes feature branch: ReaReaRea timestretch mode
* Includes feature branch: GR metering as embedded UI for third-party VSTs
* Includes feature branch: JSFX new features and EEL2 preprocessor
* Includes feature branch: render dialog statistics display improvements
* Includes feature branch: media item fixed lanes
+ Action list: add join/heal as default synonyms
+ Group manager: fix redundant refreshes
+ Media item lanes: add fixed lane button mouse modifiers to insert or delete lane
+ Media item lanes: allow creating a comp area in the comping lane
+ Media item lanes: allow creating a new comp area within the bounds of an existing comp area
+ Media item lanes: comp areas respect region editing
+ Media item lanes: display non-playing MIDI media items similar to muted items in the MIDI editor
+ ReaScript: support "C_LANEPLAYS" in GetSetMediaItemInfo(), read-only
+ macOS: improve compatibility of 'Open source file' mouse modifier dragging [p=2636376]
# Media item lanes: better handling when drag/dropping multiple files onto empty TCP area [p=2636364]
# Media item lanes: don't auto-promote new recording when recording into comping lane
# Media item lanes: don't move a comp area to a nonexistent lane due to track grouping [p=2636363]
# Media item lanes: fix creating comp areas when multiple razor edits exist [p=2636111]
# Media item lanes: fix drawing glitch during playback when razor edits and comp areas exist [p=2636115]
# Media item lanes: support healing adjacent comp areas by clicking the edge with the delete mouse modifier
# Media item lanes: undo improvements
# Media item lanes: when editing with mouse modifier to allow empty space between comp areas, or editing unsynced areas, restrict the edit to the edges of adjoining comp areas [p=2636114]
# Media item lanes: when initiating comping on a grouped track, ensure that other grouped tracks have a comping lane [p=2636225]

[Kenny Gioia]

+ Media item lanes: allow creating a new comp area within the bounds of an existing comp area

+ Media item lanes: allow creating a comp area in the comping lane

This was my idea and I assume it was a reversion of some previous conversations that I missed.

Please come at me for bringing this back and let's discuss why or why it shouldn't have.

Thanks.

[awelex]

Originally Posted by bolgwrad

v6.73+dev0117 - January 17 2023
+ macOS: improve compatibility of 'Open source file' mouse modifier dragging [p=2636376]

Can confirm that this is working swimmingly in macOS now! Thanks for adding.

[ferropop]

[ferropop]

This has been a thing forever, but especially fighting against it with Lanes.

Just want to place the track at the center of the screen!

When near the bottom, you cannot Hand Tool the track to the center of the screen.


Is there any way to "unlock" whatever is going in here? I only bring this up because of how frustrating this is going to be when trying to navigate many lanes.

[deeb]

Many of the zoom tcp and project are tedious to work. They move and behave in not friendly way (not smooth). Please keep things we are focused in place, so that we don’t get confused. This is huge workflow detail that reaper is missing hard. The tinny “random” moviments of the things that should stay exactly in the same place.

Examples (but there are more):
https://forum.cockos.com/showthread.php?p=2545296

[Embass]

[Embass]

[sockmonkey72]

I'd like to come back to this behavior:



In sync mode, the comp area behaves like an eraser, which still feels odd. I think the fact that I am in the middle of a mouse gesture means that the comp area should get in the way of whatever's already there, but not delete it, similar to what happens when you're in non-sync mode and you move items around.

In my imagination, releasing the mouse would finalize the gesture and delete or truncate other items.

[sockmonkey72]

+ Media item lanes: display non-playing MIDI media items similar to muted items in the MIDI editor

I was prepared to go to the barricades about this one, but it's working exactly as I'd expect using my MIDI Editing prefs (and a few others that I tried).

[Embass]

[tonalstates]

Originally Posted by ferropop

Just want to place the track at the center of the screen!

+1

[sockmonkey72]

I think this is also unintuitive behavior:



Again, I am in the middle of a mouse gesture and it feels weird that "irreversible" things are happening as part of that. I would have no problem if the stickiness begins after I drop the comp item and drag it again (in that case, I have the option to press Cmd + left drag to get the non-sticky behavior). But activating stickiness (and deleting stuff) as I am in a continuous drag operation makes me feel like I have no control over what's happening. Particularly because I wouldn't expect that moving one item would push and pull the bounds of others with which I am not working.

If I think about it, I can press Cmd and drag will have no stickiness, and won't delete stuff (since it doesn't move over the edges of other comp lane items). So from that perspective, there's a workaround, but the default behavior is still pretty odd (IMO) and I question the overall approach to initiating these side effects during mouse gestures.

[Odys]

Originally Posted by ferropop

This has been a thing forever, but especially fighting against it with Lanes.

Just want to place the track at the center of the screen!

When near the bottom, you cannot Hand Tool the track to the center of the screen.


Is there any way to "unlock" whatever is going in here? I only bring this up because of how frustrating this is going to be when trying to navigate many lanes.

Always have extra empty tracks at the end of a project.

My starting project template has 40 empty tracks so I can scroll easily and have tracks that I'm working on near top or center.

[Skorobagatko]

+ Media item lanes: display non-playing MIDI media items similar to muted items in the MIDI editor

If you choose one MIDI editor per track, it's because you don't want overlapped items to be display inside a MIDI editor. So why shouldn't it be the same for items on fixed lanes track?

Actually it doesn't work as expected. It displays MIDI items for more then one track, not for just a selected track (MIDI editor per track)
Muted notes should become visible only with one MIDI editor per project setting.

It will be hard to edit MIDI item with a lot of muted notes. It'll become unreadable and will be hard to to select the right note.

Maybe adding a new option might be a good idea?

[schwa]

Originally Posted by ferropop

right-drag screencap

I'm not able to reproduce that. Could you post a small project that's set up however it needs to be to reproduce?

[Vagelis]

There was a big change on this and previous pre regarding re-sync automatically an item on comp lane with a comp area, I preferred the behavior in dev016 much more.

In dev0116, when we were moving an item in comp lane and then back to the area to sync, it could sync while holding the mouse, which was very useful to know if a comp area and an item could sync.

In the last two pres this has changed and we can't see, we have to release the mouse and then the area and item will sync, which is not useful as a sync indicator. Can we have back the behavior of dev0116 please??

[Vagelis]

Originally Posted by Kenny Gioia

This was my idea and I assume it was a reversion of some previous conversations that I missed.

Please come at me for bringing this back and let's discuss why or why it shouldn't have.

Thanks.

Yeah what is the benefit of this behavior? I liked also how clean it was previously, what i was missing a bit, was a left click modifier to create a split marker at mouse cursor, which then we could divide an area and swap fast a comp area from another lane.

Maybe it would be nice to have an option so we could switch behavior?

[Coachz]

Originally Posted by Kenny Gioia

This was my idea and I assume it was a reversion of some previous conversations that I missed.

Please come at me for bringing this back and let's discuss why or why it shouldn't have.

Thanks.

I thought the comp lane was just to display the composite of the other selected segments below it. What purpose does selecting in the top composite lane have?

[xpander]

Originally Posted by Skorobagatko

Actually it doesn't work as expected. It displays MIDI items for more then one track, not for just a selected track (MIDI editor per track)
Muted notes should become visible only with one MIDI editor per project setting.

One MIDI editor per track is per track, not per lane. If you have fixed item lanes and MIDI items on each lane, depending on settings, you'll still see all those items in one editor per track mode and you should too. You can have muted notes (items) on lanes > you should see muted notes in editor. ME Track selector shows and works with lanes as well, so you can do visibility and editability selections from there like always.

[Vagelis]

Originally Posted by sockmonkey72

I'd like to come back to this behavior:



In sync mode, the comp area behaves like an eraser, which still feels odd. I think the fact that I am in the middle of a mouse gesture means that the comp area should get in the way of whatever's already there, but not delete it, similar to what happens when you're in non-sync mode and you move items around.

In my imagination, releasing the mouse would finalize the gesture and delete or truncate other items.

Agreed, I think i prefer deleting the area compared to the new behavior.

But I don't think would be possible not to delete something while in edit mode, because in comp lane we see whatever happens in comp area.

[sockmonkey72]

Originally Posted by xpander

One MIDI editor per track is per track, not per lane. If you have fixed item lanes and MIDI items on each lane, depending on settings, you'll still see all those items in one editor per track mode and you should too. You can have muted notes (items) on lanes > you should see muted notes in editor. ME Track selector shows and works with lanes as well, so you can do visibility and editability selections from there like always.

This is a very literal way of approaching the problem. Yes, we understand that they are lanes on a single track and that the preference says 'track'. But then again -- you wouldn't expect to see all of your takes at once in a multi-take item (although they are also on the same track).

As I mentioned above, with the prefs I posted, I don't experience the problem of seeing all of my lanes piled on top of one another.

Nevertheless, this line of argument kind of ignores the fact that seeing all the lanes piled on top of one another isn't a good default behavior (because it's not what most users will want or expect).

[Vagelis]

May I ask again for a double click context for fixed lane area? It would be useful to edit or sync or in general to divide some actions between left and double click contexts.

Edit: Maybe a double click context could also come in handy for fixed lane buttons?

[xpander]

Originally Posted by sockmonkey72

Nevertheless, this line of argument kind of ignores the fact that seeing all the lanes piled on top of one another isn't a good default behavior (because it's not what most users will want or expect).

This shouldn't be a guesswork about number of users. I for one certainly want to see all items on lanes/tracks/project how I set them to appear in settings. From my POV, you must be "literal" on those issues. However, I might have misunderstood the point here. I have my own ME settings, which work like I expect them to work so far. If the talk here is about what Reaper has as default settings for ME, I have no say about that...

[sockmonkey72]

Originally Posted by Vagelis

Agreed, I think i prefer deleting the area compared to the new behavior.

But I don't think would be possible not to delete something while in edit mode, because in comp lane we see whatever happens in comp area.

I am actually not sure whether you are agreeing with what I posted, since I don't prefer the deletion of the areas left and right of the one I am moving, if I happen to move the mouse over them.

Then again, you are generally very agreeable, so maybe it's a both/and/or/yes/no kind of thing.

[Vagelis]

Originally Posted by sockmonkey72

I am actually not sure whether you are agreeing with what I posted, since I don't prefer the deletion of the areas left and right of the one I am moving, if I happen to move the mouse over them.

Then again, you are generally very agreeable, so maybe it's a both/and/or/yes/no kind of thing.

Ah then sorry if misunderstood, compared to this behavior and the one that's removing the items as shown in your gif, i think i prefer to remove them, because what's the point of not deleting them? While moving the area in edit mode everything in lanes is in sync, in case we edit something in lanes to appear in comp lane, then moving the area in edit mode it shows the content in comp area from lanes.

[ovnis]

You can have muted notes (items) on lanes > you should see muted notes in editor. ME Track selector shows and works with lanes as well, so you can do visibility and editability selections from there like always.

It can be very painfull to do that each time you want to edit your MIDI item inside fixed lanes... Especially guys like me who use often fixed lanes track with lots of lanes and items.

This shouldn't be a guesswork about number of users.

If you read the comments on the previous thread, very few people seems to want that.

Maybe adding a new option could be a good idea? "One MIDI Editor per track and per lane"?

Like that, it would always one MIDI item displayed at once and no more grey notes or darker notes. Even with overlaped MIDI items which are on non fixed lanes track.

Actually, I think it's not a great idea to display notes of items not clicked as muted because, in fact, when a lane is muted, it's not MIDI notes which are muted.

Plus, if we edit a MIDI item which is on a fixed lane mutes, notes of this item will be muted... It can be confusing.

Moreover, how to know which note is really muted or not?

Why not follow the type of poster there is with "One MIDI editor per project" with darker notes for exemple?

There would be more consistency with the rest.

[sockmonkey72]

Originally Posted by Vagelis

Ah then sorry if misunderstood, compared to this behavior and the one that's removing the items as shown in your gif, i think i prefer to remove them, because what's the point of not deleting them? While moving the area in edit mode everything in lanes is in sync, in case we edit something in lanes to appear in comp lane, then moving the area in edit mode it shows the content in comp area from lanes.

I'm fine with deleting stuff after I let go of the mouse, but deleting stuff in a drive-by fashion is kind of brutal.

[ovnis]

Originally Posted by sockmonkey72

I'm fine with deleting stuff after I let go of the mouse, but deleting stuff in a drive-by fashion is kind of brutal.

+1000

[Vagelis]

Originally Posted by sockmonkey72

I'm fine with deleting stuff after I let go of the mouse, but deleting stuff in a drive-by fashion is kind of brutal.

So when there's no other item to auto update the comp lane and when there's an item and pass above it to stop updating in real time?

Why not moving it without edit mode on?

[bolgwrad]

Originally Posted by sockmonkey72

I'd like to come back to this behavior:



In sync mode, the comp area behaves like an eraser, which still feels odd. I think the fact that I am in the middle of a mouse gesture means that the comp area should get in the way of whatever's already there, but not delete it, similar to what happens when you're in non-sync mode and you move items around.

In my imagination, releasing the mouse would finalize the gesture and delete or truncate other items.

+1

[Vagelis]

BTW this is the exact same behavior when we 're not in edit mode and we 're moving an area from lanes, because it overlaps other areas.

I guess the reason this is important to stay like this in edit mode is because any edit in lanes should be reflected in comp lane. If one wants to move just the item in comp lane and unsync from comp area, it could be done without edit mode on.

In short: if we want to edit an item in comp lane, edit mode should be off, if we want to edit an item in a comp area in lanes, edit mode should be on and edit inside the area.

[Embass]

[Embass]

[FeedTheCat]

Originally Posted by Kenny Gioia

This was my idea and I assume it was a reversion of some previous conversations that I missed.

Please come at me for bringing this back and let's discuss why or why it shouldn't have.

Thanks.

I was previously against it. The only way to remove splits in that dev-version was dragging them out, which felt a lot like the classic take system...

I think it's fine now that we have easy ways to remove splits. At least it's consistent. I still would be interested to try if/how "drawing in" comp-areas would function (think of freehand draw envelope). Hard to tell with these things without trying.

Originally Posted by bolgwrad

# Media item lanes: support healing adjacent comp areas by clicking the edge with the delete mouse modifier

Made me wonder, wouldn't that also be great to have for the classic comp-system? E.g. a mouse modifier for alt+double click on media item edge? Would be very convenient to quickly remove unwanted splits after recording.



I briefly tried it, but apparently "heal splits in items" doesn't deal with empty takes at all. Anyhow, sorry for going off-topic.

P.S. Maybe I'm just confused at this point, but why is take 2 empty in the gif? Shouldn't it be take 1?

[vsgrt]

Originally Posted by awelex

Can confirm that this is working swimmingly in macOS now! Thanks for adding.

Yes, this is great great stuff.
I can drag from timeline directly into TAL Sampler in macOS now. Woohoo

[_Stevie_]

Hey devs,

there is an unexpected behavior introduced beginning with v6.73+dev0113 concerning splitting and trimming MIDI items (custom scripts using the API).

I suspect these guys here to be the culprit:
from 113

+ MIDI split: when trimming items, chase CC/pitch/etc

and from 114

# MIDI split: fix incorrect note added after split

I'm doing the following in the GIF:

1. Custom trim head script (revealing the area before, to show that it's gone)
2. Then splitting (also custom split script) at few bars later
= notes and a CC curve are appearing in the split item, although it shouldn't contain anything


Here's what happens with 113 and upwards:




And here's the expected behavior from 112:




If you need the custom scripts, let me now!

[Kenny Gioia]

Originally Posted by Vagelis

Yeah what is the benefit of this behavior?

In the previous build(s), you could use the mouse modifier to create a new comp area. BUT only if that area was a non-chosen area. So if you were working thru your song and picked lane 1 as your choice, you couldn't drag on lane 1 to create the next area. It would only extend the previous one. Which you could already do just by grabbing and trimming the end of that area. So you'd have to draw it on lane 2, then switch it back to lane 1 to start hearing that lane. I think that's inconsistent. Using that mouse modifier should always perform the function of creating a new area. IMHO.

Originally Posted by Coachz

I thought the comp lane was just to display the composite of the other selected segments below it. What purpose does selecting in the top composite lane have?

At this point it might seem pointless but later on people are going to want to comp while only viewing one lane. So having the ability to create the area in the final comp lane would make that possible. You can create areas and use a keyboard shortcut to switch what lane you're hearing without having to see multiple lanes.

Originally Posted by FeedTheCat

I think it's fine now that we have easy ways to remove splits. At least it's consistent.

And that was my issue. The context mm is for creating new comp areas. It should do that whenever used. If you want to extend them, just use the trim tool. It's right threre.

[Klangfarben]

Originally Posted by sockmonkey72

I'm fine with deleting stuff after I let go of the mouse, but deleting stuff in a drive-by fashion is kind of brutal.

+1111

[Justin]

Originally Posted by _Stevie_

Hey devs,

there is an unexpected behavior introduced beginning with v6.73+dev0113 concerning splitting and trimming MIDI items (custom scripts using the API).

I suspect these guys here to be the culprit:
from 113

+ MIDI split: when trimming items, chase CC/pitch/etc

and from 114

# MIDI split: fix incorrect note added after split

I'm doing the following in the GIF:

1. Custom trim head script (revealing the area before, to show that it's gone)
2. Then splitting (also custom split script) at few bars later
= notes and a CC curve are appearing in the split item, although it shouldn't contain anything


Here's what happens with 113 and upwards:




And here's the expected behavior from 112:




If you need the custom scripts, let me now!

Thanks, fixing!