Newbie here.
I have been checking out the free versions of MOscillator and MRingmodulator, build 9.03.
When using the on-screen piano keyboard to input a note, for example C3, the result is to 4 decimal places: 261.6256 Hz. But when I manually enter 263.54 Hz, the value defaults to 264 Hz with no fine resolution. Manual entry allows one decimal place up to 99.9 Hz and none from 100 Hz upwards.
The tuning control (default 440 Hz) also only inputs in whole Hz. Agreed historical tunings alone are more detailed than that.
This may sound picky, but I work with very finely tuned oscillators (eg those in Adobe Audition or in MaxMSP) and the resultant beat patterns.
Am I being stupid here or is the frequency resolution really so poor? Or does it improve with the paid upgrade?
The oscillators are absolutely fantastic, but as it stands this issue is a deal-breaker.
I'm running Win7 Pro 64-bit OS, bit using the 32-bit VST of both plugins, in the latest Reaper build.
MOscillator and MRingmodulator frequency resolution
-
- KVRer
- 4 posts since 17 Jul, 2011
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
No no, it represents all the accuracy you specify (the saving is limited to 8 digits after the period or something like that), it just doesn't show it, because it's irrelevant information in most cases. Just try putting MOscillator, set frequency to 111.111111 and use MTuner after it to detect the frequency - it will say 111.1. If you then set freq to 111, MTuner will say 111.0.
-
- KVRer
- Topic Starter
- 4 posts since 17 Jul, 2011
Thanks, very useful to know.
In that case can I make a feature request? (if this is the right place to do that.)
I would usually work with several instances of the plugin visible, one per track on the DAW, and if I want to set up different oscillator waveforms but detune them fractionally, I need to see the frequency accurately. For example, if I set 2 oscs at 120.23 Hz and 120.33 Hz respectively, I need to see that 0.1hz difference to know that the oscillators will beat every 10 seconds. So that if I change the 2nd osc to 120.43 Hz they will beat every 5 seconds instead.
Would it be a lot of additional coding to display frequency more precisely (at least say to 2 or 3 decimal places) in a future release? For both MOscillator and MRingmodulator?
I am a composer working with quite precisely pulsed ambient sound, that's why it's relevant information to me and perhaps to other sound designers. Thanks.
In that case can I make a feature request? (if this is the right place to do that.)
I would usually work with several instances of the plugin visible, one per track on the DAW, and if I want to set up different oscillator waveforms but detune them fractionally, I need to see the frequency accurately. For example, if I set 2 oscs at 120.23 Hz and 120.33 Hz respectively, I need to see that 0.1hz difference to know that the oscillators will beat every 10 seconds. So that if I change the 2nd osc to 120.43 Hz they will beat every 5 seconds instead.
Would it be a lot of additional coding to display frequency more precisely (at least say to 2 or 3 decimal places) in a future release? For both MOscillator and MRingmodulator?
I am a composer working with quite precisely pulsed ambient sound, that's why it's relevant information to me and perhaps to other sound designers. Thanks.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Well, it's not a technical problem, but more like visual thing - it needs to be short enough so that it is easy to look at. You probably noticed that the lower the frequency is, the more digits after period it shows. I'll check about adding one more digit below 1kHz though, we'll see 
.
.