I had the idea the other day that you could theoretically implement a
Winmodem driver as a JACK client. All you would need is an ALSA driver
that exposes the hardware part of the modem as a sound card, a mechanism
to inject the resulting bits back into the kernel networking layer, and
the DSP knowledge to implement a software modem...
This is almost completely pointless, but might be an interesting CS
project.
Lee
Hi, wondering if this might tickle anyone's fancy on the agnula team.
The agnula live cd is a great idea. I would love to be able to customize
that however, to add my own apps, and of course data files. I play live
shows using csound5, but would like to add jack, jammin, ladspa plugins
etc, and some of my custom apps. So obviously I need to be able to add
all those, and all the orc and sco files and any samples. Is there or
could there be a relatively straight forward way of customizing the
agnula live cd, perhaps a script or app that allowed one to make a
custom version on a small partition and then burn it or something. I
figure that would be fantastic for shows in case of hardware failure,
disk failure, or even stolen machine as one could essentially do your
show off someone else's pc if need be. It would be really sweet if you
could count on it recoginizing and being happy with all major sound and
midi cards, etc.
Any thoughts, pointers, etc?
Thanks
Iain
Hi all,
For all music notators out there, there is a new release of denemo
(denemo.sourceforge.net).
It has lots of improvements including the graphical interface and
added functions.
So if you are a denemo user now is a good time to get the latest and
greatest.
I am using the cvs which has already a bunch of bug fixes since the
release, but either way it is quite an improvement from the previous
release, with 50 undo's!
Best wishes
Aaron
Hi!
Is there some tool to accomplish such task: take some sound (wav)
file and plot (or give some kind of table) peak spectrum values
along all the file in given frequency range?
Andrew
Hi all,
Anyone going to LCA2005? (note that's LCA in Australia, not LAC in
Germany!)
I'd like to see if I can find a keyboard controller and/or guitar for my
presentation (not to mention the jam session afterwards). I'm flying in
from Melbourne and can't bring any of that stuff. Keys in particular
would be /really/ nice to have, if there's any Canberra folks around.
.. thought I'd ask. :)
Regardless, drop your name in this thread anyway - it'd be nice to have
something of a roll call
Cheers,
-DR-
Greetings:
Users are constantly wrestling with issues surrounding the software
mentioned in the subject line, and I would like to find out what
directions are planned for those projects. Here's what I see now:
1. The vstserver project is functionally dead. It cannot work with
newer versions of WINE, and it appears that Kjetil does not plan to keep
it updated to accommodate the new versions. Alas, this also means that
his nice vsti, ladspavst, and k_vst~ projects are also unusable. :(
2. The libfst project is essentially unmaintained. Again, WINE
versions wreak havoc with users who want to keep both fst and WINE
up-to-date. Paul and/or Torben: Is the libfst project going to see any
more activity from your end, or should it be considered an open project
and up for grabs ?
3. The dssi-vst bridge is still unknown to me because of issues with
RH9, and I've not had time to test it on FC3. But is there any general
feeling that dssi-vst is a better route to take, at least for the normal
user ? Btw, I like the DSSI API, but it seems slow in catching on with
developers. Is that perception correct ?
Please understand that I'm in no way criticising the work done on
these projects so far. In point of fact, I'm extremely happy they exist,
but I'm also in considerable doubt whether they can continue to be
useful without further maintenance. Users are writing to other users to
figure out how to fix small problems (usually with libfst), but these
repairs are not making their way back into the codebase, which seems
rather non-optimal to me. I'm also aware that the greater problems exist
because of WINE's inherent instability (WRT its development, not
necessarily its usability) and that Linux audio developers can't be
responsible for WINE fixes too. Perhaps more crosstalk between the WINE
developers and the LAD folk (similar to the recent discussion re: the
kernel list and LAD) would help smooth the way for a more consistent and
more manageable VST/VSTi bridge for Linux ?
So, any comments or useful suggestions ?
Best,
dp
Hiya,
Now that I've finallly gone to a 2.6 kernel (latest gentoo-sources,
2.6.11.something) I thought I'd fire up latencytest and see
what it tells me. Unfortunately, latencytest0.42 still seems
to be the latest and it no longer compiles. Anybody got a fix?
pw@kermit latencytest0.42 $ make
gcc -Wall -O2 -DUSE_PENTIUM_TIMER -c rtc_latencytest.c
rtc_latencytest.c:24:41: macro "rdtsc" requires 2 arguments, but only 1
given
rtc_latencytest.c:25: error: syntax error before '{' token
rtc_latencytest.c: In function `main':
rtc_latencytest.c:142: warning: passing arg 2 of `signal' from
incompatible pointer type
rtc_latencytest.c:143: warning: passing arg 2 of `signal' from
incompatible pointer type
rtc_latencytest.c:261:24: macro "rdtsc" requires 2 arguments, but only 1
given
rtc_latencytest.c:261: error: `rdtsc' undeclared (first use in this
function)
rtc_latencytest.c:261: error: (Each undeclared identifier is reported
only once
rtc_latencytest.c:261: error: for each function it appears in.)
rtc_latencytest.c:295:22: macro "rdtsc" requires 2 arguments, but only 1
given
rtc_latencytest.c: In function `my_exithandler':
rtc_latencytest.c:295: error: `rdtsc' undeclared (first use in this
function)
rtc_latencytest.c:365:19: macro "rdtsc" requires 2 arguments, but only 1
given
rtc_latencytest.c: In function `calibrate_loop':
rtc_latencytest.c:365: error: `rdtsc' undeclared (first use in this
function)
rtc_latencytest.c:367:19: macro "rdtsc" requires 2 arguments, but only 1
given
rtc_latencytest.c:406:21: macro "rdtsc" requires 2 arguments, but only 1
given
rtc_latencytest.c: In function `sigio_handler':
rtc_latencytest.c:406: error: `rdtsc' undeclared (first use in this
function)
rtc_latencytest.c:408:21: macro "rdtsc" requires 2 arguments, but only 1
given
make: *** [rtc_latencytest.o] Error 1
--
Paul Winkler
http://www.slinkp.com
Hello,
A question for the wizards of the USB audio drivers.
At 48 kHz, USB delivers and consumes audio samples in chunks of 48 frames.
When using ALSA's mmap inmterface, these will repackaged to the requested
period size. So one would expect to see a jitter with a range of 1 ms in
the wakeup times of a thread waiting on this interface. For example for
p = 256 the real periods will be 6ms, 5ms, 5ms, 6ms, 5ms, 5ms, ... for
an average period of 5.333 ms.
In practice, when using snd-usb-audio, the jitter range is close to 4 ms.
Why is this, and can something be done about it ?
--
FA