5 Apr
2005
5 Apr
'05
10:19 p.m.
Hi all,
First of all, please accept my apologies for cross-posting. I simply feel
that this issue may be of interest to all these groups.
After some research and experimenting with jacklaunch (libjackasyn) as well
as alsa .asoundrc jack plugin I found out that very few apps actually
cooperate with either of these.
Jack plugin for asoundrc practically works only with aplay/arecord and
freebirth. Audacity doesn't cooperate with either, while jacklaunch even
though it has been reported to work with sweep doesn't on my machines (mdk
10.0 and 10.1).
I've tested latest jack, sweep, Alsa 1.0.6 and 1.0.7 (I did not go beyond
that as 1.0.8 has apparent issues with hdsploader) and had no luck
whatsoever.
Hence, I am just wondering at this point whether asoundrc jack is still in
the testing phase (some of the errors that apps reported trying to use jack
plug were due to inability to probe some info from the alsa driver which
implies possible incompleteness of the implementation or weird probing from
the app's side) and also whether anyone has had better luck than myself
using either of these with audacity, sweep, and other non-jackified, yet
important Linux audio apps via either of the aforementioned ways.
FWIW, it would be really nice to see some united effort to jackify some of
the other critical Linux audio apps even if their original authors do not
feel like that is one of their priorities (I know, I know, if I am so
interested in such developments then I might as well set an example by doing
what I am advocating, which is something I would love to do, but
unfortunately currently the notion of "free time" in my life is but a joke).
Many thanks!
Best wishes,
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico/
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.3 - Release Date: 4/5/2005
6 Apr
6 Apr
4:22 a.m.
On Tue, 2005-05-04 at 20:19 -0400, Ivica Ico Bukvic wrote:
Hence, I am just wondering at this point whether
asoundrc jack is still in
the testing phase (some of the errors that apps reported trying to use jack
plug were due to inability to probe some info from the alsa driver which
implies possible incompleteness of the implementation or weird probing from
the app's side) and also whether anyone has had better luck than myself
using either of these with audacity, sweep, and other non-jackified, yet
important Linux audio apps via either of the aforementioned ways.
Pretty much anything that crams blocking IO into Jack will always be
dodgy. It might work a little bit sometimes maybe, if you're lucky.
Libjackasyn, bio2jack, and all that stuff are useful hacks sometimes,
but they're just that - useful hacks. They aren't, and will never be,
suitable for pro audio work.
Like you said, what needs to be done is to properly jackify these apps.
-DR-
6:24 a.m.
New subject: [linux-audio-user] Re: [linux-audio-dev] Jacklaunch vs. asoundrc jack plugin
On Tue, Apr 05, 2005 at 08:19:00PM -0400, Ivica Ico Bukvic wrote:
freebirth. Audacity doesn't cooperate with either,
while jacklaunch even
though it has been reported to work with sweep doesn't on my machines (mdk
10.0 and 10.1).
jacklaunch(1) worked for us with realplayer, which is, i know, closed
source and evil and not a major linux audio app. just for the record.
we used jacklaunch to start multiple instances of realplay in parallel
for a multichannel streaming sound installation.
m
1 jacklaunch and libjackasyn are registered trademarks of guenter
geiger, barcelona :-)
7:29 a.m.
Last Wednesday 06 April 2005 01:19, Ivica Ico Bukvic was like:
Hi all,
First of all, please accept my apologies for cross-posting. I simply feel
that this issue may be of interest to all these groups.
After some research and experimenting with jacklaunch (libjackasyn) as well
as alsa .asoundrc jack plugin I found out that very few apps actually
cooperate with either of these.
Jack plugin for asoundrc practically works only with aplay/arecord and
freebirth. Audacity doesn't cooperate with either, while jacklaunch even
though it has been reported to work with sweep doesn't on my machines (mdk
10.0 and 10.1).
I've tested latest jack, sweep, Alsa 1.0.6 and 1.0.7 (I did not go beyond
that as 1.0.8 has apparent issues with hdsploader) and had no luck
whatsoever.
Hence, I am just wondering at this point whether asoundrc jack is still in
the testing phase (some of the errors that apps reported trying to use jack
plug were due to inability to probe some info from the alsa driver which
implies possible incompleteness of the implementation or weird probing from
the app's side) and also whether anyone has had better luck than myself
using either of these with audacity, sweep, and other non-jackified, yet
important Linux audio apps via either of the aforementioned ways.
FWIW, it would be really nice to see some united effort to jackify some of
the other critical Linux audio apps even if their original authors do not
feel like that is one of their priorities (I know, I know, if I am so
interested in such developments then I might as well set an example by
doing what I am advocating, which is something I would love to do, but
unfortunately currently the notion of "free time" in my life is but a
joke).
I think it may be the case that most of the Debian packages that Guenter
Geiger maintains will work with jacklaunch. I've seen a JACK Sweep in the
menus and confess to never having used it. Is it simply that not enough other
people/distros have really made enough use of it to properly test it?
cheers,
tim hall
http://glastonburymusic.org.uk
26 Apr
26 Apr
6:22 p.m.
FWIW, it would be really nice to see some united
effort to
jackify some of the other critical Linux audio apps even if
their original authors do not feel like that is one of
their priorities
People who start to write an audio application have a
difficult decicion to do: Which soundsystem to use?
Because all this mess about audio leads in the following:
* An author of 'professional grade' audio applications will
make his application an JACK and perhaps additionally an ALSA
application
* A KDE programmer will make his application an artsd
application
* A Gnome programmer will make his application an esound
application
* Others will make their application an ALSA application
* People who want their application to run on other unixes too
will make their application an OSS application (see the
commercials like real or Skype)
There is the example JACK capture client which is a good
starting point for programming newbies.
What would really be useful would be some example code in the
ALSA wiki showing how to create an application which is
jackified but even can play and record via an ALSA DMIX
device and optionally has further input/output plugins for
esound, artsd and gstreamer. And which can automatically
detect the audio subsystem to use *sigh* ;-) .
Best regards
ce
7:52 p.m.
On Tuesday 26 April 2005 22:23, Christoph Eckert wrote:
People who start to write an audio application have a
difficult decicion to do: Which soundsystem to use?
* A KDE programmer will make his application an artsd
application
Which will be superseded in KDE 4.0 by a new layer which provides an abstract
interface for simplier Players (nothing really for pro-audio) and some kind
of detection and access to the underlying system. So by using the new system
(in about half to one year) you have a powerfull tool at your hands for
Chistoph's wish:
What would really be useful would be some example code
in the
ALSA wiki showing how to create an application which is
jackified but even can play and record via an ALSA DMIX
device and optionally has further input/output plugins for
esound, artsd and gstreamer. And which can automatically
detect the audio subsystem to use *sigh* ;-) .
Christoph and everyone who doesn't believe my sayings: Most probably there
will be a talk at LinuxTag about the new multimedia-interface of KDE, given
by Matthias Kretz who is most likely the one with the deepest
aRts-understanding after Stefan Westerfeld...
Arnold
--
There is a theory which states that if ever anyone discovers exactly what the
Universe is for and why it is here, it will instantly disappear and be
replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.
-- Douglas Adams, The Restaurant at the End of the Universe
10:49 p.m.
Last Tuesday 26 April 2005 21:23, Christoph Eckert was like:
Your posting makes me think that I have developed a very fixed view point
about such things.
FWIW, it would
be really nice to see some united effort to
jackify some of the other critical Linux audio apps even if
their original authors do not feel like that is one of
their priorities
People who start to write an audio application have a
difficult decicion to do: Which soundsystem to use? Because all this mess about audio leads in the
following:
* An author of 'professional grade' audio applications will
make his application an JACK and perhaps additionally an ALSA
application
Surely the most obvious choice would be to make it an ALSA/JACK application -
unless it doesn't need JACK? In which case, just ALSA.
* A KDE programmer will make his application an artsd
application
* A Gnome programmer will make his application an
esound
application
Erm, as a user I would regard anything that used only artsd or esd to be
involved in sound notification. I generally don't need these features. From a
user perspective Audio applications should use ALSA. If an application does
not use ALSA I will either not use that app, turn off the sound features or
figure some other workaround.
* Others will make their application an ALSA
application
...
* People who want their application to run on other
unixes too
will make their application an OSS application (see the
commercials like real or Skype)
This is the only other relevant choice.
There is the example JACK capture client which is a
good
starting point for programming newbies.
What would really be useful would be some example code in the
ALSA wiki showing how to create an application which is
jackified but even can play and record via an ALSA DMIX
device and optionally has further input/output plugins for
esound, artsd and gstreamer. And which can automatically
detect the audio subsystem to use *sigh* ;-) .
I realise that from the POV of non-music-making applications it might look
this way, especially if you were bothered about cross-platform portability. I
think if you were writing a specific Linux Audio application you would use
ALSA. Please excuse me if I'm missing something that would be obvious to a
programmer. As a musician and a Linux user I set my machine up to use ALSA
and get quite annoyed when other apps launch another sound system in the
background and block my soundcard. Actually It bothers me so much that I'm
thinking of uninstalling both artsd and esd, but I'm not sure if dependencies
will allow this.
cheers,
tim hall
http://glastonburymusic.org.uk
7205
days inactive
7226
days old
linux-audio-user@lists.linuxaudio.org
6 comments
6 participants
participants (6)
-
Arnold Krille -
Christoph Eckert -
Dave Robillard -
Ivica Ico Bukvic -
martin rumori -
tim hall