penningtron wrote: Thu Mar 20, 2025 12:29 pm I've had that happen a couple of times, and I think it has to do with mic/device permissions settings. You're on a Mac, right? If you've done any system updates lately it's possible the permissions box was unchecked. System Preferences > Security IIRC.

Another possibility is some interfaces require an app to be turned on, even if it's just in the background. My Audient interface requires that I turn the ID app on even if I don't use that specific GUI.

kerble wrote: Thu Mar 20, 2025 12:34 pm THANK YOU

penningtron wrote: Thu Mar 20, 2025 12:41 pm

kerble wrote: Thu Mar 20, 2025 12:34 pm THANK YOU

No problem! I've been there twice: first in maybe '18 when Mac introduced that stupid "security" feature, and again maybe 2 years ago when I did a major system update (Catalina to Monterrey or something like that). It's maddening every time cuz you can see and hear things working yet nothing comes through.

(it also seems like the type of thing Reaper should be able to detect and shoot you a warning prompt for but whatever)

kerble wrote: Thu Mar 20, 2025 2:52 pm yeah, using the search terms for "reaper not recording with sound but no monitor meters" was a long long journey down into useless information.
"make sure you've armed the track". Thanks, guy. I did that. The dumb google AI prompts at the top felt insulting after a while.

TylerDeadPine wrote: Wed Mar 26, 2025 12:23 am I made drums for a few tracks by playing them on midi pads, only now to realize for some reason it put double hits on each of the pads - one little knife edge hit and then the 'full' looking midi note. So then later when I added in cymbals, they're totally different volumes because they aren't doubled up.
because it was played 'live' I reaaally don't want/can't redo it.

Reaper looks like it has some functions to remove overlapping notes, but nothing seems to actually remove the offending notes. I'm resolving to making some coffee and just manually purging it all, but it also sucks because I can't window select, as it selects both notes, but I feel like there has to be a better way?

This shows the ghost note after I moved the overlapping 'right' midi hit down a note to discover it (they're on everything but cymbals, or fills I brought in as pieces )

Frankie99 wrote: Wed Mar 26, 2025 11:19 am

TylerDeadPine wrote: Wed Mar 26, 2025 12:23 am I made drums for a few tracks by playing them on midi pads, only now to realize for some reason it put double hits on each of the pads - one little knife edge hit and then the 'full' looking midi note. So then later when I added in cymbals, they're totally different volumes because they aren't doubled up.
because it was played 'live' I reaaally don't want/can't redo it.

Reaper looks like it has some functions to remove overlapping notes, but nothing seems to actually remove the offending notes. I'm resolving to making some coffee and just manually purging it all, but it also sucks because I can't window select, as it selects both notes, but I feel like there has to be a better way?

This shows the ghost note after I moved the overlapping 'right' midi hit down a note to discover it (they're on everything but cymbals, or fills I brought in as pieces )

It's a long shot, but my midi controller keyboard had a hard button on it that I accidentally clicked once, and it made any "long" depression on the key into multiple hits, whereas before they would just be high velocity normal single hits. It was labeled either "arp" or "fixed chord".

Honestly I just started mashing buttons till I fixed it and I know it was one of those 2 buttons lol.

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.