2015-12-23, 23:36
confirmed - it is an ffmpeg issue. Might be this one:
https://github.com/xbmc/FFmpeg/commit/1d...456f84b9d6
Latest ffmpeg in mainline has this already fixed ... just a stupid coincidence that i rebased to mainline when we used that ffmpeg version... Not sure if i have enough time to do a rebase and full rebuild before bedtime ...
https://github.com/xbmc/FFmpeg/commit/1d...456f84b9d6
Latest ffmpeg in mainline has this already fixed ... just a stupid coincidence that i rebased to mainline when we used that ffmpeg version... Not sure if i have enough time to do a rebase and full rebuild before bedtime ...