v7.05+dev1119 - November 19 2023

[sockmonkey72]

v7.05+dev1119 - November 19 2023

• * Includes feature branch: media items on higher numbered lanes optionally mask playback of lower lanes
• * Includes branch: improved take FX position reporting with PDC
• * Includes feature branch: large number of video items CPU use optimizations
• * Includes feature branch: record armed tracks obeying 'do not run muted tracks' preference
• * Includes feature branch: increase fixed lane limit to 256 lanes
• * Includes feature branch: improve undo behavior when comping
• * Includes feature branch: support non-SMPTE 7.1 channel order
• * Includes feature branch: improve behavior when deleting or reordering tracks while recording
• * Includes feature branch: support copying comp area edits back to source lanes
• * Includes feature branch: optionally limit media item edge edits to start/end of source media
• * Includes feature branch: FX envelope options for AI combining
• * Includes feature branch: ReaSurround support for 128 inputs
• + FX: fix automation quirks with non-1.0 project playrate on plug-ins following PDC (v7 regression)
• + Lane: fix undo after changing comping lane [p=2734645]
• + Lanes: action to reset lane names will reset lanes named like 'C1' if they have no comp areas
• + Lanes: fix possible mouse click miss when track is greatly zoomed in [p=2735023]
• + MIDI editor: fix step sequencer for VKB input and MIDI inputs with high IDs [rr=17y0f7z]
• + ReaScript: fix backwards compatibility in group membership flags [t=277048]
• + Regions: recalculate region display overlap after undo [t=276254]
• + Take FX: fix issues with glue/render actions, batch converter when PDC and project playrate are both used
• + Take FX: fix sample-accurate automation accuracy when using take start offset and project playrate
• + Tracks: add actions to crop to playing media items, or copy playing media items to new track
• + Video: allow dshow_depr to be enabled explicitly for extensions other than wmv/wma/avi/asf [t=269473]
• # Lanes: improve behavior of lane masking and automatically creating comp areas when media items in different lanes start or end at the same time [p=2734639]
• # Lanes: update vertical scrollbar after action to show/play only one lane [p=2734658]
• # Media items: fix display of media item buttons when greatly zoomed in

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

[GeneralMidi]

Working even on a Sunday. Your commitment to the software is amazing. What a development team. Mind blown.

[Vagelis]

Originally Posted by sockmonkey72

v7.05+dev1119 - November 19 2023
[*]+ Tracks: add actions to crop to playing media items, or copy playing media items to new track

These will come in handy, thanks so much!
However I've noticed that it crop/copy all items on track, resulting in losing the rest sources which aren't cropped on a different place in the timeline.
Maybe it could be possible to apply these actions for selected items as well?

Like with selected items crop only those items, if only track is selected crop all items on track.

EDIT: If possible, I think split/select audible areas would be useful and easier to apply other actions too.

[Edgemeal]

+ MIDI editor: fix step sequencer for VKB input and MIDI inputs with high IDs [rr=17y0f7z]

What URL does [rr=] refer to?

[cfillion]

Originally Posted by Edgemeal

What URL does [rr=] refer to?

Reddit. https://www.reddit.com/r/Reaper/comm...ing_no_longer/

[Edgemeal]

Originally Posted by cfillion

Reddit. https://www.reddit.com/r/Reaper/comm...ing_no_longer/

Thanks!

[BartR]

Please Devs ... please ...

[fierywater]

Originally Posted by sockmonkey72

+ MIDI editor: fix step sequencer for VKB input and MIDI inputs with high IDs [rr=17y0f7z]

Thank you! That should make it a lot easier for me to work away from the mothership.

[Justin]

Originally Posted by BartR

Please Devs ... please ...

This is not the appropriate venue, post in the bug report forum with steps to reproduce and any custom theme and reaper.ini used.

[MeWest]

container 2 and above the level does not respond to wet/bypass automation

[Sexan]

Can we get back that automap behavior that was in pre 113-115?
Its really inconvenient atm because both source and target need to be mapped and there is no user friendly way to do it via script (for end user). Since first source needs to be mapped then target there would need to be additional buttons/scripts depending of implementation and many clicks and last touches to map both.

