[onesane]

I'm getting a super weird error since the update today to 0.5.4. I wouldn't immediately assume this was a skin issue, but that's the only thing that's been updated recently and I can't replicate this issue in Estuary. I'm on Matrix 19.1.

In my actual media files on my NAS, if a movie or tv show begins with "A" or "The," I put it at the end of the folder name (e.g.: "Americans, The" instead of "The Americans"). I just like things in alphabetical order in my file structure. This has never been a problem in Kodi before today.

Since the update, any show or movie with this file or folder naming structure throws me a "Playback failed" error if I try to play it through the DialogVideoInfo "Play" button, but will play normally if I highlight the file in Kodi without going to the Information page and pressing play on my remote. 

Looking at the log file (I can post it if it would help), it seems there's multiple errors - first it can't find the folder of the show/movie on my NFS share (it doesn't seem to complete the name in it's search, leaving off the ", The" in "Americans, The"). Further down, it pops another error when trying to play the actual file, but I noticed the file name it's displaying adds "EXTRAS" after the proper name when that's not at all a part of the file name. It's the weirdest thing. 

I've already tried reinstalling the skin directly from github and that didn't fix it. Like I said, those files play just fine in the Estuary skin and they were working fine just a few days ago in Resurrection as well. They also play just fine if I play them directly instead of going through the DialogVideoInfo page. I have to assume this is a skin issue. Any idea what's going on?

that sounds like a scrapper issue I have some files I dont that with but I pre scrap with tinymediamanager, I dont have this issue that you do.

Yeah, I do the same thing with MediaElch on my mac, and I only use local info in my library (some of these files and nfos causing problems haven't changed in years). Normally the skin would be the last thing I'd suspect as the issue, but Estuary handles the files just fine in DialogVideoInfo. I'm officially out of my depth at this point. I can also confirm that it's happening in both my bedroom and my living room set ups (both running Matrix 19.1 on Shield TVs).