v6.54 - April 19 2022

[playtimer]

v6.54 - April 19 2022

• + Actions: account for reverse volume grouping when running action to adjust track volume [t=264649]
• + Actions: add actions to move media items to/from hidden child track
• + ARA: update API to version 2.1, with ARM support
• + Audio Units: improve resizing behavior of AUv3 plug-ins
• + Audio Units: fix potential AUv3 crash when plug-in outputs MIDI events on Monterey
• + Audio Units: call AudioUnitUninitialize() when unloading
• + Batch converter: update display immediately after removing all files
• + Batch converter: fix in-place conversion for non-boot macOS volumes [t=264848]
• + Free item positioning: fix minor time selection display issue [p=2538153]
• + Free item positioning: glued items inherit FIPM y-positioning
• + Free item positioning: improve interaction between free item size edits and mouse modifiers (remove hardcoded behaviors of some modifier keys)
• + Free item positioning: when recording in free item positioning mode, only adjust existing item y-positions if necessary
• + FX: add per-FX instance and per-FX chain oversampling options (if both chain and instance are set, the higher of the two is used)
• + FX: change Add-FX window pane configuration (horizontal vs vertical layout) via context menu, don't change configuration on double-clicking the divider
• + FX: improve value editing and default values for wet/bypass/delta envelopes
• + FX: when opening FX chain for a track that has no FX, by default show the Add-FX window rather than the empty FX chain window (option in Preferences/Plug-Ins)
• + Import: add option in Preferences/Media to target the top part of a track to insert new track(s) to receive the media
• + Import: on drag-import, offer to replace media source only if snapped start position of imported media is within an existing media item [t=184239]
• + Logical sorting: improve sort order of various characters in Media Explorer and other windows (underscore, hyphen, number, UTF-8, alpha) [t=264382]
• + Media buffering: update playback more promptly (bypass some media buffering) when changing item takes, mute states
• + Media explorer: add action to delete file with prompting
• + Media explorer: fix updating database metadata when database is not on the local filesystem
• + Media items: replace "show overlapping items in lanes" option with "offset overlapping items vertically"
• + Media items: add preferences for item vertical overlap percentage and opacity
• + Media items: add preference for minimum height to display peaks
• + Media items: change default item mix behavior to "items always mix", existing projects and user default project settings are unaffected
• + Media items: don't display cursor feedback when mouse is over controls of locked items
• + Media items: update mouse click prioritization to prefer opaque unselected items over transparent selected items (prevent clicking controls that are behind other items)
• + Media items: improve interaction between preferences to show/hide free item positioning, show/hide media item labels at certain track heights
• + Media items: locked items do not autocrossfade with unlocked items
• + Media items: prevent editing take envelopes when item is locked
• + Menus/Actions: update menus and actions to refer to "takes" instead of "take lanes", to avoid ambiguity
• + Metadata: support WAVEEXT channel layout tag "L R C LFE Ls Rs" instead of "L R C LFE Lsd Rsd" [p=2547580]
• + MIDI editor: fix editing left edge of notes, inserting new CC events, some other behaviors when editing looped item with start offset [t=264881] [p=2545303]
• + MIDI editor: fix note velocity sweep-editing when moving the mouse quickly [t=264954]
• + MIDI editor: reload custom .ReaScale function when opening a new project
• + MIDI editor: restore grid type properly in quantize window when quantizing with swing [t=265280]
• + MIDI inline editor: improve action window targeting behavior [t=156124]
• + Projects: support loading multiple projects in recovery mode [t=234059]
• + Projects: master hardware outputs are saved with project default settings
• + Razor edits: add click-context mouse modifiers to move areas up or down without contents
• + Razor edits: improve stretch-editing automation items in ripple-edit mode [p=2545359]
• + Razor edits: razor edits on free item positioning lanes snap to item tops/bottoms, do not necessarily span the entire track height
• + Razor edits: add "razor edits affect all track envelopes", separate from "move envelope points with media items"
• + Razor edits: fix incorrect group selection edge highlight when razor editing
• + Razor edits: fix behavior when stretching right edge of razor edit with ripple edit enabled and automation items later on the track [p=2543398]
• + Razor edits: fix flickering display after running action to cut selected area of items [t=265219]
• + ReaControlMIDI: increase length of sysex dump displayed in log from 1k to 8k bytes
• + ReaEQ: expose global gain as an automatable parameter
• + ReaInsert: do not allow processing if FX oversampling is used
• + ReaScript: add GetSetMediaTrackInfo("I_FREEMODE"), deprecate GetSetMediaTrackInfo("B_FREEMODE")
• + ReaScript: add GetSetMediaTrackInfo("P_RAZOREDITS_EXT"), to get/set free item positioning bounds
• + ReaScript: fix GetThingFromPoint handling of hidden envelopes [t=264823]
• + ReaScript: fix reaper.AddRemoveReaScript() on Windows when script path contains forward slashes [t=264181]
• + ReaSurroundPan: fix action to set input names from sending tracks when FX pin mapping has been customized [t=264484]
• + ReaSurroundPan: improve display when configuration changes so that inactive channels/speakers are displayed in the list
• + ReaSurroundPan: when inserting as take FX, increase FX output pin count to match track channel count if needed [t=265248]
• + Recording: respect option to always add takes to new recording when looping
• + Recording: when preference enabled to add recorded media at each loop, defer adding media during mouse editing [p=2543669]
• + Render: display graph of loudness values of rendered file in HTML statistics view
• + Render: apply PDC to rendered output when master track FX is set to ignore PDC or hardware-output-PDC
• + Reverse items: improve behavior of reverse items as new take with audioless video items [t=265238]
• + Super8: allow up to 500ms of RDC
• + Tempo envelope: context menu action to insert point respects default point shape (linear or square, curved shapes are not allowed on tempo envelopes)
• + Tempo envelope: don't snap to beats when editing points if project snap is disabled
• + Tempo envelope: warn if user enters time signature numerators/denominators out of range [t=265162]
• + Theme: add theme overlay color, blend mode for muted/unsoloed/inactive or locked media items and tracks
• + Track manager: display track channel count
• + Tracks/media items/razor edits: many internal changes to support future media item lane functionality
• + Video: fix behavior when enabling/disabling audio on all project video sources
• + Windows: add additional uninstall information to system
  

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

