v6.68+dev0927 - September 27 2022

[musicbynumbers]

v6.68+dev0927 - September 27 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
• + API: add support for GetSetProjectInfo_String("RENDER_TARGETS_EX"), which returns the list double-null separated ("RENDER_TARGETS" is semicolon-separated)
• + MIDI: fix retroactive record incorrect start time [t=270558]
• + Notation editor: fix caption for "Enter Text" dialog
• + Parent send: allow arbitrary channel counts for master/parent send
• + Render: support rendering stems pre-fader from render dialog
• # Razor edits: fix save/load and undo/redo when using razor edits on master track

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

[musicbynumbers]

+ Parent send: allow arbitrary channel counts for master/parent send

Wow! That's super useful for both parent and sends. Very configurable!

[ferropop]

Something's suddenly up with Auto Crossfades at Split.

They are Huge in comparison to last build.

Anyone else?

[schwa]

What length do you have set for preferences/project/media item defaults/overlap and crossfade items when splitting?

Are the crossfades different from that length?

[ferropop]

Originally Posted by schwa

What length do you have set for preferences/project/media item defaults/overlap and crossfade items when splitting?

Are the crossfades different from that length?

Rolled back a few pres, then back to dev0927 and indeed after resetting that value it seems to be holding now. I'm using Split With Crossfade as a custom action constantly so I noticed instantly that it was behaving differently - not sure what tickled it with this pre.

Anyhow thank you it seems to be syncing with that value now!

[tohubohu]

Originally Posted by musicbynumbers

v6.68+dev0927 - September 27 2022[*]+ Notation editor: fix caption for "Enter Text" dialog

It works now.
I also think that the term "whole note trill" is wrong. It does not mean anything. I don't know which name is correct but it needs to be fixed.
https://forum.cockos.com/showpost.ph...72&postcount=3

[schwa]

It's a trill that is displayed for the length of the whole (as in entire) note. "Entire note trill" ?

[EvilDragon]

Whole note trill is entirely understandable IMO. It's a trill with a whole note duration. Easy.

Or maybe it was meant as "whole TONE trill", which is a different thing (and yeah looking at the linked screenshot, that's exactly what it is!)

(Also, you'd usually write "grace note" not "gracenote" )

[schwa]

Well the note is not necessarily a whole note, so I get the wording confusion.

[EvilDragon]

https://en.wikipedia.org/wiki/Trill_(music)#Notation

OK so looks like the wavy trill is just another way to mark it, and is equivalent to just writing tr. and has no relation to note duration... Or I'm misunderstanding something. But yeah it seems that wavy trill can also span multiple notes, which is again clashing with "whole note" term tbh.




EDIT: Just checked MuseScore, and they call the wavy trill just "Trill line".

[Mordi]

+ API: add support for GetSetProjectInfo_String("RENDER_TARGETS_EX"), which returns the list double-null separated ("RENDER_TARGETS" is semicolon-separated)

Does anyone know what this means?

[nvk]

Originally Posted by Mordi

+ API: add support for GetSetProjectInfo_String("RENDER_TARGETS_EX"), which returns the list double-null separated ("RENDER_TARGETS" is semicolon-separated)

Does anyone know what this means?

This allows for you to use the RENDER_TARGETS API and correctly handle file paths with semicolons (allowed on NTFS). I use this for my Render script actually, although I haven't had anyone complain since I'm sure semicolons in filenames aren't very common.

[sockmonkey72]

• + Parent send: allow arbitrary channel counts for master/parent send

I have questions. :-)

Let's say the parent channel has 10 channels and the child has 10 channels. At the moment, you can route 1-10, 2-10, 3-10, etc. to the parent. I'm not sure I understand the use case, nor why not 1-9, 1-8, 2-6, etc. if these kinds of partial ranges are supported.

If the parent has 10 channels and the child has 4 channels, the situation makes a little more sense: 1-4, 2-5, 3-6, etc. but at the end you get 7-10, 8-10, 9-10 which again feels weird.

Much more interesting and IMO useful is creating a manual send from a 10 channel source to a 10-channel destination. There you have a menu for mono, stereo and multichannel sources to mono, stereo and multichannel destinations. That's fantastic.

I did find a bug though. If you have a 4-channel source and a 10-channel destination, you get these options, in which the nonexistent channels 11 and 12 are referenced:

[X-Raym]

I kinda agree with sockmonkey on the routing dropdown, I dont see where I would need a 3-6 kinda routing, for what scenario this has been designed ?

I also feel that this dropdown menu is way too big. A bit disturbing.
It at least there could be sub entry for Mono, Stereo and Other, it would be more easy to navigate.

[vitalker]

Originally Posted by X-Raym

I kinda agree with sockmonkey on the routing dropdown, I dont see where I would need a 3-6 kinda routing, for what scenario this has been designed ?

I also feel that this dropdown menu is way too big. A bit disturbing.
It at least there could be sub entry for Mono, Stereo and Other, it would be more easy to navigate.

Or better have two dropdown lists, where we can enter range like 1-1, 1-3, 2-6 etc.

[STOP]

En passant X-Raym le lien Changelog de ton scripte est brisé.

[bolgwrad]

Originally Posted by sockmonkey72

I have questions. :-)

