From owner-freebsd-multimedia@FreeBSD.ORG Mon Apr 25 02:38:46 2005 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D55C16A4CE for ; Mon, 25 Apr 2005 02:38:46 +0000 (GMT) Received: from parse.com (ottawa-hs-206-191-28-202.s-ip.magma.ca [206.191.28.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3C5143D45 for ; Mon, 25 Apr 2005 02:38:45 +0000 (GMT) (envelope-from root@parse.com) Received: (from root@localhost) by parse.com (8.8.8/8.8.8) id WAA25506 for freebsd-multimedia@freebsd.org; Sun, 24 Apr 2005 22:38:45 -0400 Message-Id: <200504250238.WAA25506@parse.com> To: freebsd-multimedia@freebsd.org Date: Sun, 24 Apr 2005 22:38:45 -0400 (EDT) From: "Robert Krten" X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Is it MIDI yet? (fwd) X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2005 02:38:46 -0000 > On Feb 11, Joel Ray Holveck wrote: > > I've been holding off on going to 5.3 because the MIDI driver > > evaporated. I'm getting a bit tired of waiting. I know that nobody > > owes me anything when it comes to FreeBSD, but you can understand that > > I'm a bit frustrated. > > > > What happened to the new framework? Why was the old framework removed? > > Should it be re-added, until the new one is finished? > > I'm the guy working on Midi and I just got back to it. My > available time fluctuates, and I've been busy, sick, etc, etc. > Anyway, previosuly, the MIDI that was removed did not with any cards > (that I know of) other than CSA. So I don't think there is any point > in being frustrated with its removal. Also, I've posted a few times > to the list a replacement that you can test if you have either a > soundblaster live or a es137x. Present problems including broken > sound recording and no-AMD64. > > I plan to have a cross-compilable version available this > weekend. Hi Mat et al., My motherboard claims to have an MPU401-compatible midi port on it, and I'm wondering if the stuff you've done will work with that? If so, I'd be happy to be a trial tester of the new stuff. If not, can you tell me if the old framework would work with that h/w, and, if so, how I'd go about enabling it? I've pulled down all the CVS files that I can think of dating back to 10 months ago, but it still doesn't work (he said, vaguely). It (midi.c, mpu.c) compiles (with tweaks for dev_t -> struct cdev* etc.); the sequencer.c doesn't compile yet (a few warnings left), but my device never shows up in /dev, nor is there any message in dmesg about it. This is on an i386. Suggestions? Do you recall what I need to put into my conf file, is just "device midi" sufficient, or are there other things? Thanks in advance! Cheers, -RK -- Robert Krten, PARSE Software Devices +1 613 599 8316. Realtime Systems Architecture, Consulting, Books and Training at www.parse.com Looking for Digital Equipment Corp. PDP-1 through PDP-15 minicomputers!