snapshot vs. saving the ensemble

sorry, this is pretty disjointed... it can all be summed up in the question at the bottom....

I'm having a hard time grasping the best way to save my patches in various reaktor instruments as well as acessing my patches in other daws. for example, I made an instrument and tweaked it and am using it in Logic. It always autosaves in that project folder. I want to bring it into pro tools but when I make a snapshot it does not appear when I open the ensemble in pro tools.

If I have this straight... there is the main ensemble file my docs folder, the autosaving file for the instrument in my daw, and then snapshots of that instrument only accessible by that file? does this make sense? I wish there was an easier way to just make an instrument and save it, then access just that one instrument file and save all my presets to be recalled whenever I open that reaktor instrument.

would setting my autosave folder to 1 main documents folder so that I am always overwriting it in each daw? or would that cause problems?

How do you all organize your presets/instruments?

 

i personally never use Autosave, but then that is my personal preference. if i tweak when i use an Ensemble in Logic, i save that as an amended Ensemble.

hopefully someone who does use Autosave will pass on their wisdom.

i do suggest having your Autosave Folder as part of your Reaktor User Folder though, at least it will be easier to find.

sowari

 

Hello,

I do not use Logic and Pro Tools, but normally an ensemble that you open as a standalone or as a plugin in any host should look (and sound) the same when you first open it. (except maybe BPM.) The auto save function is just as good as save in standalone, although it is probably good to have the reflex to also save the daw project afterwards.

As for the file management probably you should just save as many versions of your ensembles as needed, always into the specific Logic or Pro Tools project folders. You can do that with Auto Save, just make sure to change the destination folder, because that does not happen automatically. Ensembles do not require much space (except those with sample maps self contained), so it is not worth to be accessing the same ensembles from different places.

 

I find it easiest to have an Autosave folder in each DAW project folder. For instance, if I'm using Ensemble1 in Song1 and Song2, a copy of Ensemble1 will be saved in Song1's Autosave folder and Song2's Autosave folder.

This way I can move songs around without worrying about losing ensembles. And if I edit the ensemble or write new presets specific to the song, it doesn't mess it up for other songs. I can also better organize my folders and delete unnecessary files because I know which songs are accessing them.

This wouldn't help you access all your presets from each song though.

 

I also have an auto-save folder in each project folder.

What you maybe could do is have a preset bank that you save in a different location (the user folder for example) where you save snaps that you want to use elsewhere- just load the bank and off you go...

 

lots of good ideas...

thank you for your help!

 

Hello ,

I have Issue with Snaphots and what you said intrigued me...

I think my ensembles send 2 differents values for almost all my CC when I do a Prog change.

Could it be because I added Snapshot modules and Snaps array in the Ensemble?


In fact when I use my ensembles in Stand Alone my ensembles send corrects values to my BCR2000 and Lemur, but when I use them in Pluggin with Bidule to get the CC out, I have wrong values....
I contacted Seb@Plogue Bidule and he told me that He sees 2 differents values (at the same frame)sent by Reaktor for almost all CC when I do a program change.And this in both case Stand alone and Pluggin...The difference is the order of the reception.So in Reaktor Autonome I receive the good value in last but in pluggin I receive in last the wrong value...


Sorry it was long

So could it be the problem?

If someone could get me in the direction for Problems around Snap module and Snap array...?

It would be great!
Thanks

 

Hey,
I tested what you describe with the event watcher. I hooked up different faders and knobs of different ensembles to it and I made program changes. The test was not 100% satisactory, because somehow the downmost input of the event watcher that is connected receives more than one value, but the first and the last being always the same. All other inputs receive one value at a program change. This might be a bug of the event watcher rather than reaktors, and anyway, you say that almost all parameters have different values relatively to standalone or plug, which is not in case here. So your problem is somewhere after reaktor in the chain. I don't own one of those "interactive" controllers, so probably someone else can help better. Maybe you could post a pic of your bidule layout?