I did find a bug though. If you have a 4-channel source and a 10-channel destination, you get these options, in which the nonexistent channels 11 and 12 are referenced:

Save that the destination channel count is incremented to match 9-12, which makes sense.

[sockmonkey72]

Originally Posted by bolgwrad

Save that the destination channel count is incremented to match 9-12, which makes sense.

That would only make sense (to me) if I were clearly notified that this is what's going to happen, which is currently not the case.

[nofish]

Originally Posted by musicbynumbers

[*] * Includes feature branch: track media/razor edit grouping

Mouse modifier "Move item loop section contents ignoring snap" doesn't work on all track edit grouped tracks (neither on grouped/selected items), only for the currently touched item.
Could this be added please?

[PhelixK]

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

hmm, here save/auto-load of last active RE selection isn't working on master, tried with/without .RPP-UNDO. Save/load still works on regular tracks.

Undo/redo is fine.

[MinorKey]

Originally Posted by musicbynumbers

• + Render: support rendering stems pre-fader from render dialog

Thank you!!!

[jubalakub]

Originally Posted by musicbynumbers

v6.68+dev0927 - September 27 2022
[*] * Includes feature branch: media item fixed lanes

when is this feature will be added to official release?

there is a script made by sexan that can do swipe comping, that script uses this feature
it can't be used on official release
that thread was created 7 months ago

I know things might take a long time, but 7 months? come on.

[mschnell]

Originally Posted by jubalakub

when is this feature will be added to official release?

Rather pointless question. As it is a "feature branch" it obviously is under test and due to optimization. It is utmost impossible to estimate the time a software verification and optimization might take. Usually the longer the higher quality is targeted.
-Michael

[BartR]

Originally Posted by jubalakub

when is this feature will be added to official release?

there is a script made by sexan that can do swipe comping, that script uses this feature
it can't be used on official release
that thread was created 7 months ago

I know things might take a long time, but 7 months? come on.

I do agree with MSCHNELL ... and mre over: there are things in that feature are temporarily disabled because the grouping they are working into, created some issue. I do think that when this is solved, they will continue to reactivate that stuff and they il successfully complete the feature.

I can't wait for it as well, but I "bite my lips" and wait for it.

[User41]

Ha I check these threads religiously. Don’t know dick about developing software but am always just looking for the update on quick swipe comping in Reaper.

[vitalker]

Originally Posted by jubalakub

when is this feature will be added to official release?

there is a script made by sexan that can do swipe comping, that script uses this feature
it can't be used on official release
that thread was created 7 months ago

I know things might take a long time, but 7 months? come on.

You should read notes on the top of pre-release builds site:

596+dev1009: development version. Includes functionality that will likely not end up in
the next release (and may not end up in any release, ever)