in $PORTDIR/profiles/package.mask on 2013-02-13 some time ago: --- # Starting from this version, some decoders and encoders (like AAC or APE) # switched to outputing or needing planar audio, this breaks some applications # at runtime and the tree needs to be checked. For instance, <xbmc-12, # <vlc-2.0.6 break. >=media-video/ffmpeg-1.1 --- It is easy to USE "-AAC -APE" and to emerge vlc-2.0.6 to get the newest ffmpeg running when you have unstable ~amd64. And it runs flawlessly. Is this mask simply forgotten by time since then?
have you checked the whole tree ?
@Alexis, no - I am just an ~unstable user having a little Mac-mini box. I am running a quiet complete Kde and vlc and (google) chromium ... I didn't encounter any AAC or APE formats, which I would be unable to view. So I thought: If other applications obsolete old formats, why should not ffmpeg? (But I must admit I just have a vague memory of ape beeing some sould codec?)
I have further info: Downloaded a torrent video having an -AAC- at the end in the name. I could see and hear sound using vlc kplayer I could see and but not hear sound using kaffeine It is a xine-lib issue ...
(In reply to comment #3) thanks, so xine-lib doesn't work; could you please file a separate bug for this ? AFAIK nobody has performed a wide analysis of what may break and what is fine with ffmpeg 1.1 and later; for example, xbmc 12 can now decode aac fine but aac spdif output is still broken
(In reply to comment #4) > (In reply to comment #3) > > > thanks, so xine-lib doesn't work; could you please file a separate bug for > this ? just to be clear: only if this is fine with ffmpeg 1.0 and fails with 1.1 and later of course
minitube -gstreamer doesn't play sound! The bad: Using minitube gstreamer has a serious bug: It is pausing after about 40 minutes after the first video before going on.
Ulenrich, do you still experience problems with any of the packages you use?
@Tom, as ever minitube - but these are youtube api issues I guess. My system is very stable using with linux-3.9.7: dev-libs/boost-1.53.0 kde-base/ffmpegthumbs-4.10.4 media-libs/alsa-lib-1.0.27-r2 media-plugins/alsa-plugins-1.0.27 media-plugins/gst-plugins-ffmpeg-0.10.13_p201211 media-plugins/gst-plugins-pulse-0.10.31 media-sound/pulseaudio-4.0 media-video/ffmpeg-1.2.1 media-video/vlc-2.0.7 sys-devel/gcc-4.7.3 virtual/ffmpeg-9 www-client/chromium-28.0.1500.52
should be better now; I didnt check everything but it's probably best to go for ~arch testing and wait for reports as those are runtime issues. unmasked.
