#118 Support Phonon Audio Framework

open
nobody
None
5
2012-11-29
2007-11-05
No

Would it be possible to support the Phonon audio framework included in the upcoming KDE 4 release?
I'd be willing to help implementing the necessary stuff, but I'd need pointers to start with the current code.
I already had a quick look at the sources of rdesktop 1.5 but I didn't understand the architecture so far.

As rdesktop is used by KRDC, the remote desktop utility of KDE, support of the new framework would be much appreciated.
I already filed a feature request for KRDC but the author told me I should talk to the rdesktop devs instead.

Discussion

  • Ilya Konstantinov

    Logged In: YES
    user_id=335423
    Originator: NO

    We already have OSS and ALSA support. We don't need any special multimedia features.

    What does Phonon give us?

     
  • Ilya Konstantinov

    Logged In: YES
    user_id=335423
    Originator: NO

    Please note I didn't ask "where can I learn more about Phonon?"
    I asked: What benefits Phonon will bring to rdesktop beyond what OSS or ALSA can provide?

    (And do remember that in ALSA you can have userspace plugins to take audio up to any userspace daemon.)

     
  • Christian Nitschkowski

    Logged In: YES
    user_id=849608
    Originator: YES

    Basically Phonon abstracts the application from the underlying hardware.
    This way rdesktop wouldn't have to care about wether OSS or ALSA is used.
    One further advantage is the user has an easy way to configure which soundcard is used.
    This is why I came up with the idea.
    I tried to use krdc (which in turn starts an instance of rdesktop) to connect to my Win2K-VM.
    When I played sound in Win2K, I didn't hear it on my host.
    After searching for the problem I figured out rdesktop played to the first available sound device (which has no speaker connected in my case) instead of the one I configured in ALSA and Phonon.
    So I filed this report: http://bugs.kde.org/show_bug.cgi?id=151269
    As you can see, the developer of KRDC told me to get in contact with you - and so I did.

    I'm interested in having a solution for this problem - be it using Phonon or some other way.
    I'm willing to help with this.

     
  • Ilya Konstantinov

    Logged In: YES
    user_id=335423
    Originator: NO

    "Basically Phonon abstracts the application from the underlying hardware."

    So does OSS and ALSA. In ALSA, in particular, we play to the "default" PCM device. The "default" device can be anything you *configure* in /etc/asound.conf. In fact, if Phonon developers write an ALSA plugin to redirect the audio to some Phonon daemon, it can be the "default" PCM device.

    For example, PulseAudio and JACK supports this way of operation.

     
  • Christian Nitschkowski

    Logged In: YES
    user_id=849608
    Originator: YES

    Regarding your first post:
    I haven't seen your question before I wrote my first comment (with a link to Phonons introduction).
    Just wanted to add this info to my original request.
    Didn't want to offend you.
    Hope my second post (at 14:33) was more helpful.

     
  • Christian Nitschkowski

    Logged In: YES
    user_id=849608
    Originator: YES

    My current version of rdesktop (1.5.0) doesn't support playing to alsa.
    At least it seams so as I couldn't find a command line switch to use ALSA instead of OSS.
    The sources I downloaded from www.rdesktop.org (http://prdownloads.sourceforge.net/rdesktop/rdesktop-1.5.0.tar.gz?download) don't have support for ALSA either.
    So I guessed there's no ALSA support and rdesktop uses OSS.
    Which plays to the wrong device for me, unlike other OSS applications which use the correct one.
    As I saw there's no ALSA in the current sources I thought a Phonon-backend would be a nice addition as it would bring support for ALSA and <driver framework of your choice> for free.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks