PlanetZ forums - scopeusers.com

Thanx Shayne. I will crashtest the thing today.

Hi Shayne. Nice job with the switch. It still doesn´t solve the problem we have. We need to have a (midi controlled)button per channel. With your switch it´s still only possible to go from channel 1 to 8 with a CC signal( 0 - 127).

Your switch reminds (with some modifications) of "switch it". See our earlier post.

Thanx.

yeah, for the application requested each channel needs a gate (or 0/127 volume) switch controlled by a CC that toggles between 0 and 127.
If a channel is selected and goes ON all the others have to go OFF.
Imho it's not that simple - a logic table like
if 1 is on, then 2,3,4,5,6,7,8 off
if 2 is on, then 1,3,4,5,6,7,8 off
etc
appeared as most easy to me.

cheers, Tom
ps: this one could be really nice for A/B ing because it has a level control, very useful.


<font size=-1>[ This Message was edited by: astroman on 2005-02-13 20:55 ]</font>

But I don't see how a MIDI on/off switch (0/127) is going to get you to switch between 8 inputs. How is that going to work?

very simple: if one channel receives the 'activation' controller, it 'bounces' the inverse controller to all the others. See above

cheers, Tom

Well spoken, Astroman!

@Shayne: Each channel should have it´s own individual switch. Only one switch can be on at a time. Your switch looks great and works great, if the on/off button problem that Astroman adressed could be solved, then we would be forever greatfull. If you wan´t something for your trouble, let me know.

BTW - isn´t possible to download SDK anywhere? Would be great if I could be a contributer instead of just a user.

<font size=-1>[ This Message was edited by: omnibounce on 2005-02-14 02:14 ]</font>

Ok, I'll see what I can do...but one question: how does your button operate? Does it send out a 127 signal and then immediately a 0? (Some buttons in Scope send out a 1 signal and then immediately a 0.) Or do you press your button once to go to 127 and then another time to go to 0? I need to know how your button operates.

I'm not sure if I'll be able to come up with anything, but I'll try!

It all really depends on the buttonmode on the controller. The switch we would prefer responds to one press to make a channel go "on" (holding 127) and when the a new button is activateted (on the midicontroller) the previous channel goes "off" (holding 0) and the new channel is activated. Kind of "or" in the electronics world, if you know what i mean.

But to make a long story short: the controller puts out and holds "127" when activated. When pressed again it sends "0".


If you need some instead messaging i´m at msn jesperulrich@mail.dk

Thanx.

Hi,

you could try my switches (8x and 4x switch).
The buttons are midi controllable.
You can find them at http://www.worldless.com/sfp/hd.html

cheers
Wolfgang

On 2005-02-14 02:11, omnibounce wrote:
...
BTW - isn´t possible to download SDK anywhere? Would be great if I could be a contributer instead of just a user.

if you own a 14/15 DSP card you automatically qualify for the SDK, otherwise not at all.
You will have to sign a non-disclosure agreement which has to be physically mailed to CWA (in paper form) and they'll send you a CD.

Wolf's switches have the same on/off toggle problem. They could be used, but before switching to a new channel you have to tap off the previously selected. Dunno if that's possible for the singer without visual feedback on stage...

cheers, tom

On 2005-02-14 02:40, omnibounce wrote:
It all really depends on the buttonmode on the controller. The switch we would prefer responds to one press to make a channel go "on" (holding 127) and when the a new button is activateted (on the midicontroller) the previous channel goes "off" (holding 0) and the new channel is activated. Kind of "or" in the electronics world, if you know what i mean.

But to make a long story short: the controller puts out and holds "127" when activated. When pressed again it sends "0".

OK, I think I get it: you have several buttons, and when you press one, another goes off, right? Then I think the STM-1632 might work. It's a mixer, but it has solo buttons, and they're MIDI controllable.

Shayne... to help you out...

like the solo on the STM 1632 if and ONLY IF the 'kill solo' button is (automatically) triggered immediately before the solo button's action starts.
In other words: you click solo, the click is intercepted and send to the 'kill solo' button, which releases the previous (if any) solo, and then the 'clicked' solo is executed.

cheers, Tom

That is a "solo in place" (in Cubase terms), isnt it?

Well, I'm sorry, but I can't make such a device for you. My knowledge of the SDK isn't that advanced, and I have no idea how to do solo or kill solo or anything related to solo. I apologize.

Shayne

Hi Shayne,
How about this:
-------------------------------------------
8:1Mux (audio Mux Modeling)
____
ANI0
ANI1 |
ANI2 |>> AOUT
...........|
ANI7 /
____/
^
|||
SEL[2:0] (From De-MUX)
--------------------------------------------


8:3 DeMUX (Modeling with Latches output)
____
SW0
SW1 |
SW2 | >> SEL[2:0] (Connected to MUX)
...........|
SW7 /
____/
----------------------------------------------
Notes:
ANIX: Audio Inputs Multiplexer, where X is 0 to 7.
AOUT: Audio Output Multiplexer.
SWX: Switches Button (GUI), where X = 0 to 7 as the User Selection inputs.
Each switches should has the Attached MIDI channels assignment.
Then the output SEL0-2 will connect to the 8:1 Multiplexer SELECTION (MUX8:1's SEL[2:0]).

Option: The MIDI selection can has the conjunction with the 8:3 De-Multiplexer.
So that the MIDI Channels/Switches automatically selected per the SWX changed/Selected as needed.

Restriction: With default value (no selection) and deboucing circuitry + timer per mili-second for the Switches would be nice.

--------------------------------------------
I do not have the SDK but someone has?
Can we do this? Anyone?
Does the Logical Block Diagram here work that what you want?
--------------------------------------------

LongStudio


<font size=-1>[ This Message was edited by: LHong on 2005-02-16 22:32 ]</font>

On 2005-02-16 23:49, hubird wrote:

LOL

yeah, poor Shayne

You don't really need to debounce anything within the SDK =P. Also you don't need to have 3 input bits to select, a single value will do fine. But should be do-able yeah, I've done MUX/DEMUX with async modules, shouldn't be too hard to do with sync signals. It won't really help with the problem at hand tho, unless you have a pedal that sends CC values and not just gates, then I guess you can associate ranges of CC values for each selection (i.e. CC 0-7 is input 1, 8-15 is input 2, etc.)

Anyway, I have a small design that might do that you want. Single MIDI input, single audio input, 8 audio output, the CC# (not the value) you send would let you switch between the outputs. So you could have 8 pedals sending out CC gates (0 or 127), you'd only need to press a single pedal to switch on the associated audio output and shutdown the previously activated output. Would that work? I'm not home so I can't try it now, I'll try to whip up a quick beta tonite.

Alternatively I could have it switch based on CC value or MIDI channel, or even note number (or any other standard (and non-standard too) MIDI message.)

More news when I get something functionnal.

Symbiote,
Sounds interesting...
I know you can do better!
There are various ways you can implement such the Controllable MIDI device for Audio switches by the MIDI event Filter. As long as it has the MIDI attached to the switches then we can do a lot. To activate the simple parameter changed, you can detect the values greater than 0 = TRUE, otherwise = FALSE. It Does not matter Gate or CC Events!

In addition, if you can have the SW0-7/8-N GUI changed interactively with the External MIDI controller would be nice. Other is when we hold down the foot-switch or MIDI-Note, say more 2-5 secs then it will automatically selected (increment) to next SWX controller and so on, for example...
It does not matter Keyboard, Foot-switch or other MIDI compatible controller.

Just a thought,

LongStudio