v6.68+dev1003 - October 3 2022

[musicbynumbers]

v6.68+dev1003 - October 3 2022

• * Includes feature branch: razor edits on master track envelopes
• * Includes feature branch: selected media item appearance changes
• * Includes feature branch: track grouping manager dialog
• * Includes feature branch: CLAP plugin support
• * Includes feature branch: track media/razor edit grouping
• * 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
• + Fades/crossfades: limit automatically created fade length to half the width of the arrange view
• + Notation editor: by default, break beams on every 1/4 note in 4/4 time
• + ReaScript: drag/drop from FX browser to gfx windows will send filenames of @fx:fx_ident to gfx.getdropfile() [t=271052]
• + VST: activate/deactivate VST3 busses on the fly in response to pin mapper changes
• # Notation: rename "whote note trill" ornament to "trill line"

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

[bFooz]

Originally Posted by musicbynumbers

[*]# Notation: rename "whote note trill" ornament to "trill line"

Hi Devs, you have probably misunderstood what the trill problem was.

It is not about the horizontal axis but about the vertical.

Both the half-tone and whole-tone trill creates a trill line for the whole duration of the note. That works as it should.

But the half-tone trill is an oscilaltion between the base note and another note which is a semitone higher. A whole-tone trill is similar oscillation but with the note that is a whole step higher instead.

So the current change in the name makes no sense. The request was, if I remember correctly, to specify that one is half-tone and the other one is whole-tone.


Here is a demonstration between the half-tone and whole-tone trill. The notation works fine, it is just the naming.

[Daodan]

Enable "Ripple editing all tracks", create and drag razor area. Items removed.

[sockmonkey72]

I had some questions/notes about the new child/parent/send routing options here, in case they were missed.

[schwa]

Originally Posted by Daodan

Enable "Ripple editing all tracks", create and drag razor area. Items removed.

Fixing, thanks.

[X-Raym]

Click drag FX could also from TCP slots context and Mixer slots :P

[bFooz]

Originally Posted by musicbynumbers

Notation editor: by default, break beams on every 1/4 note in 4/4 time

Thanks.

This works well for 8th notes, but there is a regression with syncopated rhythms:


current dev version: (not good)



latest release version: (good)

[mpl]

Thanks Justin, works like a charm:

[mpl]

Oh this also allow FX Rack script (and other FX-related scripts with GUI) to support such drop, which is awesome.

[PhelixK]

Originally Posted by Daodan

Enable "Ripple editing all tracks", create and drag razor area. Items removed.

Originally Posted by schwa

Fixing, thanks.

FWIW this works as expected here on macOS (10.14)

[schwa]

Originally Posted by bFooz

Thanks.

This works well for 8th notes, but there is a regression with syncopated rhythms:

Ah, well, hmm. This may be a situation where the existing (before this dev version) behavior is the least bad. The general rule is that beams will break on the primary beat as defined in the metronome pattern. The default pattern for 4/4 is ABBB, so beams only break on the 1 beat. This dev version has special handling for default 4/4 to instead break on all 4 beats, but as you observed that is not desired except in specific, basic situations. So I think we will revert the change as the previous behavior was preferable in more situations.

[PhelixK]

* Includes feature branch: razor edits on master track envelopes

# Razor edits: fix save/load and undo/redo when using razor edits on master track

– here the Razor edit envelope area isn't recalled on project save/reload.

Edit:
just to show what I'm referring to above, and also reported in v6.68+dev0927.
– it's recall of the RE selection area and ofc. not the editing itself. Here's what shows when project is reloaded and where I would expect the RE selection area to include the envelope lane.

[bFooz]

Originally Posted by schwa

Ah, well, hmm. This may be a situation where the existing (before this dev version) behavior is the least bad. The general rule is that beams will break on the primary beat as defined in the metronome pattern. The default pattern for 4/4 is ABBB, so beams only break on the 1 beat. This dev version has special handling for default 4/4 to instead break on all 4 beats, but as you observed that is not desired except in specific, basic situations. So I think we will revert the change as the previous behavior was preferable in more situations.

I see. Now I don't know which one is better.

Considering that 4/4 is the most common time signature and these two cases are kind of opposite but common, it might be worth to put some worktime into it.

[ovnis]

When we click on a sample inside the media explorer, It would be great to have the possibility to create a track with the mpl's instrument instead of reasampler.

[tohubohu]

Originally Posted by bFooz

Thanks.

This works well for 8th notes, but there is a regression with syncopated rhythms:


current dev version: (not good)



latest release version: (good)

I didn't understand how you manage to write these notes. Could you please detail with a gif the process of inserting the notes in this example? thank you

[tohubohu]

Originally Posted by schwa

Ah, well, hmm. This may be a situation where the existing (before this dev version) behavior is the least bad. The general rule is that beams will break on the primary beat as defined in the metronome pattern. The default pattern for 4/4 is ABBB, so beams only break on the 1 beat. This dev version has special handling for default 4/4 to instead break on all 4 beats, but as you observed that is not desired except in specific, basic situations. So I think we will revert the change as the previous behavior was preferable in more situations.

in the version before, in 3/4 and 2/4 there was no problem and it broke on the first, second, et third time for 3/4 and first and second time for 2/4 . I understand nothing.

[schwa]

Originally Posted by tohubohu

in the version before, in 3/4 and 2/4 there was no problem and it broke on the first second et third time for 3/4 and first and second time for 2/4 . I understand nothing.

2/4 and 3/4 have special handling that treats the default AB and ABB patterns as AA and AAA instead for the purpose of notation breaks. The change in dev1003 was to handle 4/4 similarly, but that creates the unwanted situation that bfooz describes above.

[tohubohu]

Originally Posted by bFooz

Thanks.

This works well for 8th notes, but there is a regression with syncopated rhythms:


