Registered Member
|
Firstly - phonon is based on KDE/Qt, and a lot of people just hates it - so this solution will be really only to KDE users... With Pulse it is not the case
Secondly - I think that these forces of creating another sound server will be more helpful to the PulseAudio project itself... Let's do PulseAudio better! Why doing something completely new when we can just make something existant better?... And it will help to develop our world, the progress won't stop |
Registered Member
|
If KDE started developing its own sound system, what makes you think it'll be more robust than PulseAudio while incorporating the same features?
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
@Madman
KDE code is clean for the most part, having been totally rewrote in version 4.x. Its result was a much more intuitive piece if software with a lot less "hacks" I think the same thing would apply to a new sound server. Basically, write it clean in the first place and the bugs will be minimized. Write it with functions that interface well together with a standard API, and other people who want to write code for it will have a lot less problems with bugs as well. Write it with the purpose of being the end-all solution to sound-serving in Linux, and that's what it will become. Trying to make a program do something it wasn't originally designed to do is a two-steps forward, one back situation. |
Registered Member
|
You haven't stated anything that would differentiate a new sound server from KDE to PulseAudio. It is no different to how KDE 4.0 was. The difference is, Plasma is sexy, while interfacing with existing sound-systems in a single, standardized method with clean code and a standard API... not so much.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Erm... Plasma is cool*.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Heh, that was pretty funny XD.
Ok, so it would differ from PulseAudio in a few ways. 1. It would have the ability to patch audio from different applications, no matter what protocol was being used (Jack app to Pulse app, OSS app to Alsa app). 2. It would have a GUI for easily mixing application sounds, loading LADSPA plugins, and patching audio. 3. It would have the option to make a network stream from the GUI, and that would be accessible through the patch tab. 4. Just because, it would have a system wide equalizer loaded automagically, which could then be accessed through the GUI interface. All this in addition to everything PulseAudio can do. I especially like the simplified network streaming interface, because it would be awesome to stream the music playing from Amarok (insert favorite music player here) to all of your mobile devices or send the audio portion of your computer to a friend online. The system wide equalizer has been a wanted feature for quite some time for many. Anything is really possible. |
Registered Member
|
But... PulseAudio already does this. It provides plugs for applications using ALSA or OSS which then go through Pulse, meaning more advanced sound systems like Jack also go straight through Pulse.
Again, this is available through Pulse and, as shown above, nearly complete.
PulseAudio... Again... it would be less hassle to just make KDE pulse-aware and provide a GUI for network streaming (lots of Ubuntu users already use this for bluetooth headsets).
Again... see above.
Thing is, all you've really described... IS PulseAudio. :/
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
[/quote]
Ok, I am very curious how you did this. Jack applications going directly through pulse? Without the Jack server running? If this is possible without a whole lot of bugs, I would appreciate a pointer to the information so I can set this up. Also, you say there is a way you can manually patch sounds to other applications in PulseAudio? In real time? Do tell how. I've been wanting to do that for a long time. I know that pulseaudio can stream to the network, but it is too complicated to set up for many common users. |
Registered Member
|
Oh come now, I never said that. See, this is why people say sound on Linux is a mess: actually, yes, you do need the Jack sound server running (it will run whenever you start an application that needs it anyway, so I don't see that as much of a problem), which then accesses Alsa directly to manipulate the hardware. Fortunately, Alsa is already supported by PulseAudio (http://pulseaudio.org/wiki/AboutPulseAudio#Details), so by default, yes, Jack is supported by PulseAudio. And OK, you got me there: I miss-read. I thought you just wanted to control the volume of individual applications e.g. through KMix, which PulseAudio supports. In fact, I don't know what you mean by, "patching" audio. :/
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Ah, ok. By patching, I mean the ability to take the output of any program and pipe it directly to another application's input. For example, taking the audio directly from a YouTube video and sending it to a recording program like Audacity or sending the sound from your microphone to a LADSPA plugin or two and then sending it to both sound recording software and to the internet as a stream.
That jack solution sounds way too hack-like (which is probably why it has so many bugs :s) |
Registered Member
|
Not really: Jack accesses Alsa like any old sound application would. To PulseAudio, the Jack server is an application.
And yeah, I see what you mean now. Still, would be much harder to re-write all of PulseAudio under KDE just to include that one feature, especially with PulseAudio's pluggable architecture being an alternative.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
KDE already tried developing its own sound server. It was called arts, and ended up dieing because no one wanted to continue supporting it. After that episode, you are going to have a really hard time convincing anyone to try again, and an even harder time convincing the KDE community to use it. The whole point of Phonon is that it is independent of the underlying sound system.
Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system which can be mass-produced by unskilled labor.
-NASA in 1965 |
Registered Member
|
I suppose that the problem is primary the fact that isn't simple to understand what PulseAudio, Phonon, Alsa, Jack and other are and what they exactly do.
Developers should explain this matter in a well visible document. |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot], Yahoo [Bot]