1st release

Release Notes:

Feel free to comment here for any feature request or bug report. I’ll be happy to scroll through all of them.

Also note that we’re working on a fix for the AU failing to load in Logic Pro X, and GUI stuff for the modulation section.
We’re planning to had a Dry In parameter to our delay lines.

v 0.0.1 : 14.05.2018

  • First Release.
  • New plugin engine.
  • New macros.
  • Modulation of modulation parameters.
  • VST2, AAX, AU compatibility

9 thoughts on “1st release

  1. Hi,
    i had a great try the last night, but where can we put some Bugreports and recommendations?

  2. ok 😉
    My System:
    Win 7 Pro (i7 4770k, Asus Z97)
    Ableton Live 10.0.1

    – changing (draggin/copying) the Infinty from one channel to another crashes Live hard – reproducable
    – maximizing the plugin gui inside live produces harsh audi crackles – reproducable

    – overall great sounding, versatile, amazing multi fx delay possibilitys!
    – a “wet vol” knob would be great next to the dry vol knob (fast changing of the fx level without turning both dly volumes down)
    – using better sounding pitch-shift algorythms (less artefacts with pitched sounds)
    – using better sounding Distortion algorythms (maybe from Ohmicide, which i love?)
    – maybe a 1 tilt eq in the reverb section? to blend from dull to to crisp reverb

    -why are coming the taps thru, if the corresponding delay is with no volume?


    1. bug:
      – when changing the reverb mix1 via a red macro to full mix, the reverb is singnificant louder than when it`s pushed without macro to max

      1. Hello LuxLibra,

        We’re trying to replicate your bugs here but so far no success. This may be bc we don’t have Live 10 but we should have that pretty soon now. We’re still digging.

        That being said I was wondering – what’s your buffer setting ?

        1. RME Audio Buffer is at 64ms – on a quite stable and performant system.
          No other glitches or problems so far.

        2. To clarify – 64 buffer is really short even at 44100kHz and is proner to react to CPU use spike with crackles whereas 128 would probably not and 256 should definitely not. 64 buffer @ 44100 is rough 1.5 ms – by comparison your screen likely displays one image every 17ms. I am sure you’re familiar with buffer values ; we tend to go for the target of 256 for live tweaking and MPC style playing /wo needing to go easy on the reverb.
          My current test machine is an i7-2600K and it works for me there (although for video recording I have to lower that because of the CPU use of the recorder).

Leave a Reply to LuxLibra Cancel reply

Your email address will not be published. Required fields are marked *