Error: Failure playing back file

[gEd]

http://forums.gbpvr.com/showpost.php?p=2...ostcount=2

[sp4rky]

Sorry gEd, no luck with that hotfix


Could you repost the link to the filter check program? the link in the post has the "..." as part of the link.

[Nomad101]

Have a look at this thread:

http://forums.nextpvr.com/showthread.php?t=28972

In post number 8 he has the same errors in his log. Looks like installing a different Cyberlink mux solved the problem.

You can get the Cyberlink muxes here:

http://www.gbpvr.ynosgroup.com/

or follow the link from this thread:

http://forums.nextpvr.com/showthread.php?t=25630

5.0.0.1307 seems to be known as a fairly stable one.


Cheers
Tony

[sp4rky]

Ok, I've just been through that other thread and tried out the suggestions... using every single Cyberlink mux available on the gbpvr.ynosgroup site (one at a time) I still have no joy.

I even tried using a file from the 1.0.8 distro too (psiparser.ax) as suggested.





Edit: I tried de-registering all filters found by muxchecker in the hope that GBPVR would have to fall back on the default Microsoft DVR-MS but I still had the same result.

[stustunz]

you only had one cyberlink mux registered at a time didnt you ?

[sp4rky]

correcto.

[gEd]

sorry, I'm out of ideas atm. Now isn't the best time to be having problems what with Sub being on vacation.

You could approach the problem from a different angle and give up on the DVB EPG and instead download your tv listings as an xml file and then import that into gbpvr (like I do) - the quality of the programme descriptions (from radio times) is a lot better as well.

http://www.birtles.org.uk/xmltv/

[sub]

I think there is something in the stream that GB-PVR doesnt like that is causing a crash which stops the listings from being loaded. Hard to guess what exactly that might be, and why it doesnt seem to be affecting other UK users.

After I get back to New Zealand, we could get you to try capturing a transport stream from your device so I could analyse it a bit closer.

(I cant remember if I'd seen this mentioned in this thread or not, but if you're using the 1.0.8 PsiParser.ax on 1.0.16, you should reproduce the problem using the original 1.0.16 parser and repost the logs)