Hi,
I am adding a Daemon mode to jackEQ and have most of the code in place now.
I am stuck at the point where the daemon starts up and keeps going.
Essentially I need the daemon mode equivalent of gtk_main() that keeps
ticking over until the app is told to stop or otherwise shutdown.
I have not threaded the app at this point so hopefully there is a very
simple solution.
Any thoughts on this are appreciated.
Cheers.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.comHttp://lau.linuxaudio.org - The Linux Audio Users guide
========================================
"Anything your mind can see you can manifest physically, then it will
become reality" - Macka B
Now that mingo's (et al) RT patches are coming into mainstream, what is
the corporate rationale behind it and the running order of urgency?
I am fishing for some information on; if it is the disk-drives, the
network drivers, the usb stack or something else that I am too ignorant
to have noticed?
What worries me the most, is corner-cases on network, blocking multiple
cpu's.
FYI: I have been asked to set up a bunch of Xeon boxens to serve a VPN
over WiFi, they/we are currently using kernel 2.6.17 (debian etch as of
today.) So this is not stricly about audio, but I would guess all of us
would like some clarification here. After all, we have followed the
evolvement of these patches for quite a few years by now.
--
mvh // Jens M Andreasen
Hello!
Did any of you guys ever tried to use the OpenAL API interface towards a
Firewire sound device like FA-101? I see that it appears on your lists as a
device that has drivers on Linux.
Best regards,
Helge Fredriksen
How about we stop the seemingly endless discussion and instead all roll-up
our sleeves and actually do this?
Here's what I offer on behalf of linuxaudio.org:
1) generous hosting space
2) virtually unlimited bandwidth
3) docs.linuxaudio.org and apps.linuxaudio.org domains
4) accounts to maintainers
5) server support as needed
What we need volunteers to do:
1) port Dave's pages over into a legible and appealing format to
apps.linuxaudio.org
2) cross-link those pages to docs.linuxaudio.org page (in addition to apps
homepages) which will be a wiki with documentation templates and
standardized layout
3) need to design an appealing interface for both sites (hence consider this
an open call for volunteer designers) -- this cannot be emphasized enough:
we do not want an ugly, plain website, but a nice inviting and user-oriented
resource.
4) create a generic wikipedia entry which gives a summary, philosophy, and
notable achievements of the linux audio scene and provides critical links
(hence it would be used as a portal rather than an exhaustive resource for a
moving target which would never fly with the wikipedia editors anyhow)
On a side note, here's another offer:
As per my discussion with Joern, on behalf of linuxaudio.org I also offer
free unlimited space for porting over LAU and LAD lists to
lists.linuxaudio.org in hopes that we continue consolidating these
invaluable resources. Maintainers will be given appropriate access
privileges etc.
Any takers?
Best wishes,
Ico
Helge Fredriksen wrote:
>
> Did any of you guys ever tried to use the OpenAL API interface towards a
> Firewire sound device like FA-101? I see that it appears on your lists as a
> device that has drivers on Linux.
AFAIK OpenAL doesn't talk to hardware directly - it provides an API for
programs to use but sends data to the soundcard via the operating system's
native sound system. Therefore the devices supported by OpenAL are the
devices supported by the underlying operating system. For many sound cards
under Linux, that native sound system is ALSA (http://www.alsa-project.org).
OSS was the previous default native sound system under Linux and is still in
use by numerous programs.
The FA-101 is (as you'd know) a firewire interface. Support for firewire
interfaces is starting to gain momentum now but for various technical
reasons this is not provided by ALSA at this time. The support effort is
the so-called Freebob project (http://freebob.sourceforge.net) in
combination with the JACK system (http://www.jackaudio.org/), a low-latency
audio API. Only a small number of firewire audio interfaces are supported
by freebob at this time, but from what I read the FA-101 is one of them.
Getting back to your question, if OpenAL supports JACK under Linux then in
theory you could talk to an FA-101 via OpenAL. According to the OpenAL
website it currently only supports OSS and ALSA under Linux. Therefore at
this point in time you can't use OpenAL to send audio to an FA-1-1.
However, unless you particularly wanted the 3D modelling features of OpenAL
you'd probably be better off using the JACK API directly.
It should be noted that a long-term goal of the freebob project is to
implement an ALSA driver for the firewire interfaces. However, there is
still much to do before that will occur so I can't see it appearing any time
soon. Once it did appear (and assuming OpenAL don't implement an interface
to JACK earlier) you would be able to use OpenAL with the FA-101.
Regards
jonathan
After several months without a stable release but lots of development
activity, we are pleased to announce CLAM 0.95
CLAM (http://clam.iua.upf.edu) is a C++ framework for doing research and
app development in audio and music. It comes with a set of applications
ready-to-use.
Most important in this release is NetworkEditor 0.4, with a radically
reworked UI based on Qt4.2, lots of work on stability and usability, and
new visual-prototyping features.
You can visually prototype standalone apps (or audio plugins):
Edit audio networks with NetworkEditor, then edit its UI using Qt Designer
and CLAM widgets plugins. Finally, Prototyper let you run the audio network
with its UI.
This is better shown in this quick tutorial:
http://iua-share.upf.es/wikis/clam/index.php/Network_Editor_tutorial
This release comes with many new processings, mostly spectral
transformations.
But we want to highlight the tonal-analysis which does chords identification
at real-time, and its related visualizations. This code is based on the
work done by researchers at Queen Mary University (London) and Universitat
Pompeu Fabra (Barcelona). More credits are in the About box.
These and many other improvements can be found in the ChangeLog:
http://clam.iua.upf.edu/ChangeLog.txt
This release brings new packages for Linux (Debian sid, Ubuntu edgy) and
Windows installers.
In Linux, you can simply add new sources to /etc/apt/sources.list
deb http://clam.iua.upf.edu/download/linux-debian-sid ./
deb http://clam.iua.upf.edu/download/linux-ubuntu-edgly ./
Both Linux and Windows comes with desktop integration and several examples
ready to use. Mac OSX packages will be catching up next weeks.
Bug reports and any feedback is very welcomed (and needed).
The CLAM team
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Greetings:
I've not checked out recent SVN sources, but watching the devel mail
list I get the distinct impression that there's no internal development
going on with Hydrogen. Almost all traffic on the list is concerned with
translations.
So, what's the story ? Is there a Hydrogen 1.0 in the works or is it a
deader ?
It would be a deep shame to see Hydrogen's development languish.
Best,
dp
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've started to convert the information from linux-sound.org into a
distributable doku-wiki.
http://linux-sound.sonologic.nl/
This is a prototype installation and experimental suggestion!
Please review and comment before further development proceeds.
** content information **
it's basically a database of http://linux-sound.org chopped up into text
files. I have added URLs to [external] screenshots and logos to some
pages and updated or deleted a few dead links.. it's still a long way to
go, but some tasks could be semi-automated (fi. searching for dead links..)
I am open to suggestions on how to maintain the content. This prototype
is open for editing to all registered users (email verification).
I can share experiences or rewrite and improve the dokuwiki to some
extend, and may contribute to content but not on a day to day basis.
patches, suggestions and comments are welcome.
** design/layout look&feel **
no efforts have been taken to change the default dokuwiki look and feel.
Is anyone interested in
a) designing and writing a dokuwiki template
b) start a discussion on aims and goals for good user interaction design
c) create a wiki-page to host a design contest
d) rewriting the dokuwiki template ;-)
** technical- and mirror information. **
The data set is a 20MB git repository.
dokuwiki keeps it's data in txt files. I've started to put them under
git version control. The idea for mirror-sites is to
check out and branch their wiki while maintainers can merge information
upstream. dokuwiki only requires php.
The wiki itself is available as a separate git repository (incl.
pre-installed plugins and config) - the independent data-set git repos
should work with every dokuwiki installation. The whole system including
generated-meta data is about 50 MB.
more information:
http://linux-sound.sonologic.nl/devel:githttp://linux-sound.sonologic.nl/devel:setup
#robin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFfI+seVUk8U+VK0IRAgrzAKDEF5aI9h8yZOis11v+T+GRTugL3wCfVc/z
N/dkTVHWwZMWz9ca8iVnDcY=
=z/Nj
-----END PGP SIGNATURE-----