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

Event Table Persistence

Discussion in 'Building With Reaktor' started by Lowkus, Mar 1, 2004.

Thread Status:
Not open for further replies.
  1. Lowkus

    Lowkus NI Product Owner

    Messages:
    802
    I have an event table in an ensemble I'm building, but when I change snaps the table remains unchanged. What is the common way of storing the settings for an event table so that it persists according to the snap it is on? Is there a setting somewhere that I missed, or will I have to go through some convoluted means?
     
  2. kim (keem)

    kim (keem) Forum Member

    Messages:
    323
    convoluted. or just use the y value for destructive editing.
    you can use "snap values" if you have little data to store and recall.
    i have found that a simple, and effective way, is to have one "active table" and one "storage table" where the active table is written ( recalled ) to and stored to the "storage table" by means of the snapshot module and some iterations.
     
Thread Status:
Not open for further replies.