Reply to thread

Message

Hi.
Sadly it's very hard to identify what exactly causes this problem. It definitely came from missing or inaccurate external data (from TMDB or similar) or from faulty media files (playable, but with not well formatted file header causing mediainfo to deliver crap). Nearly 80% of the whole code of Media-Buddy is to catch faulty external data as you have to find and catch every single bit of possible issue one by one. It simply is impossible to find every single possible issue with the data as long as the don't appear here. Everything I find here, I instantly fix. Maybe this is already fixed in my local version...

When I can reproduce the issue here running the not compiled script, I can see the real line of code, that is causing this. But in compiled version all includes are listed in one big piece, so the shown line did not say anything. Easiest would be, if you install Autoit (it's free) and run the source (Is included in the installation) from within the IDE. Then the given line easily identifies the exact place in code where the issue appear. Without logs and running the compiled version only it simply is impossible to find, what's causing this.

<blockquote data-quote="Lehmden" data-source="post: 1291314" data-attributes="member: 109222">Hi.Sadly it's very hard to identify what exactly causes this problem. It definitely came from missing or inaccurate external data (from TMDB or similar) or from faulty media files (playable, but with not well formatted file header causing mediainfo to deliver crap). Nearly 80% of the whole code of Media-Buddy is to catch faulty external data as you have to find and catch every single bit of possible issue one by one. It simply is impossible to find&nbsp; every single possible issue with the data as long as the don't appear here. Everything I find here, I instantly fix. Maybe this is already fixed in my local version...When I can reproduce the issue here running the not compiled script, I can see the real line of code, that is causing this. But in compiled version all includes are listed in one big piece, so the shown line did not say anything. Easiest would be, if you install Autoit (it's free) and run the source (Is included in the installation) from within the IDE. Then the given line easily identifies the exact place in code where the issue appear. Without logs and running the compiled version only it simply is impossible to find, what's causing this.</blockquote>

[QUOTE="Lehmden, post: 1291314, member: 109222"] Hi. Sadly it's very hard to identify what exactly causes this problem. It definitely came from missing or inaccurate external data (from TMDB or similar) or from faulty media files (playable, but with not well formatted file header causing mediainfo to deliver crap). Nearly 80% of the whole code of Media-Buddy is to catch faulty external data as you have to find and catch every single bit of possible issue one by one. It simply is impossible to find every single possible issue with the data as long as the don't appear here. Everything I find here, I instantly fix. Maybe this is already fixed in my local version... When I can reproduce the issue here running the not compiled script, I can see the real line of code, that is causing this. But in compiled version all includes are listed in one big piece, so the shown line did not say anything. Easiest would be, if you install Autoit (it's free) and run the source (Is included in the installation) from within the IDE. Then the given line easily identifies the exact place in code where the issue appear. Without logs and running the compiled version only it simply is impossible to find, what's causing this. [/QUOTE]