IGL read error

[mvallevand]

Martin:

When I open this .7z file, it contains an imageGrabLite.exe image dated 1/31/2013. Is this correct?

Sorry about that everyone, time to clean up some old files. Here is the proper installer.

Martin

[drew156651]

no more error thank you!! will give it a whirl next episode Thanks again!! Great app

[drew156651]

no more error thank you!! will give it a whirl next episode Thanks again!! Great app

Worked out great Thanks again!! all errors fixed!!

[mvallevand]

Thanks for the update. I bet there are more errors to be found.

Martin

[BrettB]

Thanks for the update. I bet there are more errors to be found.

Hey, Martin!

I think that I may have found another one of those errors. Since I installed this latest version of IGL, I've had problems playing some recordings on the RPi via X-NEWA. It seems to try to play the file, but can't. (It's weird, because sometimes I can come back later, and it will play OK.)

Upon investigating some, I noticed that IGL seems to be adding "#0" to the end of the filename for some programs. I'm attaching the log file for the latest instance (Feed the Beast). I'm guessing that somehow this "#0" is confusing SMB on the RPi or something. And I don't have any idea why IGL would be adding it. I see that it did that for the 1st episode of Feed the Beast, too. But that one is playing OK for me via X-NEWA.

Any ideas?

[BrettB]

I think that I may have found another one of those errors. Since I installed this latest version of IGL, I've had problems playing some recordings on the RPi via X-NEWA. It seems to try to play the file, but can't. (It's weird, because sometimes I can come back later, and it will play OK.)

FYI: they play problem may be related to the path substitution or something else entirely. When I play the problem files directly from the Kodi video library, they play just fine every time.

At any rate, it seems like there is a problem with this version of IGL adding the "#0" for no reason.

[mvallevand]

Hi Brett, I don't think it is new it could be a case mismatch with SD and thetvdb.org

2016-06-07 22:11:22.092 [DEBUG][1] Changing Feed the Beast to Feed The Beast

Do you have other examples?

Martin

[BrettB]

Hi Brett, I don't think it is new it could be a case mismatch with SD and thetvdb.org

2016-06-07 22:11:22.092 [DEBUG][1] Changing Feed the Beast to Feed The Beast

Do you have other examples?

Scanning the recordings still on my drive, it looks like Feed the Beast is the only one. So, I'm sure you're correct that it is just a problem with this specific show.

[mvallevand]

Scanning the recordings still on my drive, it looks like Feed the Beast is the only one. So, I'm sure you're correct that it is just a problem with this specific show.

This fixes the problem with the case mismatch. However In my testing this shouldn't have been a visible problem since in web client the file and the database were both named the same with the #0 at the end.

Martin

[BrettB]

This fixes the problem with the case mismatch. However In my testing this shouldn't have been a visible problem since in web client the file and the database were both named the same with the #0 at the end.

Yes, the playback problem with the X-NEWA client on the RPi is strange. The problem isn't that the file was named differently between the database and the drive. And the really strange part is: once I successfully begin playing the file directly from the Kodi Videos file list, then I can go back into X-NEWA and it plays just fine. It's just weird and just recently started happening occasionally. I'll keep troubleshooting that as a totally separate issue.