[dangguidan]

I found that this latest version is even darker for the color of silent tracks.
In fact, I couldn't see clearly before. Now it's more serious.

[EpicSounds]

Originally Posted by dangguidan

I found that this latest version is even darker for the color of silent tracks.
In fact, I couldn't see clearly before. Now it's more serious.

* + Theme: add theme overlay color, blend mode for muted/unsoloed/inactive or locked media items and tracks

[dangguidan]

I found a custom option. It's actually improved, but now the default 0.5 is too gray.

[Whelfen]

Wow, three long-awaited features have been added! The developers are back from holiday :P.

Thanks!

[alphoc]

Finally, muted tracks are prevented from blacking out, but there should be a separate feature for muted items. It would be better if the color adjustment we made to the track (fine tuning in the theme) does not affect the items. Making the muted item a darker color makes sense, but I don't want the entire track to go dark either.

[svijayrathinam]

Hi Developers,

I found a Bug.

+ Metadata: support WAVEEXT channel layout tag "L R C LFE Ls Rs" instead of "L R C LFE Lsd Rsd" [p=2547580]

When I use this feature and render a file, I expect it to have the channel order embedded in the file so other DAWs like Protools should read it and import files in the correct channel order. But that doesn't seem to work.


Also the channel order required are as follows

LR- Stereo
LRC - 3 Channel SMPTE
LCR - 3 Channel Film
L-C-R-Ls-Rs-Lfe - 5.1 Film
L-R-C-Lfe-Ls-Rs - 5.1 SMPTE
L-C-R-Lss-Rss-Lsr-Rsr-Lfe - 7.1 Film
L-R-C-Lfe-Lss-Rss-Lsr-Rsr - 7.1 SMPTE
L-R-C-Lfe-Lss-Rss-Lsr-Rsr-Lts-Rts - 7.1.2 Atmos SMPTE
L-C-R-Lss-Rss-Lsr-Rsr-Lts-Rts-Lfe - 7.1.2 Atmos Film

The channel configuration in the metadata window is quite confusing.


For Example MPEG 5.1C has 8 channels. Shouldn't that be MPEG 7.1 C then ?

[schwa]

Re channel configurations, there are two metadata formats that support a channel configuration tag, WAVEXT and CAFINFO (core audio).

The WAVEXT tag doesn't support rearranging channel order, only marking channels within a fixed-order list as existing or not existing. The set of WAVEXT tags that REAPER can embed is:

L R
L R Ls Rs
L R C LFE Ls Rs
L R C LFE Ls Rs Lsd Rsd

In other words something like "L C R Ls Rs LFE" cannot be represented as a WAVEXT tag, because the channels are not ordered in a way that the tag supports.

Everything else listed under the channel configuration dropdown is a CAFINFO layout tag. The tags are taken verbatim from the Core Audio definitions.

