1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

User Page Recommended Style?

Discussion in 'KORE' started by Lowkus, 25/2/17.

  1. Lowkus

    Lowkus NI Product Owner

    Messages:
    802
    When you open a KSD, how do you prefer your user pages to be designed?
    1) Lots of user pages (ideally in logical grouping) to cover every mappable control on the VST. You jump through a lot of pages but have access to everything.
    2) A few user pages, mapping only the controls that have a significant impact on the sound. You jump through pages, you have access to most of what you need.
    3) A few user pages, mapping the controls that not only have a significant impact on the sound but also sound good when sliding between grid variations. You jump through pages, you might be missing some helpful controls but you can trust that dragging the sound grid won't cause problems.
    4) A single user page, with the most effective knobs and buttons to keep the interface simple. You don't jump through pages, the knobs are what you use and you make those basic elements work for you.
    5) A few user pages, where each page is designed to be used as the one page for an entire song (every page has it's own Volume control). You select the page you want for a song, then it's just you and those knobs until the song is over.
    6) A couple of pages with controls for a performance, with additional pages that map all controls.
     
    Last edited: 27/2/17
  2. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19.938
    A combination of 4 and 1. First have a few pages with the greatest impact parameters, then full control logically laid out pages. Since Kore can assign the same parameter to multiple pages, that works. :)
     
  3. nielsdolieslager

    nielsdolieslager NI Product Owner

    Messages:
    2.122
    The first. I also assign single knobs to two controls like dry/wet and in/out combinations, reversed if needed.
     
  4. Kymeia

    Kymeia NI Product Owner

    Messages:
    6.268
    A performance page on the first page containing a few chosen params for quick sound shaping - sometimes this may include macros

    Then the rest, usually I try to group them logically to reflect the structure of the plugin
     
  5. Lowkus

    Lowkus NI Product Owner

    Messages:
    802
    I've added item #6 to account for the feedback so far.
     
  6. oodoodsiin

    oodoodsiin NI Product Owner

    Messages:
    113
    remember that you can go directly to a page with control+1-8. once you know by heart where everything is, this allows you to program nearly as fast as on a full panel, no jumping thru pages. therefore I rarely need to make custom user pages while producing, so I'm in favor of #1.