From owner-freebsd-current@FreeBSD.ORG Tue May 20 04:36:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 020A737B401 for ; Tue, 20 May 2003 04:36:17 -0700 (PDT) Received: from 255-133.ip.ll.net (255-133.ip.ll.net [209.131.255.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 063D143FAF for ; Tue, 20 May 2003 04:36:16 -0700 (PDT) (envelope-from jimd@siu.edu) Received: from siu.edu (localhost [127.0.0.1]) by freebsd2.localnet10 (8.12.9/8.12.9) with ESMTP id h4K6dZFC008358; Tue, 20 May 2003 06:39:40 GMT (envelope-from jimd@siu.edu) Message-Id: <200305200639.h4K6dZFC008358@freebsd2.localnet10> Date: Tue, 20 May 2003 06:39:35 +0000 (CDT) From: jimd@siu.edu To: mat@cnd.mcgill.ca In-Reply-To: <20030519025947.GD60782@cnd.mcgill.ca> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-current@freebsd.org Subject: Re: MIDI on SB Live! ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2003 11:36:17 -0000 I can see /dev/mid* devices under my FBSD-4.8-STABLE system, but I don't see these under FBSD-5.1-BETA. Is "newmidi" related to "device midi"? I can't find any "newmidi" entries in the 5.1-BETA /usr/src/sys/i386/conf files. Or is this like "device pcm" -> "newpcm"? On 18 May, Mathew Kanner wrote: > On May 18, jimd@siu.edu wrote: >> I downloaded the emu10kx module, compiled, and ran it, but didn't see >> anything that indicated MIDI input. It might very well be, however, my >> "system": I have a SoundBlaster Live! PCI card AND something-or-other >> onboard AC97, but FBSD-4.8 and FBSD-5.1-BETA can't "see" the motherboard >> AC97 device. >> >> While I have the "official" Creative Labs MIDI to DB15 cable, there is >> also a possibility that IT is not working properly. I DID verify that the >> MIDI output port was "live": I removed the MIDI cable from it to one MIDI >> keyboard that was in MIDI playback mode, and working, and inserted the >> Creative Labs MIDI cable, but nothing else appeared on the console. >> >> Below is what appeared on the console, but I am sure that you have already >> seen this: >> >> emu10kx0: port 0xcc00-0xcc1f irq 5 at de >> vice 7.0 on pci0 >> emu10kx0: Card Configuration ( 0x00000e15 ) >> emu10kx0: Card Configuration ( & 0xff000000 ) : >> emu10kx0: Card Configuration ( & 0x00ff0000 ) : >> emu10kx0: Card Configuration ( & 0x0000ff00 ) : [GPOUT1] [GPOUT2] [Joystick] >> emu10kx0: Card Configuration ( & 0x000000ff ) : [AUTOMUTE] [LOCKTANKCACHE] [AUDI >> OENABLE] >> emu10kx0: sc = 0xc6a8e800 >> EMU_ENATIMER: sc=0xc6a8e800, go=0) >> midi0: on emu10kx0 >> midi0: MIDI Attach called for port 1... > > Note this using the newmidi that's currently available in > fbsd. It can read/write on the raw port (/dev/midi%d) and writes to > the sequencer (/dev/sequencer). > A simple test would be > dd if=/dev/midi0 of=/dev/null bs=1 > Which should produce a stream of bytes corresponding to active > sensing requesting (provided they aren't filtered) and note on /note > off events. > Also, you should see irq's for reading. (provided your > equipment is connecting, you will get an irq 3-5 a second while the > keyboard is connected, 0 while disconnected) > Playmidi should compile in the ports by changing the > #include to > #include > Then play a .mid file. > > emu10k1 provides an mpu401 which should be relatively easy to > support as far as midi hardware goes (since the code already exists). > > > --Mat >