v6.26+dev0331 - March 31 2021

[mabian]

v6.26+dev0331 - March 31 2021

• * Includes feature branch: VST3 bridging
• * Includes feature branch: ReaSurroundPan
• * Includes feature branch: media item lanes
• * Includes feature branch: media item channel mapping
• + ReaScript: correct documentation for Set/GetMasterTrackVisibility
• # JSFX: fix flushing of inf/nan to zero [t=251603]
• # Media item lanes: fix dragging items into lane-add area [p=2425679]

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

[Vagelis]

Originally Posted by mabian

v6.26+dev0331 - March 31 2021[*]# Media item lanes: fix dragging items into lane-add area [p=2425679]

Much better now, thanks a lot for the fix

Regarding dragging multiple selected items into lane-add area, if we drag them from the first item into lane add area, they all drop ok. If we drag from the second or third item, even if they are all selected, they don't drop all on lane-add area.
Would it be possible to drop all selected items no matter from which item we drag them?

[mabian]

JS total weirdness here:

Wrong result:
p_outputval = p_minval + ((p_maxval - p_minval)*CalcValue(p_inputval));

Right result 1:
p_outputval = p_minval + (CalcValue(p_inputval)*(p_maxval - p_minval));
(just inverted the order in the second sub expression)

Right result 2:
v = CalcValue(p_inputval);
p_outputval = p_minval + (v*(p_maxval - p_minval));
(computing the CalcValue before multiplying it)

CalcValue(), p_minval, p_maxval always between 0 and 1.
p_maxval > p_minval

The "Wrong result" expression can return numbers < 0, which is impossible... dev331 is the first version I'm seeing it.

- Mario

[mabian]

Attaching example screenshot and script.
Output value cannot be negative.

- Mario

[Justin]

Originally Posted by mabian

JS total weirdness here:

Wrong result:
p_outputval = p_minval + ((p_maxval - p_minval)*CalcValue(p_inputval));

Right result 1:
p_outputval = p_minval + (CalcValue(p_inputval)*(p_maxval - p_minval));
(just inverted the order in the second sub expression)

Right result 2:
v = CalcValue(p_inputval);
p_outputval = p_minval + (v*(p_maxval - p_minval));
(computing the CalcValue before multiplying it)

CalcValue(), p_minval, p_maxval always between 0 and 1.
p_maxval > p_minval

The "Wrong result" expression can return numbers < 0, which is impossible... dev331 is the first version I'm seeing it.

- Mario

Thanks, this is very helpful! Edit: duplicated, fixing!

[mschnell]

Originally Posted by mabian

JS total weirdness here:

MANY thanks for checking this !!!
-Michael

[mabian]

Originally Posted by mschnell

MANY thanks for checking this !!!
-Michael

It was not that hard, just noticed by pure accident while working at a JS plugin that things simply started being nonsense

- Mario

[svijayrathinam]

Hi Schwa,


I do not find the Clang 12 installers from the last two Dev versions. For Some reason all the text like the FX browser plugin text appeared bigger in clang12 releases on Mac OS Big Sur. Now with the regular clang and the regular Mac OS installer that's not the case.

[Paul1982]

Please devs, is it possible to bring back auto media lanes?

If there are many of us asking for its return, it is because it has advantages over fixed media lanes.

With auto media lanes, we haven't hatched line which takes place and when an item is not under another item, its height is at the maximum. So it's more readable. Moreover, when we want to put one item under another we don't have to enlarge the size of the track. So, it's faster.

Thanks for your understanding.

[gxray]

Originally Posted by Paul1982

Please devs, is it possible to bring back auto media lanes?

If there are many of us asking for its return, it is because it has advantages over fixed media lanes.

With auto media lanes, we haven't hatched line which takes place and when an item is not under another item, its height is at the maximum. So it's more readable. Moreover, when we want to put one item under another we don't have to enlarge the size of the track. So, it's faster.

Thanks for your understanding.

This as an option would be nice as it's a fair bit faster, and as you mention doesn't require minimum track height. But I'd imagine there's probably a good technical reason why it was removed.

(IE maybe some nasty complexity that was going to be a lot more difficult to maintain versus manual, or more edgecases/bugs)

Who knows though, who here can't say at least part of the reason why they love REAPER is the daily lotto-rush of checking the pre-release forum for changes and new features ;^)

Win some, lose some

[ovnis]

Sad. Auto mode was so simple, transparent (no grey lane) and powerful (and complementary with fixed lanes).

[musicbynumbers]

I too think that if it isn't going to mess with a new overall method or feature (at some point) then auto was useful to have as well.

[ovnis]

For me, auto media lanes, fixed media lanes auto and free item are great and complementary.

[Justin]

Originally Posted by svijayrathinam

Hi Schwa,


I do not find the Clang 12 installers from the last two Dev versions. For Some reason all the text like the FX browser plugin text appeared bigger in clang12 releases on Mac OS Big Sur. Now with the regular clang and the regular Mac OS installer that's not the case.

Hmm those builds were discontinued because they never end up in releases. Having said that, we can probably make the list text size configurable on Big Sur, let me look into that.

[svijayrathinam]

Originally Posted by Justin

Hmm those builds were discontinued because they never end up in releases. Having said that, we can probably make the list text size configurable on Big Sur, let me look into that.

Thank you very much

[AZpercussion]

Takes don't colored automatically in the record mode "auto-punch selected items" if punching item placed on a track with fixed lanes.