BrainModular

hy dudes

first usine seems to be what mwaiting for long time , how dont i realize that before i wana buy it soon

my first need is send the output of the envlope folower to a midi out, a make verry simple patch like this
but nothing incomeback to my sequencer (ableton)

is there a usal way to send the outpout of the ev folower to midi out?
i wana send the midi out to ableton an from ableton to a virtual midi driver and rom then to the "telecomande imput" of ableton.
this way i can make side chain on evrithing like pitch , and not only filter and dinamics.



hope that you undertand me

peace guys

Hermut wrote:hy dudes

first usine seems to be what mwaiting for long time , how dont i realize that before i wana buy it soon

my first need is send the output of the envlope folower to a midi out, a make verry simple patch like this
but nothing incomeback to my sequencer (ableton)

is there a usal way to send the outpout of the ev folower to midi out?
i wana send the midi out to ableton an from ableton to a virtual midi driver and rom then to the "telecomande imput" of ableton.
this way i can make side chain on evrithing like pitch , and not only filter and dinamics.



hope that you undertand me

peace guys

using the peak follower module (analysis) you can get out the gate of a midi message. connect the 'peak' outlet with the 'create' outlet of a create midi module (midi). set the create midi module to CC (things are a bit more difficult with NoteOn/NoteOff).

audio->midi is not an easy application. there are several free audio to midi vst's.
KTDrumTrigger
http://www.kvraudio.com/get/2117.html
supereel
http://www.kvraudio.com/get/1538.html

u could use usine as a host for KTDrumTrigger, build your own interface, modify the midi with other modules

Hi Helmut, and welcome to Usine!

If you want to create for example CC messages from the envelope follower, connect the env output to a A on an A*B module and set B to to a value that creates the range between 0 and 127 that you want. Connect the A*B to the code2 input of a CreateMidiMessage, set code1 to the CC number you want and of course select CONTROL CHANGE as msg type. Also connect a HasChanged to the A*B (maybe with a trunc or round module between them to reduce the number of messages) and the HasChanged to create on the CreateMidiMessage.

hey guys thank you for fast and top notch answering.

the solution of bsork is perfect for me, cause i need cc message from 0 to 127 for full range control of vst remote.

stay fresh dudes
letsgo patchin!

i think it not so far to work, but it dosent... yet

i can see the midi out runin by the "trace out" it seems ok.

but i cant use it back in ableton...

hello and welcome..
you just need to add something to the data 2 inlet , it's the value of your midi controller , here there is nothing so you send the controller but always with value =0....

ok

thank you Nay

It s working now!

to complete my patch i need some "fixed values" for that now i use fader ..where is the fixed value??

thank you for this great sofware and forum

I think you will find what you need in the modules under:

math--> constant

HTH,
-e

While it often is good programming practice to use the Constant module for fixed values, you don't have to use it anywhere in Usine patches, as all the input values are stored and if nothing is connected to the input it will not change.

A typical patch of some complexity will have at least some constant values in for instance logical modules to check for (in)equality, and it would IMHO be impractical to use Constant modules for stuff like that. If however you want to make a certain constant value more "visible" in the patch, or there's a constant value used several places around the patch, Constant is your friend. In both cases, it will help if your editing or creating another version of the patch later on. When mentioning "visibility"; remember that you can right-click on the module and add a description.

Ok it works fine ! really nice to be able to side chain chords fine pitch from the kik drum !

thnk you guys

Hello Usiners,

I've been testing Usine Free version for a few month and just bought the Pro Version to begin using it more seriously to play and compose music. I first begun designing the drum sequencer of my dreams (I'm really excited by the new interface builder possibilities!).

But I was stopped by a really stupid problem I've never had before: I unfortunately scrolled all my modules away from the patch design window and saved without paying attention!

Now I'm lost in my patch!!!

I can't find my modules anymore: even if I show the interface and right click on a button to "find in patch", it doesnt bring the module back in the center of the window....

Isn't there a way to "center" the modules in the patch editing window?

Welcome Leo moldo ,
maybe, try to organize your patch in sub-patch ..?
and it's a better way to use this sub patch later..?
btw , there's no way right now to center your module , but this one is "selected " and look like this :

btw , there's no way right now to center your module , but this one is "selected " and look like this :

Yes, it certainly looks like this, but I can't see it, because it's outside of the window!!!

I used subpatches, but it's a pretty big patch and I spent some time connecting all the wires, but nevermind, if there is no other way I'll restart designing it from the beginning.

It could nevertheless be an improvement suggestion to develop this "center module" function when a module is selected, but it would'nt be so useful except for silly clunky people like me!

Thank you for your answer anyway!

This is all really amazing software

Hello Usine users,

I'm also quite new to Usine, this program is really capable (e.g. this internal message system seems to offer many interesting possibilities!)

Here my first newbie question

The following script should forward the value of a connected input textfield to the connected output textfield but the output textfield doesn't change it's value if I change the string of the input textfield.

Thanks for having a look that that!

Greetings,
NaN

var pInput : TParameter;
var pOutput : TParameter;

procedure init;
begin
pInput := CreateParam('Input', ptTextField);
pOutput := CreateParam('Output', ptTextField);
SetIsInput(pInput, true); SetIsOutput(pInput, false);
SetIsInput(pOutput, false); SetIsOutput(pOutput, true);
end;

var InputString : string;

begin
InputString := GetStringValue(pInput);
SetStringValue(pOutput, InputString);
end.

It works fine here with 4.22a.

If you're using TextField modules to test with, maybe you've made the same stupid mistake as I first did now, updating the caption instead of double-clicking on the text-field in the interface and updating the text proper?

(OT: I know this is just a test script so it doesn't matter here, but remember that "init" is processed once when compiling, while the whole lot between the last "begin" and "end" is executed once for each execution block.)

Thanks bsork!

I found my problem: Perhaps it would have been a good idea to turn on the audio engine in the first place... now it works!
The script was indeed just for testing, I wanted to introduce textual debug outputs for a script I'm working on and I wondered why I didn't see any debug strings.. now I know

Greetings,
NaN

For debugging purposes (or other messages) it's easier to use the WriteLn procedure. For example:

WriteLn('loop index: ' + IntToString(i) + ' value: ' + FloatToStr(x));

Thanks again!
That is indeed easier, will use that in the future.

Is there an exhaustive description of the script language syntax and the available API calls? (I found the chapter(s) in the docu, looked at some examples and guessed some things that are similar to Pascal but a thourough spec could probably be the faster way and would presumably lead to more efficient solutions here and there.

Greetings,
NaN (will be back at the weekend)

Well, there is to my knowledge no more descriptions other than what you find in the manual and the wiki. I have a bit of bad conscience about that as I have sort of promised to make something in the wiki, but I have never got around to do that.

When (if...) I do that, I haven't really decided for myself at what level the documentation should be; an overview/getting-started kind, or a more in-depth one. At least I should start with the simple stuff, making it easier for non-programmers to get their heads around the stuff. You're right about the similarity to Pascal (or Delphi). In fact, you can use a lot more calls than those listed in the manual. For example, I used the documentation in Turbo Delphi to help me with some text file i/o stuff a year ago, using methods from the TStringList class. What other classes is available from within scripts, I haven't got the faintest clou. Senso will have to chime in...

would love to have a nice and extensive docu for the script module.
i'd offer my help to create it. maybe Senso could advise us how to do it (eg. pointing to relevant ressources)?

Hi amiga909,
such a docu would be greatly appreciated and an immensive help to make optimal use of the hidden possibilities of Usine!

Greetings,
NaN

plus 1 for script doc!