Hopefully it's configuration. I'll check for ladcca to be sure.
To answer the previous question, the support is for lash-0.5.0, I've tested it
and it works reasonbly (closing the project leads to a double-delete error in
glibc which I don't know what causes)
---
Also, for some reason lash has a
On Tue, 2006-28-03 at 12:21 +1000, Loki Davison wrote:
> On 3/28/06, Florian Schmidt <[EMAIL PROTECTED]> wrote:
> > Hmm, i don't know what's up with that, but ./configure says "build
> > without lash support" and lateron it fails:
> >
> > /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -fno-exc
On 3/28/06, Florian Schmidt <[EMAIL PROTECTED]> wrote:
> On Mon, 27 Mar 2006 22:52:49 +0100
> Robert Jonsson <[EMAIL PROTECTED]> wrote:
>
> > This release note is for MusE 0.8.1.
> > It is basically a bug fix release for a note-off bug that crept into 0.8.
>
> > [Known issues]
> > See the errata se
On Mon, 27 Mar 2006 22:52:49 +0100
Robert Jonsson <[EMAIL PROTECTED]> wrote:
> This release note is for MusE 0.8.1.
> It is basically a bug fix release for a note-off bug that crept into 0.8.
> [Known issues]
> See the errata section on the homepage for the latest:
> http://www.muse-sequencer.org
> i haven't even unpacked the split tarballs i got from benno. i am happy
> to host (i have disk space and bandwidth), but i'd be even slightly
> happier giving it to someone else to host. your call :)
:-)
Well, apropos the "consolidation" concept, IMHO I think it would be a good
idea. Then agai
This release note is for MusE 0.8.1.
It is basically a bug fix release for a note-off bug that crept into 0.8.
[General]
MusE is a multitrack virtual studio with midi, external, softsynths and audio
support. And a bunch of other things.
[URL]
http://www.muse-sequencer.org/
[Changes from the Cha
Hi all,
I'm currently writing a very simple step sequencer.
It runs fine and has many features I wanted :P
But the sync causes me headaches.
I can start my sequencer more then one time(of course), so
they all start in a sepereate window and have an own midi out thread.
My problem is to sync them al
ico wrote:
Just realized that this also matters LAD members, so I am also forwarding it
to the LAD list.
Best wishes,
Ico
-Original Message-
From: [EMAIL PROTECTED] [mailto:linux-audio-
[EMAIL PROTECTED] On Behalf Of Eric Dantan Rzewnicki
Sent: Monday, March 27, 2006 12:29 PM
To: A l
Just realized that this also matters LAD members, so I am also forwarding it
to the LAD list.
Best wishes,
Ico
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:linux-audio-
> [EMAIL PROTECTED] On Behalf Of Eric Dantan Rzewnicki
> Sent: Monday, March 27, 2006 12:29 PM
> To: A list
Richard Spindler wrote:
> 2006/3/24, Clemens Ladisch <[EMAIL PROTECTED]>:
> > The SUSPENDED and XRUN states can happen asynchronously, i.e., the
> > device can go into them at any time (from some other states), and the
> > next call to snd_pcm_writei() only reports them. In this regard, they
> > a
kurmisk wrote:
> I have write my small _alsa_test_program_.
> [C code ckunkz see below]
> It works good but now i wanna before call
> rc = snd_pcm_writei(handle, buffer, frames);
> somehow check - is sound device free for this call or not.
You could call snd_pcm_avail_update().
If you don't wan
Lee Revell wrote:
> On Fri, 2006-03-24 at 14:09 +0100, Richard Spindler wrote:
> > I'm using snd_pcm_writei to playback some audio, however, after a
> > little time the call fails with the error: "File descriptor in bad
> > state", which I believe I cannot recover from.
> >
> > Why does this happe
12 matches
Mail list logo
