Bug 269301 - Poor KDE integration
Summary: Poor KDE integration
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: jack-audio-connection-kit
Version: 7
Hardware: All
OS: All
medium
high
Target Milestone: ---
Assignee: Andy Shevchenko
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-30 20:59 UTC by Philip Ashmore
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-03 15:26:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Philip Ashmore 2007-08-30 20:59:14 UTC
Description of problem:
I want to use JACK as the audio device

Version-Release number of selected component (if applicable):


How reproducible:
very

Steps to Reproduce:
1. Start Control Centre
2. Select Sound/Multimedia/Hardware/Select Audio Device/Jack Audio Connection Kit
3.
  
Actual results:
I got a message box stating:
Sound server informational message:
Error while initializing the sound driver:
Couldn't connect to jackd
The sound server will continue, using the null output device.

Expected results:
I should be enjoying real time audio.

Additional info:
From the documentation it appears that the JACK daemon (jackd) should be started
somewhere - KDE startup maybe?

Comment 1 Andy Shevchenko 2007-09-03 15:26:24 UTC
My investigations show the jack could be used as kde sound engine only after 
starting it in other way. In other words, you should to start jack via 
initscripts or profile environment, or via QJackCtl (just install it by yum and 
start under X session). After jack is started you may choose the Jack as middle-
end sound service.

P.S. If you have some information with another description of the KDE and jack 
integration, you are welcome to reopen this bug. Also do not forget to add 
yourself into jackuser group to gain realtime priority.

Comment 2 Philip Ashmore 2007-09-03 17:52:08 UTC
You can call me picky in this regard!

It just seems to me that the functionality that QJackCtl provides should be
available as a KDE kcontrol page with a build-in ability to manage jackd just
like artsd.

Now that would be good KDE integration.


Note You need to log in before you can comment on or make changes to this bug.