faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: jackd integration
by piters on Tuesday 06/Feb/2007, @08:54
|
Hi,
certainly, having jackd interfaced somehow into Phonon would be great for everybody who wants to make music on Linux.
As far as I understand, jackd itself is not an engine... It is the way to get into your soundcard/midi and stream the data from/to there. So it is roughly at the level of ALSA or OSS...
On the contrary, Phonon relies on "hefty" backends such as xine, capable of doing all the file-decoding for mpegs, oggs, etc; and it is xine that would actually need to talk to jackd (rather than to ALSA, OSS, or so)...
So: it might be a question to the XINE developers to support jackd...
Could some of KDE/Phonon specialist tell if my thinking is right?
Any bright ideas to have jackd integrated somehow anyway? |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: jackd integration
by Matthias Kretz on Tuesday 06/Feb/2007, @09:21
|
Correct. As far as I know xine supports audio output to jackd since version 1.1.3. As soon as xine tells Phonon it supports jack, Phonon will list jack in the list of output devices (where in the screenshot above you already see arts and esd as soundservers).
|
[
Reply To This | View ]
|
Re: jackd integration
by Birger Kollstrand on Wednesday 07/Feb/2007, @03:54
|
Is there any work ongoing to secure that , I as an below avearge sound user, can have an understandable way of configuring this stuff?
Preferably one manner to configure everything regarding sound? Please! not alsa.conf for this and jack conf for that and Phonon conf ....
I have had several realy nasty encounters with sound problems earlier....
Regards Birger
|
[
Reply To This | View ]
|
Re: jackd integration
by Matthias Kretz on Wednesday 07/Feb/2007, @05:57
|
The idea is that Phonon will try to guess the correct defaults and give you the possibility to adjust those.
Regarding soundcard setup I'll try to make it smart. For example it currently uses dmix automatically, if that doesn't work fall back to hw and if that doesn't work fall back to plughw. Now the next step is to first test whether hw does mixing already, then dmix might be unnecessary or even counterproductive.
Regarding the soundservers I'd like to be able to help the user configure the soundserver correctly if he wants to use one. All that needs a lot of testing and information about different hardware and setups so that I will never be able to get it right on my own. It would be great if people can help out here.
|
[
Reply To This | View ]
|
|
Re: jackd integration
by eeos communications support on Thursday 08/Feb/2007, @08:48
|
Dear friends,
jackd is not really at the same logical level as alsa.
As far as I know, it needs alsa to work properly, so it works on top. Or am I wrong?
From the documentation:
What is JACK?
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").
<snip>
Jack has two sets of parameter options. The first part are specific to running
the jack server. The second part are run time options for how jack interfaces
with the sound driver - currently only ALSA.
The easiest way to start jack is to run this command:
jackd -d alsa -d hw:0
Of course that gives you very little control over what jack does to the audio
stream and which device you use. You can specify a card name by setting up an
.asoundrc file. Visit the online ALSA docs for your card/device to get one.
</snip>
Best
-.-
eeos communications support
http://www.eeos.biz
Company No. 05765416
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
