v6.79+dev0424 - April 24 2023

[matt_t]

v6.79+dev0424 - April 24 2023

• * Includes feature branch: visual track spacers
• * Includes feature branch: 128 channels per track
• * Includes feature branch: updated Windows manifest for newer OS features
• * Includes feature branch: always running non-bypassed FX when the UI is visible
• * Includes feature branch: crossfade new recording with existing media items if configured
• * Includes feature branch: video from background projects
• * Includes feature branch: FX containers
• * Includes feature branch: improvements to aligning takes after recording
• * Includes feature branch: arrange view override mouse modifier sections
• * Includes feature branch: toolbar armed/special animations
• * Includes feature branch: pooled and unpooled ARA edits
• * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections
• * Includes feature branch: preview item selection for grouped tracks
• * Includes feature branch: GR metering as embedded UI for third-party VSTs
• * Includes feature branch: media item fixed lanes
• + Arrange: improve scrollbar auto-scroll interactions when adjusting vertical scrollbar or horizontal zoom
• + Audio Units: possible fix for crash when loading plug-in state [t=278544]
• + Command line: support passing reascript on command line to execute, for example: 'reaper.exe projectfile.rpp scriptfile.lua'
• + MIDI: support entering blank string for default name for in-project MIDI media items
• # Command line: revert support for 'reaper.exe -reascript scriptname.lua'
• # Media item lanes: fix restoring number of lanes when undoing item move
• # Media item lanes: improve action to implode media items to one fixed lane 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

[bolgwrad]

Originally Posted by matt_t

v6.79+dev0424 - April 24 2023

• # Media item lanes: improve action to implode media items to one fixed lane track

Brilliant, thank you.

[Vagelis]

Originally Posted by matt_t

v6.79+dev0424 - April 24 2023[*]# Media item lanes: fix restoring number of lanes when undoing item move

Fixed, thx.

Originally Posted by matt_t

v6.79+dev0424 - April 24 2023[*]# Media item lanes: improve action to implode media items to one fixed lane track

I would really really love if we could implode them to the selected track and not to the track of the top item.

Some uses cases are: select multiple items on the same or different tracks and implode them to the selected track, which could be empty or with other items already.
This could be very useful to start layering with those items, comp or blend different sources.

Another idea while comping is to explode the items of the comp lane to a new track, then continue comping different variations in lanes. After it's done, implode the new items of the comp lane back to the track with the first comp variation. I think it could be a cool way to layer, comp, or just save different variations to the selected track.

[deeb]

Originally Posted by Vagelis

I would really really love if we could implode them to the selected track and not to the track of the top item.



Some uses cases are: select multiple items on the same or different tracks and implode them to the selected track, which could be empty or with other items already.
This could be very useful to start layering with those items, comp or blend different sources.

I think this is a more clear and useful workflow.

[Gass n Klang]

can we have a "Implode items on the same (/ across) track to lanes" as we have for takes?

[schwa]

Originally Posted by matt_t

+ Command line: support passing reascript on command line to execute, for example: 'reaper.exe projectfile.rpp scriptfile.lua'

A note on this, you can use 'reaper.exe -nonewinst mediafile.wav scriptfile.lua' to add media and/or run scripts in an already-running instance of REAPER. Any number of media files and scripts can be specified; they will be loaded or run in order. If you provide a project file, it will be opened in a new tab.

[sockmonkey72]

Originally Posted by schwa

A note on this, you can use 'reaper.exe -nonewinst ...' to add media and/or run scripts to an already-running instance of REAPER. Any number of media files and scripts can be specified; they will be loaded or run in order. If you provide a project file, it will be opened in a new tab.

Beautiful, that's fantastic.

[deeb]

Originally Posted by schwa

A note on this, you can use 'reaper.exe -nonewinst ...' to add media and/or run scripts in an already-running instance of REAPER. Any number of media files and scripts can be specified; they will be loaded or run in order. If you provide a project file, it will be opened in a new tab.

I still didn’t try but seems very useful. Are you planning to have more arguments? Is there more other then -nonewinst?

Would be very nice if we could have an arg for:

- defining new track(s) name
- load into a single track, single track lanes or multiple tracks

This would allow scripts to know exactly which files were loaded and do something over them if needed.

An extra one: seconds of space between loaded items in a single track.

Edit: another extras: create new project, new project name. Include template or not.

I will only be able to test this later. Thank you.

edit2: Ops , is this a windows only feature?

[mschnell]

Completely control a running version of Reaper by starting Reaper a second time (instead of doing some OSC or similar communication...) ?!?!?!?
-Michael

[schwa]

From the command line, 'reaper.exe -nonewinst' (windows only) won't start a new REAPER instance if one already exists. Instead the parameters will be sent to the existing instance.

Here is the complete current list of supported command line parameters:

Usage: reaper [options] [projectfile.rpp | mediafile.wav | scriptfile.lua [...]]

Multiple media files and/or scripts may be specified, and will be added or run in order.
-nonewinst can be used to add media files and/or run scripts in an already-running instance of REAPER.

