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
Hello - wondering what might cause a spontaneous reboot - running
2.4.25-gentoo-r2, using ALSA 1.03 with jack audio connection kit and Ardour
(the latest ebuilds) and get this spontaneous reboot, usually when switching
windows in ardour - not always that though - get it sometimes using
hdspmixer too - haven't tried much else to see if it's connected to alsa or
jack or just X or WHAT - using Xfree86 and fluxbox - although with KDE it
does it too - KDM is the desktop manager (is that what's that's called???)
hmmm...
thanks!
Forwarding this to mailing lists where others may be interested.
>Envelope-to: luke(a)audioslack.com
>From: Vedran Vucic <vvucic(a)eunet.yu>
>To: audioslack-users(a)audioslack.com
>Date: Sat, 8 May 2004 13:44:53 +0000
>
>Dear colleagues,
>
>A good friend of mine started project creating open audio card and possibly
>he is interested to find people who can maybe contribute to idea of opencores
>and open hardware having in mind that his project is related with audio
>recording and editing.
>
>www.opencores.org/projects.cgi/web/fac2222m/overview
>
>I think that such an effort may be very important contribution to efforts all
>we are committed.
>
>Best wishes,
>
>Vedran Vucic
--
Luke Yelavich
http://www.audioslack.com
luke(a)audioslack.com
Hello,
is there any tool, that could help me to cut the silence from the
beginning of a midi file? (without taking a three month course of how to
use the editor)
TIA,
Helge
Uhhhh..... My BIOS is an issue? You lost me, Ben. My motherboard manual *tells me* to set the BIOS to game if I want to use a joystick on the port, or set the BIOS to *midi* if I want to attach midi devices to it... Same situation for both the Athlon/Linux box (using AMI BIOS) and the Celeron/WinME box (using an award BIOS). The motherboard owners manuals for 2 different systems are not to be believed? I think these boxes are fairly representative of common PCs.
Also, nothing anywhere (in all the manuals) has ever mentioned needing any adapters, can you post manufacturer names and part numbers for what you are referring to? And the computers I've mentioned are PC, I know that older Macintoshes (68k era stuff) needed adapters, is that what you are thinking?
Finally, the cable that came with the keyboard has a din on one end (this end plugs into the keyboard), and the other end of the cable splits into two; the 2 ends are male and female, and the keyboard documents say that one connection is for the PC connection, the other is for a joystick. Both of these connections are D-SUB designs, of the proper type to mate with the midi connector on the 2 systems. I believe this is the cable to which you have referred as 'midi to gameport cable'. Does this cable replace the adapter that you mentioned?
-- Matthew 28:19,20
--- Benjamin Flaming <lau(a)solobanjo.com> wrote:
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
_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com
After digging around I got this card using the cs46xx alsa driver to
show 2 ins and 6 outs running jack. I am yet to test sound thru them but
will shortly.
I figured I'd need to set up a specific .asoundrc file for this but
turns out if you try the "default" setting in qjackctl you can set up
jack for 2, 4 or 6 outs on a surround type card. At least with this one
anyway. see the alsa.conf group of scripts. There are several of which
all appear to have layout for the various surround (4.0, 4.1, 5.0, 5.1,
etc) configurations.
I figure this might work with SBLive 5.1 too?
Most prolly know this but for those noobs like my self...
R~
Thanks for the heads up on amidi - can't wait to get the time on the SuSe box so I can try it. FWIW, what is PD? I've searched sourceforge for the string 'midi', nothing stood out (my newbieness thinks that means 'Public Domain').
Date: Fri, 07 May 2004 13:34:26 +0200 (METDST)
From: Clemens Ladisch <clemens(a)ladisch.de>
Subject: Re: [linux-audio-user] Is there a shortcut to merely test a
midi device?
To: A list for linux audio users <linux-audio-user(a)music.columbia.edu>
Message-ID:
<Pine.HPX.4.33n.0405071325430.26752-100000(a)studcom.urz.uni-halle.de>
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
-- Matthew 28:19,20
_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com
Thanks Dave,
DAP sounds like just the thing i need.
Rob
Hi list,
I have built XForms (1.0.90) from source without any errors
and all the files seem to be in the right place but when i try to build
DAP (2.1.5) i get :
make -f Makefile.linux
Compiling tooltips.o from tooltips.c...
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../crt1.o(.text+0x18): In
functio
n `_start':
../sysdeps/i386/elf/start.S:77: undefined reference to `main'
/tmp/ccaXaPUW.o(.text+0x39): In function `tooltips_initialize':
: undefined reference to `fl_mapcolor'
and a string of 'undefined reference to... errors
where/how do i define what needs to be defined?
sorry if i am missing something obvious,
Rob
redhat9 planetccrma
Hydrogen does not see it. Let me at this time reiterate a prior request I made: a simple bruteforce test is desired. I've already tried soo many different 'normal' configurations (GUI version of aconnect, connect the midi device to a sequencer that is launched, got nothing, tried Timidity, Muse, Rosegarden - they do not see the device, nor do I know hos to tell my midi device to be channel 1 or channel 7, etc) remember my 'too many variables' statement? I really want the simplest and most fool proof setup one can possibly attempt. Hence I asked about catting a string into a midi device - something as brute force as that, talking straight into the /dev/midi device.....
-- Matthew 28:19,20
--- Benjamin Flaming <lau(a)solobanjo.com> 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. 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
_____________________________________________________________
Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com
Hello,
a new version of AlsaModularSynth is available from Sourceforge.
Note: Remember to download the latest version of the LADSPA plugins by
Fons Adriaensen: http://users.skynet.be/solaris/linuxaudio
Otherwise the latest instrument patches just won't work !
News:
- Added hplp_instrument.ams which demonstrates the new highpass filter by
Fons Adriaensen. Due to the HPLP combination, the presets of this patch
are quite close to some of the famous "Switched-On Bach" sounds by W. Carlos.
- Added sinfonia.mid for your own experiments with hplp_instrument.ams
- Fixed bug in LADSPA module where uninitialized output control ports have
caused segfaults.
- Several small corrections in demo patches.
For more news check the respective section on the project page.
Have fun !
Matthias
--
Dr. Matthias Nagorni
SuSE Linux AG
Maxfeldstr. 5 phone: +49 911 74053375
D - 90409 Nuernberg fax : +49 911 74053483