Subject: FW: [linux-audio-dev] LADSPA problem
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Tue Oct 24 2000 - 02:54:07 EEST
Sorry I didn't post this to the list initially. Haven't recreated/spotted
the bug in analyseplugin - I'm probably being stupid. Oh, and though the
code mustn't crash if bounds are exceeded it may sound as horrid as it
likes ;-)
--Richard
-----Original Message-----
From: Richard W.E. Furse [SMTP:richard_AT_muse.demon.co.uk]
Sent: Thursday, October 19, 2000 8:07 PM
To: 'Steve Harris'
Subject: RE: [linux-audio-dev] LADSPA problem
It sounds as if you've found a bug in analyseplugin. Bounds are supported
for audio streams although they are only hints and your code must not crash
if bounds are exceeded.
I'l have a look at analyseplugin when I have a minute.
Have fun,
--Richard
-----Original Message-----
From: Steve Harris [SMTP:S.W.Harris_AT_ecs.soton.ac.uk]
Sent: Thursday, October 19, 2000 6:31 PM
To: Linux-audio-dev
Subject: [linux-audio-dev] LADSPA problem
Hi,
I've been playing with LADSPA on and off for a couple of days, but I've
hit a problem: as far as I can tell the input range of an audio stream is
not specified, I was expecting it to be -1 to 1, but it looks like the
host can choose any value it likes.
This causes problems with amplitude dependent plugins. I don't seem to be
able to specify upper and lower bounds on audio ins (analyseplugin gets
confused, anyway, always shows 0 to 0).
What are you supposed to do? The limiter I looked at works by asking
for the threshold (in arbitary units), but this isn't a very good
solution. Surely the user isn't expected to know the internal ranges
of thier application? There is a LADSPA_HINT_SAMPLE_RATE, why not a
LADSPA_HINT_AMPLITUDE?
Hoping I've missed something,
Steve
--
Stephen Harris
MALIBU Technical Officer & JoDI Webmaster
IAM Research Group
University of Southampton, UK
07970 557047
swh_AT_ecs.soton.ac.uk 023 8059 2774
This archive was generated by hypermail 2b28 : Tue Oct 24 2000 - 03:29:29 EEST