#42062 closed defect (wontfix)
mpd crashes with error "fatal_error: line 12: No such audio output plugin: osx" at startup
Reported by: | david.e.pi.3.14@… | Owned by: | rmstonecipher@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | haspatch | Cc: | jchauvel@… |
Port: | mpd |
Description
MPD as built from MacPorts does not support CoreAudio output.
I don't know if CoreAudio support has been intentionally removed from MPD in MacPorts for some particular reason or if this was not intentional... in any case, I am attaching a patch to enable it.
Attachments (1)
Change History (10)
Changed 11 years ago by david.e.pi.3.14@…
Attachment: | mpd-enable-osx-support.patch added |
---|
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | rmstonecipher@… removed |
---|---|
Keywords: | haspatch added |
Owner: | changed from macports-tickets@… to rmstonecipher@… |
Port: | mpd added |
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
Cc: | jchauvel@… added |
---|
Has duplicate #42072. Upstream disables the plugin intentionally.
comment:3 follow-up: 6 Changed 11 years ago by jchauvel@…
I talked to the dev guys on #mpd at freenode and told me they've disabled it by default because it was buggy and was unmaintained.
comment:6 Changed 11 years ago by david.e.pi.3.14@…
Replying to jchauvel@…:
I talked to the dev guys on #mpd at freenode and told me they've disabled it by default because it was buggy and was unmaintained.
Yes I suspected that... What is the recommended output plugin on OS-X then? Jack?
comment:7 follow-up: 8 Changed 11 years ago by rmstonecipher@…
I have included a dependency on libao, an audio backend that seems to be functioning fine on Mavericks.
Please let me know in this ticket if it is not functioning on other platforms.
Ryan Stonecipher
comment:8 Changed 11 years ago by jchauvel@…
Replying to rmstonecipher@…:
I have included a dependency on libao, an audio backend that seems to be functioning fine on Mavericks.
Please let me know in this ticket if it is not functioning on other platforms.
Why don't we just keep the CoreAudio backend available as a port variant? I'm pretty sure many folks will be happy with it. At least until someone takes the necessary time to clean up and debug the code.
comment:9 Changed 11 years ago by rmstonecipher@…
Resolution: | → wontfix |
---|---|
Status: | new → closed |
As one example of completely unacceptable behavior:
To use CoreAudio on a machine with HDMI audio output you must disable it prior to connecting the HDMI cable, enable it once the cable is connected, and disable it after.
Failing to do these steps in order causes mpd to crash so ungracefully that you have to [ kill -9 ?] its process after unloading it via [ port unload ?] then reload it via [ port load ?].
I do not feel it is appropriate to include a buggy, unmaintained audio backend when I have found an acceptable alternative that should work across all supported platforms.
Since this presumably changes how the software is installed, the revision should be increased.