The template engine

bsork · Unread post by **bsork** » 29 Dec 2008, 15:25

I've been scratching my head a bit on some parts of the template engine: What distinguishes "term flowtype" from "term display flow type", and where is "terminal name" applied?

So far I have only managed to see that simple changes makes the template work or not, and browsing through the defaults hasn't made me any wiser as to what values to use where.

YouTube · Unread post by **senso** » 29 Dec 2008, 16:15

we are in a deep zone of usine...
the flowtype is relative to the intern structure of the flow (data, audio, midi). It means "what the flow is supposed to contain"
the displayflowtype is relative to the way the flow is displayed. For example a data flow can be displayed as switch or gainfader or floatvalue.

the CREATE_LINK works with TERMINAL_NAME or with TERMINAL_NUMBER as parameter. Generally I prefer use the TERMINAL_NUMBER because it avoid conflicts if, for example, a sub patch contains 2 inlets with the same name.

I hope I will have time to update the manual soon.

Vincent · Unread post by **Vincent** » 29 Dec 2008, 18:49

Hi,

I've been doing some things in the template folder, and crated a few new ones.
The first thing I would say is that it opens new and wide possibilities!

It's true that for the first hours, help is hairy. But I know that manuals are great job and need time to come.
I was missing procedures for Usine itself (basically to have acces to every menu command).
On the other hand, it looks very simple and very efficient, we just have to be a little bit more familiarized with the terms and the slightly different concepts. Let's call this the Usine's Core Concept?

I've tryed to create a template for dropped wave files (not in sequencer) and noticed that if the sampler (wave player) is in a subpatch of that template, it becomes very tricky to write the procedures (and I gave up!).
My feeling is that some new modules could be implemented, modules that handle some basic procedures so that the flowtype and displayflowtype would be obvious (in/outlets) and the parameter ordrer and type would be always right. Some kind of graphic patchable procedures. Usine is a graphic modular programming soft.

I've also noticed that when you work in a TXT file and save it while progessing, you have to restart Usine. Templates are loaded in RAM when Usine starts and they cannot reflect subsequent changes.

I think I'll send very soon a new HTM page for the modules constants in alphabetic order, with switches to go to A, B,..., because it's not easy to find them (sometimes differnt names).
Olivier, is it a good idea to sort them according the browser treeview?

I just says this: Waow!

cheers

YouTube · Unread post by **senso** » 29 Dec 2008, 19:06

Be patient, I'll improve the IME slowly as much as I can!

I've also noticed that when you work in a TXT file and save it while progessing, you have to restart Usine. Templates are loaded in RAM when Usine starts and they cannot reflect subsequent changes.

No, since the beta 6 you don't have to restart Usine. Changes are automatically reflected

I think I'll send very soon a new HTM page for the modules constants in alphabetic order, with switches to go to A, B,..., because it's not easy to find them (sometimes differnt names).
Olivier, is it a good idea to sort them according the browser treeview?

If you have time it's a perfect job for the wiki?

Vincent · Unread post by **Vincent** » 29 Dec 2008, 19:14

senso wrote:since the beta 6 you don't have to restart Usine. Changes are automatically reflected

Good!

senso wrote:If you have time it's a perfect job for the wiki?

For the help file. We need help!

martignasse · Unread post by **martignasse** » 29 Dec 2008, 19:23

Vincent wrote:I've tryed to create a template for dropped wave files (not in sequencer) and noticed that if the sampler (wave player) is in a subpatch of that template, it becomes very tricky to write the procedures (and I gave up!).
My feeling is that some new modules could be implemented, modules that handle some basic procedures so that the flowtype and displayflowtype would be obvious (in/outlets) and the parameter ordrer and type would be always right. Some kind of graphic patchable procedures. Usine is a graphic modular programming soft.

Hello vincent,

Has i have to put myself in the template world.....
And interested in you're try with the sampler -> drooped files (can you explain a little please, is it to save and name files automatically ?)...
And now that i can make some user module

...

I think it can help you, or at least give it a try myself.

And it's also a good candidate for some WIKI tutorial (about template, and user module....the usine deep core concept)

PS : i have not a lot of time theses days, but it's something i have to do (deal with all my samplers files), so....here we go

Vincent · Unread post by **Vincent** » 29 Dec 2008, 19:38

martignasse wrote:And interested in you're try with the sampler -> drooped files (can you explain a little please, is it to save and name files automatically ?)...

Not such a tricky stuff!
As a matter of fact, all my midi patches send midi flow via busses to other patches, but with some changes before, allowing sequencer curves. There is no VST, no audio out, only midi busses and a few 'CreateMidiMsg'.
Since it can go to Absynth or to a sampler, they must be different (number of channels, things like that)
So I decided to do that template and to incorporate it in the dropdown context menu...
It's not yet working perfectly. I must install beta6.

cheers

martignasse · Unread post by **martignasse** » 29 Dec 2008, 20:54

Bouhou,

i just believed you want to make a template for samples names when saving samplers files automatically.

a+

