Bug 282232

Summary: Audio playback device [device] does not work falling back to .
Product: [Frameworks and Libraries] Phonon Reporter: James Kaelin <jkaelin>
Component: generalAssignee: Harald Sitter <sitter>
Status: RESOLVED DUPLICATE    
Severity: minor CC: ahartmetz, martin.sandsmark, myriam, romain.perier, tdfischer
Priority: NOR    
Version: 4.5.0 (KDE 4.6.2)   
Target Milestone: 4.5.1   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Attachments: Image of Error Message after running Test

Description James Kaelin 2011-09-17 18:22:21 UTC
Created attachment 63735 [details]
Image of Error Message after running Test

Amarok 2.4.3 Using KDE 4.7.0
Running under Windows 7 x64

Error message on start reads "Multimedia System: Audio playback device waveout does not work. Falling back to ."

It eventually ends up working and able to play music after a bit of delay. I assume after testing various options.

I tried switching Device Preference through "Settings > Configure Amarok > Playback > Configure Phonon", but each option gives the same error message only with the top selected device. Example "Multimedia System: Audio playback device aout_directx does not work. Falling back to ."

Message will show again after the first time running Test under Configure Phonon.

Also as a related issue, the Test option under configure Phonon doesn't seem to work for the individual Playback devices. Attempting to Test aout_directx gives the same error message on first run only.[See Attachment] No errors on subsequent Tests. Also note that the test sound does play despite the error message.
Comment 1 Torrie Fischer 2011-09-19 12:26:13 UTC
I assume you are using the directshow backend?

Can you try the vlc one if possible? We are kinda hard pressed for a directshow maintainer.
Comment 2 James Kaelin 2011-09-19 19:28:29 UTC
Already using Phonon VLC Backend 0.4.1

Directshow wasn't included in the install package.

amarok-setup-2.4.3-1.exe downloaded from amarok.kde.org
Comment 3 Andreas Hartmetz 2012-03-03 15:13:32 UTC

*** This bug has been marked as a duplicate of bug 255310 ***