Hi, second post here. found this program looking for ways to use touchscreens in DJ setups as i got a tabletPC running XP a while ago and would like to use it as part of my controller setup. I have tried your program and have made some faders etc. slowly starting to get a feel for how usine works but before i dig too deep i had some questions.
1) I would like to have a set of touchscreen faders that act similar to the mechanical faders on the BCF2000, where the faders move to the position of the onscreen control when i switch through scenes. for example, if in scene 1 i have fader 1 as channel 1 volume set at 80, and in scene 2 i have fader 1 as high pass set at 25, I would like the touchscreen faders to change position from 80 and 25 when i scene is changed.
part two of this is that i would also want the touchscreen faders to reflect any input or changes i might have made with say the mouse, or a control on my other midi controller. so there could be multiple mappings of the same control, without midi jump or need takeover mode. let's say i turn down the highpass with the mouse from 25 to 18, i would like the touchscreen fader to reflect this change.
I have bomes pro as well, so if that would help with the midi in's and out's if needed, but is this possible?
thanks, really hope it is.
Multidirectional? Can usine have onscreen faders that act motorized?
Hi, and welcome aboard!
"Scenes" can be stored in two ways, either as presets within (sub-)patches using one the Preset Manager modules, or with snapshots in the Conductor which stores the whole patch grid. Some (I think) is also using the sequencer mode for similar purposes, jumping back and forth on the timeline, probably by using markers. Of course you could get value jumps when recalling presets/snapshots, but that's as expected I guess.
You can assign faders, knobs, buttons and switches to some MIDI message (typically a CC), and also configure Usine to send corresponding messages back for instance to update the faders on the BCF. Whether you move a fader on a touch screen with your finger or with a mouse doesn't matter. In fact, with the touch screen your finger movements are translated into mouse movements and as such they're the same to the OS. I don't have any BCF (or similar) controller myself, but a lot of other Usiners have and I don't think they have problems with value jumps. Guess you have to some configuring, though.
What is "bomes pro"?
"Scenes" can be stored in two ways, either as presets within (sub-)patches using one the Preset Manager modules, or with snapshots in the Conductor which stores the whole patch grid. Some (I think) is also using the sequencer mode for similar purposes, jumping back and forth on the timeline, probably by using markers. Of course you could get value jumps when recalling presets/snapshots, but that's as expected I guess.
You can assign faders, knobs, buttons and switches to some MIDI message (typically a CC), and also configure Usine to send corresponding messages back for instance to update the faders on the BCF. Whether you move a fader on a touch screen with your finger or with a mouse doesn't matter. In fact, with the touch screen your finger movements are translated into mouse movements and as such they're the same to the OS. I don't have any BCF (or similar) controller myself, but a lot of other Usiners have and I don't think they have problems with value jumps. Guess you have to some configuring, though.
What is "bomes pro"?
Bjørn S
thank you for the fast reply.
to answer your last question first, i should have wrote bomes 1.7 midi translator. it can make translations in both midi in and midi out that you can define with rules and timers etc. very awesome program.
i'm sorry I'm afraid I wasn't clear enough in the first post and as a result i confused you. I don't own a BCF2000 but I would like to make a bank of touchscreen faders that have the same properties as the mechanical faders on the BCF, ie they can move by themselves to reflect the values of different scenes. so i want to emulate a BCF2000 in the touchscreen interface of usine.
The part about the using the mouse. I'm confused you on what fader i was using the mouse on. let's say i have a synth vst that i am controlling the vol with touchscreen fader 1. let's say there is also a software volume knob in the vst, that is what the touchscreen fader1 is mapped to. let's say i move the software knob in the vst with my mouse down to nothing. I would like the touchscreen fader1 also to move down to nothing.
i believe this is called multidirectional or bidirectional midi. here is a youtube vid of the BCF2000 faders moving by themselves. http://www.youtube.com/watch?v=PICs-JRQ ... re=related
hope this makes more sense,
thanks kind welcome
to answer your last question first, i should have wrote bomes 1.7 midi translator. it can make translations in both midi in and midi out that you can define with rules and timers etc. very awesome program.
i'm sorry I'm afraid I wasn't clear enough in the first post and as a result i confused you. I don't own a BCF2000 but I would like to make a bank of touchscreen faders that have the same properties as the mechanical faders on the BCF, ie they can move by themselves to reflect the values of different scenes. so i want to emulate a BCF2000 in the touchscreen interface of usine.
The part about the using the mouse. I'm confused you on what fader i was using the mouse on. let's say i have a synth vst that i am controlling the vol with touchscreen fader 1. let's say there is also a software volume knob in the vst, that is what the touchscreen fader1 is mapped to. let's say i move the software knob in the vst with my mouse down to nothing. I would like the touchscreen fader1 also to move down to nothing.
i believe this is called multidirectional or bidirectional midi. here is a youtube vid of the BCF2000 faders moving by themselves. http://www.youtube.com/watch?v=PICs-JRQ ... re=related
hope this makes more sense,
thanks kind welcome
thanks, yes that appears to be what i'm looking for and it seems kinda easy even.
i'll have to try it out when i get a second.
ok time to learn more about this "Pass if has change."
i hope that this pass if has change can be used along with scenes to give me my "mechanical" touchscreen faders.
i'll have to try it out when i get a second.
ok time to learn more about this "Pass if has change."
i hope that this pass if has change can be used along with scenes to give me my "mechanical" touchscreen faders.
just tried setting up a little demo like the how to had it setup and it works great. thanks so much guys. got to check a couple other things but i think i might be getting usine!!!
be aware you could become addict, that's the only warning we could provide you 
yeah, that happens to the best of us......
so perhaps someone can help me get my head around this. so i would have modules of presets (or scenes) for fader1 and then it would be a matter of routing which "pass if has change" the fader is reacting to right? so if in scene1 fader1 was vol at 67 and scene2 fader1 lowpass filter at 23, there could a scene button that would activate the right "pass if has change" depending on what scene i was on? then the fader1 would jump to 67 when i selected scene1 and fader1 would jump to 23 when i selected scene2.
also how could i make it so, instead of a virtual knob in the vst I was changing with the mouse, what if i wanted to have say a button, that would start a delayed descent back to zero bringing the touchscreen fader down with it?
thanks
so perhaps someone can help me get my head around this. so i would have modules of presets (or scenes) for fader1 and then it would be a matter of routing which "pass if has change" the fader is reacting to right? so if in scene1 fader1 was vol at 67 and scene2 fader1 lowpass filter at 23, there could a scene button that would activate the right "pass if has change" depending on what scene i was on? then the fader1 would jump to 67 when i selected scene1 and fader1 would jump to 23 when i selected scene2.
also how could i make it so, instead of a virtual knob in the vst I was changing with the mouse, what if i wanted to have say a button, that would start a delayed descent back to zero bringing the touchscreen fader down with it?
thanks
hello and welcome
so here an example :
1_the button play a line module ( you can edit it ,and minimum and maximum values must be the same as your knob ) giving you a fade down on a knob
2_down you can see a fader ( fader 1 ) ---> a dispatch module , ( you can use an other fader to select the routing , here delay or drive )
if you add a preset module here it can save you different scenes...
so here an example :
1_the button play a line module ( you can edit it ,and minimum and maximum values must be the same as your knob ) giving you a fade down on a knob
2_down you can see a fader ( fader 1 ) ---> a dispatch module , ( you can use an other fader to select the routing , here delay or drive )
if you add a preset module here it can save you different scenes...
hello, and thank you for the welcome and the help.
1)thanks that rocks and the ideas of a lines module is great!!! but lets say i wanted the button to turn on when the knob was at full on, then i would need a "pass if change" but where from to the button? (the vst cutoff output?)
so for your 2nd example, the Fader 1 isn't going to change depending on the selected scene right?
so am i right in thinking there would still be an "Pass if has change" needed on the outputs of the dispatch?
1)thanks that rocks and the ideas of a lines module is great!!! but lets say i wanted the button to turn on when the knob was at full on, then i would need a "pass if change" but where from to the button? (the vst cutoff output?)
so for your 2nd example, the Fader 1 isn't going to change depending on the selected scene right?
so am i right in thinking there would still be an "Pass if has change" needed on the outputs of the dispatch?
Regarding 1): If I understand you correctly, what you want is not a button but a switch.
The two controls/modules act differently: A button's normal state is 0 (which can also be described as off or false), but when it's triggered (by mouse, key, midi) it first sends a 1 (on or true), directly followed by another 0. A switch, however. is either 0 or 1, and since VST parameters go from 0 to 1, connecting the knob (or a fader - they're the same except for appearance) to a math/trunc module and from that one through a PassIfChanged and back to the knob.
I don't quite get 2), but faders will normally be stored by the Preset Manager or the Conductor, unless you use the "Not stored in Conductor/Preset" option you find by right-clicking the control. Faders, list boxes and stuff like that which are used to select preset or snapshots are for obvious(?) reasons mostly best off not stored...
You might want to check out the Fade time option of the Conductor as well (it's only visible in the "normal" Conductor window). Maybe it's sufficent for what you need?
The two controls/modules act differently: A button's normal state is 0 (which can also be described as off or false), but when it's triggered (by mouse, key, midi) it first sends a 1 (on or true), directly followed by another 0. A switch, however. is either 0 or 1, and since VST parameters go from 0 to 1, connecting the knob (or a fader - they're the same except for appearance) to a math/trunc module and from that one through a PassIfChanged and back to the knob.
I don't quite get 2), but faders will normally be stored by the Preset Manager or the Conductor, unless you use the "Not stored in Conductor/Preset" option you find by right-clicking the control. Faders, list boxes and stuff like that which are used to select preset or snapshots are for obvious(?) reasons mostly best off not stored...
You might want to check out the Fade time option of the Conductor as well (it's only visible in the "normal" Conductor window). Maybe it's sufficent for what you need?
Bjørn S
yes, by what you are saying i would want a switch, other software programs call them both buttons, but differentiate between them by calling one toggle and one momentary.
i'm going to try to have a go at it with a fresh mind tomorrow and you'll probably be hearing from me with my questions.
i'll try to make it really simple what i'm looking for:
i want a fader1 that is controlling vst delay, decay and drive knobs through a dispatch module and present module. the scene selection will be done with a seperate knob1.
scene1 fader1 controls delay
scene2 fader1 controls decay
scene3 fader1 controls drive
let's just give values to each
scene1 equal to 10
scene2 equal to 50
scene3 equal to 89
i want it so when i move knob1 to scene1 then fader1 moves to match the vst delay value of 10. when i move knob1 to scene 2 then fader2 moves to match the vst decay value of 50. when i move knob1 to scene3 then fader1 moves to match the vst drive value of 89. with a physical controller you need mechanical/automated faders that can move to match their respective value in whatever scene they are in.
i'm going to try to have a go at it with a fresh mind tomorrow and you'll probably be hearing from me with my questions.
i'll try to make it really simple what i'm looking for:
i want a fader1 that is controlling vst delay, decay and drive knobs through a dispatch module and present module. the scene selection will be done with a seperate knob1.
scene1 fader1 controls delay
scene2 fader1 controls decay
scene3 fader1 controls drive
let's just give values to each
scene1 equal to 10
scene2 equal to 50
scene3 equal to 89
i want it so when i move knob1 to scene1 then fader1 moves to match the vst delay value of 10. when i move knob1 to scene 2 then fader2 moves to match the vst decay value of 50. when i move knob1 to scene3 then fader1 moves to match the vst drive value of 89. with a physical controller you need mechanical/automated faders that can move to match their respective value in whatever scene they are in.
if well understood, this is one solution:
(the curve is made of 2 points, the fader value, and the "to reach" value.
avoid wiring:
http://www.sensomusic.com/forums/upload ... values.pat
but maybe you need to check the conductor/preset manager feature also, offer simple way to store and recall various status...
if fact the question is do you want the changes to be instantaneous (then better use conductor/preset manager) of does it need smooth time (then like this exemple)
(the curve is made of 2 points, the fader value, and the "to reach" value.
avoid wiring:
http://www.sensomusic.com/forums/upload ... values.pat
but maybe you need to check the conductor/preset manager feature also, offer simple way to store and recall various status...
if fact the question is do you want the changes to be instantaneous (then better use conductor/preset manager) of does it need smooth time (then like this exemple)
I misunderstood what you meant by a "scene". For me a "scene" or a "snapshot" in this context means an "über-preset" for a whole mixer or something like that, just like what the Conductor does in Usine.
Anyway, here's another, simple example of how you can use one control to select what another will update on a VST. I've used a list box instead of a knob so that the fader caption can be updated. Since list/combo boxes starts counting from 0, I've added +1 to control the dispatcher and the selector. With a knob or a fader you would probably just set min=1.
In this example, the fader will be updated to the current value of the VST parameter when the list box changes. However, one thing to keep in mind is that the Preset Manager or the Conductor would store the whole thing "as is", so you would have to set the parameters currently not selected by the list box to their correct values before storing.
[edit]:
I've uploaded the patch as well: http://www.sensomusic.com/forums/upload ... params.pat
Anyway, here's another, simple example of how you can use one control to select what another will update on a VST. I've used a list box instead of a knob so that the fader caption can be updated. Since list/combo boxes starts counting from 0, I've added +1 to control the dispatcher and the selector. With a knob or a fader you would probably just set min=1.
In this example, the fader will be updated to the current value of the VST parameter when the list box changes. However, one thing to keep in mind is that the Preset Manager or the Conductor would store the whole thing "as is", so you would have to set the parameters currently not selected by the list box to their correct values before storing.
[edit]:
I've uploaded the patch as well: http://www.sensomusic.com/forums/upload ... params.pat
Bjørn S
Clever patching Bsork as usual!
Seb.Dub
you guys are great. thank you. downloaded the pat files and going to try it.
very clever indeed. the more i look at this program the more impressed i am by it. the community around it is nothing short of amazing, it is inspiring.
very clever indeed. the more i look at this program the more impressed i am by it. the community around it is nothing short of amazing, it is inspiring.
well i tried Bsork's on my vista desktop and the decay, cutoff, and resonance faders respond to vst knob movements made by the mouse, but the when i go from one preset to another, the fader position doesn't change. so if cutoff is at .27 and delay is at 76, and i'm currently on the cutoff scene when i change to delay, the delay value changes to .27 and likewise when i select resonance it's value changes to .27
is that how yours works too or is my install on this vista computer messed up or am i completely confusing everyone?
i appreciate the help.
EDIT: maybe i don't have it setup right or am missing something.
can someone explain what this means "However, one thing to keep in mind is that the Preset Manager or the Conductor would store the whole thing "as is", so you would have to set the parameters currently not selected by the list box to their correct values before storing."
thanks
is that how yours works too or is my install on this vista computer messed up or am i completely confusing everyone?
i appreciate the help.
EDIT: maybe i don't have it setup right or am missing something.
can someone explain what this means "However, one thing to keep in mind is that the Preset Manager or the Conductor would store the whole thing "as is", so you would have to set the parameters currently not selected by the list box to their correct values before storing."
thanks
I think you need to press "S" store on the preset manager and click the preset nb. (first set your values on scene 1, press "S" and preset 1, then go to scene 2, adjust your values, press "S" and preset 2 ect... then swiching presets should recall respecting values.
in other words, the preset manager will make a recallable snapshot of all your parameter (scene 1: fader at 10, list box at 1 so routed to delay , scene 2: fader at 50, list box at 2 so routed to decay ect...)
in other words, the preset manager will make a recallable snapshot of all your parameter (scene 1: fader at 10, list box at 1 so routed to delay , scene 2: fader at 50, list box at 2 so routed to decay ect...)
thanks let me try that.23fx23 wrote:I think you need to press "S" store on the preset manager and click the preset nb. (first set your values on scene 1, press "S" and preset 1, then go to scene 2, adjust your values, press "S" and preset 2 ect... then swiching presets should recall respecting values.
in other words, the preset manager will make a recallable snapshot of all your parameter (scene 1: fader at 10, list box at 1 so routed to delay , scene 2: fader at 50, list box at 2 so routed to decay ect...)
wait where is the S ? thanks, sorry usine makes me feel kinda slow sometimes....
the preset manager is a module found in modules/interface control, drop it in your pach, set all the values for your preset, press the S, then preset nb 1to16. once youve made all your preset they will be recalled clicking on their respective nb, you can add a listbox/fader/knob to control preset nb, but you will have to display it in the interface builder, right click on it and check "not stored in preset manager", otherwise it will make a loop.
don't worry it takes a few weeks to understand usine possibilities (endless) but don't forget to read the help, helped me a lot -
cheers
i'm not quite getting it setup correctly. anyone mind putting it together quick and making a pat file for me to try. thanks alot.
just download Bsork latest pach, and just add a preset manager (modules/interface control), set your list box and fader for scene 1 (example list box is 1,fader 10, press S on the preset manager and 1 on the preset manager(like the picture above). then change your list box and fader to what they should be in scene 2(exemple list is 2 and fader 50), press S on the pm and 2..
then if you click on the preset manager nb 1, the list box will automatically go for1, the fader for 10, if you press 2, they'll take the values you stored in 2 ect..
then if you click on the preset manager nb 1, the list box will automatically go for1, the fader for 10, if you press 2, they'll take the values you stored in 2 ect..
Who is online
Users browsing this forum: Bing [Bot] and 159 guests