The confusing part I suppose is that under the common metadata scheme, both WAVEXT and CAFINFO tags are listed, even though wav files will only support the WAVEXT tags. Maybe we should list only the WAVEXT tags in the common scheme list.

I don't know what other DAWs look at these tags when importing, all REAPER can do is embed the tag.

[svijayrathinam]

Originally Posted by schwa

Re channel configurations, there are two metadata formats that support a channel configuration tag, WAVEXT and CAFINFO (core audio).

The WAVEXT tag doesn't support rearranging channel order, only marking channels within a fixed-order list as existing or not existing. The set of WAVEXT tags that REAPER can embed is:

L R
L R Ls Rs
L R C LFE Ls Rs
L R C LFE Ls Rs Lsd Rsd

In other words something like "L C R Ls Rs LFE" cannot be represented as a WAVEXT tag, because the channels are not ordered in a way that the tag supports.

Everything else listed under the channel configuration dropdown is a CAFINFO layout tag. The tags are taken verbatim from the Core Audio definitions.

The confusing part I suppose is that under the common metadata scheme, both WAVEXT and CAFINFO tags are listed, even though wav files will only support the WAVEXT tags. Maybe we should list only the WAVEXT tags in the common scheme list.

I don't know what other DAWs look at these tags when importing, all REAPER can do is embed the tag.

Thank you for the reply. I wonder what is this "Channel Layout Text" under CAFINFO is for ? Maybe that's for Custom channel Order ?

[svijayrathinam]

Originally Posted by schwa

Re channel configurations, there are two metadata formats that support a channel configuration tag, WAVEXT and CAFINFO (core audio).

The WAVEXT tag doesn't support rearranging channel order, only marking channels within a fixed-order list as existing or not existing. The set of WAVEXT tags that REAPER can embed is:

L R
L R Ls Rs
L R C LFE Ls Rs
L R C LFE Ls Rs Lsd Rsd

In other words something like "L C R Ls Rs LFE" cannot be represented as a WAVEXT tag, because the channels are not ordered in a way that the tag supports.

Everything else listed under the channel configuration dropdown is a CAFINFO layout tag. The tags are taken verbatim from the Core Audio definitions.

The confusing part I suppose is that under the common metadata scheme, both WAVEXT and CAFINFO tags are listed, even though wav files will only support the WAVEXT tags. Maybe we should list only the WAVEXT tags in the common scheme list.

I don't know what other DAWs look at these tags when importing, all REAPER can do is embed the tag.

Also Here is a file bounced from Protools.


https://drive.google.com/file/d/1S0e...ew?usp=sharing


Here is the same file exported from Soundminer

https://drive.google.com/file/d/1S3W...ew?usp=sharing

You can see Soundminer is doing something right. Hence Protools seems to read the channel order correctly as it should.


Here is the same file exported from Reaper


https://drive.google.com/file/d/1S5L...ew?usp=sharing

This file doesn't play in protools with the right channel order


I opened it in reaper as well as Soundminer. Both app seems to read the channel Layout as it should. Maybe if reaper tries to embed the channel layout in the same way as sound miner other apps such as protools will read it too ?


Also Checkout The attached screenshot. When I open the reaper exported file and protools exported file in Soundminer, Soundminer shows the channel layout order in the protools exported file but not on the reaper exported file

[schwa]

Are you sure you are setting the channel layout tag when rendering from REAPER? Your MZT_R02_Add_Scene_Football_20th_April_2022_Reaper. wav file does not appear to contain the channel layout tag.

Importing both files into REAPER, these are the media source properties for the Pro Tools rendered file:

Length: 2:42.666
Sample rate: 48000
Channels: 8
Bits/sample: 24 (int)
Total samples: 7,808,000
Blockalign: 24
Datablock start: 1024
Channel configuration: L R C LFE Ls Rs Lsd Rsd
Start offset: 2:11:47.041
Metadata:
    Date: 2022-04-20

and for the REAPER rendered file:

Length: 2:42.666
Sample rate: 48000
Channels: 8
Bits/sample: 24 (int)
Total samples: 7,808,000
Blockalign: 24
Datablock start: 736
Start offset: 2:11:47.083
Cues:
    001 0:00.000 PIC START
Metadata:
    Date: 2022-04-20

Here is the same MZT_R02_Add_Scene_Football_20th_April_2022_Reaper. wav file, rendered back out from REAPER with the channel configuration set to "L R C LFE Ls Rs Lsd Rsd":

Length: 2:43.666
Sample rate: 48000
Channels: 8
Bits/sample: 16 (int)
Total samples: 7,856,000
Blockalign: 16
Datablock start: 760
Channel configuration: L R C LFE Ls Rs Lsd Rsd
Metadata:
    Date: 2022-04-20

