Old 12-20-2022, 05:16 PM   #1
STOP
Human being with feelings
 
STOP's Avatar
 
Join Date: Jul 2013
Location: Québec
Posts: 512
Default v6.72+dev1220 - December 20 2022

v6.72+dev1220 - December 20 2022
  • * Includes feature branch: selected media item appearance changes
  • * Includes feature branch: media item fixed lanes
  • + API: add midi editor play cursor preview override API for playtime
  • + Audio devices: fix input/output audio channel aliasing when only removing some outputs [t=273424]
  • + Grouping: improve some corner case behaviors when track media/razor edit groups are used in addition to automatically grouping selected tracks
  • + Media explorer: avoid freeze/redraw when accidentally doing a tiny file drag from file list
  • + Media explorer: avoid temporary freeze when accidentally doing a tiny drag from playback preview area
  • + Media items: improve display performance when media items have many take markers outside the visible bounds of the item [t=273948]
  • + Peak building: fix corner case where peaks would fail to build for some media [t=273919]
  • + Razor edit: fix deleting areas on master track envelopes with ripple-all-tracks enabled [p=2625216]
  • + Razor edits: fix grouped preview on FIPM and fixed-lane tracks
  • + Razor edits: fix grouped preview on FIPM tracks
  • + ReaScript: add MEDIA_EDIT_LEAD/MEDIA_EDIT_FOLLOW to documentation for GetSetTrackGroupMembership, etc
  • + Render: improve speed of writing outfile.render_stats.html when rendering many files at once [t=273917]
  • # Grouping: prevent weirdness when grouping razor edits on envelope lanes of fixed lane tracks [p=2625549]
  • # IDEs/ReaScript: improve/fix win32 international keyboard issues
  • # Media items: clear grouped item selection preview when disabling item grouping via action
  • # Media items: make preference to display grouped selection preview enabled by default
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
STOP is online now   Reply With Quote
Old 12-21-2022, 12:42 AM   #2
PitchSlap
Human being with feelings
 
PitchSlap's Avatar
 
Join Date: Jan 2008
Location: Vancouver, BC
Posts: 3,815
Default

I've noticed render window loudness stats can be way off.
They are correct when the render is finished, but don't seem to always update during (noticed with multiple projects.)
Also maybe it's resolution dependent, but there's more than enough space in the column to write "TruePeak"
__________________
FRs: v5 Media Explorer Requests, Global Quantization, Session View
Win10 Pro 64-bit, Reaper 6(x64), AMD 3950x, Aorus X570 Master, 64GB DDR4 3600, PowerColor Red Devil 5700XT, EVO 970 2TB, 10TB HD, Define R6
PitchSlap is offline   Reply With Quote
Old 12-21-2022, 04:11 AM   #3
Zeno
Human being with feelings
 
Zeno's Avatar
 
Join Date: Sep 2018
Location: HH
Posts: 925
Default



IMO there is no benefit to displaying the current values numerically, since no one can read them that quickly unless the time constants of the dynamics processor are set quite high. Currently, it just adds a lot of clutter when the GR values are running up and down like crazy all over the mixer.

My suggestion:
For the numeric GR value I would prefer a max hold. Preferably on the left side of the meter. As the scale of the meter adjusts to an increasing gain reduction, this provides a clear view of the meter bar.
It shows the max value, holds it for - let's say 3 or 5 sec - and then releases it.

If the meter bar additionally draws a small vertical line as an indicator for the max hold position, we have a ton of information.


  1. We know the numeric max value.
  2. We have an indicator of where the max value is on the meter bar.
  3. We have a red bar as an indicator of where the current value is on the meter.
  4. From these 3 pieces of information, it is possible to derive quite precisely which current value the red meter bar displays in relation to the max value.


...

Last edited by Zeno; 12-21-2022 at 03:51 PM.
Zeno is online now   Reply With Quote
Old 12-21-2022, 04:47 AM   #4
Embass
Human being with feelings
 
Embass's Avatar
 
Join Date: Jan 2014
Posts: 923
Default

Embass is offline   Reply With Quote
Old 12-21-2022, 06:35 AM   #5
Embass
Human being with feelings
 
Embass's Avatar
 
Join Date: Jan 2014
Posts: 923
Default

Embass is offline   Reply With Quote
Old 12-21-2022, 11:18 AM   #6
alphoc
Human being with feelings
 
Join Date: Apr 2019
Posts: 399
Default

Quote:
Originally Posted by Embass View Post
Off topic, but what exactly is this? Which feature? Numbers 1 and 2 on TCP, two items on the same track..is it a new feature?
alphoc is offline   Reply With Quote
Old 12-21-2022, 12:55 PM   #7
vitalker
Human being with feelings
 
vitalker's Avatar
 
Join Date: Dec 2012
Posts: 13,338
Default