Vincent · Unread post by **Vincent** » 29 Dec 2008, 21:54

Hi Martin,
I don't undesrtand what you mean!
To save files, anyway, you need a saving procedure, and I did not find it... maybe in next releases.
Can you make user modules with procedures like that?
Don't tell me. I should not have a look to SDK stuffs. No time for that.

martignasse · Unread post by **martignasse** » 29 Dec 2008, 22:35

I didn't look in the template engine, i was just 'in need' for this kind of things and your words :

I've tried to create a template for dropped wave files

made me believe it was possible.

But it could be an elegant way to make this possible... if it exist.....

Vincent · Unread post by **Vincent** » 29 Dec 2008, 22:49

Maybe it is possible....
I don't know. The template engine is quite a new stuff and I think it's good to have a look at it, because there you can see future Usine's releases coming!
But I'm just composer and musician. I hate spending nights on programming, and I am not crazy about patching; I just do the absolute minimum for what I need! In other words, I use a tool and that tool is very powerfull.
Be patient. In only a few weeks, you'll have guys to kindly and clearly explain everything to you, isn't it, Bjorn?

martignasse · Unread post by **martignasse** » 29 Dec 2008, 22:58

Yep, i just have no time now to explore this new beast....

But i had a quick look and it seems not possible to deal with this for now....in fact, it just miss a filename inlet on the sampler module to make it possible, i believe (and even without the template engine, but with 'classic patching')

....where is the boss.....senso....can you here me ?

bsork · Unread post by **bsork** » 29 Dec 2008, 23:36

@Senso: Thanks for the explanation - I understand a little more now.

@Vincent: If you're suggesting that yours truly will be able to help others soon with the new features, I hope to be able to, but like Martignasse, I don't have much time to spend on Usine for the time being so... Anyway, are you trying to create templates for dropped WAVs where the sampler resides in a sub-patch? If so, is the template creating a patch from scratch or is it adding the sub-patch and possibly other modules to an existing patch (as in "add group")? Just curious - so I can have that in the back of my head when I do have time to fool around with this.

Vincent · Unread post by **Vincent** » 30 Dec 2008, 00:13

bsork wrote:is the template creating a patch from scratch or is it adding the sub-patch and possibly other modules to an existing patch (as in "add group")?

Hi Bjorn!
In my first attempt, I used one of my patches as template. Then, I tryed to use an ADD GROUP.
And then, I had so many questions that I gave up!
One of those questions: is it possible to do stuffs like this

Code: Select all

CREATE_LINK SRC_MODULE SRC_TERMNUM+1 out1 2
// where 1 is added to the variable SRC_TERMNUM

And yes, I'm sure you'll soon be a master in templates domain just like in others!

cheers

Vincent · Unread post by **Vincent** » 31 Dec 2008, 16:22

up... :
Question: is it possible to do stuffs like this:

Code: Select all

CREATE_LINK SRC_MODULE SRC_TERMNUM+1 out1 2
// where 1 is added to the variable SRC_TERMNUM &#40;this line doesn't work&#41;

Could be fine for stereo connections or for multi-module insertion.
Thanks

antwan · Unread post by **antwan** » 04 Jan 2009, 18:57

Hello,

Laying my first looks on 4.1... My my, I'm really impressed.

I'm joining in on the Templates Engine & Internal Messages Language discussion with great enthusiasm.
It seems to already be doing a lot of what I was seeing in my wildest dreams just a short while ago (referring to this discussion: http://www.sensomusic.com/forums/viewtopic.php?id=1117).

I've been playing around with the Send Usine Messages -module learning the very basics. I don't understand much of the Templates Engine at all yet but I see it in action and like it. Anyways for now I am interested in the Send Usine Messages -module and using SendUsineMsg() in scripting. But I didn't get the SendUsineMsg call in a script to work at all. I didn't get the syntax from the help files and I get nothing but errors from the compiler.

I guess what Vincent is asking for (manipulating variables within the code, conditional statements) isn't possible in the Internal Messages Language but perhaps it could be done combining IML with scripting? I'm also interested in this.

Other than this I have just minor headaches and suggestions at the moment:
- I managed to create a sub-patch but I didn't manage to make the newly created sub-patch the target patch. For example:
SET_TARGET_PATCH SENDER_PATCH
CREATE_MODULE SubPat 6 100 100
SET_TARGET_PATCH LAST_CREATED_MODULE_NAME
CREATE_MODULE fader 3 100 100
I expected that this would've created a sub-patch in the current patch, then created a fader within the sub-patch called "SubPat"... But clearly it didn't work this way. Is there any way to do this?

- It would be lovely if the names for CREATE_MODULE or SET_STRING_VALUE or SET_COMMATEXT would remain case-sensitive. Now if I create a module called SubPat it ends up being SUBPAT. And if I make a Listbox entry with comma-separated strings they all end up in capital letters.

But this is superb. I can't wait where this takes us.

Cheers,

antwan

Welcome to %s forums

The template engine

Who is online

Login • Register