Enter your feature wish or bug report

Wavetable-like scanning / Multiple waves

I'd like to have wavetable-like scanning and/or morphing through the 10 waveforms, or across a selected range eg from wave 2 to 6, or in a defined sequence 3,4,1,7.

See also http://cableguys.uservoice.com/forums/84071-curve/suggestions/1183305-lfo-secondary-wave-choice

51 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jakob RangAdminJakob Rang (Founder, Cableguys) shared this idea  ·   ·  Admin →

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • vladvlad commented  · 

        Would be nice to modulate crossfade with lfo or eg.

      • jasonswejasonswe commented  · 

        I agree but it sound complicated to implement! I just purchased a Blofeld wavetable synth and I am loving it. Waldorf fanboy here as well now. Modulating inside a wavetable is pure bliss indeed. Maybe I spend some votes here later but this seems to me more advanced upgrade that I think would be very nice to push ahead in the future AFTER all the present-day common modulation settings/routings are added into Curve's existing,...and possibily future second mod matrix. And more should be done with the Preset browser/Patch bank organisation first as well. :) Great patches btw, Ingo!

      • Ingo WeidnerIngo Weidner commented  · 

        This was one of my first ideas after testing curve. As i'm a "Waldorf fanboy" (and Waldorf betatester + sound designer) this is quite obvious... :)

      • Jakob RangAdminJakob Rang (Founder, Cableguys) commented  · 

        This feature has a time estimate of: 13

        The order in which we implement features is determined by the "bang". This is your votes divided by a time estimate (specification + implementation time).

        A simple feature will have a time estimate of "1". A more complex feature that takes 20 times as long to implement has an estimate of "20", and needs 20 times as many points as the simple one before we address it.

        Of course the bang is not the only thing that influences us, we also see our role in making the final decision. But we need strong arguments if we postpone a feature with a high bang.

      Feedback and Knowledge Base