Taupter wrote:
[ALSA sequencers and that repeating note problem]
> try noteedit.
Of course! Ok so, NoteEdit worked fine and so I reinspected our code and lo
and behold found a little bugette with our note off matrix. Now fixed.
Sorry for the false alarm.
B
At Thu, 1 Aug 2002 10:08:38 +0100,
Richard Bown wrote:
>
> Taupter wrote:
>
> [ALSA sequencers and that repeating note problem]
>
> > try noteedit.
>
> Of course! Ok so, NoteEdit worked fine and so I reinspected our code and lo
> and behold found a little bugette with our note off matrix. No
Martin Langer wrote:
> On Wed, Jul 31, 2002 at 12:26:33PM +0200, Clemens Ladisch wrote:
> >
> > IMHO the garbled device name is strange, too. ;-) This is a (rather
> > harmless) buffer overflow which has been fixed by the latest version of my
> > other patch.
>
> Rather harmless buffer overflows
Takashi Iwai wrote:
> well, so the problem doesn't lie on alsa side?
No, it was in our app code. I'm afraid this doesn't help you too much if you
suspect there's a bug in the emu10k synth driver anyway - I'll keep listening
out for one though.
B
--
On Wednesday 31 July 2002 11:55 am, Bob Ham wrote:
> On Mon, 2002-07-29 at 22:25, Bob Ham wrote:
> > On Mon, 2002-07-29 at 21:53, Paul Davis wrote:
> > > you will also probably want to turn down the line-in level, so that
> > > the direct feed is not audible. that is also an sblive issue.
> >
> >
Hi Benny,
At Sat, 27 Jul 2002 01:01:48 +0200,
Benny Sjostrand wrote:
>
> Hi again!
>
> Seems there's quite big interest in the cs46xx stuff. Finally i've been
> able to have output from
> the rear channel on the secondary CODEC. For the moment the output are
> same on both
> rear and front ch
>
>
>
>I merged your codes into the cvs.
>The codes are almost identical except for small bugfixes,
>re-indentation, and replacement of debug printing.
>
-:)
>
>To be sure, the old dsp image is still chosen unless
>CONFIG_SND_CS46XX_NEW_DSP is set to yes.
>For compiling the new dsp image, please
At Thu, 01 Aug 2002 11:39:37 +0200,
Benny Sjostrand wrote:
>
> >
> >
> >
> >I merged your codes into the cvs.
> >The codes are almost identical except for small bugfixes,
> >re-indentation, and replacement of debug printing.
> >
> -:)
>
> >
> >To be sure, the old dsp image is still chosen unless
On Thu, 2002-08-01 at 12:18, Gareth Duncan wrote:
> I don't know if this is of any help at all, but maybe if you can replace the
> capture of the Line item with the equivalent on the livedrive (whatever that
> might be) it might work.
It should work. It doesn't.
--
Bob Ham: [EMAIL PROTECTED
>
>
>
>
>about the secondary codec on terratec xfire: it's still not detected.
>could you test the latest cvs driver? i'm afraid that i did something
>wrong in merging...
>
My quick look on the cvsweb everything looks just fine, just one small
critical
fix that I missed in my 0731 release, I bel
Anyone on the list have echo hardware? (darla,gina,layla,etc)
-Dan
--
[-] Omae no subete no kichi wa ore no mono da. [-]
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Dan,
I have a Gina, and emailed Echo tech support a while back and they
indicated they would be releasing their core C++ drivers as open source.
They indicated 1-2 weeks until driver release, but it is now going on 3
weeks i think, so I don't hold out too much hope for a prompt release.
Even
On Fri, 2 Aug 2002, Pete Black wrote:
> They indicated 1-2 weeks until driver release, but it is now going on 3
> weeks i think, so I don't hold out too much hope for a prompt release.
They have released it here:
http://www.echoaudio.com/Download/Developer/EchoGenericDriverA0.zip
-Dan
--
[-] O
>On Fri, 2 Aug 2002, Pete Black wrote:
>> They indicated 1-2 weeks until driver release, but it is now going on 3
>> weeks i think, so I don't hold out too much hope for a prompt release.
>
>They have released it here:
>http://www.echoaudio.com/Download/Developer/EchoGenericDriverA0.zip
wow.
no
>
>
>
>about the secondary codec on terratec xfire: it's still not detected.
>could you test the latest cvs driver? i'm afraid that i did something
>wrong in merging...
>
I've done a quick test with the CVS code now, and it seems to work just
fine, i just got some newbie
questions, how do acti
Hi all,
I got a midisport2x2 interface. I had it working with the usb-midi driver but then I
found out that alsa .rc3 had support for usb-midi. So I got the CVS version and all
compiled fine. I had it working, too. Now, for some strange reason, no matter what I
try I am only able to get M
16 matches
Mail list logo
