]]>
antwan
Statistics: Posted by antwan — 11 Nov 2008, 14:50
]]>
thanks for your replies!
Yesterday I did not manage to try your suggestions (damn headaches), but hopefully I can do so today! I´ll check back later!Statistics: Posted by Stefan — 11 Nov 2008, 08:37
]]>
one of the thing's i like most about usine is that there is little division between stream types - you can treat audio pretty much as data, midi or make it an array, and mix it all up almost any way you like!!!
Statistics: Posted by Clearscreen — 11 Nov 2008, 00:14
]]>
The 'pass only if changed' passes the data when the value has changed. The rest of the time it sends nothing - which is different than zero.
Let's say you have a switch that decides when the audio should pass to output and when not to. You could for example have a combination of two 'pass event flow' modules and one 'NOT' math module.
So try these connections:
Switch -> pass.PassEventFlow1
Audio -> in.PassEventFlow1
PassEventFlow1.out -> audio out
Same switch -> in.NOT
NOT.out -> pass.PassEventFlow2
PassEventFlow2.out -> audio out
... Then set the in.PassEventFlow2 to 0.
This way everytime the Switch is on, the audio signal is passed through to the output.
Everytime the Switch is NOT on, a zero is passed to output.
Does that work for you?
Cheers,
antwan
Statistics: Posted by antwan — 10 Nov 2008, 14:51
]]>
yes, that´s true, I can see that the value on the bus isn´t 0, so it must be the last data sent.
But how can I make sure an 0 is send as the last value, when audio stops? Yesterday I tried with 'pass only if changed', but I think this may scramble some types of audio data?
Statistics: Posted by Stefan — 10 Nov 2008, 14:17
]]>
You should either make sure that a 0 is sent instead of the audio stream, or use one of the audio volume modules.
Statistics: Posted by bsork — 10 Nov 2008, 09:26
]]>
ah, I can use the audio input/output in the subpatch! Thanks!
I just did a quick test, it works, but I still got *beeeps* when I bypass the source of an audioBus. In this case I used a sampler as source.
About the aux buses: yes I saw them, but they always send the sum of a whole track (like an additional input for tracks). I´d like to be able to use one track in 'all'-mode and later get the signal of any of the single patches.
Statistics: Posted by Stefan — 10 Nov 2008, 09:05
]]>
The first thing is, I used a fader to provide a 'pin' for the outgoing audio-signal, because I obviously want to use this as a subpatch. I suppose this isn´t a good idea, but how can I provide a 'pin' in a different way?
Second problem: when I stop the playback of a source signal for a bus, there remains a constant value on the bus (=hanging note => *beeeeeep* ). I tried to fix this with 'pass only if changed', but I´m not sure, if this is ok for audio data?
And generally: I am trying to create my own routing with audioBusses. Basically I want to use 6-8 different VSTi´s and route them to several loopers and vst-effects. In the end I would like to mix all the signals together in some kind of 'master patch'. Is this totally weird (= can´t and shouldn´t be done) or do you think, that this could work?
Hi Stefan, you should replace the faders with 'audio output' modules that're found under 'input-output' in the modules section of the browser. this may also fix your second problem, but i'm not certain about that - see what happens and let us know i guess Second problem: when I stop the playback of a source signal for a bus, there remains a constant value on the bus (=hanging note => *beeeeeep* ). I tried to fix this with 'pass only if changed', but I´m not sure, if this is ok for audio data?
And generally: I am trying to create my own routing with audioBusses. Basically I want to use 6-8 different VSTi´s and route them to several loopers and vst-effects. In the end I would like to mix all the signals together in some kind of 'master patch'. Is this totally weird (= can´t and shouldn´t be done) or do you think, that this could work?
your audio bus routings sound like something you can do. i haven't done anything that complex with them myself but i can't think of a reason for them not to work. my only suggestion is that it might be easier to simply use the aux send busses (i'm guessing you've already tried them, but thought i'd mention it just in case...), but if the send busses aren't suitable for what you want then by all means see if the data busses will work.
Statistics: Posted by Clearscreen — 10 Nov 2008, 00:48
]]>
I tried to build two patches to 'wrap' the AudioBusses and to make working with them easier. Some things are ok, for example: I have a list or combobox with predefined names, so its easy to choose a bus by name from the send- and get-patches. It also works by adding the letters L or R for the left and right channels automatically. That was very easy. This is the getFromBus patch:
But: there are some things, I just don´t get right.
The first thing is, I used a fader to provide a 'pin' for the outgoing audio-signal, because I obviously want to use this as a subpatch. I suppose this isn´t a good idea, but how can I provide a 'pin' in a different way?
Second problem: when I stop the playback of a source signal for a bus, there remains a constant value on the bus (=hanging note => *beeeeeep* ). I tried to fix this with 'pass only if changed', but I´m not sure, if this is ok for audio data?
And generally: I am trying to create my own routing with audioBusses. Basically I want to use 6-8 different VSTi´s and route them to several loopers and vst-effects. In the end I would like to mix all the signals together in some kind of 'master patch'. Is this totally weird (= can´t and shouldn´t be done) or do you think, that this could work?
Greetings,
Stefan
Statistics: Posted by Stefan — 09 Nov 2008, 21:32
]]>
[after three failed attempts to read the anti-spam code]
I SWEAR I know my letters and numbers..... they're not different in french, are they??
Maybe your pronounciation?I SWEAR I know my letters and numbers..... they're not different in french, are they??
Tip: before entering the antispam code, I do a CTR+C on my post. We never know!
Statistics: Posted by Vincent — 09 Nov 2008, 17:47
]]>
]]>
the GetBus-Module could have a combobox listing all the internal data busses for the interface builder
+1!And a fature that lists all busses used in the WKP in a window or a context menu, allowing "find in patch"!
Statistics: Posted by Vincent — 09 Nov 2008, 15:20
]]>
]]>
If not, I have a feature request...
It would be great, if
a) Usine would name additional busses automatically on creation with something like "DataBus"+TrackNo+RunningNo (just for convenience)
and if
b) the GetBus-Module could have a combobox listing all the internal data busses for the interface builder
By the way, Usine works much much better for me since version 4.0! Great work (as usual)
Stefan
Statistics: Posted by Stefan — 09 Nov 2008, 12:43
]]>
So the number value on the bus is irrelevant?? Is that the data they are sending??
Sorry, today we're even slower in answering, but yes - the input is data to send through the bus.Statistics: Posted by bsork — 28 Oct 2008, 08:25
]]>
Do you think I have all day??? I'm a busy man!!!!
I'll try again to make the busses work. It was very late, and I was probably missing something.
So the number value on the bus is irrelevant?? Is that the data they are sending??
Well, I'll try again tomorrow, and see if I can get it to work.
I do think a combo of existing names would be nice, so you didn't have to remember your exact wording. But...... someday. Not a big priority.
-e
Statistics: Posted by woodslanding — 28 Oct 2008, 07:01
]]>
Hey, I won with 12 seconds!
I'll blame it on the spam controll k
Statistics: Posted by kara — 27 Oct 2008, 13:23
]]>
]]>
Now create a new path with the helios synth and connect midi in to a 'get from midi bus' named 'tovsti'.
The helios synth will receive midi from the piano roll
k
Statistics: Posted by kara — 27 Oct 2008, 09:01
]]>
The busses behaves much like the sub-patch in-/outputs with the exception that the busses can exist practically everywhere and still communicate creating unlimited routing possibilities. A (very) simple test case: Create a send bus in one patch/track, and a receive bus within another patch/track. Connect something that creates data to the send bus in the first patch, and watch the data coming in on the receive bus of the second patch.
When I say "practically everywhere", I must add that I'm not sure whether there are some limitations as to where the busses exists and can communicate, or if the data perhaps arrives in the next execution block (like using WaitOne) in some circumstances. I don't think so, however.
---
The site stuff isn't what I know very much about, but I'm wondering if you enter the right case of letters. For some reason, the codes I get mostly contain uppercase letters, and I've always been careful to use the case I see and haven't had any problems except that I sometimes find the codes hard to read. But that is intentional, anyway...
One thing just crossed my mind (and I'm probably missing the target completely here): The codes are graphics, could it be (I don't remember), that it uses "continental" characters like 7 and J with a small line across the middle?
Statistics: Posted by bsork — 27 Oct 2008, 09:00
]]>
What is the secret??
Thanks,
-e
[after three failed attempts to read the anti-spam code]
I SWEAR I know my letters and numbers..... they're not different in french, are they??
Statistics: Posted by woodslanding — 27 Oct 2008, 07:46
]]>