I feel that my translated text has been conveyed incorrectly, so I will write it in a different way.
•I am in favor of implementing this feature and would like to use this feature.
•The program itself to downsample is simple, but I am not sure if the REAPER developers would find this feature important. I am not sure that REAPER developers would find this feature important, since I would guess that only 1/1000th of the people would use this feature compared to oversampling (and I am one of those people). And perhaps the place where the user would set up this feature would be added to the current oversampling menu, so we would also have to consider what to do with that menu. (More on this below)
•[
https://www.waves.com/support/tech-s...-rate-support] If the information at this URL is correct, at least 68.5% of Waves plug-ins do not support the 192 kHz sampling rate and behave erratically when used at 192 kHz. Therefore, this feature is also essential for those who want to use 68.58% of plug-ins correctly with Reaper at 192 kHz.
About the downsampling setting menu.
(requires playback stop/start to take effect)
☑ No oversampling
Oversample up to 88.2k/96k
Oversample up to 176.4k/192k
Oversample up to 352.8k/384k
Oversample up to 705.6k/768k
The current menu looks like this, I have selected No oversampling because I am using a 96 kHz REAPER, but it is actually 96 kHz, the same as [Oversample up to 88.2k/96k].
The reason this menu uses [No oversampling,Oversample up to 88.2k/96k,Oversample up to 176.4k/192k] instead of [No oversampling/2x/4x] is that you can decide "at what sample rate to run the plug-in" instead of "at what oversampling The advantage of this is that you can decide what sample rate you want to run the plug-in at, rather than how many times you want to oversample it.
The advantage of this is that you can, for example, decrease or increase the sampling rate of REAPER and never go below your target sample rate.
This has worked fine up to now, but it is a different story when downsampling is implemented.
(requires playback stop/start to take effect)
Downsampling down to 22.05k/24k
Downsampling down to 44.1k/48k
☑ No oversampling
Oversample up to 88.2k/96k
Oversample up to 176.4k/192k
Oversample up to 352.8k/384k
Oversample up to 705.6k/768k
For example, let's say you get a menu like this. Sure, all the numbers seem to line up, but there is a problem with this: a 176.4k/192k REAPER cannot be downsampled to 88.2k/96k.
(requires playback stop/start to take effect)
To 22.05k/24k
To 44.1k/48k
☑ To 88.2k/96k
To 176.4k/192k
To 352.8k/384k
To 705.6k/768k
How would this work? The first problem is that it will not be compatible with most previous projects.
Reaper's rpp files do not store what sample rate the project was worked at unless you set the project sample rate in the Project Settings.
This means that the No oversampling in the old project file should be 88.2k/96k in my case, but REAPER cannot determine what to put in.
(requires playback stop/start to take effect)
1/8x
1/4x
1/2x
☑ 1x
2x
4x
8x
This is also not compatible.
(requires playback stop/start to take effect)
Downsampling down to 22.05k/24k
Downsampling down to 44.1k/48k
Downsampling down to 88.2k/96k
Downsampling down to 176.4k/192k
Downsampling down to 352.8k/384k
☑ No oversampling
Oversample up to 44.1k/48k
Oversample up to 88.2k/96k
Oversample up to 176.4k/192k
Oversample up to 352.8k/384k
Oversample up to 705.6k/768k
(fixed samplerate)
To 22.05k/24k
To 44.1k/48k
To 88.2k/96k
To 176.4k/192k
To 352.8k/384k
To 705.6k/768k
(constant)
1/8x
1/4x
1/2x
2x
4x
8x
There is little that this cannot be done, but the list of items is too large.
(requires playback stop/start to take effect)
Downsampling down to 44.1k/48k
Downsampling down to 88.2k/96k
Downsampling down to 176.4k/192k
Downsampling down to 352.8k/384k
☑ No oversampling
Oversample up to 88.2k/96k
Oversample up to 176.4k/192k
Oversample up to 352.8k/384k
Oversample up to 705.6k/768k
Probably the most realistic menu yet.
Any other good ideas?
Translated with
www.DeepL.com/Translator (free version)