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

5.6.1 not remembering settings

Discussion in 'Technical Issues - KOMPLETE (Archive)' started by tonecontroller, Oct 18, 2011.

  1. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    I have a pile of ensembles I've created myself over the years and when working in Logic will often create a sound and simply save the whole session as part of the Logic song file. In every version of Reactor until 5.6.1 this has never been a problem but I'm finding now it won't recall the settings and just initialises the patch for every instance.

    I've been switching back to 5.6 but this is not ideal as some of my sessions won't now load after being saved in 5.6.1

    I don't know if 5.6.2 is going to fix this but in the meantime any help would be greatly appreciated :)
     
  2. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    you need to create a 'local' version of the Ensemble. do you not get asked to do that?

    sowari
     
  3. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    Thanks for the reply Sowari.

    It's actually the settings within the ensembles that are not restored, the ensembles themselves are loading correctly. I'm not saving new sounds as new snapshots which has always worked fine in earlier versions.

    I'm also not getting any error or locate file messages.
     
  4. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    sorry, but if you make changes to the settings you have to save the Ensemble - and that has always been the case.

    please save a version of the Ensemble in your Logic Project Folder.

    sowari
     
  5. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    I appreciate the fast response but this is incorrect.

    I have been using my own Reaktor ensembles in Logic for many years and have never had to make local copies before. It's always restored all my edited settings completely reliably every time until version 5.6.1. I work for a busy production company and this issue has seriously disrupted our work flow.

    Any tricks to get my edits back into 5.6.1 would be greatly appreciated.
     
  6. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    I've run some tests (in Logic 9.1.5) by creating blank sessions and making basic edits in Reaktor and saving the Logic sessions. I've swapped between 5.6 and 5.6.1 and tested both, 5.6 is remembering the setting perfectly and 5.6.1 is consistently forgetting the settings. Therefore something seems to have changed internally between these versions.

    For new work I've gone back to 5.6 but unfortunately I have some songs I can't recall where I've made edits and saved an ensemble in 5.6.1

    I'm really hoping 5.6.2 will fix this.

    In the meantime any other ideas would be greatly appreciated.
     
  7. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    please give examples of what you mean by changing settings.

    do you create new Snapshots?

    i still say you should save a local version of the Ensemble.

    also, the Save a Local Ensemble is a feature and makes perfect sense to me if you are using the same Ensemble in different situations.

    sowari
     
  8. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    Thanks for the response Sowari

     
  9. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    if you re uainf one copy of an Ensemble and you make changes to it, then you need to save those changes as a snapshot and re-save the Ensemble using the Reaktor GUI Save As - which you seem to be doing.

    but you need to make sure that you load that in your Song. this is still possible with 5.6.1

    on the other hand:

    sorry, but Save a Local Copy is very quick to do and once you have done all changes you make are automatically saved. this extra housekeeping takes 5 seconds!

    sowari
     
  10. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    Thanks for your continued help trying to sort this - appreciated :)

    This is a bit involved but let me try to explain the issues with the options you've outlined.

    I am occasionally saving snaps and re-saving the ensemble but not very often. If I have several instances of a particular ensemble being used in a Logic session and one has been updated, the others remain as they were before in RAM until the song is re-loaded and Logic then loads the latest version of the edit plugs into all slots. This doesn't' work as if I save a second sound in the same ensemble (but on another instance in logic) while the session is open (which I would want to do all the time), the new edits and snap on the first one are lost when you re-load the song as you've written over that one. This is why it's such a hassle and you get into a muddle very quickly. We rely on custom synths and fx for a huge amount of our production work and we have to work to very tight deadlines so I can't afford to get into this.

    Your other suggestion, saving a local copy has other problems. While I am programming something, I will regularly re-visit older saved Logic sessions and pick up a sound I've previously created from another session. This may be a stack of 2 or more Reaktor ensembles which I will import using the session import option in Logic. In view of the issues of saving snaps above, this has always been an easy and reliable way to pick up existing sounds - until V5.6.1 where it no longer works, the ensembles themselves are fine but the sounds wont recall. If I save another local copy of the ensemble, it might recall the sounds in each case but it's a huge amount of house keeping to keep track of all those extra copies of ensembles and give them all unique names so I would know which one to pick up for which sound. This is really not a viable option. Once logic sessions have been finished, we archive them but leave a single composite copy on our system - again storing all those individual ensembles so they could be identified quickly would be an absolute nightmare.

    As I've said, we have been working this way for years and we have never ever had any issue until 5.6.1. Even now if we revert to 5.6 (which we have now) it's all fine. However, we have some lost sounds we really need to get back soon or we're going to have to try to recreate them again - never as good as the first time.
     
  11. selfinflict3

    selfinflict3 Account Suspended

    Messages:
    68
    let me know when they fix this, cause this is a big, HUGE problem..
     
  12. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    i doubt if the system for saving will be changed

    i suggest you get in touch with tech support if you have issues.

    sowari
     
  13. selfinflict3

    selfinflict3 Account Suspended

    Messages:
    68
    i hear this bug has been reported.. dont have time to sit and argue about it though. i have no way too save my razor settings while using maschine.. i thought it may be a user error, but a few people informed me its a bug that NI said they are working on
     
  14. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    do you have the full version of Reaktor or the Reaktor Player version?

    if you have the full version you can save Razor as an Ensemble and save settings as new Snapshots and save those as an Ensemble.

    you can also save Razor Settings as Reaktor Presets.

    in Maschine, you can also save changed Razor settings as Maschine Presets.

    have you tried any of the above?

    sowari
     
  15. selfinflict3

    selfinflict3 Account Suspended

    Messages:
    68
    i only have the player version..so if i save it in maschine as a preset setting, do i have to recall it everytime i open that song? i dont understand why when you save it, it doesnt open how you left it?
     
  16. tonecontroller

    tonecontroller NI Product Owner

    Messages:
    18
    Can any kind person confirm if this issue has been fixed in 5.6.2. I'm right in the middle of a project and can't afford to take the gamble.