Don't try to delay throw without this! REAPER DAW Tip
HTML-код
- Опубликовано: 15 июл 2024
- There's a mixing technique called Delay Throws where you automate the send level to add echos to certain words. But there's a preference in REAPER that might make that impossible.
Thanks for watching!
Subscribe and hit that LIKE button!
Visit The REAPER Blog for many more tips, tricks and tutorials.
reaperblog.net
/ reaperblog
/ thereaperblog
/ reaperblogcommunity
/ thereaperblog 
Хобби
Oh boy - you just came to my rescue! Thank you so much!
OMG! I switch from Samplitude to Reaper. That problem makes me almost angry and never figured out how to do that like on "analog" console - send and it appears on FX machine and add up to stereo buss...
You are soooo great man, thank you a lot for that video !
From now on, Reaper in my opinion is the best DAW in the world !
Nice! I always had the pref to Always, but didn't know it's doing this as well. Trim envelope just help do last min balancing with tons of automation in as well :)
THIS. Is extremely helpful to know. Thank you.
Nice fix. I didn't have the same problem, but this helps my work flow. Thank you!
i just use the send mute automation and un mute the send when i want to throw the delay. gives me the benefit of being able to globally set the level afterward. reaper and pro tools are the only daws i'm aware of that allow this.
That was really useful. Thanks so much! I have been having that problen myself
Very cool. Great information, thank you.
Nice. Good find.
Nice tip.
I don't generally use automation for that kinda thing though, I just make a wet-only track and copy out items I want delayed. Easier and no having to draw or keyboard jack my way to make env curves. Blind musician, so any time I can avoid autos I do. lol. Good vid anyway.
Oh. My. God. I've been annoyed by this "bug" for over a year now! Thank you so much John! I always thought it was an issue where the automation was written to the read envelope, but somehow the trim level gets corruped or something and setting trim level to 0 fixes it.
In opposite view, you can find a good level for track, and then add little changes or fade in/out with automation. In this case default "never" will be better. Because the scale around 0 gives you more accurace.
I always consiered this feature is advantage of reaper.
Of cource, you can add automation and turn it down to -inf at once.
Thanks you!!!!
There was a problem in FL Studio where automated sends would bug when when they had latecy involved. If the initial volume was at 0 and you automated it, FL didn't understand that it only had to periodically compensate latency of the send, so you had to input 0,00001 instead of 0. Producing music is hard at times.
Thanks. For some reason mine was set like that although I don't remember using it before. Who knows in reaper, the many options are like a hell dimension. 😈
I checked and found out that in my case, the default setting was already "Always" and not "Never". I wonder if this was changed between some Reaper versions and you may have done export/import with your settings when upgrading, overriding the new defaults with the old? Just guessing.
Mine was set to Always. Thankfully, cause I would have thrown the computer out the window before I figured out what I needed to set in the preferences, if it was set to Never.
Interesting! In comments, it seems experience varies with default settings. I know for sure I didn't alter my settings and it was Always with default volume +0.00db.
Finally i found this
Interesting. What is the default setting? I have never seen this issue until our mutual friend on the FB group showed it. After watching your video, i realize it is because my setting is already set to "Always," I have no recollection of ever changing this setting, so my assumption is that it is the default?
Might be a good default.
If you have sends set to default to 0 dB, then this doesn't matter? Or does it?
Like @reaperblog stated, you would have to automate where you would not want the delay send in this case.
That parameter defaults to Always on a new installation. You probably changed it loong time ago
Questions..... are existing/old projects envelopes affected when you change the setting?
existing envelopes are not. Only new ones. as far as I can tell.
I normally just automate the fader for the delay send as opposed to automating the send level itself. Is there anything different happening when doing it that way?
fader is after the delay, so if you want to control the level going in for saturation effects you won't have control over that.
Странно. Я очень давно под себя рипер настроил и именно с этой проблемой не сталкивался.
UPD. Ну да логично. У меня настройка выставлена в нужное положение Always
how do you add effects like this ?
Interested in that too 🔥🔥🔥
right-click fx button for quick-add list
@@TheREAPERBlog Is it possible to get same Quick Add FX menu in MCP?
yeah its there if you right-click an insert slot or the fx button
Hmm, my Reaper installs are all already set to Always.
same config since reaper 4 here. For track volume envelopes I don't think it matters. Sends is completely broken.
@@TheREAPERBlog I think the config on my main rig goes back to early v3.x. I am always finding settings that are different than the current default. But it's also set to Always on my day-job computer, installed in the late v5.xx... 🤷🏼♂️
@@StephenTack Mine was always default also, never had any problems, was wondering why he was doing a video, though i do really appreciate his content
even if it doesn't make a different for you specifically, now you know about the default send level, and what the 'apply trim to envelopes' preference does. pros and cons of either way
@@TheREAPERBlog indeed, thank you.
I'm mostly curious how/when the fragmentation in the default of this setting occurred. 🤔
There should be a historical Reaper wiki...but alas, your What's New in Reaper X.XX videos are the closest we have.
Man you just made a 7 min video about something that would take me two seconds with the default settings.
Wanna know how I do it?
Send, use pre fx volume automation. Done.
OK a different workaround. Think about the limitations of automation with that envelope.
@@TheREAPERBlog I was just being the littlest bit of a smart ass lol.
About the same effect as controlling the send honestly.
I get that it's the same function for a single send track so it would be useful on a fx send that has multiple things going to it. I will probably use this trick for that situation, otherwise prevolume would function the same.
@@TheRantingsofaMadman
big downside of that way for me is not being able to assign it to a controller and perform the mix move.