BrainModular

I ve been trying the send usinemsg from the help section, very exciting
tried to reproduce: CREATE_MODULE "name" 54 100 100

where can we find modules names couldn't find in the help, for example what do i must type to get a fader
(of course i tried "Fader" but get the previous created module delay from help, don't understand all, or should we request a filename in usine directory, or create templates?

any quick explain/enlightment?

seems a good first step for me before diving into scripts, since it seems to use the same language from what I understand..

there's a list at the end of the wiki page of the ID used by the create module

example :
CREATE_MODULE test 222 //

give tou a midi fader named "test"

( btw , i don't succed to choose x, y values ..? do you ..? )

http://www.sensomusic.com/wiki/doku.php ... l_messages

cool big thx nay! that was exactly what I was searching, strange I had a look at the wiki and couldn't find.
will try and report you for xy, worked with exemples if i well remember..gonna try

hi 23fx23 and nay,

just tested with

SET_TARGET_PATCH SENDER_PATCH
CREATE_MODULE test 222 50 200

working like a charm, x and y position are ok

23fx23 wrote:seems a good first step for me before diving into scripts, since it seems to use the same language from what I understand..

It's lot more low-level and powerful than that. See it like a console command language (like in game), to communicate directly with Usine internal command system.
Each action Usine can do is in fact one of those command (in theory), Script and SDK have the ability to dynamically send request for these command thru the internal message language.

And the user interface of usine is 'just' a more comfortable way to send those request too, it's litteraly a 'Graphical interface to internal command converter'

yep , you're right martin..don't know what's happen last try...??!!
and yes , it's a powerful tool , the delete link message ( as used by ethnix ) is a really good example and i'm sure it will be used more often now ! !

thx matignasse, that confirm what i felt.
i wanted to look at the console while paching to observe, but it closes as soon as going to pach, any way to lock it open? arf no usine on my girlfriend computer (mmm im gonna dl it and hide the folder hehe)
the console seems very powerful to wach, learn and try to reproduce no,? gonna print the wiki also

i definitely still have years of learning usine facets, thought i was starting to catch, this go far beyond what i imagined...
great!

still not completly understand what really sdk is.. catch scripts and sendusine msg concepts, but not yet sdk...

about console :
double click on it to open it
or
menu/window/show console

23fx23 wrote:i wanted to look at the console while paching to observe, but it closes as soon as going to pach, any way to lock it open?

Strange, if you click on the log window (top right) it make the console appear (the same as menu Windows->Show Console), after that, it should not disappear until you re-click in the log or re-choose in the menu. At least it's the behavior i have.
Locking at the console while dropping some module is magic, you see the power of the template engine at work. It's a good way to learn, for sure (and looking in the Templates folder of usine distrib is very interesting too )

still not completly understand what really sdk is.. catch scripts and sendusine msg concepts, but not yet sdk...

SDK (aka Software Development Kit) is to make your own module (imagine your synthesis pack with modules instead of VST) .

To compare with scripts, as script commands are interpreted on fly by Usine when executed, user modules created with the SDK are compiled to machine language at development time (like VST plugs). thus, it's really more speed to execute by Usine as it haven't to interpret nothing, just execute some machine language.

In fact, Usine modules are very similar to vst specialized to Usine functionality, the SDK is the foundation code to needed make these modules.

ok make sense, many thanks for clarification, I think i will much more have a look at the console and template now,
seems "accessible" one day if observing,trying , asking hehe, at least very powerful if scripts and usine msg share the same usine language, can't wait to test. was scotched by the create/dlete wires of ethnix . not sure/will be much longer to create modules I guess, but that's more your job now
thank nay also, I think i did something wrong for the console, today it works! (i wasn't drunk?)

I wonder if some sort of event recorder /player in Usine could be usefull. Then you could crteate a send Usine command by simply recording the action as you do it.

gurulogic wrote:I wonder if some sort of event recorder /player in Usine could be usefull. Then you could create a send Usine command by simply recording the action as you do it.

In fact, Usine already work like a macro player, who execute templates file on demand.

the useful tool would be to have like a macro recorder, who store all the commands sent by templates when you make some patch, and a macro player who can modify those templates and send them to Usine.

Actually, there is no way to intercept or store internal message sent to usine by the template engine (maybe we just need to add a callback function and a flag in the SDK :rolleyes:) the rest should be possible with the SDK.

nice idea, there is a such function in photoshop kind of scripts for dummies , rec stop/replay then adjust, would be awesome.
already tons of thingz to test..

Not quite macro recording, but you can copy the text from the console window by right-clicking and choosing Copy. Makes it a bit easier and saves some typing.

hehe thought abould it good old' ctrl c ctrl v

bsork wrote:Not quite macro recording, but you can copy the text from the console window by right-clicking and choosing Copy. Makes it a bit easier and saves some typing.

Yep, i tested to convert some console text to usine message, but the console not always show the exact message received by Usine (ex: Create module, or Add Connection). Anyway, it's a good start.