Quote:
Originally Posted by alphoc View Post
Off topic, but what exactly is this? Which feature? Numbers 1 and 2 on TCP, two items on the same track..is it a new feature?
Read purple lines in the first post.
vitalker is online now   Reply With Quote
Old 12-21-2022, 07:22 PM   #8
Mercado_Negro
Moderator
 
Mercado_Negro's Avatar
 
Join Date: Aug 2007
Location: Caracas, Venezuela
Posts: 8,701
Default

Quote:
Originally Posted by Zeno View Post


IMO there is no benefit to displaying the current values numerically, since no one can read them that quickly unless the time constants of the dynamics processor are set quite high. Currently, it just adds a lot of clutter when the GR values are running up and down like crazy all over the mixer.

My suggestion:
For the numeric GR value I would prefer a max hold. Preferably on the left side of the meter. As the scale of the meter adjusts to an increasing gain reduction, this provides a clear view of the meter bar.
It shows the max value, holds it for - let's say 3 or 5 sec - and then releases it.

If the meter bar additionally draws a small vertical line as an indicator for the max hold position, we have a ton of information.


  1. We know the numeric max value.
  2. We have an indicator of where the max value is on the meter bar.
  3. We have a red bar as an indicator of where the current value is on the meter.
  4. From these 3 pieces of information, it is possible to derive quite precisely which current value the red meter bar displays in relation to the max value.


...
Wholeheartedly agree.
__________________
Pressure is what turns coal into diamonds - Michael a.k.a. Runaway
Mercado_Negro is offline   Reply With Quote
Old 12-21-2022, 09:06 PM   #9
JRTaylorMusic
Human being with feelings
 
Join Date: Feb 2019
Location: Austin, TX
Posts: 415
Default

Would be nice though if it had the same peak hold options as the regular meters.
JRTaylorMusic is offline   Reply With Quote
Old 12-22-2022, 12:58 AM   #10
ferropop
Human being with feelings
 
ferropop's Avatar
 
Join Date: Jan 2016
Location: Los Angeles, CA
Posts: 3,199
Default

Even some steps indicating 3dB increments of GR would be easy enough to read, in lieu of displaying the number. Like a 1-pixel vertical tint every 3dB...
__________________
FERRO
Songs I've Written/Produced : https://t.ly/OtOM-
Instagram : http://www.instagram.com/ferropop
ferropop is online now   Reply With Quote
Old 12-21-2022, 06:39 AM   #11
thommazk
Human being with feelings
 
thommazk's Avatar
 
Join Date: Jun 2020
Location: Brazil
Posts: 205
Default

Quote:
  • + Media items: improve display performance when media items have many take markers outside the visible bounds of the item [t=273948]
It's fixed and it's great now, thanks a lot! ♥
thommazk is online now   Reply With Quote
Old 12-21-2022, 07:59 AM   #12
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 11,828
Default

Gain reduction is a general indicator. Peak is the only number I'd ever be interested in. The rest is covered by the actual meter, which only needs to rise quickly. Sort of like an RTW gas peak meter.

It is extremely rare now that I ever look at the numbers.
__________________
Using Latch Preview (Video) - Faderport 16 setup for CSI 1.1 , CSI 3.10
Website
"My ego comes pre-shrunk" - Randy Thom

Last edited by airon; 12-21-2022 at 08:43 AM.
airon is offline   Reply With Quote
Old 12-21-2022, 10:25 AM   #13
bolgwrad
Human being with feelings
 
bolgwrad's Avatar
 
Join Date: Mar 2011
Location: On my arse in Glasgow, Scotland
Posts: 2,106
Default

Is it intended that (since the column view mod) the render stats on-the-fly display is no longer available, or is there a setting?
[edit]
__________________
www.sachetsofrelish.com

Last edited by bolgwrad; 12-21-2022 at 10:32 AM.
bolgwrad is offline   Reply With Quote
Old 12-21-2022, 10:34 AM   #14
Tale
Human being with feelings
 
Tale's Avatar
 
Join Date: Jul 2008
Location: The Netherlands
Posts: 3,670
Default

Quote:
# IDEs/ReaScript: improve/fix win32 international keyboard issues
Yeah, now I can type double quotes, accented letters, etc. again. Thanks!
Tale is offline   Reply With Quote
Old 12-21-2022, 12:05 PM   #15
stillshaded
Human being with feelings
 
Join Date: Oct 2018
Posts: 204
Default

Quote:
Originally Posted by STOP View Post
[*]+ API: add midi editor play cursor preview override API for playtime
Interesting. How does this work exactly? Is there anyway this could be used to create a midi scrub action that doesn’t move the play cursor? Probably not, but just checking. I’ve been looking for a way to do this since I started using reaper, which is the way midi scrub works in fl studio.
stillshaded is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 08:24 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.