1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192 |
- ../ev-in -path ev-main -path ../ev-main -path ev-pano -path ../ev-pano
- -path ev-pro -path ../ev-pro -path libs/gil -path ../libs/gil -path
- libs/kollabs -path ../libs/kollabs -path media -path ../media -path
- ev-glsl -path ../ev-glsl;
- 2 8 0 14 -99865 -262144 0;
- 3 8 0 14 -162280 -1 0;
- -66577 0;
- 0 12 -162280 -1 0;
- -66577 0;
- -66577 0;
- abstractions to register parameters for storage and osc communication
- ;
- domain \, see [ev_storage-help] for details;
- of (internally) connected FX all GUI-controls are ranging from 0 to
- 1 \; either drag coursor in slider or in numberboxes;
- ;
- ;
- ;
- ;
- ;
- ;
- ;
- ;
- 0;
- -1 -1;
- under a new name within ./ev-main. Then create your just saved abstraction
- in you patch & program into it whatever you like \; Remember \, all
- storage and control related parameters still rely on the parameter-list
- below \, so you want to make sure \, that you create your own created
- effects with UNIQUE-IDs to avoid paramter-mixup \; What happens \,
- if you dont take care of this? \; Both \, the original [ev_base] and
- the [ev_pix_fx] are initialised with the same ID \, so changing a parameter
- on [ev_base] changes it on the other as well \; \; _______________________ADVANCED___________________________
- \; to add additional parameters \, please have a look in the helpfile
- for [ev_storage] under <Registering Variables>;
- \, other GEM-functions or whatever your needs are easily in your ExtendedViewToolkit-based-patches.
- It allows you to instantly take advantage of the built-in storage and
- transition features \, ultimately allowing for faster patching when
- preparing a show or installation \; There is a BYPASS-funtion and some
- parameters already integrated.;
- toolkit/ gpl v3;
|