[FFmpeg-trac] #3133(undetermined:new): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC
FFmpeg
trac at avcodec.org
Sat Nov 30 13:57:07 CET 2013
#3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC
-------------------------------------+-------------------------------------
Reporter: EricV | Owner:
Type: defect | Status: new
Priority: important | Component:
Version: git-master | undetermined
Keywords: vdpau | Resolution:
regression | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by ordroid):
> It would be great if you could verify this because it would indicate a
different bug than what I thought so far. The difference in the XBMC
source code would be that the new API uses a "hwaccel" and the
"h264/vc1/etc. decoder while the new API was based on specific decoders
h264_vdpau, vc1_vdpau etc.
The bundled ffmpeg in XBMC is version 1.2 and states "VDPAU hardware
acceleration through normal hwaccel". Not sure how I'd go about verifying
the shared behaviour.
> > It's compiled against ffmpeg master as of yesterday.
>
> I don't think it is generally ok to use an older shared library instead
of the one you compiled against, using a newer one may be ok (bugs are of
course possible), ideally you would recompile to get valid results.
Are there any combinations I could try to help isolate this problem?
> While this is quite certainly unrelated, your configure line looks very
broken;-(
> Perhaps testing with {{{./configure --enable-shared && make}}} wouldn't
hurt...
I'm using the Gentoo git ebuild and actually had to remove some flags to
compile these revisions. Incidentally all those enable flags map to the
libraries I have installed through portages USE flags. But for simplicitys
sake I'll do --enable-shared :)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3133#comment:34>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list