Hej Justin,
This is something I discovered while working with "Skaven"
on some content this afternoon.
I'd been working with a 192k file of me eating spaghetti, pitched down heavily for some monster noises. It was pitched by just stretching it out on the timeline. I keep adjusting different bits to find an interesting pitch for that section of the recording. I would plan to affect the timing of transients (with timestretch) after I've chosen my edits based on modified frequency content I like.
But the recording had some (inaudible) noise from some nearby electronics that became audible after pitching down.
I'm about 6 weeks new to Reaper, with only about 10 working days logged using it on a project (migrating from a mix of Cubase/Vegas/Abelton). So there's a bunch of reaper-specific tricks and workflows that I'm learning from the other Reaper users here.
First I went old school and tried to notch out the noise (image 05.png). But every time I affected the pitch with stretch, I'd have to re-do the notch.
Then Skaven pointed out that I might be able to add a spectral edit that would follow the frequency range I wanted to remove, up and down, as I stretched and edited the clip.
That's when we found a few problems.
1) First was that the spectrograph showed the frequency domain of the source clip, not that of the stretched clip, as I'd hoped/expected. You can see that as the noise became audible through the down-shift, it'd be helpful to have it visible at the right relative range in the spectrograph (images 01 and 02). I added image 04, to show that as the clip stretches and the frequency content changes, the spectrograph image - and the spectral edit canvas - remains the same.
2) Then, after I'd set the project settings to 192, setup the spectral edits, and reverted the project to 48 (one of Skaven's suggested workarounds), the edits behaved weirdly. They moved to the top of the clip, but were offset oddly, and they stopped removing the frequencies I'd set them on (the noise audibly returned) (images 02 and 03).
Overall, the spectral edit feature-set is amazing. This use-case(s) contains a few things that I guess weren't originally in the requirements capture. Addressing most of the above would probably count as 2nd-pass feature work and useability improvements, rather than bugs. The strange behaviour in (2) might be an issue.
(I'm also new as to how else to communicate feature requests to you)
For now, I can cope by consolidating/freezing/rendering my pitched clips and then attacking the noise, clip by clip. But I can imagine a better workflow.
The process of working with high frequency recordings to find weird sounds for sound design is becoming more common, as the equipement (mics and digital hardware) become more affordable. I'm not really expecting to ever look back now I've switched to Reaper, so it'd be nice to see the above addressed at some point on the mid-horizon.
Hope this was useful info.