Steve Harris wrote:
>I think the frontpage could do with some cleaning up, I'm the last
>person to criticise about srcuffy out-of-date webpages, but I'm going
>to anyway ;)
Thanks for the feedback.
>Its quite hard to read becaues of the gifanims. the one in the top
left >is hard to make out and the page it links to is very out of date.
It's about due for a redo anyway. The info is still pretty vital. Notice
that there have been almost no questions about how fast Linux latency is
since it was put up.
That's true the link is out of date. But it's the only page I know of
which has so much information on the low latency patch. I can't force
Benno to do the work that he has stated would be done.
>The logos along the top are all in clashing styles and many of them are
>aliased.
I cannot do much about the images provided by other sites.
>There are a few too may colours, and mixing red and blue is generally >bad
As in the NZ, Australian, British, French and US flags?
>On my browser there is a mixture of 2 and 3 coloumn layouts which
makes >it very wide and hard to follow.
What is your browser? I have been trying to keep it working with
netscape 4.x, mozilla, IE, lynx.
>Lots of the information on the frontpage should probably be on >subpages.
The aim is to provide access to most of the info with one click and
without having to scroll.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
Hi all,
I just read this in the latest kernel traffic:
"George Anzinger announced:
This, patch implements the POSIX clocks and timers functions. The two
standard clocks are defined(CLOCK_REALTIME & CLOCK_MONOTONIC)."
I've got a feeling 2.6 is going to be very good for l-a-d :)
Bob
>also, I didn't realize that the "Company Name" is necessary
>to get the web URL to show up.
Fixed :)
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
Is anyone working on this: http://www.ircam.fr/equipes/repmus/OpenMusic?
Apparently they GPL'd the sources, and you can download it, but it's
written in Lisp, and MCL PPC Lisp at that. However, as they put it:
"At the beginning, this will make sense only to people owning the
Digitool compiler. Although we are conscious that this limitation does
not fit clearly into the GPL framework, we think that making the sources
available is an oppurtunity to raise collaborations leading to new
versions of OM that would depend only on open sources compiler,
particularly on linux platforms"
I did speak with some Ircam people at Darmstadt this past summer, and I
don't think they really have the interest in doing the port themselves.
However, Ircam certainly isn't anti-Linux, so they might be
able/willing to help/be persuaded to work on it. (François, and
Norbert, if you're on this list, feel free to comment.)
-dgm
I'm trying to get a picture in my mind as to what is out there. Could
someone please give me a list of Wave editors that are seen as
potentially really good under Linux?
Cheers,
-Lea.
http://plugin.org.uk/meterbridge/
Added a correlation meter to the JellyFish, thanks to Ari Kauppi for
pointing me to the maths. Its calculated using the non-parametric
correlation function Tau, incase anyone cares.
Changed the default meter type to PPM.
Also added a simple osciloscope display.
Hopefully this will be the last release for a while (unless there are any
bugfixes).
- Steve
I contacted the author of the VQF plugin about opinions of running
windows plugins under Linux. He is not subscribed to LAD so he told me
to forward this mail to the list.
cheers,
Benno
On Tue, 22 Oct 2002, Benno Senoner wrote:
> We are currently discussing about the possibility to run VST or
DirectX audio
> plugins on Linux in real time.
> I remember you wrote an xmms plugin that allowed to run the windows
VQF plugin
> under Linux using wine & co.
> <snip>
> It would be cool if you could write on the linux-audio-dev list about
> experiences in that field.
I am afraid I will have to keep this short as I'm really busy at the
moment. I also am a long way from being an audio expert or wine so I
doubt
my experiences will be of much use to you hence I didn't subscribe to
the
list . Feel free to forward this to the audio-dev list and cc me on it
if
you wish
First, the solution I used for the VQF plugin was extremly clunky. There
was no way of letting the plugin run inside XMMS without causing
segfaults. They simply did not merge well no matter what I tried.
I suspect but never proved that it was how WINE has to lay out it's
memory
to be able to mimic how Windows sees things like segments. The layout is
drastically different to how a Linux app normally sees things. By the
time
a VQF plugin could be loaded, the two very differnet approaches to
managing memory simply did not work well together
In the end, the solution used was this;
1. At XMMS start, fork and exec an application that uses libwine to load
the windows DLL. Communicate with the parent through pipes, sockets
or
shared memory
2. Start up XMMS as normal
3. The plugin just implements stub functions for every routine a plugin
is
meant to implement and communicates the information to the child
This had a number of issues. First, it was difficult to get information
from the plugin. It opened the sound device directly itself which meant
that visualisation data was not available.
At one point, this was resolved by hacking wine itself to write the PCM
data to a named pipe rather than playing to a device but needless to
say,
it was too ugly to live and couldn't really be distributed easily. (I
considered it unreasonable to get users to patch and compile WINE just
to
play a piece of music, visualisations weren't that important).
If I had a nice plugin, what I would try to do is set up two unamed
pipes
at application start to a child application using libwine. One pipe for
writing would send commands and one pipe for reading would take PCM
data.
I don't know how viable this is for you.
> I'm not a windows / wine expert but commonsense says me it should be
> possibile to run these windows plugins under Linux in real time with
small
> buffer sizes in order to get low response times (low latency).
I would be inclined to go the other way. With the above solution, I
would
try and buffer as much data as humanly possible to try and avoid the
overhead of calling wine constantly. For example, I would try and get 10
seconds worth of data from the windows plugin before starting to play
anything. Once I had the PCM data, it would not matter if the plugin
could
not make real time contraints.
> It should be possible to let wine handle the GUI stuff . (if word and
excel
> runs then it should be able to run plugin GUIs too).
It can, but remember that if you are trying to use this plugin with a
normal application, you are likely to run into a lot of trouble. At
least
I did, but this was a few years back. Things might be different now
I imagine you already have checked out how avifile loads it's plugins.
When I last looked at it (a few years back), it was using a stripped
down
version of WINE to just load the plugins and get the function pointers.
It
might be worth checking into.
--
Mel Gorman
MSc Student, University of Limerick
http://www.csn.ul.ie/~mel
I'm really late on this one, but I finally looked at the linked
waveforms. Here is what I see.
Ignoring push-pull crossover distortion, there are basically two kinds
of distortion happening. There are two stages to the amplification, a
pre-amp and an output amp. The pre-amp provides soft clipping of the
input signal, generating harmonics of the input signal. As the input
level is increased, the pre-amp output looks more like a square wave but
with rounded edges. The pre-amp is outputting at its maximum voltage
(saturation). The output amp sees this square wave as a dc step input.
The output circuit is under damped, meaning that its step response will
include ringing. The frequency of the ringing is related to the design
of the output circuitry and has nothing to do with the frequency of the
input signal, since the output amp sees its input as dc. The degree of
clipping from the pre-amp determines how long the output amp sees its
input as a step, and determines how long the output signal contains the
ringing. The output amp is not operating at maximum output voltage.
This is what allows the overshoot and undershoot spikes in the ringing
to pass unclipped. For even more distortion the output amp could be
biased to clip the overshoot portion of the ringing.
This pseudo-knowledge comes from a distant dream of having studied
impulse, step, and ramp responses of analog circuits 20+ years ago.
Tom
Apologies taking time to package this up. The patches included are
tested against 2.4.19 or later.
This patch fixes a few bugs and implements full n-channel support of
greater-than-stereo USB audio devices, such as the emagic emi 2|6. I
also opted to make the minor extention to OSS to define 24 and 32 bit
AFMT modes, and the patch includes this. It does not break any
existing OSS compatability, and unaware apps can continue to be
unaware. The modified audio.c will build without the OSS extentions
to soundcard.h.
As suggested, I didn't bother with OSS mixer extentions. The device I
care about most doesn't expose a per-channel mixer feature regardless.
Also, I was wrong: 2.5's audio.c is different, but the differences
appear to be for the sake of keeping up with other changes to USB
support. I did not attempt to apply the included patch to 2.5's
audio.c, but I'd give it even odds with sufficient fuzz.
Monty