v6.59+dev0604 - June 4 2022

[Sexan]

v6.59+dev0604 - June 4 2022

• * Includes feature branch: various drawing integer overflow fixes with non-sensical values [t=267310]
• * Includes feature branch: fixed lane play markers
• * Includes feature branch: pre-FX/pre-fader output recording
• * Includes feature branch: improve experimental silent-track CPU reduction option to include FX tail length
• * Includes feature branch: media item fixed lanes
• * Includes feature branch: internal pin management overhaul for future extension
• + Preferences: move preference for overlapping media item display to Preferences/Appearance/Media
• + Preferences: remove preference to collapse FIPM/fixed media item lanes at a minimum height (lanes/positioning are always displayed)
• + Render: always display one momentary, one short-term, and one integrated render statistic in render dialog
• + Render: make clearer in preferences that either LUFS or RMS will be calculated/displayed for a given period (momentary, short-term, or integrated)
• + Render: slight improvement in render statistics calculation CPU usage
• # Media item fixed lanes: adjust lane play marker crossfade mouse hit area [p=2565909]
• # Media item fixed lanes: allow running actions that depend on lane play markers even when track is small
• # Media item fixed lanes: fixed pasting razor edits that contain lane play markers [p=2565725]
• # Video: improve preview responsiveness when creating marquee selections and razor edits and aggressive updates are enabled

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

[ovnis]

"+ Preferences: remove preference to collapse FIPM/fixed media item lanes at a minimum height (lanes/positioning are always displayed)"

It's a good thing!

[Sexan]

[ovnis]

Is it a bug?
The color of the track lane player marker is the same than the color of track play lane add area.

[ovnis]

The solo fixed lane (of the fixed track muted) has not the same color as the regular muted track.

There is a particular reason?

For me, it's illogical. They should have the same color when tracks are muted.

And in this case, If we are not attentive, we might think than fixed track is not muted.

[schwa]

Originally Posted by ovnis

The solo fixed lane (of the fixed track muted) has not the same color as the regular muted track.

There is a particular reason?

For me, it's illogical. They should have the same color when tracks are muted.

Same reason that the active take is displayed differently from inactive takes, even on a muted track. So you can see what would play back if the track were unmuted. For that matter, it's the same reason that anything at all is displayed on muted tracks

[ovnis]

In the previous case, the issue is: If we are not attentive, we might think than fixed track is not muted.

In this case (photoshop): the lane has the good color and we can see it's the solo lane and the fixed track is muted. All is good.

[Sexan]

Items dont get deleted but get shifted to other lane

[Sexan]

Markers are not copied when one or more items are selected on same track (works when pasting on other track)

[Sexan]

Lane solo stays on wrong lane (I guess this is connected with deleting bug above)

[Sexan]

Should this happen (I suppose but maybe all lanes?)?

"Item lanes: Insert fixed lane play markers and play only razor edit areas" action

[ovnis]

We can't disable "toggle playing lane". It's me or?

"Play only lane" context menu is necessary? I mean who wants to prefer select only one lane with only one click rather two clicks (context menu)?

[Sexan]

