2 Apr
2003
2 Apr
'03
3:48 p.m.
Hello,
I just started playing around with RTMix. But I can't figure out the real-time MIDI
stuff in RTMix. I've set it up to read from the correct MIDI port. The MIDI is
working and MIDI logging enables me to see incoming MIDI. However, MIDI events seem not
to trigger any action. I'm probably missing some basic understanding...
this line:
text([>say]={"MIDI received"} [>at]={"rt[0]"}
[>kill]={"none"} [>accel]={"midi: 128, 255, 0, 127, -1,
127"});;
doesn't print 'MIDI received' no matter what I do. With MIDI logging on I can
see all sorts of midi messages flying by. The same thing using
[>accel]={"a"}, for instance, works as expected.
Also, I was under the impression that if I filter MIDI events the log will only display
the events that get through. However, the line below results in the exact same log as the
log above.
text([>say]={"MIDI received"} [>at]={"rt[0]"}
[>kill]={"none"} [>accel]={"midi: 144, 144, 0, 127, -1,
127"});;
I'm lost.
./MiS
--
_
__ __ (_)___ Michal Seta
/ \/ \ _/^ _|
/ V |_ \ @creazone.32k.org
(___/V\___|_|___/
http://www.[creazone]|[noonereceiving].32k.org
2 Apr
2 Apr
11:18 p.m.
Hi there!
Just to make sure, you want this text to be displayed on the
_notification interface_ (main black widget on the 1st tab of the main
window) or in the console?
Text events display _exclusively_ on the Notification interface, so it
can be used for performance settings. Console displays and logs overall
activity information/errors etc. (in that respect it is different from
jMax/Max Console) -- it's kind of a debugger in that respect.
If you want the Console to be verbose about your triggered events, but
do not want to see logged MIDI data, make sure to enable the "VERBOSE"
button found on the real-time tab and disable MIDI LOGGING button. This
may, however hinder your real-time performance (which is fixed in the
current dev version by threading the whole console separately).
Midi logging is there more for debugging purposes than for a performance
(so that you can see whether your events are being triggered as they
should be).
Now, onto your problem:
I tried running just the first line in my RTMix (ver. 0.72 that you
prolly have, which is the last released version -- if you don't have
this version, please get it to ensure we're on the same page :-), and
the "MIDI received" message shows up without any problems in the
_notification interface_, not the console (which is as expected).
Hope this helps!
Ico
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-
admin(a)music.columbia.edu] On Behalf Of Michal Seta
Sent: Wednesday, April 02, 2003 1:41 PM
To: linux-audio-user(a)music.columbia.edu
Subject: [linux-audio-user] RTMix & MIDI
Hello,
I just started playing around with RTMix. But I can't figure out the
real-time MIDI stuff in RTMix. I've set it up to read from the
correct
MIDI port. The MIDI is working and MIDI logging
enables me to see
incoming MIDI. However, MIDI events seem not to trigger any action.
I'm
probably missing some basic understanding...
this line:
text([>say]={"MIDI received"} [>at]={"rt[0]"}
[>kill]={"none"}
[>accel]={"midi: 128, 255, 0, 127, -1, 127"});;
doesn't print 'MIDI received' no matter what I do. With MIDI logging
on I
can see all sorts of midi messages flying by. The
same thing using
[>accel]={"a"}, for instance, works as expected.
Also, I was under the impression that if I filter MIDI events the log
will
only display the events that get through. However,
the line below
results
in the exact same log as the log above.
text([>say]={"MIDI received"} [>at]={"rt[0]"}
[>kill]={"none"}
[>accel]={"midi: 144, 144, 0, 127, -1, 127"});;
I'm lost.
./MiS
--
_
__ __ (_)___ Michal Seta
/ \/ \ _/^ _|
/ V |_ \ @creazone.32k.org
(___/V\___|_|___/
http://www.[creazone]|[noonereceiving].32k.org
7907
days inactive
7907
days old
linux-audio-user@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Ivica Bukvic -
Michal Seta