v6.34rc1 - August 7 2021

[Edgemeal]

v6.34rc1 - August 7 2021
+ Automation: improve behavior when using freehand draw and snapping to grid [t=256238]
+ FX: improve default position saving behavior [p=2467019]
+ FX: workaround weird issues with RealGuitar on Win64 [p=2465441]
+ JSFX: fix sticking gfx_getchar('/') etc on Windows [t=236374]
+ LV2: fix incorrect meaningless timestamps when passing control messages from UI to plug-in
+ Master VU: clear loudness meter when clearing peaks, even for background projects
+ Master VU: faster loudness meter response when preference enabled to reset meters on play/seek [p=2467063]
+ Metadata: add "Parts" category
+ Metadata: support embedding ID3:TPOS field
+ Peaks: add action to reset project peaks gain
+ Peaks: rename actions to adjust peaks display zoom (rather than peaks view gain)
+ Peaks: separate peaks display slightly for multiple channels
+ Preferences: fix persistence of IDE editor doubleclick option [t=256058]
+ Razor edit: improve paste behavior when pasting across projects with different tempo maps [t=256099]
+ Razor edits: improve undo behavior when editing FX parameter envelopes [t=256230]
+ ReaScript: add I_LASTY/I_LASTH for GetSetMediaItemTakeInfo
+ Render: add options to disable calculating loudness statistics
+ VST3: fix issue with Reason 11 [t=255482]
+ Wave writing: support writing INFO metadata scheme to RF64 files
+ Wave64: fix corrupt output when writing Auto-Wave64 with metadata
+ Wave64: support reading more metadata schemes
+ Wave64: support writing more metadata schemes

Full changelog / Latest pre-releases

[Paul Eye]

+ Render: add options to disable calculating loudness statistics

This would be really handy to have as an option in the render dialog, so that it could be saved into a render preset. Existing presets could of course use whatever's set in the preferences. Of course I understand that it would require a bit of a redesign of the render dialog.

[jm duchenne]

Hi,

Since there has been a lot of work done in the Render window, perhaps that it is the good time to adress this very old request : could it be possible now to make it show all the channels in use ?
Only the first 40 ones are displayed...

Perhaps to be able to resize the window ?

[Justin]

Originally Posted by jm duchenne

Hi,

Since there has been a lot of work done in the Render window, perhaps that it is the good time to adress this very old request : could it be possible now to make it show all the channels in use ?
Only the first 40 ones are displayed...

Perhaps to be able to resize the window ?

An rcX thread is rarely the right time for that sort of request but maybe in the next cycle?

[Reflected]

Originally Posted by Edgemeal

v6.34rc1 - August 7 2021
+ Automation: improve behavior when using freehand draw and snapping to grid [t=256238]

nice
regarding the automation
can you please check if you can fix this "bug" that cause inaccurate automation: https://forum.cockos.com/showthread.php?t=256073

reaper's automation is staring at 0:42 sec https://youtu.be/-kvWpLTM3Vc

[Goofball Jones]

Did this get sent to the release version prematurely? This thread says 6.34rc1 and was posted today, on the 7th, but you look at the main downloads page on the main page and 6.34 is listed released today, and REAPER 6.33 says there's an update when you open it.

[Edgemeal]

The devs work very fast!

v6.34 - August 7 2021
+ Automation: improve behavior when using freehand draw and snapping to grid [t=256238]
+ FX: improve default window position saving behavior [p=2467019]
+ LV2: fix incorrect event timestamps when passing control messages from UI to plug-in
+ Master VU: clear loudness meter when clearing peaks, even for background projects
+ Master VU: faster loudness meter response when preference enabled to reset meters on play/seek [p=2467063]
+ Metadata: add "Parts" category
+ Metadata: support embedding ID3:TPOS field
+ Peaks: add action to reset project peaks gain
+ Peaks: rename actions to adjust peaks display zoom (rather than peaks view gain)
+ Peaks: separate peaks display slightly for multiple channels
+ Preferences: fix persistence of IDE editor doubleclick option [t=256058]
+ Project files: default to using quotes for all filenames to improve legacy script compatibility [t=256027]
+ Razor edit: improve paste behavior when pasting across projects with different tempo maps [t=256099]
+ Razor edit: improve marker/region behavior when using ripple-all [t=255278]
+ Razor edit: improve undo behavior when editing FX parameter envelopes [t=256230]
+ ReaScript: add I_LASTY/I_LASTH for GetSetMediaItemTakeInfo
+ ReaScript: fix sticking gfx_getchar('/') etc on Windows [t=236374]
+ Render: add options to disable calculating loudness statistics
+ VST3: fix RealGuitar on Win64 [p=2465441]
+ VST3: fix incorrect parameter setting in response to MIDI CCs (fixes Reason 11 issues) [t=255482]
+ Wave writing: fix corrupt output when writing large Wave64 files with metadata
+ Wave writing: improve reading/writing of Wave64 metadata
+ Wave writing: support writing INFO metadata scheme to RF64 files


