Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 820842" data-attributes="member: 18896">Re: AW: Re: Missing MediaInfo Logos - wrong fanartAny regular &quot;&lt;drive-letter&gt;\path&quot; and &quot;\\UNC\path&quot; is limited to 248 and 260 character limits as set by the backwards compatability that Windows OS carries.You need to use &quot;\\?\&lt;drive-letter:\path&quot; and &quot;\\?\UNC\path&quot; to switch to the new unicode system that gives much more room and is only supported on the recent Windows OS-es (Vista, and up). For example &quot;\\?\C:\&quot; works fine on Vista+, but fails on XP. Since C# is unicode aware and the .NET framework relies on all the API standards then unless some specific non-unicode methods are used in code for MovingPictures, you should be able to adjust all your import paths without any problems. Of course '?' is normally a character not allowed in filenames and/or paths (which is why it was used for this new system), so if any filtering is done to eliminate that you will get issues, but that's an easy test to do.Of course you can also locate the path and/or filename in question that is causing the problem, there are tools for that I'm sure. A quick Google search gives me: <a href="http://www.theutilityfactory.com/summaries/find-long-filenames.htm" target="_blank">FileBoss</a>As for your other issue, the file in question was a multi-track file. That is dealt with by the splitter, now for playback that has always caused me issues and forced me to use the Haali splitter. The MPC-HC standalone splitter can not properly deal with multi-track files and would cause lot of issues. I'm not happy with the Haali splitter as it causes some init delays, but haven't been able to find a better splitter yet, though looks like I might have to try the LAV splitter (hopefully it plays nice with other codecs, because I'm not gonna uproot my MPC-HC standalone codec setup). Of course a new MPC-HC update is around the corner as well so it might all just resolve itself.Anyway, the splitter is of course seperate from the MediaInfo process as you clearly at least get first track filled in proper it looks like via the &quot;File Info&quot; screenshot. But I'm wondering if it still in someway relates to eachoter. So do you have any problems with playback of those multi-track media files, or are you already setup with a good splitter/codec combination that can handle it fine?Otherwise the only thing I can think off is that somehow what you see in &quot;File Info&quot; is not the same as to what is used. For example if it uses &quot;1080i &quot; vs &quot;1080i&quot; then you actually need &quot;1080i .png&quot; to make it show logo image. You would have to open the MovingPictures.db3 file with an SQLite tool and manually verify the field data to verify that. The table in question is &quot;local_media&quot; that contains all the info, so verify that it indeed has all the correct data inside of it. You can use the &quot;local_media__movie_info&quot; table to match the ID from &quot;local_media&quot; table to the ID from &quot;movie_info&quot; to then match it with the actual movie (also works in reverse).</blockquote>

[QUOTE="RoChess, post: 820842, member: 18896"] [b]Re: AW: Re: Missing MediaInfo Logos - wrong fanart[/b] Any regular "<drive-letter>\path" and "\\UNC\path" is limited to 248 and 260 character limits as set by the backwards compatability that Windows OS carries. You need to use "\\?\<drive-letter:\path" and "\\?\UNC\path" to switch to the new unicode system that gives much more room and is only supported on the recent Windows OS-es (Vista, and up). For example "\\?\C:\" works fine on Vista+, but fails on XP. Since C# is unicode aware and the .NET framework relies on all the API standards then unless some specific non-unicode methods are used in code for MovingPictures, you should be able to adjust all your import paths without any problems. Of course '?' is normally a character not allowed in filenames and/or paths (which is why it was used for this new system), so if any filtering is done to eliminate that you will get issues, but that's an easy test to do. Of course you can also locate the path and/or filename in question that is causing the problem, there are tools for that I'm sure. A quick Google search gives me: [b][url=http://www.theutilityfactory.com/summaries/find-long-filenames.htm]FileBoss[/url][/b] As for your other issue, the file in question was a multi-track file. That is dealt with by the splitter, now for playback that has always caused me issues and forced me to use the Haali splitter. The MPC-HC standalone splitter can not properly deal with multi-track files and would cause lot of issues. I'm not happy with the Haali splitter as it causes some init delays, but haven't been able to find a better splitter yet, though looks like I might have to try the LAV splitter (hopefully it plays nice with other codecs, because I'm not gonna uproot my MPC-HC standalone codec setup). Of course a new MPC-HC update is around the corner as well so it might all just resolve itself. Anyway, the splitter is of course seperate from the MediaInfo process as you clearly at least get first track filled in proper it looks like via the "File Info" screenshot. But I'm wondering if it still in someway relates to eachoter. So do you have any problems with playback of those multi-track media files, or are you already setup with a good splitter/codec combination that can handle it fine? Otherwise the only thing I can think off is that somehow what you see in "File Info" is not the same as to what is used. For example if it uses "1080i " vs "1080i" then you actually need "1080i .png" to make it show logo image. You would have to open the MovingPictures.db3 file with an SQLite tool and manually verify the field data to verify that. The table in question is "local_media" that contains all the info, so verify that it indeed has all the correct data inside of it. You can use the "local_media__movie_info" table to match the ID from "local_media" table to the ID from "movie_info" to then match it with the actual movie (also works in reverse). [/QUOTE]

Verification