Cannot marquee select markers when lane is smallish (maybe intentional don't know)


Embass spirit left my body now

[ovnis]

"Delete other lanes" inside lane context menu could be amazing. When we think we have a good record lane, we can delete other lanes. It could be very fast.

"Copy outpout of lane play markers to new lane at top of track" would be great on track lane context menu instead of marker context menu.

And adding "Copy outpout of lane play markers to new lane at top of track and delete other lanes"?

What is the interest of "Copy items to new lane at top of track"?

[Embass]

[musicbynumbers]

# Video: improve preview responsiveness when creating marquee selections and razor edits and aggressive updates are enable

Video seems to be quite responsive again with only around a 100ms or so of dropped frame "green" when pressing stop and then a solid playback from there on out so thanks for that

I'll double check the videos I capture don't have intermediate frames as maybe that's why it's not instant. Anyway, Thanks!

[Embass]

action 'Insert fixed lane play marker and play only lane under mouse' does not work when only one lane exist

[Embass]

double click on play marker/region inserts new MIDI item

[Embass]

[Embass]

[Embass]

[Nixon]

Devs can we please have

+ ReaSamplomatic5000: support typing in sample pitch

for "Note start" and "Note end" too?

[musicbynumbers]

+ Preferences: remove preference to collapse FIPM/fixed media item lanes at a minimum height (lanes/positioning are always displayed)

Unless I'm missing something I'm not sure how this is better? Seems like a massive step back to me in terms of moving/editing a whole project without having to zoom in.

Ideally wouldn't it be better to have a clever system whereby when shrinking the height enough, the lanes collapse down to one lane but with the correctly soloed items showing for clarity in terms of the right waveform/colour etc.

This would allow then easy moving of the whole play marker edited area.

Right now when track is at the smallest height. Right click select, razor or time selection cannot completely and reliably grab all track lane items (unless you are very careful) and play markers are ignored completely (although maybe that's a new preference I missed)?

If I want to copy and paste or just move my lanes now it's a lot more fiddly to make sure all are selected than even the old way when they were all on top of each other.

It's great as an option but unless more changes are to come, I can't see it being the best way on it's own..


This is another reason I think an "item container" that can span multiple tracks is a good idea.


As an additional potential bug..

copying a region doesn't copy across the play markers.


.

[schwa]

Originally Posted by Embass

double click on play marker/region inserts new MIDI item

There is no double-click context for the lane play markers or regions, so the message is passed through to the track context. I am guessing you have customized the track double-click behavior to insert a new MIDI item.

[Valle]

@ SCHWA:

Seems like the columns have swapped again ... (which was fiexed in v6.51+dev0312 - March 12 2022)

Edit: Also, LUFS I dosen't show (says "inf" only") in the HTML chart (unless I'm doing something wrong).

Ref: https://forum.cockos.com/showpost.ph...52&postcount=9

[playtimer]

Originally Posted by Sexan

[b][*]+ Render: slight improvement in render statistics calculation CPU usage

I hope this will resolve this culprit: https://forum.cockos.com/showthread.php?t=267088

[ferropop]

I find there is a weird delay when loading Plugin GUIs in this pre. Something that just started. Kontakt specifically...anyone else?

[musicbynumbers]

Originally Posted by ferropop

I find there is a weird delay when loading Plugin GUIs in this pre. Something that just started. Kontakt specifically...anyone else?

It might be part of the optimisation that happened so that plug GUIs don't take up cpu when not showing and also that they let reaper respond first before they do.

For a few of us this has made a massive difference to low latency performance on big orchestral projects.

I've not noticed the slowdown in loading though yet. I'll keep an eye out for it.

Hope it's not this though as don't want to go back if possible!

[ferropop]

Originally Posted by musicbynumbers

It might be part of the optimisation that happened so that plug GUIs don't take up cpu when not showing and also that they let reaper respond first before they do.

For a few of us this has made a massive difference to low latency performance on big orchestral projects.

I've not noticed the slowdown in loading though yet. I'll keep an eye out for it.

Hope it's not this though as don't want to go back if possible!

Thanks for the heads up on this. Is it a replacement behaviour or can I toggle an option to test on/off?

[srdmusic]

+optimize performance with many docked-but-invisible FX chains

Can someone explain this new feature/ fix?

[musicbynumbers]

ferropop.

I might have to go back to the previous dev build but it might actually feel a bit slow on this version after all so there might have been a change yes.

There's not a way to turn it off and on but if you go back a few dev builds you can test it there.

[musicbynumbers]

Originally Posted by srdmusic

+optimize performance with many docked-but-invisible FX chains

Can someone explain this new feature/ fix?

It means that any GUI's or I think general processing for plugins not used or shown doesn't take up CPU like it did before.

This one change has made a <MASSIVE difference to performance and pops and clicks on big orchestral setups like using 32 SWAM instruments etc.

I hope if it does need tweaking to help with Ferropop's issue above that it becomes a option we can tweak somewhere in options

[ovnis]

Maybe after an amount of FX windows docked (or FX inside windows docked?) ===> auto toggle to the new behavior?

We could indicate the quantity of FX windows docked before the switch (or FX inside windows docked?) inside pref.

[musicbynumbers]

potentially. A preference would be good too though for cornercases..

BUT.. I'm hoping this is an unforeseen consequence and can be fixed without any downsides though

I have just noticed too that opening up tracking routing window is very slow too now..

I'd be happy to have that if it meant I didn't get pops and crackles at 64 samples latency

[ovnis]

The new behavior is faster when there are lots of FX windows docked but slower when there are few FX windows docked. It seems to be faster to display vector than raster.

edit:
Maybe this option too: new behavior only with vector plugs?

[bolgwrad]

Originally Posted by Sexan

Items dont get deleted but get shifted to other lane

I get this, but only on lane 4, and lane 12 in a 20 lane track, not tested further. It looks like the previous lane gets deleted. (No crossfades, solos or markers).
[Edit] beg pardon: lane 8 too. [Edit 2] Adding an empty lane 1 causes this to happen on almost every lane, (ie lane -1 is deleted) but can't work out the pattern, some are OK.

[Justin]

Originally Posted by ferropop

I find there is a weird delay when loading Plugin GUIs in this pre. Something that just started. Kontakt specifically...anyone else?

ah fixing this

[Embass]

[Embass]

[Embass]