THANKS FOR THE UPDATES!

[Javier Robledo]

Nice

Thanks

[jm duchenne]

Originally Posted by Justin

An rcX thread is rarely the right time for that sort of request but maybe in the next cycle?

Sorry... and thanks !

[daxliniere]

Originally Posted by Justin

An rcX thread is rarely the right time for that sort of request but maybe in the next cycle?

I've wished for that many times, myself.

[daxliniere]

Something funky going on in 6.34 when Take Lanes are visible:

[schwa]

Originally Posted by daxliniere

Something funky going on in 6.34 when Take Lanes are visible:

I can't reproduce this, can you send your reaper.ini file to support at cockos?

[daxliniere]

Originally Posted by schwa

I can't reproduce this, can you send your reaper.ini file to support at cockos?

Errm... neither can I. Today it's working fine. :shrugs:

[Reflected]

Since 2009
https://forum.cockos.com/project.php?issueid=1326

about the time?

[Phazma]

Originally Posted by Reflected

Since 2009
https://forum.cockos.com/project.php?issueid=1326

about the time?

As long as you keep spamming it probably won’t happen. Just try to act more smart, perhaps bump the FR shortly after a release. The devs do check the FRs and at some point they might think “ah now is the time”. No need to constantly invade the prereleases section with this. It will come when it will come.

[Reflected]

I was thinking that 12 years is somehow a lot these days...

I used to love the FR system, there was a feature request, people love it and vote, once it became elevated, the devs tried their best to implement it, everyone is happy, reaper becomes more powerful...

these days I just think that it's a waste of time according to what happens here.

ps - it was actually one of the main reasons I bought reaper (the top feature requests were actually got attention from the devs)

[EpicSounds]

the devs see every post.
There are only two of them and they're not obligated to respond to every request.

if the request isn't
easy,
critical error effecting many users, or
interesting to them at the moment...

then it might not happen. Can't take it personally.

[daxliniere]

Originally Posted by EpicSounds

the devs see every post.
There are only two of them and they're not obligated to respond to every request.

if the request isn't
easy,
critical error effecting many users, or
interesting to them at the moment...

then it might not happen. Can't take it personally.

Exactly this.

[Phazma]

Originally Posted by Edgemeal

+ Render: add options to disable calculating loudness statistics

The dropdown with the different configurations of displayed statistics is nice but wouldn't it be better to have a popup with checkboxes or something similar to let us enable/disable each possibly visible stat individually?

Every user might have different needs. Someone may want to see both Peak and True Peak but not care about any RMS or Loudness, someone else might want to see all three LUFS-M, LUFS-S and LUFS-I but not care about peak levels, someone may only need TP and LUFS-I and yet someone else cares only about RMS....

Enabling only the stats we need and skipping the others would make the analysis easier to read and perhaps save some space for the file name.

[Reflected]

Originally Posted by EpicSounds

the devs see every post.
There are only two of them and they're not obligated to respond to every request.

if the request isn't
easy,
critical error effecting many users, or
interesting to them at the moment...

then it might not happen. Can't take it personally.

why not hiring another dev to help?
I just see all those great scripters in the forum and I think to myself how great it would be if someone could help with the software itself.

the process is great but too slow these days imho.
there are lots of features that we are missing due to man power... :/

I really don't understand, no offense.. we are in the same boat with the devs and I want it to be the best DAW after all.