current dev version: (not good)



latest release version: (good)

I can't reproduce this on Mac. by minimizing ties, one obtains the correct writing. I don't understand too.

[mpl]

Originally Posted by ovnis

When we click on a sample inside the media explorer, It would be great to have the possibility to create a track with the mpl's instrument instead of reasampler.

With last version this does not make sense since rack does not take RS5k actual note as a mark for appending to specific note, but internal track data. There are couple internal of variables created inside track on drop sample, so implementing it from Reaper side seems impossible.

Btw drop from media explorer works as well as 'show sample in ME' buttons. And probably I can take if you do "export sample to new rs5k track' from media explorer, and the new created somewhere inside rack folder structure (but again, rack does not catch children by folder structure).

[bFooz]

Originally Posted by tohubohu

I can't reproduce this on Mac. by minimizing ties, one obtains the correct writing. I don't understand too.

Yes, this is actually true. I use Minimize ties for all notes at OFF. For reasons such as this:

(Minimize ties for all notes ON:

)

So the question is what should be the default behavior for syncopated rhythms:

• On the one hand, in the current dev version, you can always manually minimize ties for the notes.

• On the other hand, in the official release, the you can always manually break the beams either by settings AAAA pattern yourself or by the "Beam Together" command.

So probably the original behavior. You can have the current dev behaviour in it as well but the opposite is not true.

Ofcourse for me the ideal would be the best of both worlds: proper beaming automatically and proper tieing automatically.


The pattern is set either in the "Metronome and pre-roll settings" or for each individual tempo marker. This is actually a hidden feature, I have learned about this only a few days ago that this thing affects beaming.

[tohubohu]

Originally Posted by bFooz

(Minimize ties for all notes ON:

)

you write like that rather don't you? with the voices and the change of direction of the stems?

Originally Posted by bFooz

The pattern is set either in the "Metronome and pre-roll settings" or for each individual tempo marker. This is actually a hidden feature, I have learned about this only a few days ago that this thing affects beaming.

you teach me. thank you

[tohubohu]

Originally Posted by schwa

2/4 and 3/4 have special handling that treats the default AB and ABB patterns as AA and AAA instead for the purpose of notation breaks. The change in dev1003 was to handle 4/4 similarly, but that creates the unwanted situation that bfooz describes above.

and is it complicated to add in the code another default behavior of beams for syncopated rhythms? (if I understand everything correctly )

[operator]

Originally Posted by mpl

Oh this also allow FX Rack script (and other FX-related scripts with GUI) to support such drop, which is awesome.

How is it with Keyboard-Shortcuts? Are they`re working there too? That would be sooo incredible... I have my Instruments/FX (ca.50) set on KB-shortcuts. This is one of my most favorite feature about/in Reaper --> which allows working at the speed of thought where other software is crippeling you mentally with "click-traps".
Being able to insert certain FX via Keyboard Shortcut is pure gold [economically and creativly].

[mccrabney]

* Includes feature branch: razor edits on master track envelopes

i noticed that this doesn't work on the tempo envelope. why is this? seems like it would be a prime candidate.

indeed, razor edit selections started in the track fields and ended in the master track should allow users to move entire blocks of their project with the tempo map intact, rather than requiring two separate edits.

[mccrabney]

(first, tangential to the main point of this post: a crash occurs when you move a big RE spanning a project that includes a portion of the master track envelope space.)

in this gif, i am restructuring my project by creating and moving a large RE that intends to include the relevant tempo envelope.

normally, i'd use regions to do this, but as per my recent bug report, this badly warps untrimmed AI when your project contains tempo changes. moving by RE does not have this issue.

so instead, i use big RE selections to do it. however, since it doesn't pick up the tempo envelope, i would have to manually select, cut, and paste the points elsewhere.

tempo points are part of the project, tied in time to the objects being selected and move by RE. please allow them to follow RE movement, it's the most important envelope that the master track has.

[schwa]

Originally Posted by mccrabney

(first, tangential to the main point of this post: a crash occurs when you move a big RE spanning a project that includes a portion of the master track envelope space.)

Hm, I'm having trouble reproducing that crash. Is it possible for you to share a minimal project that shows the problem?

[schwa]

Originally Posted by bFooz

The pattern is set either in the "Metronome and pre-roll settings" or for each individual tempo marker.

You can also edit the pattern from the notation editor, by right-clicking on the start of a measure and choosing "change tempo / time signature / rhythm pattern".

[mccrabney]

project attached. it seems like this occurs more when you have more data onscreen, eg a near-complete project. with little/no data onscreen, it takes more dramatic shaking/moving to trigger the crash.

[tohubohu]

Originally Posted by bFooz

YThis is actually a hidden feature, I have learned about this only a few days ago that this thing affects beaming.

Originally Posted by schwa

You can also edit the pattern from the notation editor, by right-clicking on the start of a measure and choosing "change tempo / time signature / rhythm pattern".

maybe it should be added in the window that the pattern affects the beams?!
because you can't guess

[bFooz]

Originally Posted by tohubohu

maybe it should be added in the window that the pattern affects the beams?!
because you can't guess

+ 1

[MonkeyBars]

Just a quick note that I'm working on a super secret (not really lol) script project offering a routing feature missing in Reaper natively with a complex workaround that would really benefit by being able to select parent channels. (For example, setting ch 5-6 to go out the master/parent send)

However, the current dev implementation doesn't really seem to work on my end. Would be great for 6.69!

[daxliniere]

Originally Posted by MonkeyBars

Just a quick note that I'm working on a super secret (not really lol) script project offering a routing feature missing in Reaper natively with a complex workaround..

Post-fader FX?!?!?

[MonkeyBars]

Originally Posted by daxliniere

Post-fader FX?!?!?