forwarded 745060 https://bugzilla.libav.org/show_bug.cgi?id=674 tags 745060 upstream thanks
2014-04-17 23:07 GMT+02:00 Jeroen Massar <jer...@massar.ch>: > On 2014-04-17 21:03, Bálint Réczey wrote: > [..] >>> Thus for people who want to upgrade to xbmc13 on this platform, you might >>> want to have this bug resolved first ;) >>> This could be related to VDPAU, or just a regression in XBMC. Googling for >>> the error does pop up >>> some similar reports, but the typical answer is to disable VDPAU/VDAPI, >>> this while XBMC12 works fine. > [..] >> This problem has been reported as #742896 , but using the radeon driver. >> I planned setting up an nVidia config, but thanks to you I don't have to. > > Hence, why filing a bug is a good thing ;) > > (also because google indexes them really well, and then people might > find a solution easier or avoid upgrading as they can see there is a > problem.... it is in the experimental branch for a reason ;) > >> Upstream's position is that it is a Libav bug, since the video plays >> fine with the embedded ffmpeg copy shipped with vanilla XBMC. > > Makes sense; > > (I quite understand btw why they do not like maintaining multiple video > libraries) > >> I have to agree with them thus I hereby reassign both bugs to libav. >> If this is a result of API difference between FFmpeg and Libav, please >> help me out, too. > > I had not noticed that libav10 was being used; I checked and indeed it > is libav10 that it is linked against. Is libav10 a requirement, as > otherwise linking to libav9 might be an option that might just work ;) > (and would exclude in a way if the fault is in xbmc or libav...) The API changes between libav 9 and 10 make testing this path hard. > > Reinhard Tartler wrote: >> I am having a hard time seeing from this report what the problem is. > > I guess that you mean what is causing it rather than the problem, as the > problem is easy: no rendering as something fails (likely libav) > > With no crash dump or otherwise extended details that is indeed going to > be hard. One would have to either modify xbmc to print out all the > arguments passed to the API calls. > > At least, the good thing is that it is checking the results of the calls > and hence reporting an error. > >> What API is at fault here? can you provide a minimal example program >> that demonstrates what the problem is? > > I am just a user in this case, the "minimal program" would also be quite > hard to do I think... as well video stuff is never minimal. > > Now... if you had a minimal example program, I would be quite willing to > try that out of course and see if that exhibits the same problem. > > I don't seem to find a simple example in the libav sources. I hope we can get some help from Libav upstream, they are kindly helping in API migrations usually. Cheers, Balint _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
