Now supports connecting to input ports and you can control the number of
columns of meters with -c, -c 1 will give you a vertical strip.
Input monitoring "works" by disconnecting everything from the port,
connecting it to the meter in and connecting the monitor out of the meter
to the original port. When it quits it tries to put things back the way
they should be, but it might not always get it right.
If you run too many (8+) then things start to get dodgy, jack carries on
running, but you can't quit meters. I don't know why.
Thanks to Joern and Gerd for testing the extra-alpha versions, and Kai for
fixing the autoconf mess.
I've tried to subscribe to Eric A Walsh's TiMidity mailing list but it doesn't
appear to be working... (or there's too little latency in my patience...)
So... would anyone be even vaguely interested in...
a) an aRtsd patch (trivial, really)
b) an extension to the "order=o" soundfont parameter to make it somewhat more
c) some minor "fixes" (hopefully just code tidy-ups)
d) some documentation I've written while reading the code (I've been trying to
get a handle on exactly what TiMidity++ does and doesn't do as a soft-synth)
...being posted to this list? (Feel free to pick'n'choose.)
(The patches amount to 746 lines against the current beta. The doc amounts to
608 lines but it's not completely finished yet...)
> -----Original Message-----
> From: Joern Nettingsmeier [mailto:email@example.com]
> Steve Harris wrote:
> > http://plugin.org.uk/meterbridge/meterbridge-0.0.4.tar.gz
> either it is not really compressed, or my browser performed some
some browsers automatically uncompress, even though they do not change
name, as far as I know IE does it, maybe some other browsers do it as
just a short question to those who already have Richard Boulanger's "The
Csound Book". I was going to order one soon, what is your
impression/opinion on it? I understand that a certain degree of
knowledge about synthesis/computer music is required in order it to make
sense to the reader (I hope I have that), but if that is fulfilled, can
you recommend this book? Or what are its weak spots in your opinion?
Frank (expecting at least one answer from bright.net ;-)
In the interests of making life easier for my fellow penguinistas Boost
Hardware has aquired a new user friendly, audio centric, domain name.
You can now point your browser at
and the space occupied by the LAU guide and the quicktoots will be
rendered before your eyes.
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
from kernel traffic:
Linus agreed that if the VM is as good as it seems to be, indeed
the upcoming release deserves to be called 3.0. But he also pointed
out that there are many silent users who tend not to speak up until
there is an official release. He asks, "people who are having VM
trouble with the current 2.5.x series, please _complain_, and tell
what your workload is. Don't sit silent and make us think we're good
to go.. And if Ingo is right, I'll do the 3.0.x thing." ---
since the VM system has screwed us streaming audio types in the past,
it seems wise for us to try it out soon. still, i can't say i'm
thrilled at the prospect ...
Sorry, this is not directly audio related.
I'm hacking together a VU meter app for jack, using FLTK, and it works OK,
except that when the update rate falls out of sync with the video refresh
rate the window flickers. I'm pasting a bigass image as the background,
see screenshot http://inanna.ecs.soton.ac.uk/~swh/vu-ss.png (apologies
for the tacky brushed steel background, its a placholder, honest).
I seem to remeber that on the Amiga and in GL I could issue a call to wait
for the next vertical blank, forcing the redraw to be in sync with the
video hardware. Is there an equivalent in FLTK or X?
How do other people get round this?
PS I know a VU meter in a PCM system is about as much use as an underwater
hairdryer, but its a stepping stone to a PPM meter, and you can run it
in peak mode, but with a VU scale and balistics.