Here is the re-rendered file: download.

[svijayrathinam]

Originally Posted by schwa

Here is the same MZT_R02_Add_Scene_Football_20th_April_2022_Reaper. wav file, rendered back out from REAPER with the channel configuration set to "L R C LFE Ls Rs Lsd Rsd":

I just tried with the channel configuration set to "L R C LFE Ls Rs Lsd Rsd, it seems to work in Protools. But the problem is reaper should render out as L R C Lfe Lsd Rsd Ls Rs (Exactly like how you hear me say it in the project). But I am not able to do this. Can you pls support this ?


https://drive.google.com/file/d/1S9O...ew?usp=sharing


Above Link is a test file exported from Reaper.


Below Link is a reaper project for testing.


https://drive.google.com/file/d/1SAT...ew?usp=sharing

In this reaper project I recorded myself saying the channel names. I would like to export this in the channel order Of L C R Lss Rss Lsr Rsr Lfe.

But I am not able to do it. Can you pls provide a solution for this ?

[schwa]

Unfortunately it's not possible to embed L R C Lfe Lsd Rsd Ls Rs as a WAVEXT tag. If you post a file rendered from Pro Tools that has that channel order embedded, we can see if there is some other metadata they are exporting.

[svijayrathinam]

Originally Posted by schwa

Unfortunately it's not possible to embed L R C Lfe Lsd Rsd Ls Rs as a WAVEXT tag. If you post a file rendered from Pro Tools that has that channel order embedded, we can see if there is some other metadata they are exporting.

I just tried exporting a file from protools with the same channel order announcements.

https://drive.google.com/file/d/1SBZ...ew?usp=sharing

Here is a link. When I imported it in reaper the sides and rear are swapped. But If I import the same file in another protools session it seems to play it correctly. Some solution for this will be very useful. Pls

[EpicSounds]

possible bug?
"prevent editing take envelopes when item is locked"

seems to be just for mouse. locked item envelopes can still be changed with actions.

maybe you need to also block this action when locked SWS/BR: Select envelope at mouse cursor

[schwa]

Originally Posted by svijayrathinam

I just tried exporting a file from protools with the same channel order announcements.

https://drive.google.com/file/d/1SBZ...ew?usp=sharing

Here is a link. When I imported it in reaper the sides and rear are swapped. But If I import the same file in another protools session it seems to play it correctly. Some solution for this will be very useful. Pls

Thanks for the link. You linked a PT exported file in post 10 and another one in post 14. Let's call the first file A and the second file B.

A:
channel layout: L R C LFE Ls Rs Lsd Rsd
embedded WAVEEXT tag with value "3F 06 00 00" which means L R C LFE Ls Rs Lsd Rsd
embedded "minf" chunk with value "28 51 27 70 D3 54 D8 01 01 00 00 00 00 00 00 00"

B:
channel layout: L R C LFE Lsd Rsd Ls Rs
embedded WAVEEXT tag with value "3F 06 00 00" which means L R C LFE Ls Rs Lsd Rsd
embedded "minf" chunk with value "38 14 C9 86 E8 54 D8 01 01 00 00 00 00 00 00 00"

Both files contain the same WAVEEXT tag. Apparently PT is using this tag not to mean "this is the channel order" but instead "these are the embedded channels which might be in any order."

That means the channel order is likely encoded in that minf chunk, but as far as I can tell, that is not a known specification. It may be their own proprietary way of encoding the channel order and/or other information.

[bwsd]

+ FX: add per-FX instance and per-FX chain oversampling options (if both chain and instance are set, the higher of the two is used)

Please, add oversampling option when rendering.

[nofish]

Originally Posted by EpicSounds

maybe you need to also block this action when locked SWS/BR: Select envelope at mouse cursor

This just uses API to select/manipulate (take) envelopes.
E.g. this works also on locked items when take env. is visible in v6.54:

item = reaper.GetMediaItem(0,0)
take = reaper.GetTake(item,0)
takeEnv = reaper.GetTakeEnvelope(take, 0)
reaper.SetCursorContext(2, takeEnv)
reaper.SetEnvelopePoint(takeEnv, 0, nil, 0.7)

So I guess actual question is should API be also prevented to modify take env's of locked items? (not sure myself...)

[svijayrathinam]

Originally Posted by schwa

Thanks for the link. You linked a PT exported file in post 10 and another one in post 14. Let's call the first file A and the second file B.

