26 Aug
2010
26 Aug
'10
9:23 p.m.
Hi all,
I do have a question for all the midi-freaks:
I have a korg nanokontrol and would like to use it to control a mixer
(behringer ddx, not my own). For faders this works quite well, for the mute-
buttons I am stumped:
The ddx wants ctrl 104 with the channel as value to mute and ctrl 105 with the
channel to unmute.
The nanokontrol can only send one controller with two different values per
button.
So I thought about making the nanokontrol send the channel as controller and
104 as value for mute 105 for unmute. And then use a midifilter to switch ctrl-
number and value before sending it to the ddx.
And this is where the fun begins.
midish is not able to do that (at least I couldn't make it work during one
evening).
qmidiroute is not able to do that (at least I couldn't make it work during one
evening).
puredata is not able to do this. While it is easy to connect ctlin with ctlout
and switch ctrl and value, it sometimes uses the value from the event before
and I couldn't get that to work either... (If some pd crack can give me a
hint, I am very open to that, the problem seems to be that the events are
passed/handled in the wrong order.)
Is there any other easy midi-router / -filter that even thinks about these use
cases? (Note: I didn't yet try pidim...)
Thanks for your answers,
Arnold
26 Aug
26 Aug
9:46 p.m.
On Thu, 26 Aug 2010 21:23:14 +0200
Arnold Krille <arnold(a)arnoldarts.de> wrote:
Hi all,
I do have a question for all the midi-freaks:
I have a korg nanokontrol and would like to use it to control a mixer
(behringer ddx, not my own). For faders this works quite well, for the mute-
buttons I am stumped:
The ddx wants ctrl 104 with the channel as value to mute and ctrl 105 with the
channel to unmute.
The nanokontrol can only send one controller with two different values per
button.
So I thought about making the nanokontrol send the channel as controller and
104 as value for mute 105 for unmute. And then use a midifilter to switch ctrl-
number and value before sending it to the ddx.
And this is where the fun begins.
midish is not able to do that (at least I couldn't make it work during one
evening).
qmidiroute is not able to do that (at least I couldn't make it work during one
evening).
puredata is not able to do this. While it is easy to connect ctlin with ctlout
and switch ctrl and value, it sometimes uses the value from the event before
and I couldn't get that to work either... (If some pd crack can give me a
hint, I am very open to that, the problem seems to be that the events are
passed/handled in the wrong order.)
Is there any other easy midi-router / -filter that even thinks about these use
cases? (Note: I didn't yet try pidim...)
Thanks for your answers,
Arnold
If I understand you right, this comes down to a MIDI 'translator' that
can identify a specific command and exchange it for a specific
alternative. This would seem in theory (haha) to simply require a pair
of linked editable look-up tables.
I would *very* much like to see this, and don't have a clue how to
implement it myself :(
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
11:31 p.m.
Hi,
On Thursday 26 August 2010 21:46:17 Folderol wrote:
On Thu, 26 Aug 2010 21:23:14 +0200
Arnold Krille <arnold(a)arnoldarts.de> wrote:
Actually (I am a programmer, not a guy looking into lists:) its "just" a
matter of "switch controller number and its value and send it on". Bonus
points for "if the controller number is greater then 62, subtract 62, switch
controller number and value and send it on, otherwise just send it on". That
way you can also have the volume faders (sending controllers <62) control the
faders of the ddx.
BTW: One cool feature of the ddx is that each channel is controllable, not
each "front-side" fader. I used that to control the faders of channels 17-24
which had the "unimportant" keys, while the ddx was constantly showing the
first 16 channels where the more difficult channels where located...
Have fun,
Arnold
I do have a question for all the midi-freaks:
I have a korg nanokontrol and would like to use it to control a mixer
(behringer ddx, not my own). For faders this works quite well, for the
mute- buttons I am stumped:
The ddx wants ctrl 104 with the channel as value to mute and ctrl 105
with the channel to unmute.
The nanokontrol can only send one controller with two different values
per button.
So I thought about making the nanokontrol send the channel as controller
and 104 as value for mute 105 for unmute. And then use a midifilter to
switch ctrl- number and value before sending it to the ddx.
And this is where the fun begins.
midish is not able to do that (at least I couldn't make it work during
one evening).
qmidiroute is not able to do that (at least I couldn't make it work
during one evening).
puredata is not able to do this. While it is easy to connect ctlin with
ctlout and switch ctrl and value, it sometimes uses the value from the
event before and I couldn't get that to work either... (If some pd crack
can give me a hint, I am very open to that, the problem seems to be that
the events are passed/handled in the wrong order.)
Is there any other easy midi-router / -filter that even thinks about
these use cases? (Note: I didn't yet try pidim...)
Thanks for your answers,
If I understand you right, this comes down to a MIDI
'translator' that
can identify a specific command and exchange it for a specific
alternative. This would seem in theory (haha) to simply require a pair
of linked editable look-up tables.
I would *very* much like to see this, and don't have a clue how to
implement it myself :( 
27 Aug
27 Aug
2:49 p.m.
On Thu, Aug 26, 2010 at 11:31 PM, Arnold Krille <arnold(a)arnoldarts.de> wrote:
Actually (I am a programmer, not a guy looking into
lists:) its "just" a
matter of "switch controller number and its value and send it on".
mididings has already been suggested. It has a somewhat steep learning
curve, but it'll convert any MIDI event (almost) any way you like.
To simply swap controller number and value, run this in a shell:
mididings "Ctrl(EVENT_VALUE, EVENT_PARAM)"
Bonus points for "if the controller number is
greater then 62, subtract 62, switch
controller number and value and send it on, otherwise just send it on".
One of many ways to do that:
CtrlFilter(range(63, 128)) % (
Chain(CtrlMap(n, n-62) for n in range(63, 128))
> Ctrl(EVENT_VALUE, EVENT_PARAM)
)
Cheers,
Dominic
26 Aug
26 Aug
10:37 p.m.
Le jeudi 26 août 2010 à 21:23 +0200, Arnold Krille a écrit :
Hi all,
I do have a question for all the midi-freaks:
I have a korg nanokontrol and would like to use it to control a mixer
(behringer ddx, not my own). For faders this works quite well, for the mute-
buttons I am stumped:
The ddx wants ctrl 104 with the channel as value to mute and ctrl 105 with the
channel to unmute.
The nanokontrol can only send one controller with two different values per
button.
So I thought about making the nanokontrol send the channel as controller and
104 as value for mute 105 for unmute. And then use a midifilter to switch ctrl-
number and value before sending it to the ddx.
And this is where the fun begins.
midish is not able to do that (at least I couldn't make it work during one
evening).
qmidiroute is not able to do that (at least I couldn't make it work during one
evening).
puredata is not able to do this. While it is easy to connect ctlin with ctlout
and switch ctrl and value, it sometimes uses the value from the event before
and I couldn't get that to work either... (If some pd crack can give me a
hint, I am very open to that, the problem seems to be that the events are
passed/handled in the wrong order.)
Is there any other easy midi-router / -filter that even thinks about these use
cases? (Note: I didn't yet try pidim...)
Thanks for your answers,
Arnold
If the matter is to swap a controller parameter with its value,
i can luckily code that now. Would the process be:
if (event_type == CONTROLLER) {
if (event_channel == channel_to_work_on) {
if (event_param == controller_to_work_on) {
swap = event_value;
event_value = event_param;
event_param = swap;
}
}
}
?
- Benoît
11:35 p.m.
On Thursday 26 August 2010 22:37:05 Benoît Rouits wrote:
Le jeudi 26 août 2010 à 21:23 +0200, Arnold Krille a
écrit :
Yes. And in which app/frame-work do I program that?
Note that I am very capable of writing the code myself, it just surprises me
that many "flexible" midi-routers exist but none can fulfill these simple(?)
task. Or in the case of pd can't fulfill it reliably.
I didn't think this task would require me to write my own midi-router. (Which
I would probably name "yet another flexible midi router that is actually
flexible" or yafmrtiaf.)
Have fun,
Arnold
Hi all,
I do have a question for all the midi-freaks:
I have a korg nanokontrol and would like to use it to control a mixer
(behringer ddx, not my own). For faders this works quite well, for the
mute- buttons I am stumped:
The ddx wants ctrl 104 with the channel as value to mute and ctrl 105
with the channel to unmute.
The nanokontrol can only send one controller with two different values
per button.
So I thought about making the nanokontrol send the channel as controller
and 104 as value for mute 105 for unmute. And then use a midifilter to
switch ctrl- number and value before sending it to the ddx.
And this is where the fun begins.
midish is not able to do that (at least I couldn't make it work during
one evening).
qmidiroute is not able to do that (at least I couldn't make it work
during one evening).
puredata is not able to do this. While it is easy to connect ctlin with
ctlout and switch ctrl and value, it sometimes uses the value from the
event before and I couldn't get that to work either... (If some pd crack
can give me a hint, I am very open to that, the problem seems to be that
the events are passed/handled in the wrong order.)
Is there any other easy midi-router / -filter that even thinks about
these use cases? (Note: I didn't yet try pidim...)
Thanks for your answers,
Arnold
If the matter is to swap a controller parameter with its value,
i can luckily code that now. Would the process be:
if (event_type == CONTROLLER) {
if (event_channel == channel_to_work_on) {
if (event_param == controller_to_work_on) {
swap = event_value;
event_value = event_param;
event_param = swap;
}
}
}
11:57 p.m.
Le jeudi 26 août 2010 à 23:34 +0200, Arnold Krille a écrit :
Yes. And in which app/frame-work do I program that?
None, it is already (and freshly) done in Pidim revision 18.
The program is called pidim_ctrl_swap you can check out it by:
$ svn co https://herewe.servebeer.com/svn/pidim
$ more README
#install required libraries and dev files
$ ./autogen.sh
$ ./configure
$ make && sudo make install
$ pidim_ctrl_swap [instance_name_or_simply_number]
On Thursday 26 August 2010 22:37:05 Benoît Rouits
wrote:
> Le jeudi 26 août 2010 à 21:23 +0200, Arnold Krille a écrit :
> > Hi all,
> >
> > I do have a question for all the midi-freaks:
> >
> > I have a korg nanokontrol and would like to use it to control a mixer
> > (behringer ddx, not my own). For faders this works quite well, for the
> > mute- buttons I am stumped:
> > The ddx wants ctrl 104 with the channel as value to mute and ctrl 105
> > with the channel to unmute.
> > The nanokontrol can only send one controller with two different values
> > per button.
> >
> > So I thought about making the nanokontrol send the channel as controller
> > and 104 as value for mute 105 for unmute. And then use a midifilter to
> > switch ctrl- number and value before sending it to the ddx.
> >
> > And this is where the fun begins.
[...]
Thanks for your answers,
Arnold
If the matter is to swap a controller parameter with its value,
i can luckily code that now. Would the process be:
if (event_type == CONTROLLER) {
if (event_channel == channel_to_work_on) {
if (event_param == controller_to_work_on) {
swap = event_value;
event_value = event_param;
event_param = swap;
}
}
} Note that I am very capable of writing the code
myself, it just surprises me
that many "flexible" midi-routers exist but none can fulfill these simple(?)
task. Or in the case of pd can't fulfill it reliably.
Pd would probably do the trick, but it is a foreign realm to me.
I didn't think this task would require me to write
my own midi-router. (Which
I would probably name "yet another flexible midi router that is actually
flexible" or yafmrtiaf.)
:-)
Have fun,
Arnold
27 Aug
27 Aug
9:33 a.m.
On 2010-08-26 23:34, Arnold Krille wrote:
Yes. And in which app/frame-work do I program that?
I've done things like that with pyseq (and python obviously). It's quite
easy to get going...
--
Atte
http://atte.dk http://modlys.dk
26 Aug
26 Aug
11:33 p.m.
On Thu, Aug 26, 2010 at 12:23 PM, Arnold Krille <arnold(a)arnoldarts.de>
wrote:
Is there any other easy midi-router / -filter that
even thinks about these
use
cases? (Note: I didn't yet try pidim...)
http://das.nasophon.de/mididings/
///////////////////////////////////
///////////////////////////////////
///////////////////////////////////
mididings is a MIDI router and processor based on Python, supporting ALSA
and JACK MIDI. It is available under the GNU GPL and currently runs on
Linux.
Features:
MIDI routing and filtering
Filter events depending on their event type, channel, note number, velocity,
etc., and freely route them between an arbitrary number of input and output
ports.
Modifying and converting MIDI events
Transpose notes, apply velocity curves, change controller values and ranges,
or convert events to any other MIDI event type. mididings also includes more
complex functions like a diatonic harmonizer, floating split points, latched
notes, and more.
Seamless switching between patches
Set up different "scenes", each with its own MIDI routing and processing,
and switch between them at any time, even while playing. Switching scenes
does not affect notes already held, and does not result in dropouts or stuck
notes!
MIDI event monitoring, running external commands
Print MIDI event data to the console to help debugging your patches and
configuring your MIDI controllers. In addition to its MIDI output, mididings
can also execute shell commands and send OSC or DBUS messages.
///////////////////////////////////
///////////////////////////////////
///////////////////////////////////
Niels
http://nielsmayer.com
PS: as a recent convert to Vala ( http://spekle.googlecode.com ) I wish
there was a http://live.gnome.org/Genie version of mididings ...
11:44 p.m.
On Thu, 26 Aug 2010 14:33:47 -0700
Niels Mayer <nielsmayer(a)gmail.com> wrote:
On Thu, Aug 26, 2010 at 12:23 PM, Arnold Krille
<arnold(a)arnoldarts.de>
wrote:
Wow! That ticks ALL the boxes!
Even has both Jack and Alsa MIDI :)
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Is there any other easy midi-router / -filter
that even thinks about these
use
cases? (Note: I didn't yet try pidim...)
http://das.nasophon.de/mididings/
///////////////////////////////////
///////////////////////////////////
///////////////////////////////////
mididings is a MIDI router and processor based on Python, supporting ALSA
and JACK MIDI. It is available under the GNU GPL and currently runs on
Linux.
Features:
MIDI routing and filtering
Filter events depending on their event type, channel, note number, velocity,
etc., and freely route them between an arbitrary number of input and output
ports.
Modifying and converting MIDI events
Transpose notes, apply velocity curves, change controller values and ranges,
or convert events to any other MIDI event type. mididings also includes more
complex functions like a diatonic harmonizer, floating split points, latched
notes, and more.
Seamless switching between patches
Set up different "scenes", each with its own MIDI routing and processing,
and switch between them at any time, even while playing. Switching scenes
does not affect notes already held, and does not result in dropouts or stuck
notes!
MIDI event monitoring, running external commands
Print MIDI event data to the console to help debugging your patches and
configuring your MIDI controllers. In addition to its MIDI output, mididings
can also execute shell commands and send OSC or DBUS messages.
///////////////////////////////////
///////////////////////////////////
///////////////////////////////////
Niels
http://nielsmayer.com
PS: as a recent convert to Vala ( http://spekle.googlecode.com ) I wish
there was a http://live.gnome.org/Genie version of mididings ... 
27 Aug
27 Aug
6:54 a.m.
On Fri, Aug 27, 2010 at 4:23 AM, Arnold Krille <arnold(a)arnoldarts.de> wrote:
Hi all,
puredata is not able to do this. While it is easy to connect ctlin with
ctlout
and switch ctrl and value, it sometimes uses the value from the event
before
and I couldn't get that to work either... (If some pd crack can give me a
hint, I am very open to that, the problem seems to be that the events are
passed/handled in the wrong order.)
I'm by no means a pd crack, but I believe there are a number of ways to get
this done in pd. I'd be inclined to use a a pack object to ensure all event
values are coupled with their controller number. You can then use a route
object to split the toggle states of your nanokontrol button presses into
ctlout 104 or ctlout 105 triggers, with the appropriate values assigned. The
attached patch seems to work for me, assuming your hi/low toggle values for
your buttons are set to 127/0.
-mjn
5231
days inactive
5232
days old
linux-audio-user@lists.linuxaudio.org
10 comments
7 participants
participants (7)
-
Arnold Krille -
Atte André Jensen -
Benoît Rouits -
Dominic Sacré -
Folderol -
michael noble -
Niels Mayer