XBMC Borked
#16
spiff Wrote:afaik this has only ever been reported on windows. i suspect some windows-only code in ffmpeg aint all that thread safe.

So its possible the codec has got corrupted ? Which would possibly mean it will be a fruitless exercise trying to find the problem within xbmc?
Reply
#17
nah, issue is with the caller (i.e. xbmc) if my suspicion is correct. we already have some of these functions protected. and we ship our own ffmpeg so we are in control there in any case.
Reply
#18
No, the file would be a specific media file that fails to extract information.
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


Image
Reply
#19
Nailed it down to one file after rebuilding my video library, it appears to be a m2ts file which may explain why xbmc may have struggled to extract the required info ??

Needless to say its not in the library no more, if you need a sample i will sort you one.

Thanks for help nice to having it working again Big Grin
Reply

Logout Mark Read Team Forum Stats Members Help
XBMC Borked0