6 May
2004
6 May
'04
1:16 p.m.
Howdy all....
I have been trying to learn a few things at once, possibly too many, and I'd like to
cut some unknowns out of the big picture. I'm hoping that someone can help me with a
down and dirty test of my midi hardware.
Details:
I am trying to learn about setting up and using midi in SuSe 9.0, and also am kinda new to
Linux. Also, the keyboard might be defective... the 3 octave keyboard is 'new' in
regards that I just bought it last year (was still shrink wrapped), but it is leftover
stock - the manufacturer is out of business. To give a clue about the age, the keyboard
came with Windows 3.1 software (no mention of 95). I only had Windows ME on a celeron
system; when I installed the included software, it could not find the keyboard, but I
suspected the age of the software and the differences in OS revisions were more the
problem. And I assume that the celeron system was properly configured.... but nothing ever
noticed a keyboard.
I then took the keyboard to my Linux box... it still seems to be uncommunicative, but
I'm new to Linux.
There are just too many variables in the pot right now:
a] Does the keyboard even work? It powers up and appears to change functions per written
instructions. But no communications.
b] Does my Linux box (SuSe 9.0, AMD Athlon, DFI AK75EC mobo) have a hardware or BIOS
defect? BIOS says midi/game is set to midi (only other option for that port is game)....
the cable is definitely connected to the correct port.
c] Does my Linux box have all the proper modules? I see MPU401, virmidi, and all the
soundcard playback stuff works fine. (Via 686 based chipset, AC'97 compatible). I can
issue aconnect -lio and see a difference when the module is inserted, but do I have all
the proper steps completed, etc etc etc.
Ignore answering all the above, please; I'd rather try to send strings to the midi
port and see if the keyboard is receptive, see how it responds, etc, so I can have some of
the variables removed from the wide matrix that I presently face.
Any suggestions on brute force communications w/midi devices? Can I cat some string int
/dev/midiwhatever? I once used 'cat ATO > /dev/ttys00' for testing a modem,
that was slick, but what commands are sent in MIDI? That kind of test would be, IMO, very
useful.
TIA!
-- Matthew 28:19,20
_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com
6 May
6 May
1:45 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
Lee Dunbar wrote:
I am trying to learn about setting up and using midi
in SuSe 9.0
I have the same suse but did not try a midi keyboard on it.
however, time ago, I got a second hand Yamaha keyboard (I could find the
ref if necessary - it's time of win31) and could not make it work. I got
it to a specialised dealer who achieve the cabling and I have cautiously
kept the cable :-). It was a problem with din pins but also needed some
resistors in the way. so may be a cable dealer can help you (at least
trying your keyboard to see if it works). I still have the keyboard.
jdd
--
pour m'écrire, aller sur:
http://www.dodin.net
2:30 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
On Thursday 06 May 2004 10:09 am, Lee Dunbar wrote:
[snip: trying to connect an old MIDI keyboard from
windows 3.x era]
Just for the record, I also have such a keyboard, and it still works just
fine. If it a is standard MIDI device with a MIDI-to-gameport cable, there
should be no problem.
BIOS says midi/game is set to midi (only other option
for that port is
game)....
This *may* be wrong, and *might possibly* be the source of your trouble.
Is the port actually a MIDI port? If it isn't, you might be confusing things
by telling the BIOS that it is. I'm not sure how that particular BIOS
setting would affect port communication, but it is common to use a standard
gameport for MIDI, via an adapter. You shouldn't have to change your BIOS
settings.
You could probably do a bit of testing under Windows by installing the
gameport MIDI driver. I don't remember what the driver is called, but look
for something with MPU401 in the name. It may be installed already. I'm not
advocating that you move away from Linux, of course, but this could give you
another temporary testing platform by which to establish whether or not your
keyboard and cabling is okay.
Good luck,
|)
|)enji
2:31 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
On Thu, 2004-05-06 at 08:09, Lee Dunbar wrote:
Howdy all....
I have been trying to learn a few things at once, possibly too many, and I'd like to
cut some unknowns out of the big picture. I'm hoping that someone can help me with a
down and dirty test of my midi hardware.
Details:
I am trying to learn about setting up and using midi in SuSe 9.0, and also am kinda new
to Linux. Also, the keyboard might be defective... the 3 octave keyboard is 'new'
in regards that I just bought it last year (was still shrink wrapped), but it is leftover
stock - the manufacturer is out of business. To give a clue about the age, the keyboard
came with Windows 3.1 software (no mention of 95). I only had Windows ME on a celeron
system; when I installed the included software, it could not find the keyboard, but I
suspected the age of the software and the differences in OS revisions were more the
problem. And I assume that the celeron system was properly configured.... but nothing ever
noticed a keyboard.
I then took the keyboard to my Linux box... it still seems to be uncommunicative, but
I'm new to Linux.
There are just too many variables in the pot right now:
a] Does the keyboard even work? It powers up and appears to change functions per written
instructions. But no communications.
b] Does my Linux box (SuSe 9.0, AMD Athlon, DFI AK75EC mobo) have a hardware or BIOS
defect? BIOS says midi/game is set to midi (only other option for that port is game)....
the cable is definitely connected to the correct port.
c] Does my Linux box have all the proper modules? I see MPU401, virmidi, and all the
soundcard playback stuff works fine. (Via 686 based chipset, AC'97 compatible). I can
issue aconnect -lio and see a difference when the module is inserted, but do I have all
the proper steps completed, etc etc etc.
Ignore answering all the above, please; I'd rather try to send strings to the midi
port and see if the keyboard is receptive, see how it responds, etc, so I can have some of
the variables removed from the wide matrix that I presently face.
Any suggestions on brute force communications w/midi devices? Can I cat some string int
/dev/midiwhatever? I once used 'cat ATO > /dev/ttys00' for testing a modem,
that was slick, but what commands are sent in MIDI? That kind of test would be, IMO, very
useful.
TIA!
Dont know that your going to get off that easy! :)
If it were me I would do the following...
Use Qjackctl (Assuming your running "X" and guis's) it has a myriad of
useful interfaces for midi and the alsa pcm ports. Before even running
Jack, see if your midi port shows under the midi tab in the "connect"
window. If so, then I would take that as your system seeing your midi
port and subsequent applications. Also cat /proc/asound/devices. I use
alsamixergui for that too...click on "Alsa" logo in top right corner.
If those are there, try running vkeybd (small software midi virtual
keyboard) make sure your sending midi data on the right channel. I think
the Kalsatools package has a little gui app that show what midi data is
being received. Aseqview is another handy little gui app for seeing what
midi data is being sent.
The other thought that comes to mind...does you card or sound chip have
in built wavetable? if not, you might be sending midi stream to it but
it has no sounds to play. I use fluidsynth and the new Qsynth for this
and load soundfonts. Google around some.
Dont know if any of this is useful to you but these things have saved my
butt with the elusive midi connections.
R~
-- Matthew 28:19,20
_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com
6:06 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
i tend to use a combination of gmidimon, PD, and a couple of simple
csound patches to test midi input/output. gmidimon, in particular, is
fairly effective for seeing whether you're getting midi input or not,
although it's kinda buggy. for sending out you could probably use PD
(or jmax), or one of the other apps mentioned in prior emails.
glyn
Russell Hanaghan wrote:
Dont know that your going to get off that easy! :)
If it were me I would do the following...
3:18 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
On Thursday 06 May 2004 10:09 am, Lee Dunbar wrote:
[snip: how to test a MIDI keyboard]
Another idea would be to use Hydrogen for testing. Start the program,
and choose "Preferences..." from the File menu. Switch to the "Midi
System"
tab, and select the input which you think represents your keyboard. Click
Ok, and watch the "Midi in" light. If it blinks when you press keys, you
know that communication is okay.
|)
|)enji
5:44 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
On Thursday 06 May 2004 17:15, Benjamin Flaming wrote:
On Thursday 06 May 2004 10:09 am, Lee Dunbar wrote:
Yup, Qjackctl & Hydrogen are the two applications I usually bring up first to
check the system. There are command line utilities like aplaymidi &
arecordmidi (or amidi if you want to send sysex). I used to use timidity for
this purpose, but I haven't had it working properly for a while.
cheers
tim hall
[snip: how to test a MIDI keyboard]
Another idea would be to use Hydrogen for testing. 
6:54 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
tim hall wrote:
On Thursday 06 May 2004 17:15, Benjamin Flaming
wrote:
A nice feature in Reaktor Session is the ability to play a patch using
the standard keyboard. z-? provide an octave with a few keys in the next
row up (s,d,f,h,j, etc.) providing sharps.
Does no Linux soft synth provide some capability like this?
I think it would be a nice little app for someone to provide a simple
MIDI keyboard emulator using the qwerty keybaord. (Or is this what
virmidi does? I've never used it.)
Cheers,
Mark
On Thursday 06 May 2004 10:09 am, Lee Dunbar
wrote:
Yup, Qjackctl & Hydrogen are the two applications I usually bring up first to
check the system. There are command line utilities like aplaymidi &
arecordmidi (or amidi if you want to send sysex). I used to use timidity for
this purpose, but I haven't had it working properly for a while.
cheers
tim hall
[snip: how to test a MIDI keyboard]
Another idea would be to use Hydrogen for testing. 
7:13 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
Mark Knecht wrote:
I think it would be a nice little app for someone to
provide a simple
MIDI keyboard emulator using the qwerty keybaord. (Or is this what
virmidi does? I've never used it.)
http://helgo.net/simon/clavier/
http://helgo.net/simon/midikb/
I think there's another one I've forgotten to list...
Best,
dp
7:53 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
Dave Phillips wrote:
Mark Knecht wrote:
Thanks Dave. Those appear to be exactly the sort of little app I was
thinking would help Tim with his testing.
Cheers,
Mark
I think it would be a nice little app for someone
to provide a simple
MIDI keyboard emulator using the qwerty keybaord. (Or is this what
virmidi does? I've never used it.)
http://helgo.net/simon/clavier/
http://helgo.net/simon/midikb/
I think there's another one I've forgotten to list...
Best,
dp
7:24 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
On Thu, 2004-05-06 at 13:46, Mark Knecht wrote:
Thats exactly what vkeybd does...only not QWERTY. More like AZSXFVGBHNJMKL. 8~}
You patch it in via one of the many gui apps.
I dont know if Reaktor registers a midi in port or not.
tim hall wrote:
> On Thursday 06 May 2004 17:15, Benjamin Flaming wrote:
>
>>On Thursday 06 May 2004 10:09 am, Lee Dunbar wrote:
>>
>>>[snip: how to test a MIDI keyboard]
>>
>> Another idea would be to use Hydrogen for testing.
>
>
> Yup, Qjackctl & Hydrogen are the two applications I usually bring up first to
> check the system. There are command line utilities like aplaymidi &
> arecordmidi (or amidi if you want to send sysex). I used to use timidity for
> this purpose, but I haven't had it working properly for a while.
cheers
tim hall
A nice feature in Reaktor Session is the ability to play a patch using
the standard keyboard. z-? provide an octave with a few keys in the next
row up (s,d,f,h,j, etc.) providing sharps.
Does no Linux soft synth provide some capability like this?
I think it would be a nice little app for someone to provide a simple
MIDI keyboard emulator using the qwerty keybaord. (Or is this what
virmidi does? I've never used it.)
Cheers,
Mark
7:27 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
On Thu, May 06, 2004 at 08:36:50PM +0100, tim hall wrote:
On Thursday 06 May 2004 17:15, Benjamin Flaming
wrote:
Along the same lines, PD has a nice built-in quick test.
It's in Media -> Test Audio & Midi
--
Paul Winkler
http://www.slinkp.com
On Thursday 06 May 2004 10:09 am, Lee Dunbar
wrote:
Yup, Qjackctl & Hydrogen are the two applications I usually bring up first to
check the system. There are command line utilities like aplaymidi &
arecordmidi (or amidi if you want to send sysex). I used to use timidity for
this purpose, but I haven't had it working properly for a while. [snip: how to test a MIDI keyboard]
? ? ?Another idea would be to use Hydrogen for testing. 
8 May
8 May
11:59 p.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
I'm fond of PD for midi testing. It doesn't use the ALSA sequencer
interface but it gives you the actual numbers of incoming
note/velocity/channel events, CC's and has a random noteout test.
-lee
On May 6, 2004, at 3:36 PM, tim hall wrote:
On Thursday 06 May 2004 17:15, Benjamin Flaming
wrote:
On Thursday 06 May 2004 10:09 am, Lee Dunbar
wrote:
Yup, Qjackctl & Hydrogen are the two applications I usually bring up
first to
check the system. There are command line utilities like aplaymidi &
arecordmidi (or amidi if you want to send sysex). I used to use
timidity for
this purpose, but I haven't had it working properly for a while.
cheers
tim hall
[snip: how to test a MIDI keyboard]
Another idea would be to use Hydrogen for testing. 
7 May
7 May
9:42 a.m.
New subject: [linux-audio-user] Is there a shortcut to merely test a midi device?
Lee Dunbar wrote:
Any suggestions on brute force communications w/midi
devices? Can
I cat some string int /dev/midiwhatever?
Yes, or you could use the amidi tool.
But you should send valid MIDI commands if some MIDI device is
listening at the other end.
I once used 'cat ATO > /dev/ttys00' for
testing a modem, that was
slick, but what commands are sent in MIDI?
http://www.borg.com/~jglatt/tech/miditech.htm
To see how such commands look like, run "amidi -p virtual -d" and play
some .mid file to the virtual port.
HTH
Clemens
7597
days inactive
7599
days old
linux-audio-user@lists.linuxaudio.org
14 comments
11 participants
participants (11)
-
Benjamin Flaming -
Clemens Ladisch -
Dave Phillips -
glyn -
jdd -
Lee Azzarello -
Lee Dunbar -
Mark Knecht -
Paul Winkler -
Russell Hanaghan -
tim hall