Hi,
Since I have yet to try Debian, I might change my religion also, if I do :-)
For now I'm quite content with Mandrakes current offers, very slick, VERY
uptodate. Not quite bugfree, but I've been with them for a while and know my way
around.
The latest releases (8.1 and 8.2) have also been
I got it last night with:
cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvspsrv/cvsroot co -d
ecasound-cvs sound/ecasound
no login
Paul Winkler wrote:
> Hi,
>
> I want to try ecasound with jack, but I find the 2.1dev7
> tarball won't build with latest jack cvs.
>
> audioio_jack_manager.cpp:
Hi,
I want to try ecasound with jack, but I find the 2.1dev7
tarball won't build with latest jack cvs.
audioio_jack_manager.cpp:690: passing `const char *' as argument 2 of
`jack_port_disconnect(jack_client_t *, jack_port_t *)'
make[3]: *** [audioio_jack_manager.lo] Error 1
make[3]: Leaving dire
On Mon, 15 Apr 2002 20:24:06 +0200
Frank Barknecht <[EMAIL PROTECTED]> wrote:
> Hi Dave,
> Dave Phillips hat gesagt: // Dave Phillips wrote:
>
> > OTOH, (and as you say, to be fair), MusE apparently does now compile
> > under 2.96 so I'm wondering whether the path of least resistance is to
> > s
On Mon, 15 Apr 2002 22:28:59 +0200
J Nettingsmeier <[EMAIL PROTECTED]> wrote:
> Kevin Conder wrote:
> >
> >
> > Does the fault really lie with RedHat? Or does it lie with Linux
> > audio application projects that don't supply RedHat packages? Why don't
> > programmers at least test thei
Kevin Conder wrote:
>
>
> Does the fault really lie with RedHat? Or does it lie with Linux
> audio application projects that don't supply RedHat packages? Why don't
> programmers at least test their applications on different distros?
because programmers should spend their time programmi
Kevin Conder hat gesagt: // Kevin Conder wrote:
> Does the fault really lie with RedHat? Or does it lie with Linux
> audio application projects that don't supply RedHat packages? Why don't
> programmers at least test their applications on different distros?
Ah, come on. They should code, no
On Sun, 14 Apr 2002, Dave Phillips wrote:
> rm wrote:
> > but to be fair, i don't think redhat figured in to the issues you were
> > having one way or another. :D
>
> Well, yes and no. My troubles began when RH's 2.96 compiler gave me fits
> over compiling MusE (briefly: it was impossible) so I d
If there is a project to add alsa support for these cards, I'd like to
help out. I have a USB Duo. Has anybody asked for the specs yet?
cheers,
reynald
Paul Davis wrote:
>>>I think a more exact description of the gphoto approach is:
>>>application<->gphoto-lib<->usb-lib<->low-level-generic-US
Hi Dave,
Dave Phillips hat gesagt: // Dave Phillips wrote:
> OTOH, (and as you say, to be fair), MusE apparently does now compile
> under 2.96 so I'm wondering whether the path of least resistance is to
> simply reinstall RH 7.2 on this machine and plan on a Debian install to
> a new disk.
Insta
> [EMAIL PROTECTED] writes:
>
>
>Title : The MIDI Wire Protocol Packetization (MWPP)
>Author(s) : J. Lazzaro, J. Wawrzynek
>Filename: draft-ietf-avt-mwpp-midi-rtp-03.txt
>Pages : 41
>Date: 12-Apr-02
>
Hi all.
The amSynth beta2 tarball is available now.
Works going slow with all my academic work at the moment, the main new feature is
polyphony limiting (you can specify the maximum polyphony manually). This seemed to be
the main problem with the old one, so read the README for info on that an
On Sunday 14 April 2002 22.47, Jörn Nettingsmeier wrote:
> all in all, a nice distro, if a little bloated. if you're a
> pssionate do-it-yourselfer, i'd recommend against it, but if you
> want a quick start and can tolerate excessive eye-candy, suse80
> might be for you.
I am a do it myself - so
>>I think a more exact description of the gphoto approach is:
>>application<->gphoto-lib<->usb-lib<->low-level-generic-USB driver.
>>
>>Only the low-level kernel USB drivers and the usbdevfs filesystem are in
>>kernel space, beyond that the hardware driving is done via the user-space
>>libusb. I
--- James Tappin <[EMAIL PROTECTED]> wrote:
>On Monday 15 Apr 2002 13:16, Patrick Shirkey wrote:
>> --- Paul Davis <[EMAIL PROTECTED]> wrote:
>> >>>framework for ALSA worked out, which is even more of a problem. Its
>> >>>still unclear at this point whether the ALSA framework will be:
>> >>>
>> >>
On Monday 15 Apr 2002 13:16, Patrick Shirkey wrote:
> --- Paul Davis <[EMAIL PROTECTED]> wrote:
> >>>framework for ALSA worked out, which is even more of a problem. Its
> >>>still unclear at this point whether the ALSA framework will be:
> >>>
> >>>
> >>> application<->alsa-lib<->alsa-driver<
--- Paul Davis <[EMAIL PROTECTED]> wrote:
>>>framework for ALSA worked out, which is even more of a problem. Its
>>>still unclear at this point whether the ALSA framework will be:
>>>
>>> application<->alsa-lib<->alsa-driver<->low-level-ALSA-USB-class-driver
>>>
>>>OR
>>>
>>> application
17 matches
Mail list logo
