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

How to manage/edit all automation IDs used by an ensemble?

Discussion in 'Building With Reaktor' started by sighduck, Dec 21, 2018.

  1. sighduck

    sighduck New Member

    Messages:
    3
    I previously started a thread, but I think it may have been too convoluted to understand, so I have started this one to be more clear.

    So basically... I would like to add an XY panel to the Razor ensemble. I also want to make the panel cursor automatable from withing a DAW, which requires two automation IDs (one for the X value and one for the Y value).

    Reaktor allows us to set one explicit automation ID for an XY panel, which becomes the X value's automation ID.
    The Y value's automation ID is not explicitally set by the user. It is set to the value following the X value's automation ID.
    For example, if you set an XY panel's automation ID to 5, then the Y value's automation ID will be set to 6 (if the ID is free).

    The problem I'm having seems to be that Razor is already using all of its automation IDs, hence I can't find any automation ID slots that are free (and I need a pair of free IDs which are right next to each other, numerically speaking). What keeps happening is that the automation ID for the Y value of my XY panel keeps getting set to some number greater than 1000, which is the max ID that a DAW can detect. Whenever I select 'Compress IDs' or 'Compress&Sort IDs', this usually breaks Razor's automation setup in various ways.

    So my question is... how do I manage all the automation ID's being used by a Reaktor ensemble, without having to actually go inside the ensemble and find the specific node associated with every single one of them?

    Essentially I am looking for any information regarding the advanced management of automation IDs. Ideally there would be some way to view all the automation IDs being used by a Reaktor ensemble, as well as the names of parameters that they are assigned to, so that we can easily reshuffle/reassign any and all parameters to their automation IDs manually. Is there any way to do this, or any other solution to the problem of not being able to explicitally set the Y value's automation ID on XY panels?
     
  2. Michael O'Hagan

    Michael O'Hagan NI Product Owner

    Messages:
    1,163
    this has been an issue in Reaktor for years...

    the only easy solution is to increase the "max ID" number in the preferences panel and then add the XY panel at the very end of the list.
     
    • Like Like x 1
  3. Philippe

    Philippe Well-Known Member

    Messages:
    1,553
    Michael, is 1000 actually the max id number a DAW can detect ? Isn’t this different for every DAW/ host ? Not sure...
     
    • Informative Informative x 1
  4. Michael O'Hagan

    Michael O'Hagan NI Product Owner

    Messages:
    1,163
    I Think 1000 is the maximum for any DAW, I'm not sure but I think that's a VST 2 limitation.
     
    • Informative Informative x 1
  5. Philippe

    Philippe Well-Known Member

    Messages:
    1,553
    mmm, this VST 2 limitation triggers something in my mind. Will have a search.
    Thanks for your answer :)
     
  6. tomtakestooth

    tomtakestooth NI Product Owner

    Messages:
    170
    100x this! It can become a royal pain, especially when you've got a large ensemble. I'd love to see the same for OSC.
     
  7. Quietschboy

    Quietschboy NI Product Owner

    Messages:
    564
    I don´t own Razor. But i can imagine it needs tons of automation IDs.
    OTH, 1000+ IDs seem to be too much, imo. 1000 or more user definable parameters? Really?
    To me, it more looks like that the developer missed to deactivate automation for internal-only parameters like send-receive connections and so on.
    Maybe you can deactivate Automation for some of those useless parameters inside the range (maybe hard to find for a newbie..)?
    NI should be informed if my assumption is really the case. Maybe Razor needs an update, then!?
     
    • Informative Informative x 1