Edit: only thing that was "issue" with that as I was told was for some users list was extremely big and was causing slowness with scripts which iterate parameters because it would iterate the list which has over 4000 entries (I've seen the track chunk and it was huge with over 10 000 parameters mapped)


This is dev 113-115

EDIT2: Inspecting that track they sent me, it has some ghost/empty entries? It goes to infinity
https://imgur.com/r2bnqsi

Link to tracktemplate in issue (again this is all dev 113-115)
https://drive.google.com/file/d/1rvM...usp=drive_link

[smandrap]

+ Lane: fix undo after changing comping lane [p=2734645]
# Lanes: improve behavior of lane masking and automatically creating comp areas when media items in different lanes start or end at the same time [p=2734639]

Thanks for the fixes

[daxliniere]

Originally Posted by Sexan

EDIT2: Inspecting that track they sent me, it has some ghost/empty entries? It goes to infinity

Oops. (following)

[svijayrathinam]

Dear Developers,

I have noticed a Shearing issue while zooming and scrolling the arrange view ever since reaper 7.


https://youtu.be/rNeyVypvQYw


I made a video showing it. Pls watch it. In the audio I talk about the issue.

I hope you can fix this issue.

[Justin]

Originally Posted by Sexan

Can we get back that automap behavior that was in pre 113-115?

Can you be more specific? Do you mean +dev1113 and +dev1115? also what behavior do you refer to?

[Sexan]

In that versions parameter from child fx would automatically map to parent container

[Justin]

Originally Posted by Sexan

In that versions parameter from child fx would automatically map to parent container

...in response to?

[Sexan]

Dev 113:
This was the result when adding FX into Container via API: Adding ReaEQ into Container.


All parameters are mapped to parent automatically I did not have any code in the script to do mapping, maybe this was a bug or not intentional but was nice behavior.

Lastest dev and few previous ones don't do that anymore

[mschnell]

Kontakt always has 1000 Parameters. That would be a mass ?!?!?!?

[Sexan]

Originally Posted by mschnell

Kontakt always has 1000 Parameters. That would be a mass ?!?!?!?

Its basically exposing the parameters to its container. Its the same as you click on parameter list while its in the root. So from users perspective nothing changed at all

[Justin]

Originally Posted by Sexan

Dev 113:
This was the result when adding FX into Container via API: Adding ReaEQ into Container.


All parameters are mapped to parent automatically I did not have any code in the script to do mapping, maybe this was a bug or not intentional but was nice behavior.

Lastest dev and few previous ones don't do that anymore

Hmm that wasn't us, maybe it was a script?

[Justin]

Originally Posted by svijayrathinam

Dear Developers,

I have noticed a Shearing issue while zooming and scrolling the arrange view ever since reaper 7.


https://youtu.be/rNeyVypvQYw


I made a video showing it. Pls watch it. In the audio I talk about the issue.

I hope you can fix this issue.

Hmm, we haven't been able to duplicate this. You might find that disabling optimized drawing (Metal) in prefs/general/advanced (and restarting REAPER) will fix? It seems like they may have made the non-metal drawing path sufficiently fast on Sonoma...

[Justin]

Originally Posted by Sexan

Can we get back that automap behavior that was in pre 113-115?
Its really inconvenient atm because both source and target need to be mapped and there is no user friendly way to do it via script (for end user). Since first source needs to be mapped then target there would need to be additional buttons/scripts depending of implementation and many clicks and last touches to map both.

Edit: only thing that was "issue" with that as I was told was for some users list was extremely big and was causing slowness with scripts which iterate parameters because it would iterate the list which has over 4000 entries (I've seen the track chunk and it was huge with over 10 000 parameters mapped)

Hmm this does look like a bad behavior by a script.. at any rate, I think we'll make the stuff that saves chains/rpp/etc state not include invalid mappings that have been misconfigured by a script.

[Sexan]

Originally Posted by Justin

Hmm that wasn't us, maybe it was a script?

Script does not do any mapping (i did not yet implemented it), I literally dont have 1 single line of code that does mapping. Script behaves diferently between 113 dev and 117 dev so I thought you guys added/removed feature.

So I guess some API is bugging out?

[Sexan]

Originally Posted by Justin

Hmm this does look like a bad behavior by a script.. at any rate, I think we'll make the stuff that saves chains/rpp/etc state not include invalid mappings that have been misconfigured by a script.

But this does not happen anymore on latest pres, only on 113-115-116

[Justin]

Originally Posted by Sexan

But this does not happen anymore on latest pres, only on 113-115-116

If you have steps to reproduce with any version I'd be very interested!

[Sexan]

Ok will let you know tomorrow (late here)

[Sexan]

Ok tracked down what is causing it.
Affected dev versions 113,114,115

STEPS:
1. Add empty track
2. Run the script (it will insert container and ReaEQ then move it inside of container)

local r = reaper
local track = r.GetSelectedTrack(0,0)
local cont_pos = r.TrackFX_AddByName( track, "Container", false, -1000 )
local eq_pos = r.TrackFX_AddByName( track, "ReaEQ", false, -1001 )
local fx_id = 0x2000000 + 1 + (r.TrackFX_GetCount(track)) + 1
r.TrackFX_CopyToTrack(track, eq_pos, track, fx_id, true)

-- UPDATE POSITIONS
local fx_id = 0x2000000 + 1 + (r.TrackFX_GetCount(track)) + 1

for p_id = 0, r.TrackFX_GetNumParams(track, fx_id) do
  local fx_env = r.GetFXEnvelope(track, fx_id, p_id, false)
end

So calling this for all parameters would map everything even CREATE is false (which you said if you toggle envelope it will automap to parent)

r.GetFXEnvelope(track, fx_id, p_id, false)

Also this would create that "ghost/empty/invalid" mappings (113,114,115) but its harder to reproduce

P.S. Sorry for all confusion with "automapping feature". It literally started happening in that dev releases and since I have no code for mapping I thought it was a new feature. Later it stop doing it and I thought feature was removed. (my code did not changed from 113 to now so its exactly same code)

[BartR]

Originally Posted by Justin

This is not the appropriate venue, post in the bug report forum with steps to reproduce and any custom theme and reaper.ini used.

Hi Justin

I did it ... and now I completed it with the information on how to achieve it (since I thought it was obvious, I didn't declared how to get it, but now there is. I added it into a comment.)

[Justin]

Originally Posted by Sexan

Ok tracked down what is causing it.
Affected dev versions 113,114,115

STEPS:
1. Add empty track
2. Run the script (it will insert container and ReaEQ then move it inside of container)

local r = reaper
local track = r.GetSelectedTrack(0,0)
local cont_pos = r.TrackFX_AddByName( track, "Container", false, -1000 )
local eq_pos = r.TrackFX_AddByName( track, "ReaEQ", false, -1001 )
local fx_id = 0x2000000 + 1 + (r.TrackFX_GetCount(track)) + 1
r.TrackFX_CopyToTrack(track, eq_pos, track, fx_id, true)

-- UPDATE POSITIONS
local fx_id = 0x2000000 + 1 + (r.TrackFX_GetCount(track)) + 1

for p_id = 0, r.TrackFX_GetNumParams(track, fx_id) do
  local fx_env = r.GetFXEnvelope(track, fx_id, p_id, false)
end

ah, yes -- GetFXEnvelope() with a false create parameter should not create any mappings (that fact that it did was a bug).

If you want to create a mapping without creating the envelope, use the newer API:

reaper.TrackFX_GetNamedConfigParm(track, container_id, "container_map.add." .. fx_id .. "." .. p_id)

Also, worth noting that API is flexible, it can take a fx_id which is a 0x2000000-based address (which could be deep in a container hierarchy), or 0 for the first FX in the container, 1 for second FX in container, etc.

[Buy One]

Originally Posted by Justin

If you want to create a mapping without creating the envelope, use the newer API:

reaper.TrackFX_GetNamedConfigParm(track, container_id, "container_map.add." .. fx_id .. "." .. p_id)

Also, worth noting that API is flexible, it can take a fx_id which is a 0x2000000-based address (which could be deep in a container hierarchy), or 0 for the first FX in the container, 1 for second FX in container, etc.

I think this note deserves to be included in the API doc

[Reno.thestraws]

Hi guys!

A big "mistake" with LTC timecode using "insert SMPTE LTC timecode generator"

The created item doesn't take the project start time set in the project settings into account

Exemple : set the project start time to 01:00:00:00 (using frame timeline)

insert timecode on a new track

send this track to any hardware -> not in sync!

I did a simple test

set the start time to 0
insert timecode -> glue

set start time at 01:00:00:00
insert time code on another track

play both track with one reverse -> complete null!

Thanks

Reno

[Justin]

Originally Posted by Buy One

I think this note deserves to be included in the API doc

It is, though a little more briefly: "FXID can be a full address (must be a child of the container) or a 0-based sub-index (v7.06+)"

[Buy One]

Originally Posted by Justin

It is, though a little more briefly: "FXID can be a full address (must be a child of the container) or a 0-based sub-index (v7.06+)"

Ah, was looking at the outdated doc, 7.03

[Suzuki]

Originally Posted by Justin

ah, yes -- GetFXEnvelope() with a false create parameter should not create any mappings (that fact that it did was a bug).

If you want to create a mapping without creating the envelope, use the newer API:

reaper.TrackFX_GetNamedConfigParm(track, fx_id, "container_map.add." .. fx_id .. "." .. p_id)

Also, worth noting that API is flexible, it can take a fx_id which is a 0x2000000-based address (which could be deep in a container hierarchy), or 0 for the first FX in the container, 1 for second FX in container, etc.

I just tried this, but argument #2 is container's id, right?

reaper.TrackFX_GetNamedConfigParm(track, container_id, "container_map.add." .. fx_id .. "." .. p_id)

[Justin]

Originally Posted by Suzuki

I just tried this, but argument #2 is container's id, right?

reaper.TrackFX_GetNamedConfigParm(track, container_id, "container_map.add." .. fx_id .. "." .. p_id)

Correct yeah sorry, updated my post with that correction