On Tue, Mar 4, 2014 at 1:07 PM, Stefan Gofferje <[email protected]> wrote:
>
> Hei,
>
> On 03/04/2014 10:19 PM, J. Liles wrote:
> > Sounds cool. I know there are some podcasters out there using Non Mixer.
> > Maybe someone with experience will chime in. You might also ask on the
> > linuxmusicians forums.
>
> Gotta check this out.
>
> > You have to 'bind' module parameters to controls first. So open the
> > module parameter editor for the monopan (or whatever) right click on the
> > control and choose 'bind'. Then, on the 'controls' view, you will see
> > that the controls listed there are enabled for learning. Over
> > complicated you say? Maybe, but there has to be *something* to
> > associated the learning to and this is how it works currently.
>
> Ok... Is there a way to manually assign MIDI channels to controls? :D


Not really. This is taken care of by the learning process. You can
manually edit the project files of the non-midi-mapper program (which
acts as the MIDI<->OSC gateway in this scenario) though.

>
>
> > If you are using a hardware MIDI controller, it should be trivial to
> > reprogram it to invert the meaning of the LED for the mute button. I
> > believe one can do this on e.g the BCF2000.
> >
> > But it sounds like maybe what you're really looking for is a 'solo'
> > button? If so, it's already on the TODO list...
>
> No, actually, the "Select" or "On" button on BC mixers is pretty much an
> inverted "Mute" button. But not 100% exactly, because historically, BC
> mixers have different buses, e.g. for talking to the producer in the
> control room or for talking to guests in the studio off air. So
> precisely spoken, that "On" button is more like a "Send to broadcast
> bus" button. Some BC mixers additionally have a "Mute" button in the
> strip which kills the signal pre-fader, means that input would be muted
> on all buses at the same time.
>
> From this point of view, a "Select" module with a button in the fade
> view would be beneficial to people who are used to BC workflows.


Maybe. I need more justification than that though, because it sounds
like it would just confuse everyone else (myself included). I'd
suggest using NM as is for the work you're doing and then maybe
submitting another feature request with more information. I'm sure we
can come up with something that will work.

>
>
> > Connections will not be saved in the project. If you use NSM and
> > jackpatch, then jackpatch will save the connections.
> >
> > There are two methods of making/breaking connections in non-mixer. Drag
> > n' drop from the connection plug icons on the JACK modules, or using the
> > auto input/autoconnect rules (found in the context menu that comes up
> > when you right-click on a strip). I'm afraid this is not documented yet.
> > For anything really complex you're better off managing it in Patchage or
> > similar anyway (but the auto connect feature works quite well for most
> > mixes).
>
> Ok, I'll play around with that some more. However a double- or
> right-click dropdown would be a very simple solution (for the user).


You mean a context menu to select a port to connect to? Yeah, that's
on my list. I thought the Drag and Drop thing would be cool, but it
didn't turn out to be all that useful. Context menus stop being useful
pretty quickly as the number of JACK ports increases though.

>
>
> > Yeah, I've thought about doing that. I rarely use mono pan myself,
> > preferring ambisonics. Feel free to submit a feature request here:
> >
> > https://github.com/original-male/non/issue
> >
> > Otherwise I'm likely to forget about it.
>
> https://github.com/original-male/non/issues/108
>
> >     Is there a list of MIDI-controllers which are known to work with
> >     NON-mixer and NON-timeline? How about feedback? Does NON-mixer know how
> >     to send values back to a MIDI-controller to control e.g. motorized
> >     faders?
> >
> >
> > Yes it sends feedback. I only have a BCF2000 (which works wonderfully).
> > MIDI is MIDI though, so pretty much anything should work.
>
> Very cool, I was actually looking at the X-Touch Compact because it
> already has a pretty "broadcasty" layout :). Does the Behringer USB-MIDI
> interface work in Linux or do you use an additional MIDI-interface?


The BCF2000 works just fine over USB, in fact in the case of Non,
that's the preferred method of connection because you can have
multiple BCF2000s connected without them interfering with one another
(great care must be taken of course when daisy chaining actually MIDI
connections to avoid CC # collisions).

That X-Touch looks pretty cool. I like the jog wheel. However, BCF2000
works fine and can be found waaaaay cheaper (I got mine for ~$50).


Reply via email to