A:
channel layout: L R C LFE Ls Rs Lsd Rsd
embedded WAVEEXT tag with value "3F 06 00 00" which means L R C LFE Ls Rs Lsd Rsd
embedded "minf" chunk with value "28 51 27 70 D3 54 D8 01 01 00 00 00 00 00 00 00"

B:
channel layout: L R C LFE Lsd Rsd Ls Rs
embedded WAVEEXT tag with value "3F 06 00 00" which means L R C LFE Ls Rs Lsd Rsd
embedded "minf" chunk with value "38 14 C9 86 E8 54 D8 01 01 00 00 00 00 00 00 00"

Both files contain the same WAVEEXT tag. Apparently PT is using this tag not to mean "this is the channel order" but instead "these are the embedded channels which might be in any order."

That means the channel order is likely encoded in that minf chunk, but as far as I can tell, that is not a known specification. It may be their own proprietary way of encoding the channel order and/or other information.

Reaper supports User metadata. so does that mean I can write into "minf" chunk ? If so any idea how I can do that ? can you pls help ?

[schwa]

As far as I can tell, 'minf' is not a known specification. It may be Pro Tools proprietary way of encoding the channel order and/or other information. It's 16 bytes of binary data, it's not like it says "here is the channel order."

[matt_t]

[*]+ Theme: add theme overlay color, blend mode for muted/unsoloed/inactive or locked media items and tracks

Is this why splits/crossfades have changed from looking like this



to this?



(I prefer the old way ...)

[ovnis]

"+ Media explorer: add action to delete file with prompting"

Do you know where I can find the action to delete a file from data base, please?

When we delete a file from data base, the window scrolls all alone! It can be an issue when we have to delete lots of file from data base.

[EpicSounds]

Originally Posted by nofish

So I guess actual question is should API be also prevented to modify take env's of locked items? (not sure myself...)

personally, I'm not bothered either way. I only found it when going through the change log and trying everything. I don't think in normal use someone would run into this.
Without sws it works as intended.
On the other hand maybe locked items should be locked and prevent any changes.

[ovnis]

+ Import: add option in Preferences/Media to target the top part of a track to insert new track(s) to receive the media

There is a problematic bug when we use lots of samples like me. That happens to me lots of time!

There are odd behaviors with tracks, midi items or envelopes when we use this new feature and undo.

Here: Midi items move automatically after insert 2 new tracks with the media import and 2 undos.

- Insert 1 new track with the import of 1 file.
- Insert 1 new track with the import of 1 file.
- Undo
- Undo
- Bug!





Edited.

[ovnis]

Here, the track green is automatically duplicated after undo.

- Insert 1 new track with the import of 1 file.
- Insert 1 new track with the import of 1 file.
- Undo
- Undo
- Insert 1 new track with the import of 1 file.
- Insert 1 new track with the import of 1 file.
- Undo
- Bug!

I can give the *.rpp.

[Justin]

Originally Posted by ovnis

Here, the track green is automatically duplicated after undo.

- Insert 1 new track with the import of 1 file.
- Insert 1 new track with the import of 1 file.
- Undo
- Undo
- Insert 1 new track with the import of 1 file.
- Insert 1 new track with the import of 1 file.
- Undo
- Bug!

I can give the *.rpp.

Thanks, fixing!

[playtimer]

Originally Posted by Justin

Thanks, fixing!

I just saw v6.55 is already available on Cockos download page, but no specific changelog in regard to v6.54?

Have we skipped RC versions because of some urgent fix or...?

EDIT: Ah, just saw there was RC1 but still don't know what exactly has been changed in final release.

[vitalker]

Originally Posted by playtimer

I just saw v6.55 is already available on Cockos download page, but no specific changelog in regard to v6.54?

Have we skipped RC versions because of some urgent fix or...?

EDIT: Ah, just saw there was RC1 but still don't know what exactly has been changed in final release.

Check the download page. Everything is there.

[playtimer]

Originally Posted by vitalker

Check the download page. Everything is there.

Yeah, I just was keen to see the changes for v6.55 specifically.

Never mind, just found it all in this thread: https://forum.cockos.com/showthread.php?t=265818

[nvk]

Originally Posted by playtimer

[*]+ Theme: add theme overlay color, blend mode for muted/unsoloed/inactive or locked media items and tracks

Are there settings here that can mirror the old way things used to look? On my theme it defaulted to 0.5 Normal Blend with RGB(48,48,48) and it doesn't look very good. I've become quite used to the existing look so this is a big downgrade for me since I rely on being able to see muted items/tracks in my sessions.

Edit: it seems like changing Normal to Multiply gives the old look. Would be nice to have confirmation