Changes since 5.964 (recalled):
+ MIDI editor: fix synchronization of grid with arrange for "Measure" setting [t=214947]
+ MP3 encoder: add option to prevent joint stereo from being used
+ MP3 encoder: add option to include ReplayGain tag
+ ReaScript: GetSetProjectGrid() can be used to set/get measure mode
- Fix render queue options issue [p=2071567]
+ Arrange: improve vertical scroll behavior on undo, showing/hiding envelopes en masse
+ Audio Units: do not show parameters that are not automatable
+ Audio Units: AU v3 support
+ Audio Units: track parameter IDs across sessions for envelopes/track controls/etc
+ Automation: do not apply envelope trim value to new envelopes when envelopes are bypassed outside of automation items
+ Automation: prevent alt+drag and certain undos from leaving stale envelope panels open [t=192424]
+ Automation: always reset automation-item related options when loading old (pre-automation item) projects
+ Automation: fix undo state point adding for actions that show/hide all envelopes
+ Batch converter: improve updating of output filenames when changing output configuration
+ Comps: include item mute state in addition to active take
+ FX: improve performance of ReaPlugs on x86_64
+ Grid: fix drawing glitches while continuous scrolling
We only support writing the Xing/LAME header tag (LAME actually handles this completely), not the ID3v2 tag.
TL;DR: if you generate a mp3 file that is too loud or too quiet, and include a ReplayGain tag, playing that mp3 file in a player that supports ReplayGain will make it quieter and/or louder than your actual mix.
This option is off by default in REAPER, but on by default using the command-line LAME. As a result, if you use the command line LAME with default options, the results may sound different than REAPER's encoder (with ReplayGain off), even though they're otherwise producing the same results (as discussed here: https://askjf.com/index.php?q=4486s )
v5.965 - December 19 2018
[list]
Changes since 5.964 (recalled):
+ MIDI editor: fix synchronization of grid with arrange for "Measure" setting [t=214947]
So nice...now we only need actions that preserve grid type (dotted/triplet) in arrange to have full MIDI editor/arrange grid sync!
We only support writing the Xing/LAME header tag (LAME actually handles this completely), not the ID3v2 tag.
TL;DR: if you generate a mp3 file that is too loud or too quiet, and include a ReplayGain tag, playing that mp3 file in a player that supports ReplayGain will make it quieter and/or louder than your actual mix.
This option is off by default in REAPER, but on by default using the command-line LAME. As a result, if you use the command line LAME with default options, the results may sound different than REAPER's encoder (with ReplayGain off), even though they're otherwise producing the same results (as discussed here: https://askjf.com/index.php?q=4486s )
Do you know of any MacOS media player that uses Lame's ReplayGain tag to change playback level?
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
Shouldn't I be able to specify a dB value for the ReplayGain tag, so the player knows how much to attenuate or amplify the mp3?
At least that's how I thought ReplayGain works, maybe I'm wrong though.
edit:
Or is the dB value determined automatically when rendering?
Shouldn't I be able to specify a dB value for the ReplayGain tag, so the player knows how much to attenuate or amplify the mp3?
At least that's how I thought ReplayGain works, maybe I'm wrong though.
edit:
Or is the dB value determined automatically when rendering?
Exactly. This is how RG works, to my knowledge, as well. So if we can't write our own dB value... what good is it?
Exactly. This is how RG works, to my knowledge, as well. So if we can't write our own dB value... what good is it?
lame decides when it encodes. Anyway the point of that option is so that you can tell REAPER to render in such a way that produces bit-identical results to lame command line... I wouldn't recommend anybody use the RG option (nor the disable joint stereo option for that matter!).
[list]
Changes since 5.964 (recalled):
+ MIDI editor: fix synchronization of grid with arrange for "Measure" setting
How do you insert let's say a 1/16 note with the grid set to "Measures"? It always inserts whole notes here which makes the "Measures" mode useless (at least when editing via mouse).
How do you insert let's say a 1/16 note with the grid set to "Measures"? It always inserts whole notes here which makes the "Measures" mode useless (at least when editing via mouse).
Use the action that's mapped to the insert key? But yeah that behavior is ugh, thanks, fixing.
Why not do a replaygain scan on completion of render . It’s an integrated LUFS scan with a -18 LUFS reference.
And then you might as well include that as an alternate RMS meter display option. Hehe.
Replaygain tags are hardly useful without a value in them.
That option is just telling LAME to do what it does by default on the command line anyway (which is to do the scan while encoding and write the information to the LAME MP3 header).
Any chance of getting the old behavior back as an option?
I tend to record my L and R rhythm guitar takes on one track, duplicate that item to the next track, set the dupl to take 2, then select both and 'T' through takes of both items for a combination of *different* takes that sound good, ie. (1/5, 2/5) > (2/5, 3/5) > etc..
Now switching takes of multiple items that are set to different takes, syncs them all to the same take, ie. (1/5, 2/5) > (3/5, 3/5) > (4/5, 4/5) > etc.
I really liked the old behavior. I'm willing to downgrade if there's no chance of getting it back as an option. (This is my first post so apologies if I wasn't very clear.)
01:04 - MIDI Learn: optionally only respond to learn while effect configuration is visible
04:32 - MIDI Editor: select-all only selects notes within the editable part of a trimmed media item
05:52 - MP3 decoder: show source file channel mode in source properties
06:36 - MP3 encoder: add option to prevent joint stereo from being used - add option to include ReplayGain tag
08:14 - ReaScript: IDE add duplicate selected text or current line via Ctrl+D/Cmd+D
08:57 - Render: add $bitdepth wildcard
09:22 - render wildcards can have character substitution
10:57 - support up to 10,000 alternate filenames
11:17 - Video: add Gaussian Blur
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
With this update I have noticed that in the MIDI Devices list now I can see every single device that I have ever connected to my computer (I just finished audio school, so I used a bunch of different school-owned controllers in the last year...), that "feature" does not seem very useful and reminds me a certain Avid product.
It is not a big deal, I just had to select the devices that I don't actually use and choose "forget device", but I really don't see the point in adding this "feature" to Reaper.
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
It wasn`t added as a Reaper feature - MS screwed around a bit as usual with opne of theier updates & Reaper inherited this as an "undocumented feature". At least you figured out how to deal with it without having to search this forum for all the many threads by other people who DIDNT find the solution for themselves!
It wasn`t added as a Reaper feature - MS screwed around a bit as usual with opne of theier updates & Reaper inherited this as an "undocumented feature". At least you figured out how to deal with it without having to search this forum for all the many threads by other people who DIDNT find the solution for themselves!
this would be accurate if it wasn't total bollocks. It was a change to reaper in version 5.95.
Showing all MIDI devices doesn't happen on just windows, it's the same on Macs. There are several good reasons for this and I'm not going to list them because I already addressed it in a video a couple months ago.
Save those to Your AppData/REAPER/Scripts directory, then add them in the actions list, you can map T/shift+T to them to have the old behavior
well.. I expected this behavior to be the one when items are Grouped. For non grouped items the NEXT TAKE action should just go to the next active take on each item...
+ Render: render wildcards can have character substitions (see built-in help)
Great flexibility for render naming!
But my monitor is too narrow (1366x768) and the wildcards are too many to see all of them at once, so I want them to be categorized into some submenus...
I cant wait to see Reaper 6 and buy it. I desperately want to see separate vsti browser for creating music purposes. It's very hard sometimes to switch between vsti and vst when i lookin for specific vst for vsti track.
I cant wait to see Reaper 6 and buy it. I desperately want to see separate vsti browser for creating music purposes. It's very hard sometimes to switch between vsti and vst when i lookin for specific vst for vsti track.