JACK RELEASE 0.98.0
JACK is a low-latency audio server, written primarily for the GNU/Linux
operating system. It can connect a number of different applications to
an audio device, as well as allowing them to share audio between
themselves. Its clients can run in their own processes (ie. as normal
applications), or can they can run within the JACK server (ie. as a
"plugin").
JACK is different from other audio server efforts in that it has been
designed from the ground up to be suitable for professional audio work.
This means that it focuses on two key areas: synchronous execution of
all clients, and low latency operation.
JACK is available at http://jackit.sf.net
***CHANGES***
Fixed bug when using non-dithered 16bit output.
Fixed crashing bug with JACK clients that use SSE.
three new functions in JACK API:
int jack_client_name_size(void);
int jack_port_name_size(void);
int jack_port_type_size(void);
These sizes are inclusive of the final NULL character.
Automatic server startup (more on this below).
Added OSS JACK driver.
New option -m,--no-mlock:
Do not attempt to lock memory, even if --realtime.
New option -p,--port-max n:
Set the maximum number of ports the JACK server can manage.
The default value is 128.
New option -T,--temporary:
jackd will exit when last client disconnects.
Configuration process reworked for better portability. This has
helped jack run on MacOSX and FreeBSD.
Added JACK thread initialization callback.
***AUTO START SERVER FUNCTIONALITY***
libjack will now try to automatically start jackd when jack_client_new()
is called if it isn't already running. Because this changes the
semantics of jack_client_new() and confuses certain apps, the new
semantics apply if and only if $JACK_START_SERVER is defined and
$JACK_NO_START_SERVER is not defined. This will change in future
releases.
libjack determines the proper arguments to pass to jackd by first
checking ~/.jackdrc, failing that /etc/jackd.conf, failing that
hardcoded strings that we've determined to be the most likely to work on
a variety of platforms.
The format of ~/.jackdrc and /etc/jackd.conf is as follows:
absolute path to the jackd or jackstart binary to be executed, followed
by the regular arguments all on one line. libjack will automatically
insert the --temporary argument so that any auto started jack server
will exit when the last client has disconnected.
If libjack is unable to start the server, jack_client_new() will fail
normally.
We hope that this new functionality will make using JACK easier and more
seamless with the JACK client.
Taybin
Should there be 3 seperate irc rooms then? One for each concurrent lecture?
Taybin
-----Original Message-----
From: Joern Nettingsmeier <nettings(a)folkwang-hochschule.de>
Sent: Apr 20, 2004 5:33 AM
To: Linux Audio Development Mailing List <linux-audio-dev(a)music.columbia.edu>,
Linux Audio User Mailing List <linux-audio-user(a)music.columbia.edu>
Cc: Frank Neumann <Frank.Neumann(a)st.com>, Goetz Dipper <goetz(a)zkm.de>,
"Dr. Matthias Nagorni" <mana(a)suse.de>
Subject: [linux-audio-user] laconf2 call for help w/ irc and streaming
hi everyone!
as you will certainly have heard, we are getting closer to the 2nd
linux audio conference at zkm (http://www.zkm.de/lad).
as you might also have heard, we will have live streams of all talks
and lectures in ogg format for those who can't make it there in person.
last year, we had an irc "feedback channel", meaning i would sit in
the lecture room with a notebook, answer questions from people who
were listening to the stream and relay their questions to the
audience if necessary. i want to do the same this year.
problem is: there are three lecture rooms now.
so i'm looking for a couple of people who'd be willing to help out.
specifically, i need people who
* are at the conference :) preferably the whole time
* bring their own laptop with working sound output and headphones
* have some experience with networking
* have or can operate a webcam on their machine and are willing to
install xawtv
* like to chat
your tasks will be:
* to attend talks
* to have an irc window open and answer and relay questions
* to set up a webcam that will provide the listeners with stills so
that they'll know which slide is up atm etc.
* to monitor the outgoing stream and to ping the relays from time to
time.
the more helpers, the less work for all of us. last year, it has
been great fun, although chatting, monitoring (with some 5 seconds
lag) and listening at the same time can make your head spin in funny
ways.
please cc: me privately on any replies. thanks.
regards,
jörn
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Germany
http://spunk.dnsalias.org (my server)
http://www.linuxaudiodev.org (Linux Audio Developers)
Paul Winkler:
>
> Howdy, I'm trying to compile radium too...
>
> On Mon, Apr 19, 2004 at 02:40:04PM +0200, Kjetil Svalastog Matheussen wrote:
> > It shouldn't be very important. Just go into the Makefile and
> > remove "-Werror" from line 71. That might "solve" other
> > potentional compiling problems as well.
>
> It fixes Michael's error - at least it does here :-)
>
> FYI, I had to change the makefile a bit because
> you defined $(QTDIR) as the qt lib/ directory, and
> on gentoo, the QT headers are not in $(QTDIR)/include, they're
> in $(QTDIR)/../include.
> That fixes a bunch of errors with missing headers.
>
> Now I'm stuck here:
> g++ Qt/Qt_EventReceiver.cpp -c -g -Wall -DNOPAUSEPLAY -I/tmp/radium/gc6.1/include -I/usr/X11R6/include -IQt/ -I/usr/qt/3/include -I`cat pypath.comp` -DGUIISQT
> Qt/Qt_EventReceiver.cpp:63: error: brace-enclosed initializer used to
> initialize `int'
> make: *** [Qt_EventReceiver.o] Error 1
>
Go to line 63 in Qt/Qt_EvenReceiver.cpp and change
struct TEvent tevent={{0}};
to:
struct TEvent tevent={0};
--
hi everyone!
as you will certainly have heard, we are getting closer to the 2nd
linux audio conference at zkm (http://www.zkm.de/lad).
as you might also have heard, we will have live streams of all talks
and lectures in ogg format for those who can't make it there in person.
last year, we had an irc "feedback channel", meaning i would sit in
the lecture room with a notebook, answer questions from people who
were listening to the stream and relay their questions to the
audience if necessary. i want to do the same this year.
problem is: there are three lecture rooms now.
so i'm looking for a couple of people who'd be willing to help out.
specifically, i need people who
* are at the conference :) preferably the whole time
* bring their own laptop with working sound output and headphones
* have some experience with networking
* have or can operate a webcam on their machine and are willing to
install xawtv
* like to chat
your tasks will be:
* to attend talks
* to have an irc window open and answer and relay questions
* to set up a webcam that will provide the listeners with stills so
that they'll know which slide is up atm etc.
* to monitor the outgoing stream and to ping the relays from time to
time.
the more helpers, the less work for all of us. last year, it has
been great fun, although chatting, monitoring (with some 5 seconds
lag) and listening at the same time can make your head spin in funny
ways.
please cc: me privately on any replies. thanks.
regards,
jörn
--
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Germany
http://spunk.dnsalias.org (my server)
http://www.linuxaudiodev.org (Linux Audio Developers)
I am getting the error:
watchdog _NOT_ running SCHED_FIFO
When running muse with the -R option in 2.6.5 and 2.6.6-rc1 with
superuser privileges. Jack seems to run fine (ish) though..
Any ideas?
James
Michal Seta:
>
>
> I'm getting the following error when trying to build under python 2.3:
> ideas?
>
> gcc common/eventreciever.c -c -g -Wall -Werror -DNOPAUSEPLAY -I/tmp/radium/gc6.1/include -I/usr/X11R6/include -IQt/ -I/usr/lib/qt3/include -I`cat pypath.comp` -DGUIISQT
> In file included from /usr/include/python2.3/Python.h:8,
> from common/eventreciever.c:22:
> /usr/include/python2.3/pyconfig.h:844:1: "_POSIX_C_SOURCE" redefined
> In file included from /usr/include/limits.h:26,
> from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.2.2/include/limits.h:132,
> from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.2.2/include/syslimits.h:7,
> from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.2.2/include/limits.h:11,
> from common/nsmtracker.h:40,
> from common/eventreciever.c:20:
> /usr/include/features.h:171:1: this is the location of the previous definition
> make: *** [eventreciever.o] Error 1
It shouldn't be very important. Just go into the Makefile and
remove "-Werror" from line 71. That might "solve" other
potentional compiling problems as well.
--
Thomas,
You said that you were "considering" switching to Linux for audio. If I
were interested in doing *only* what you mentioned doing, I would myself not
move to Linux audio. However if you have *other* reasons, then you may
have a good argument for switching. I should say that I'm making these
statements as someone who detests Microsoft and Windows, so it's not
easy for me to recommend Windows for what you plan to do. I myself do
Linux audio programming because I'm doing more audio research than music
per se, and I wouldn't perform serious technical tasks any other way.
However, in good conscience, I myself cannot recommend Linux audio for
the task you described any more than I could recommend that my
brother-in-law replace all his Windows business software with Linux.
If you don't have time for Debian or Gentoo, then you may not have time
for Linux audio.
Perhaps you already know this, but many people don't:
Linux isn't about free software, it's about USER-SUPPORTED software.
This means you contribute to your own support as well as the support
of others.
Now if you insist on going all-Linux, you've come to the right place.
The people here are very helpful.
On Mon, Apr 19, 2004 at 07:51:12PM +0200, Jan Weil wrote:
> On Mon, 2004-04-12 at 18:29, Paul Winkler wrote:
> > FYI, I'm still planning to implement my own proposal which has
> > been discussed quite a lot in the L-A-U archives.
> > I do somewhat similar sites for a living. It just needs me to block out a
> > chunk of time (1 or 2 weekends) to bang it out.
>
> Hi Paul,
>
> I'd like to assist so I've written a little script to automatically
> extract all the links from linux-sound.org.
> It depends on Ruby, wget, lynx and sed.
>
> The output is tab separated csv (tsv) containing three fields per row:
> text, urls and category.
> Some of the <li>s contain more than one url. For these the urls are
> separated by blanks ' '.
Cool, this is very nice and will definitely be useful!
Thanks!
I really want to get an alpha version of my site up ASAP.
Unfortunately this coming weekend is booked solid,
I'll be one of the insane participants in
24 Hour Comics Day:
http://www.24hourcomics.com/24HCD.html
--
Paul Winkler
http://www.slinkp.com
Hi,
I'm considering switching for Windows to Linux for my audio stuff. I have a
few questions.
1) I have some Cubase projects, and I mostly care about the midi sequencing.
If I export them to midi files, will I be able to restore most of the
information in Linux?
2) This is my first install. Can you suggest a distro for a 1.6 GHz Athlon
machine that would be good and stable for audio yet not be too hard to set
up and get working? Preferably something with a 2.6 kernel. I was going to
go with Mandrake, but I really don't know. Definitely something like Debian
or Gentoo is too involved for me right now.
3) I have a Soundblaster Audigy. Should I look into getting a new
soundcard? What is a good internel or external box that is supported well?
4) Can you recommend a set of software that will be enough to get started
with? I know that there are many many options and I would just appreciate a
little direction so I don't get discouraged. I just want to record vocals,
record midi and use my synthesizer, mix them together, and process it all
with some plugins.
That's all, and thanks for any information.
Thomas
_________________________________________________________________
MSN Premium: Up to 11 personalized e-mail addresses and 2 months FREE*
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht…