I guess the limit’s there for a reason, but you can use the Custom waveform LFO to circumvent this… especially making use of Ext. Editor function it should be easy, e.g.
Add LFO, set Type to Custom, press Ext. Editor
Ctrl+A to select all
right click, process, Create Sine Curve
in the box below where the resolution says 64, make that 1024
press Ctrl+C, Ctrl+P for continuous paste
voila you have much higher frequency
for square wave this is even more usable, because you need only 2 points to have square wave… (set the interpol mode to points)
Agreed with cas - especially since there’s several envelope modes available for ex. if you want to make a sinewave, squarewave etc. out of just 2 envelope “units” (ticks?) per oscillation. And the envelope’s maximum size is 1024 units, which is pretty huge for this purpose.
Still, it would be quicker and easier (and more intuitive) if the LFO’s could directly use higher frequencies.
Probably not so very easy to do. I think I remember certain parameters will only get updated at tick rate, not at audio-/samplerate. Now calc yourself how fast different bpm/lbp/tpl settings will “sample”, and judge if that rate were suitable for high frequency modulation.
Effects can be automated at rate much higher than TPL, you can zoom in as far as you can in the automation editor to see the resolution (it is LPB and BPM dependant of course, but is absolutely not low too).
However, meta devices only have a TPL resolution. Therefore to try out how an HFO would work with any parameter, take an LFO, sets it’s frequency to 1, bind it to lets say, pitch, nowincrease the LPB, TPL, BPM.
The issue is that quite a few effects aren’t designed to be HFOed so you’ll, at least, get serious aliasing, and I don’t think you want that as you want to do FM, more over notice the processing power required to automate that.