Ivica Bukvic wrote:
> The firmware loads fine, and the midisport is properly recognized. The
> problem is that I only have one MIDI port available even though this is
> the 2x2 version (I had 2 ports in Mdk 9.0, usually /dev/midi(0) and
> /dev/midi1). Now I only have /dev/midi.
>
> The interesting
I am trying to use a Soundblaster Live! on a ALPHA 164SX.
My main interest is the sequencer support.
Before it worked except loading large soundfonts.(> ~2 MB)
Now when I try to build the latest versions of alsa, it stops with this errors:
In file included from /lib/modules/2.4.20/build
Dana,
I don't think the tinny sound et al. should be blamed on the ALSA
drivers, perhaps you should be looking into the SB Live card and your setup
first as candidate for review. I also am a musician and have invested
considerable research into my choice of O.S driver and card and Alsa (f
Vineet Agrawal wrote:
> gcc -static -Wall -pipe -gtest_latency1.c -o test_latency1
> ...
> undefined reference to `snd_...'
> ...
You have to link with the ALSA library. Add -lasound to the compiler
command line.
HTH
Clemens
---
This
I have a TerraTec DMX XFire1024 too and no problems (except the sound
distortions with PCM volume >75%, but that's not related to this).
I use the 0.9.2 ALSA drivers, XFree86 4.2.1 and a self-compiled Kernel 2.4.20.
To upgrade to the latest nvidia drivers, just download this file:
http://download
Hallo,
Dana Olson hat gesagt: // Dana Olson wrote:
> I didn't ever want to use ALSA, but as the dev kernel has now merged it,
> it will become the standard very quickly, and I don't want to hold back.
You also will find, that practically every (semi-)pro audio software
for Linux somehow requires
Thanks for your help!
However, I am a bit confused, since this feature with /dev/midi stuff
worked like a charm just a couple weeks ago (ver. 0.9.1). So, did
something change dramatically since?
Can you also point me in the right direction where I can see a simple
ALSA code to accessing the both
Did anybody get any sound from this chipset? If yes what rev. number of
the driver did you use, and what options in #ALSA section ?
> Hi.
> I had to post this again because first post didn't show my :lspci,
lsmod and sndstat.
> I can't get any sound from my MB. I compiled all like is said in
in
On Thu, 2003-04-03 at 14:12, C. Dummy wrote:
> Did anybody get any sound from this chipset? If yes what rev. number of
> the driver did you use, and what options in #ALSA section ?
>
I've sound only with the cvs version (I've tried with the cvs of 6 hour
ago) not with the 0.9.1 nor 0.9.2 version
What nr of cvs version?
Thanks for answer.
Andrey
Laurent Luyckx wrote:
On Thu, 2003-04-03 at 14:12, C. Dummy wrote:
Did anybody get any sound from this chipset? If yes what rev. number of
the driver did you use, and what options in #ALSA section ?
I've sound only with the cvs version (I
On Wed, 2003-04-02 at 15:36, Friedrich Ewaldt wrote:
> Hmm, I also had some lockups with the nvidia drivers.
>
> Download newest nvidia driver + GLX module.
Hmmm. Turns out I'm behind again on this. I'll download tonite and see
what happens.
> Check for the correct driver and GLX version (must
On Wed, 2003-04-02 at 13:18, Adam Jones wrote:
> On 02-Apr-03, Lance A. Brown wrote:
>
> > Man, I thought I was the only one getting this problem. I've got a
> > Santa Cruz Turtle Beach in my system and a GeForce2 MX400 and thought
> > I was having problems with my crappy cheap motherboard (ECS K7
On Thu, 2003-04-03 at 16:54, C. Dummy wrote:
> What nr of cvs version?
Sorry I'm not at home right now.
Try maybe with the actual cvs...
> Thanks for answer.
> Andrey
> Laurent Luyckx wrote:
>
> >On Thu, 2003-04-03 at 14:12, C. Dummy wrote:
> >
> >
> >>Did anybody get any sound from this ch
Sorry if this does not thread!
From: "Laurent Luyckx" <[EMAIL PROTECTED]>
> On Thu, 2003-04-03 at 16:54, C. Dummy wrote:
> > What nr of cvs version?
> Sorry I'm not at home right now.
>
> Try maybe with the actual cvs...
>
> > Thanks for answer.
> > Andrey
> > Laurent Luyckx wrote:
> >
> > >On
From: "Laurent Luyckx" <[EMAIL PROTECTED]>
> On Thu, 2003-04-03 at 16:54, C. Dummy wrote:
> > What nr of cvs version?
> Sorry I'm not at home right now.
>
> Try maybe with the actual cvs...
>
> > Thanks for answer.
> > Andrey
> > Laurent Luyckx wrote:
> >
> > >On Thu, 2003-04-03 at 14:12, C. Dum
S. Anthony Sequeira wrote:
From: "Laurent Luyckx" <[EMAIL PROTECTED]>
On Thu, 2003-04-03 at 16:54, C. Dummy wrote:
What nr of cvs version?
Sorry I'm not at home right now.
Try maybe with the actual cvs...
Thanks for answer.
Andrey
Laurent Luyckx wrote:
On Thu, 2003-04
i am still experiencing the issue described below with alsa-source
0.9.2. unfortunately, i don't have any additional debugging information
to append.
tia for any help...
andy
- Forwarded message from [EMAIL PROTECTED] -
> Date: Wed, 26 Feb 2003 17:18:34 -0800
> Subject: Re: [Al
Hi all,
answers from me may take a lot, but I was just coming home
right now.
Thanks to all. I'll try the Option "NvAgp" "0" I have also
this setting for my card.
I'm just downloading the latest nvidia driver.
And actually nothing sharing an interrupt with my GeForce
card.
Here some facts:
Alsa
Dear ALSA users
I have a sound card (Delta 44) up and running with
ALSA driver. I am trying to do some speech procesing
in real time with this cad. With the help of you guys,
I was able to compile latency.c, but when I tried to
execute it, it gave me this error:-
cannot set sample format (Invali
Hi list,
Recently I bought a new motherboard+cpu+memory with an on-board sound
card (the CMI-PCI8738). When I play some audio, everything is fine,
however, when I try to record something, it performs really bad: there
IS sound, but it sounds some kind of 'metallic'.
So, I tried my plain old Enson
On Thu, 2003-04-03 at 05:57, Frank Barknecht wrote:
> Hallo,
Thanks for replying. :)
> Dana Olson hat gesagt: // Dana Olson wrote:
> > I didn't ever want to use ALSA, but as the dev kernel has now merged it,
> > it will become the standard very quickly, and I don't want to hold back.
>
> You als
It may not be ALSA's fault per se, but it is more likely a problem with
my ALSA configuration. As I said, everything is perfect if I rmmod all
the ALSA stuff and use the OSS emu10k1 driver. There are no problems
with that driver, so it has to be a configuration issue with the other.
That said, I d
Hallo Dana,
Dana Olson hat gesagt: // Dana Olson wrote:
> It doesn't happen in OSS. OSS sounds perfectly. My connections are fine,
> I don't plug and unplug stuff all the time, everything is stationary. I
> think I've unplugged stuff about 10 times since I got the card. It's
> never been bumped or
If I use the freshrpms it works fine, but if I try to compile my own
alsa kernel drivers from cvs(for jack and ardour) I get missing symbol
schedule_work. I have tried compiling using the i686 config file in the
kernel/configs directory. I know something is missing from the Redhat
source kernel tha
I am using Debian 3.0r1 Woody with KDE 3.1, kernel 2.4.18. AMD XP 2100+
256MB and 0.91 ALSA driver, Onboard Realtek 6 channel sound, motherboard
is Asus A7V8X. If not enough information, I will post more about my system.
Now I installed the driver and it worked. Sound came out and it was ok.
Dana,
So your saying it sounds like some sort of digital distortion. Again
I would look into googling on "Linux Audio Quality" as a starting point
this issue is covered. Without knowing the specifics of your setup perhaps
the architecture of the OSS drivers are masking an issue that is m
Andy,
Investigate the SysReq keys in the kernel hacking sections and try
compiling them in. this (Alt+Sysreq+e) should exit you from a hang and help
you sort out the problem
---
This SF.net email is sponsored by: ValueWeb:
Dedicated
Vineet Agrawal wrote:
> I have a sound card (Delta 44) up and running with
> ALSA driver. I am trying to do some speech procesing
> in real time with this cad. With the help of you guys,
> I was able to compile latency.c, but when I tried to
> execute it, it gave me this error:-
>
> cannot set samp
Hmm, I've tried running the alsa-lib/test/ramidi test and tried using it
as:
rawmidi -i hw:2,0
This starts it up but I don't get any events in. Can anyone tell me why?
Any other setting (i.e. hw:2,1) reports an error that such a device was
not found.
Interesting thing is that when I do ./rawmi
Actually please disregard the part about not receiving input using
rawmidi. Forgot to include -v option for verbose.
Yet, I still cannot get the second port of the Midisport 2x2 to become
available no matter what. /proc/asound/cards lists only one midisport
2x2 device (which is ok, I guess, since
Ivica Bukvic wrote:
> Hmm, I've tried running the alsa-lib/test/ramidi test and tried using it
> as:
> rawmidi -i hw:2,0
> ...
> Any other setting (i.e. hw:2,1) reports an error that such a device was
> not found.
The first number is the card number, the second is the device number, and
the third
31 matches
Mail list logo
