anyone know a way to make table multi client without saving them to a file?

all the ensembles i make use an absurd amount of tables, and the only way i know to make them multiclient is to save to a file and load that file into another table. (i'll also try to use less tables and store the data in a common format)

is there a way to have multiclient tables that are just backed up with the instrument?

if there is then people will be able to use my ensembles without problems whether they have a mac or pc

fyi, reaktor crashes if you load an instrument/ensemble that has a table module refering to a file that does not exist on your system.
having them in memory and backed up w/the ens/ism would avoid that problem.

thanks,

Romulus

PS. after seeing that you can use pop up windows (a la the Caterpillar Ensemble) it seems that reaktor is powerful and limitless enough to make full fledged audio apps, including audio editors with higher level mathematical functionality. is that what it should be used for?
or is it just for making quick usable things that sound good (kind of like a software version of my 3 crates of analog stomp boxes
it seems like reaktor could be the master environment though.
what's your opinion?

PPS. i'm working on making a multidimensional control shaper interface (i.e. 12 controls would graph to an 11 dimensional plane in 12 space instead of just having 12 1 dimensional graphs to affect a parameter-- it seems like parameters in acoustic instruments all interact with eachother, a change in one changes all the others, so it's more like one 11 variable function than eleven 1 variable functions). is anybody working on/interested in that? if so what are thoughts about it?
that'd be a cool addition to a sampler or synth if it was easy enough to use.

 

about table saving

hmm, i just create a table in the event table itself. it gets saved with the instruments automatically.

is that your problem? (sorry im tiered

 

i see what your saying. its when you load a file into the table- then its always linked to that file. why cant you just use new tables as oppose to loading one? why do you need mulitable tables with the same data?

/timothy _-_ trash80

 

figured it out...

hey,
if you name the table in the file section to a word with no path name, and do not save it, then if you copy the table both of them will share data.

i wanted to do this so that you can edit parameters in one window, and have them used in the main window (to avoid having an interface as large as the gigantalupulous sampler--it's about 9'x9'

but now i'm starting to use 1 client tables to hold all config data
(of a given type) and just pump it out from a central location.

but at least now i know how to use memory-only multiclient tables

peace and good luck with your ensembles,

elon

 

more on multi client tables

if you have a table with a bunch of clients in one instrument and only have 1 with "backup data" then if that table is deleted the instrument is not able to load the next time.

I've removed all multiclient tables from MIDAS except the drum map editor, and it works with no problems now.