Roger Larsson wrote:
>
> ...
> An alternative would be Andrew Mortons amlat - it is simpler, possibly better
> in an automated environment.
That would require a kernel patch.
I always use a mucked-with version of Mark Hahn's `realfeel'
application. Simple, accurate.
Attached here.
/*
* This
>From: [EMAIL PROTECTED]
>
>Soft real-time: average case is X, standard deviation is Y
>Hard real-time: worst case is X.
Thanks for the defs.
What is the practical worst case in standard Linux in terms of
audio latency (say)? Last I checked the worst case was good enough
for disk recorder/player.
On Fri, Jul 12, 2002 at 03:28:29 +0200, Martijn Sipkema wrote:
> > So, one vote for adding the version
> > to the API ?
>
> I would like to add that old LADSPA plugins can be easily identified
> because they lack the \'version\' symbol, so there really is not segfault
> problem as far as I can se
>> encoding, the value (generally) varies between -(2^N) and (2^N)-1,
>> where N is the number of bits used to store the value. So a 16 bit
>> value will vary between -65536 and 65535. there are other ways of
>
>Errr, I think you meant "... between -(2^(N-1)) and 2^(N-1)-1 ... "
>So you get a ran
Hi Paul,
> encoding, the value (generally) varies between -(2^N) and (2^N)-1,
> where N is the number of bits used to store the value. So a 16 bit
> value will vary between -65536 and 65535. there are other ways of
Errr, I think you meant "... between -(2^(N-1)) and 2^(N-1)-1 ... "
So you get a
On Fri, Jul 12, 2002 at 04:01:29PM +0300, Juhana Sadeharju wrote:
> >From: [EMAIL PROTECTED]
> >>
> >> I agree. That's why it is needed. And for realtime threads SCHED_FIFO/RR
> >
> >You lost me there. A RT scheduler is needed for RT tasks.
>
> You're selling RT Linux, right?
Of course. But RT
>Yes I did have a look at this tutorial and it has been quite good,
>but I don't understand the signal which is produced there.
>I guess this seems to be a digital 101010... signal.
>But it sounds like an disordered signal and I don't
>understand how to unfluence the volume or the of frequency thi
> >Well, it\'s not _that_ important, but there are a few good reasons...
> >
> >1) The LADSPA API was not designed for ABI changes (most notably the
> > interface version is not exported by plugins). This means that
> > old plugins that you didn\'t remember to delete/recompile can
> > caus
>From: [EMAIL PROTECTED]
>>
>> I agree. That's why it is needed. And for realtime threads SCHED_FIFO/RR
>
>You lost me there. A RT scheduler is needed for RT tasks.
You're selling RT Linux, right?
The standard Linux in our application can be considered as
a real-time system because audio cards
Hi Philipp,
> But it sounds like an disordered signal and I don't
> understand how to unfluence the volume or the of frequency this signal.
> I actually have an algorythm for sine signals but it's too complex
> for undestanding.
It seems like you're missing the basic understanding how digitial a
Hello dear Dr. Nagorni,
Yes I did have a look at this tutorial and it has been quite good,
but I don't understand the signal which is produced there.
I guess this seems to be a digital 101010... signal.
But it sounds like an disordered signal and I don't
understand how to unfluence the volume or
On Fri, Jul 12, 2002 at 10:31:14AM +0200, Peter Hanappe wrote:
> [EMAIL PROTECTED] wrote:
> > On Fri, Jul 12, 2002 at 01:40:42AM +0200, Peter Hanappe wrote:
> >
> >>[EMAIL PROTECTED] wrote:
> >>
> >>
> >>>For example, in RTLinux, fifos shared
> >>>between Linux (non-rt) processes and RT threads a
> 2) Marketing. Only way to make developers believe that your
>ABI is truly stable and will not change all the time is
>to keep it stable. Just saying that "after this change there
>won't be any modifications" every six months just doesn't cut it.
>Whether this is a problem for LAD
13 matches
Mail list logo
