Public SourceMage Discussion List

[Unet <burududu AT hotpop.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The alsa-driver-virmidi passes the option to build the virtual MIDI sound 
card, so it can't be used as a virtual MIDI router between different audio 
interfaces - i.e. from the MIDI input of you soundcard to a softsynth like 
TiMidiTy++. - since many of the soundcard doesn't have (yet!) wavetable 
support.

Of course, it'll vanish as soon as the alsa-driver spell will be reworked to 
allow more than one sound card...

Cheers

Unet

On Friday 13 September 2002 18:21, Jeremy Kolb wrote:
> But if you check out the spells, alda-driver-virmidi is almost
> identical, except that alsa-driver-virmidi passes one more option to
> configure... at least that's all that i saw, but i wasn't looking very
> hard. alsa-driver-virmidi works fine, except that apparently it's set up
> to use two sound cards? i wish somebody would enlighten us on the
> difference between the two spells, so far i haven't heard a thing. why
> do we have two? wouldn't one suffice?
>
> Jeremy
>
> Lyon Lemmens wrote:
> >Eric,
> >
> >I've manually changed rc3 in rc2 in the DETAILS file and did a cast. Works
> >like a dream. Ergo, the problem is in the alsa sources, so that can't
> >probably be fixed by clever spell building.
> >
> >On Wednesday 11 September 2002 15:25, Eric Sandall wrote:
> >>Hmmm...I hadn't thought of that.  I'll look into reverting the version
> >>and seeing if that fixes the symbols problems.  Anyone else care to test
> >>this as well?
> >>
> >>-One of Four
> >>a.k.a. sandalle
> >>
> >>Lyon Lemmens said:
> >>>On Monday 09 September 2002 06:43, Eric Sandall wrote:
> >>>>Jeremy Kolb said:
> >>>>>ok, just sorcery updated and now when i cast alsa-driver i get a
> >>>>
> >>>>whole bunch of undefined symbols in my
> >>>>
> >>>>>/lib/modules/2.4.19-preempt-3/kernel/sound/*.o files. then i go to
> >>>>
> >>>>cast alsa-lib and it decides to uninstall alsa-driver and install
> >>>>
> >>>>>alsa-driver-virmidi instead (which is at rc2 where as the rest of
> >>>>
> >>>>the alsa spells are rc3). then it finally gets to compiling alsa-lib
> >>>>and then dies because halfway through the /usr/src/alsa-lib-0.9-rc3
> >>>>(something like that) directory mysteriously disappears. just posted
> >>>>to bugzilla bug 919.
> >>>>
> >>>>>Jeremy
> >>>>>
> >>>>>P.S. and what is the difference between alsa-driver and
> >>>>>alsa-driver-virmidi? that should be clearly defined in the DETAILS
> >>>>
> >>>>section, but i see no difference between the two. is this "better"
> >>>>then the plane old alsa-driver?
> >>>>
> >>>>Are your linux modules installed into /lib/modules/2.4.19-preempt-3/,
> >>>>or does the alsa-driver spell create that?  If so, then I believe the
> >>>>problem is that the alsa-driver spell is misreading the kernel version
> >>>>of where to put it (it's set to go to /lib/modules/`installed_version
> >>>>linux-new`/).
> >>>>
> >>>>And I have no idea what the difference is, though I've been asked a
> >>>>few times already.  :)
> >>>>
> >>>>-One of Four
> >>>>a.k.a. sandalle
> >>>
> >>>I have got the same problem with the plain-vanilla linux kernel. After
> >>>alsa  updated I get the undefined symbols.
> >>>
> >>>The problem, IMHO, is that alsa keeps pace with the kernel releases. So
> >>>eg.  after 2.4.19-rc3, you also get a alsa-rc3.
> >>>
> >>>Now, we don't do kernel rc's (I hope), so we probably shold hold off on
> >>>alsa  updates until the next kernel release. I would suggest you revert
> >>>to the  previous alsa version.
> >>>
> >>>--
> >>>Lyon Lemmens
> >>>redlemon AT knoware.nl
> >>>_______________________________________________
> >>>SM-Discuss mailing list
> >>>SM-Discuss AT lists.ibiblio.org
> >>>http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9gvJwGvlPIwGmdSQRAjfzAJwJrZBeYZHd3KKZV4uuWhSx9hQvlACcChvm
oCOnwL0f4avrCMxVISyVOKY=
=WBz9
-----END PGP SIGNATURE-----