Complex LFO
  • Very useful cross modulating LFO! Also includes its stripped down little brother.


    image

    Inputs:

    Left - g
    reset both LFOs

    Middle - g
    reset LFOA (left)

    Right - g
    reset LFOB (right)


    Outputs:

    Top right - m
    Complex LFO output

    Bottom Left - m/-
    LFOA output and inverse

    Bottom Right - m/-
    LFOB output and inverse


    Controls LFOA&B:

    Hz - LFO speed. Speed ranged by Oct and Range controls.
    wave - Morphs between sine (0) -> triangle (.33) -> square (.66) -> saw (1)
    oct - sets the base oscillator octave, -22 to 6
    range - sets the maximum octave swing of Hz control 1 to 4 octaves
    -/+ - output DC attenuverter
    + - offset

    Controls Shared:

    F/AM - fades between frequency and amplitude cross modulation from LFOB to LFOA
    beam - adjusts the draw rate of the oscilloscopes from 10ms to 30s - faster settings will register quick changes more accurately while slower settings will display the overall range of the LFO. Finding a good medium can help you adjust the range of the LFO and see how they are affecting one another.
    -/+ - (bottom of module) Complex LFO DC attenuverter


    Display:
    3x oscilloscopes for LFOA&B (left/right) and Complex LFO (center).
    Screen Shot 2017-05-12 at 3.05.52 PM.png
    521 x 586 - 109K
    Complex LFO.audulus
    362K
  • @biminiroad - thanks for sharing!
  • Why is audio panning done with sine and cosine functions rather than a crossfade?
  • @RobertSyrett - test the difference and you'll see that the volume appears to dip when the audio is panned center on a linear pan. The audio panner keeps it level across the stereo field.
  • I wonder how people figured that out :)
  • biminiroad - may be a dumb question, but when MIDI out is implemented in a new (hopefully, soon) update, will it be possible to output these to a CC (even at audio frequency)?
  • USB Midi is pretty high bandwidth, but it's not audio rate, I'm certain Taylor will have to make some sort of decision about what data rate to support. It may be related to the talk of separating control signals vs audio signals within Audulus. MIDI 1.0 spec winds up working out to being pretty much exactly 1 midi message per millisecond (1000hz). That might be a fine defacto standard, and could maintain compatibility with usb to midi adapters. Although if you have lots of 1000hz outputs going to a single usb to midi adapter, you'll see spooling happening in the usb drivers and your messages will get delayed. But it wouldn't be a problem sending midi from program to program. It's an interesting problem, how to open up the possibilities without crippling midi output rates or making midi hardware interfacing a constant nightmare.
  • Probably the simplest solution would be to have each midi node sample rate adjustable. So some of them could be high bandwidth and some could be low bandwidth. If you make the default 100hz, then you could have ten of them running out to a hardware adapter before you start to see any buffering issues.
  • CV / audio output with forthcoming DAC object ;)