ErikG wrote: Wed Mar 26, 2025 9:42 am Maybe switch to event list view and manually delete the extra notes? Should be apparent which are the bad ones based on velocity or duration anomalies.

That's probably how I'd approach it but there probably is a speedier function that I'm unaware of.

You're my hero. From event view I found one of the offending hits, then Filter > Set Filter from Selection, de-select everything but note and length and bam, got rid of all the garbage.

I probably could've filtered before and the key was 'Set filter from selection' because the filter length dropdown doesn't give you options small enough, but your advice got me there. Thank you!

If you don't think you can do it in Reaper, you probably can.






Except for pre-mute sends, because Cockos refuses to fix that for some reason. My only gripe with Reaper.

Nate Dort wrote: Wed Apr 02, 2025 8:08 pm If you don't think you can do it in Reaper, you probably can.






Except for pre-mute sends, because Cockos refuses to fix that for some reason. My only gripe with Reaper.

it's spectacularly annoying. My way of dealing with it has been to create an extra track and route the source to it, Unassign the source track from the master, and use the new track as a sub master so all the sends from the source track stay active if I mute the new sub group master. I sometimes just hide the original source track so I still only see one track for that source... but not always. I thought foldering the track would work, but no. If you mute a folder master, it actually mutes the sub tracks as well. it dumb. It should just be in the pull down menu for your aux route.

EDIT
Holy shit Update: I looked because I figured this cannot still be a problem and it is fixed. In settings, under Audio:Mute/Solo: there is a box called "prefader sends survive muting" and it fixes the issue. Sucks that it is global and not on a per send level, but it is there. Half-thanks Reaper.

Kniferide wrote: Thu Apr 03, 2025 1:01 pm EDIT
Holy shit Update:

YEAH WE'RE COOKING NOW

Kniferide wrote: Thu Apr 03, 2025 1:01 pm EDIT
Holy shit Update: I looked because I figured this cannot still be a problem and it is fixed. In settings, under Audio:Mute/Solo: there is a box called "prefader sends survive muting" and it fixes the issue. Sucks that it is global and not on a per send level, but it is there. Half-thanks Reaper.

Thanks for pointing this out. I'm sad to report that regardless of this setting, folder tracks with pre-fader sends are still pre-mute so it doesn't help me with most of my normal workflow, but it's still nice to know.

ipitcher wrote: Sat Apr 05, 2025 11:17 am

Kniferide wrote: Thu Apr 03, 2025 1:01 pm EDIT
Holy shit Update: I looked because I figured this cannot still be a problem and it is fixed. In settings, under Audio:Mute/Solo: there is a box called "prefader sends survive muting" and it fixes the issue. Sucks that it is global and not on a per send level, but it is there. Half-thanks Reaper.

Thanks for pointing this out. I'm sad to report that regardless of this setting, folder tracks with pre-fader sends are still pre-mute so it doesn't help me with most of my normal workflow, but it's still nice to know.

If I have a track feeding another track via a prefader post aux send with this setting on, it survives the muting of the track sending the signal, and the folder track being muted as well. Are you sure your send is pre fader? Any post fader send will mute, as I would expect it to.

Friend showed me an interesting thing the other day.

Open a fresh Reaper project, and drag any Reaper Project file (.RPP) into the time line, a prompt will open and ask if you want to insert as Media Item. You do. You will see the project you dragged in open in another project tab and start rendering. When it is done it will close and you will have a render of your project in the new project. Now, the cool part... double click on that audio file and it will open the full session of that audio in another tab, you can make changes to the mix and when you SAVE the session, it will auto-magically start rendering it out again and when you go back the New project the render will reflect your changes. Putting in markers named =START and =END will determine the render area.

This is a coo thing if you are doing Masters like me where I load all the tracks in one session and strap Izotope on every track, and on the Master. Now if you need to jump in and fix one little thing in the project you can easily.

Maybe not usefull at all but it is wild that Reaper can do this.

I just accidently opened a project that I did in the newest version of reaper on my laptop, forgetting I hadn't updated my PC.

A popup saying there were some settings from a newer version that weren't understood, and then proceeded to open perfectly. From a software design point of view this makes sense - if some things were added, just ignore those things and open everything else up.

Except that in 41 years of my life I've never had a 'tool' software ever, ever allow you to do that. Amazing. Reaper for president.