what i wonder about is that the patch works with a pair of faders but does not with a rang fader....
thanx
ps...a little language bug
"as" should be "has" i guess..
Statistics: Posted by lalo — 11 Jan 2007, 10:49
]]>
'pass only if it as changed' module
It will help you.
next release
Statistics: Posted by senso — 11 Jan 2007, 10:45
]]>
]]>
]]>
but it doesn't work like i expected....
i mean it work with external midi learned controllers...but the range fader doesn't send any value if moved directly with the mouse...
wich is what i'm trying to achieve ..as with other ui controllers...they work both mid-learned and on the gui
thanx
Statistics: Posted by lalo — 06 Jan 2007, 12:07
]]>
Statistics: Posted by senso — 29 Dec 2006, 08:32
]]>
Statistics: Posted by senso — 29 Dec 2006, 08:16
]]>
I'll try to make an example and post it in the add-ons.
hi senso, did you try some solution?..the event scheme of usine is not so clear to me
Statistics: Posted by lalo — 28 Dec 2006, 15:26
]]>
fader1 out --> fader 2 in ---> fader1 in
if Usine was conceptually perfect, you shouldn't able to move any fader: fader 1 is master and slave of the fader 2.
It's an unless loop.
Fortunately, Usine is not perfect (you know that!) and the endless loop is broken. The patch, in that case, is calculated in a precise order: the older (the first created fader) is calculated first and the older is calculated after (the second fader).
They is a solution to your problem: use 'has changed" and "stop event flow" modules to break the endless loop. I do it often. Stop event flow means "the wire is deleted" in Usine language.
I've discovered a small bug: in your example, you can change the second fader position, but is has no effect: only the fader display changes but not the real value. Bug fixed now.
Statistics: Posted by senso — 18 Oct 2006, 17:12
]]>
Would it be possible to "unlock" (or what I should call it) the input of the interface design modules? In fact, for two faders you're almost there already: I tried to hook up two faders in a "loop" out1>in2, out2>1, and when moving fader 1, fader2 followed as expected, but not the other way around.
(And yes, I know the example is pretty far-fetched and useless...)
Statistics: Posted by bsork — 18 Oct 2006, 16:10
]]>
I know that the range fader is "uncomfortable".
Actually, It's impossible to make a midi learn on It.
If fact the best thing should be to have a midi learn on the left side, right side, and both.
It's hard with the actual Usine structure. (only simple midi learn are allowed).
For me, the best way is to create a sub patch with 'has changed' and 'stop event flow' modules to allow simple learn (on faders, as you do actually) and allows modifications in the range module itself.
I'll try to make an example and post it in the add-ons.
Statistics: Posted by senso — 18 Oct 2006, 12:41
]]>
the current range fader is a bit unconfortable..if you link 2 faders to the range fader to automate start and end of the range via midi..you'll not be able to move the range fader on the usine patch itself...
at present time range fader can't be directly "midi-learned"..would be nice if it could be
thanx
Statistics: Posted by lalo — 18 Oct 2006, 00:01
]]>