Statistics: Posted by nay-seven — 22 Jun 2009, 08:28
]]>
]]>
now I remember senso spoke about this, seems hard to achieve sadly, otherwise the busses are very powefull, to be able to change buss names dynamically is really awesome, and that work very well in other side that's true, having several "get" buss with same name work like a charm and avoid many wires, just need to be organised on syntax
Statistics: Posted by 23fx23 — 22 Jun 2009, 01:38
]]>
connect the separate values
to different elements of an array, and retrieve the data using another array module in the receiving patch(es).
...hum...interesting !to different elements of an array, and retrieve the data using another array module in the receiving patch(es).
can you develop /illustrate this..bsork..?
please..
Statistics: Posted by nay-seven — 21 Jun 2009, 23:03
]]>
If you want to send several buttons or whatever to other patches via busses, the best thing to do would IMO either to have separate send and receives busses for each value, or (my preferred method for data related data), connect the separate values
to different elements of an array, and retrieve the data using another array module in the receiveing patch(es).
Statistics: Posted by bsork — 21 Jun 2009, 22:55
]]>
another way is using AxB modules to multiply the data by the buttons, send them to bus (so you can use differents but same label)
then on the other side you will receive always 0 or a value when press, so you can make a "pass if positive" using an A>B to check if the bus is positive, then the value pass (pass module, link the A>B out to the "pass"inlet) but if you need to sometimes send 0 this won't work, then you can collect all the buttons out (not values) to a send bus that will be used to feed the pass.
there must be tons of others ways also..
edit mm checked even my tec doesn't work, very strange I figured same named bus would act as one also..
maybe work if in two diferents sub pachs, if in the same should use only one named bus? have to check.
edit nope, enlightments?
Statistics: Posted by 23fx23 — 19 Jun 2009, 00:02
]]>
I'll try this one as well !
but now I have a more subtle question. It obviously seems that if I want to send several [ "button"-"pass event flow"] modules to the same bus, I'm not allowed to create several "send to bus" objects feeding the same bus. Cos if so, the bus remains stucked with the first "send to bus" object having fed him. So I have to create only one "send to bus" and link it to everyone.
Can you confirm this, or is it a side effect of a big mistake I was'nt aware of ? !)
thanks for sharing your knowledge.
Statistics: Posted by oxyredox — 18 Jun 2009, 22:03
]]>
as far as this goes:
try using a switch instead of a button - a switch operates as a toggle and a button is an impulse only.My first idea was to multiply the output of the button, but it always ends with 0... so I always end with program 1..
if you want to get more/less complicated you could also use arrays for this i think...
Statistics: Posted by Clearscreen — 18 Jun 2009, 01:49
]]>
23fx23 : thanks to your tip I've played a bit around with the dispatcher module and I'll remember it form now on. Yet since it only routes data, I have the same problem as before, but ahead of the dispatcher : have a single button send my single integer. Anyway, I was glad to learn that the "0to1" and "1to0" modules send impulses and not just 1 as it says in the documentation !!
My first idea was to multiply the output of the button, but it always ends with 0... so I always end with program 1...
nay-seven : I think your way is the most simple : it works and only takes 2 small modules. So I'll stick to "pass event flow" and a "button". thank U.
grego mondo : your idea with scenes and mapper is really intertesting.
"Not sure it's the best way for your "problem" but it's always useful to see how other people would do ..."
I do totally agree!
ok, now I can go back to work...
Statistics: Posted by oxyredox — 17 Jun 2009, 09:51
]]>
I'd use the switch and "multiply" or the "pass even flow" way or a mapper way ...
a mapper value with the condutor for example
get the number of the scene from the conductor and then map it
(for example scene 1 = data 3 for track 1 / data 5 for track 2 / data 9 for track 3
and for scene 2 = data 7 for track 1 / data 2 for track 2 / data 4 for track 3)
one mapper per buse (wich means 3 mappers)
Mapper 1 (0=0, 1=3, 2=7) Mapper 2 (0=0, 1=5, 2=2) Mapper 3 (0=0, 1=9, 2=4).
Not sure it's the best way for your "problem" but it's always useful to see how other people would do ...
Hope it helps ...
Statistics: Posted by grego mondo — 16 Jun 2009, 22:15
]]>
then set the inlet " in" to whatever value you want ( it's keep his value )
hope this help
Statistics: Posted by nay-seven — 16 Jun 2009, 21:54
]]>
hope it helps.
Statistics: Posted by 23fx23 — 16 Jun 2009, 21:45
]]>
CONTEXT :
I'm using USINE to manage several virtual instruments, and all the program changes. So there's one track per instrument (let's say 1: pianoteq, 2: kontact, 3: some modular synth) plus one track with a patch that manages program changes ofr the first 3 tracks. So I have one data bus per instrument.
PROBLEM :
In the program manager patch, I need one button per song which would send an integer in each data bus.
There comes my problem :
the button only sends a quick sequence {1,0} and I don't know what to do with it. I know the "constant" module but it doesn't have a trigger inlet. PLUS the "1 to 0" or "0 to 1" module, (from which I expected a simple 1 I could then multipliy by whatever constant I need) always send {1,0} (in other words it doesn't work when put after a button)
Has anyone a simple way of dealing with it ? just sending 36 or 67 in a data bus without moving a fader or a knob ?
thanks
Statistics: Posted by oxyredox — 16 Jun 2009, 21:39
]]>