Options:
  -audiocfg : show audio configuration at startup
  -cfgfile file.ini : use full path for alternate resource directory, otherwise uses default path
  -new : start with new project
  -template filename.rpp : start with template project
  -saveas newfilename.rpp : save project (after creating/loading) as file
  -renderproject filename.rpp : render project and exit
  -ignoreerrors : do not show errors on load
  -nosplash : do not show splash screen window
  -splashlog /path/to/filename.log : write splash screen message log to file
  -newinst | -nonewinst : override preference for new instance checking
  -close[all][:save|:nosave] : close project(s), optionally not prompting for save
  -batchconvert filelist.txt : batch converter mode, filelist.txt includes:
     filename.wav
       (or)
     filename.wav(TAB CHARACTER)outputfile.wav
       (any number of additional files)
     <CONFIG block (optional) which can contain:
       SRATE 44100 (omit to use source samplerate)
       NCH 2 (omit to use source channel count)
       RSMODE modeidx (resample mode, copy from project file)
       DITHER 3 (1=dither, 2=noise shaping, 3=both)
       USESRCSTART 1 (1=write source media BWF start offset to output)
       USESRCMETADATA 1 (1=attempt to preserve original media file metadata if possible)
       PAD_START 1.0 (leading silence in sec, can be negative)
       PAD_END 1.0 (trailing silence in sec, can be negative)
       OUTPATH 'path'
       OUTPATTERN 'wildcardpattern'
       NORMALIZE 1 -6.0 0 (1=peak, 2=true peak, 3=lufs-i, 4=lufs-s, 5=lufs-m,
                           2nd parameter is dB,
                           3rd parameter: 1=normalize only if too loud)
       BRICKWALL 1 -1.0 (1=peak, 2=true peak, 2nd parameter is dB)
       FADE 0.0 0.0 1 1 (fade-in length, fade-out length, fade-in shape, fade-out shape; length 0.001 = 1 ms)
       FXCHAIN 'fxchainfilename' (use full path if specified, otherwise FxChains directory)
       FX_NCH 4 (if not specified, FX will be configured to 4 channels)
       <FXCHAIN
         (contents of .RfxChain file)
       >
       <OUTFMT
         (base64 data, e.g. contents of <RENDER_CFG or <RECORD_CFG block from project file)
       >
       <METADATA
         (contents of <RENDER_METADATA block from project file)
       >
     >

Windows-only options:
  -noactivate : launch but do not activate

[deeb]

ohh great. thanks!

---------
I am not sure if i am getting, but i have noticed that If i use:
> open REAPER.app --args -new

and then:

> open REAPER.app --args -nonewinst ~/Desktop/audio.mp3

~/Desktop/audio.mp3 is not being imported. I don't know why.


---------
Also, If i use this:
> open REAPER.app --args -new

then again:
> open REAPER.app --args -new

I would expect to have 2 new projects created and in 2 different tabs, but no. anyway: i think i would never use this.


---------
Also noticed that if i use:
>open REAPER.app --args new ~/Desktop/audio1.mp3 ~/Desktop/audio2.mp3 ~/Desktop/audio3.mp3

Just the last file gets selected after loading, but I would expect all the 3 media to be selected. So that in a script we can know exactly which files were imported.
I think i would still like to see a new track added instead of merging into existing tracks, because it can happen that the template as already media, and if it happens that new media is merged into a track with media then , we have no way to know which files were loaded in a script. No?

[buyrunvelocity]

* Includes feature branch: GR metering as embedded UI for third-party VSTs
Great!
Thank You

[Hipox]

Originally Posted by buyrunvelocity

* Includes feature branch: GR metering as embedded UI for third-party VSTs
Great!
Thank You

Would tou mind sharing how to use this feature?

[buyrunvelocity]

Originally Posted by Hipox

Would tou mind sharing how to use this feature?

Sure, what i understand is we will be able to see Gain Reduction on Track and Mixer Control panels without opening the plugins.Actually it would be great if we could see on meter area.

[lexaproductions]

Originally Posted by schwa

From the command line, 'reaper.exe -nonewinst' (windows only) won't start a new REAPER instance if one already exists. Instead the parameters will be sent to the existing instance.

Here is the complete current list of supported command line parameters:

  -close[all][:save|:nosave] : close project(s), optionally not prompting for save

Hey Schwa, if this can be done via command line, any chance it could be done via API? To force close a project without saving?

[mschnell]

Originally Posted by lexaproductions

Hey Schwa, if this can be done via command line, any chance it could be done via API? To force close a project without saving?

That would be great for me,as well.

With my "embedded Reaper" project I used a global setting that does this, but that has other disadvantages. I'd like do have a pure "don't ask for saving before closing" setting or an action that does this, when Windows requests the program to close. (I need fast and secure closing at that point).
-Michael

[vitalker]

Originally Posted by lexaproductions

Hey Schwa, if this can be done via command line, any chance it could be done via API? To force close a project without saving?

It was possible, but probably only for a new instance:

reaper.ExecProcess('reaper.exe -close', 0 )

[deeb]

Originally Posted by matt_t

v6.79+dev0424 - April 24 2023

• * Includes feature branch: media item fixed lanes

i am struggling with this 2 things:

1 - As far as i know tracks default to "automatically remove lanes" ON and we have no way to default to OFF. This is very important to be fixed, otherwise every track we create needs to be turned off manually.

2 - Even when is ON i would never want reaper to automatically set Play 1 of the first track in this example. Or Is this intensional?



same not desired behaviour when deleting a media item: (lane should not be automatically set to play)