i don't care what the theoretical arguments are for any technology: if
you can't demonstrate that the improvement can be reliably heard by a
majority of humans in double blind testing, i'm not interested.
Higher sample rate might be an appeal for historians or librarians
because it (sort of)
STEFFL, ERIK (SBCSI) wrote:
erm, sorry, but why not use pointers
it's dangerous... null pointers, memory leaks etc. tendency is not to use
pointers unless absolutely neccessary...
References in C++ are just pointers in a sugared form. Actually they are
the same thing in a slightly different
My response to all above discussion about LADSPA and TiMidity++,
I've been playing with TiMidity++ for a while, and hacked it a bit as
well. For what I think, given the complexity of internals, it is not
worth making TiMidity++ an LADSPA host and having to add some TiMidity++
specific MIDI con
given kernel capability patch applied, does jackd give real-time
capability to existing running process (normal user) that decide to
become a jack client?
liulk
[EMAIL PROTECTED] wrote:
>Anyway (IMHO), there should really be an API which combines audio and MIDI playback
>
mostly if you design an api with both midi and audio support, you would
want to isolate the audio part and the midi part as much as possible
because someone who develops a program tha
>
>
>Even if that's feasible with the alsa sequencer, it still has problems -
>say the host wanted to "render" the `song' to an audio file - using the
>sequencer surely it would have to be done in real time?
>
>
Somehow timidity++ manages to do midi wavetable in many ways. it can
play a midi fi
Paul Davis wrote:
>to be slightly more precise: my concern was not over whether ardour
>would or would not be able to put bread on the table. my concern was
>over the possibility that somebody else (presumably with an
>established name and a significant marketing budget/team) could derive
>revenu
Steve Harris wrote:
>On Tue, May 14, 2002 at 03:21:19 -0400, Likai Liu wrote:
>
>>i promise to think about the name more seriously. btw, I have not looked
>>at the JACK API yet. is anybody aware that we absolutely cannot use or
>>take advantage of the whole or parts
Dr. William Bland wrote:
>On Tue, 14 May 2002, Steve Harris wrote:
>
>>On Mon, May 13, 2002 at 04:19:39 -0400, Likai Liu wrote:
>>
>>>I think your point of keeping ladspa the way it is for beginning plugin
>>>writers, but to make extension as another pluging
Steve Harris wrote:
>On Mon, May 13, 2002 at 09:23:11 -0400, Paul Davis wrote:
>
>>I'd prefer "VST". There are dozens of useful plugins, hundreds of
>>developers with some knowledge of it, and demonstrated functionality
>>(albeit with some of the same problems as LADSPA, but signs of them
>>being
Steve Harris wrote:
>I nominate array port types, defaults, port units, proper metadata, a gui
>standard and timestamped events for inclusion. ;)
>
>- Steve
>
one thing at a time, one thing at a time. :-)
I think your point of keeping ladspa the way it is for beginning plugin
writers, but to ma
Paul Davis wrote:
>You've apparently never used an analog modular synthesizer :)
>
Nay, I have used analog modular synth and I know what you're talking about.
>LADSPA is the same. If the plugin declares a port to accept audio, it
>can use the input in any way it wants.
>
No it doesn't work this
Paul Davis wrote:
>but we've already established that LADSPA (like VST) cannot adequately
>describe every parameter to allow easy automated GUI building. the GUI
>control you're describing isn't adequate for controlling a dynamics
>processor - the plugin would need to use LCP and provide a GUI to
Richard Guenther wrote:
>The easiest solution to this kind of problem (parameter change faster than
>nr. of run() calls) is to make the parameter (here: the envelope) another
>audio input stream - this way you get 1:1 parameter:sample mapping. The
>host can be used to feed generated waves to such
"
... ;-)
And someone would have to change the hosts to support plugins that do it.
Likai Liu
s to
make some changes. Again, this is just a proposal, and I'm not even
going to try to push people to use it.
Likai Liu
Paul Davis wrote:
>I'm afraid it would. You need to think about this some more. In any
>given unit of time, a certain number of samples are transformed into a
>varying air pressure wave. What matters is the relation between those
>samples and the original source material. The number of them remai
Lance Blisters wrote:
>>I think the time-stretching plugin is a very legitimate example
>>
>
> I'm looking for a decent-sounding time-stretching algorithm.
> can anybody recommend one?
>
> By time-stretching i mean resampling to any rate, changing
> the audio speed with the corresponding shi
is a morning of work, so please proof read for me if you find any
errors.
Likai Liu
Paul Davis wrote:
>>as a completely different issue, is there a way to indicate if a
>>non-audio port is an array (instead of a single value),
>>
>not possible.
>
>this is "ladSpa": Linux Audio Development SIMPLE Plugin Architecture
>
sigh, I knew these question would not yield any constructi
I suggest$HOME/.ladspa/presets/[plugin-name]/*for user-defined
presets.
and all other default presets in
$PREFIX/share/ladspa/presets/[plugin-name]/*are installed
read-only, but can be overridden by user-defined presets.
I think classifying the ladspa plugin types in the $PREFIX
I have a few more things to say again. You don't need to have the KDE
desktop environment running in order to use KDE applications. All KDE
applications (say, those that use DCOP) know how to start a basic set of
core, life-supporting KDE processes, and these kdeinit processes do
clean up afte
Dave Phillips wrote:
>Likai Liu wrote:
>
>>a *lot* of links on the internet need be updated. including the one in
>linux-sound.org...
>>
>No, that one is correct.
>
i must be looking at the cached version in my browser. sorry about the
misinfo. :)
liulk
I have a few things to say about the whole desktop environment thing.
First of all, if you think there is a project that should or shouldn't
be using a particular desktop environment unlike the way it is now, you
should write your code, submit the patch, optionally try to convince the
project
Jörn Nettingsmeier wrote:
>when i tried the website a week ago, it was 404.
>please keep me posted if you can find him.
>
I had a hard time trying to find the website too, but i got lucky when i
tried freshmeat.net:
http://ciips.ee.uwa.edu.au/~venki-d/greenbox.html
he probably changed his depa
25 matches
Mail list logo