Setting up Twinhan 102g with new release

[sub]

Cheers - downloading it now.

[Shaky]

Any chance you could check it on the new patch anyway? Its using this new method, and I want to make sure its not going to break it for anyone that had it working previously. As such, you probably want to backup that file before replacing it.

Ok, Sorry for the delay. I had my HTPC blow up after a power failure and had to re-load from scratch...

I tried the patch with the new diseqc commands and it works fine for scanning. I use 3 sats on A,B,C. I am having a couple other issues which I'll post in a seperate reply as I don't think they are related to the patch.

Also looks as though the setting the scan time to 30 or 40 secs and the latest psiparser patch took care of the unknowns 99%.

Cheers

-Shaky

[Shaky]

I am still unable to get any DVBEPG information from Echo 119. Express 91 works fine.

The scan for EPG data either stops with 1 second left, or appears to finish but doesn't have any data when I view the EPG. Any ideas? I think I attached a log of this a bit ago, but can do so again if you think there is something worth looking at. Anyone Else have this issue or solved it and could share how?

[sub]

I am still unable to get any DVBEPG information from Echo 119. Express 91 works fine.

The scan for EPG data either stops with 1 second left, or appears to finish but doesn't have any data when I view the EPG. Any ideas? I think I attached a log of this a bit ago, but can do so again if you think there is something worth looking at. Anyone Else have this issue or solved it and could share how?

I remember you mentioning you had this problem in the past but I dont remember seeing the logs posted. Can you post a link to the post so I can take a look.

Is Echo 119 a Dish service? I've been looking into this with btothec's supplied transport stream, but its not looking good. Dish dont use the standard DVB EPG, instead opting for some priorietary solution. I may still add support for it, but it isnt going to be quick fix.

[Shaky]

I remember you mentioning you had this problem in the past but I dont remember seeing the logs posted. Can you post a link to the post so I can take a look.

http://forums.nextpvr.com/showthread.php...37&page=21 - Near the end.

Is Echo 119 a Dish service? I've been looking into this with btothec's supplied transport stream, but its not looking good. Dish dont use the standard DVB EPG, instead opting for some priorietary solution. I may still add support for it, but it isnt going to be quick fix.

Yes, It is Dish Network. Too bad it doesn't follow the standard you have already coded I tried using Zap2it and that didn't seem to work either, I'll be playing with that some more I think. EDIT: Looks like Zap2it will work. Have to download zap2it guide first and than search transponder to map channels.

Let me know if you need me to try anything and provide different logs, and thanks for your efforts!

-Shaky

[sub]

http://forums.nextpvr.com/showthread.php...37&page=21 - Near the end.

There is no definitive reason in the logs. I suspect its just processing some garbage working on the assumption its the normal EPG info, when in fact its some non-standard Dish data which doesnt follow the same rules.

For now its probably worth just avoiding the DVB EPG option with Dish.

[sub]

It may be not the reason for the described crashing ... but ... after a lot of testing - is it possible that some of the PID-Informations that gbpvr should hand out to MD-plugin(s) via mdapifilter are "hardcoded" by mistake???

I get following informations using a magic MD-plugin

Name=VUF7
tp_id=7

CA_Typ[0]=5986 (Hex=1762)=Beta Technik (Betacrypt)
ECM[0]=101 (Hex=0065)
EMM[0]=249 (Hex=00F9)
ProviderID[0]=0 (Hex=000000)

Video_pid=160
Audio_pid=161
TeleText_pid=8191
PMT_pid=0=$0000
PCR_pid=160
ECM_PID=101
SID_pid=167=$00A7
AC3_pid=0

--> Name, tp_id, SID_pid, stay the same, no mather which channel I tune to.
With some googling I found out these values are equal to ones of the NA-programme "VUF7" on BEV. My dish is directed to Astra 19.E in europe.

--> Though the ECM-PID is forwarded correct, gbpvr should hand out them all if there are more than one ECM. Maybe it would already help if it would hand out the right PMT-PID ?!

stevie77

using vplug 1.4.0 ... working stable but dark on some channels because multiple ECM

Can you try the attached patch? This one is able to set the PMT PID, SID, TP_ID, multiple ECMs etc.

btw, which plugin shows the information passed in (PIDs etc shown above)? or are you able to confirm the correct details are passed in. The service name passed in may not always be correct - sometimes it hasnt been received by the time I have the other info ready to pass to the multidec layer, and I didnt want to hold things up waiting for it to arrive.

[Stevie77]

This version rocks !!!!

Everything's working great. No lack of channel-information. All details are passed to vplug. I can see that in the info tab of vplug.

Tested with vplug v 1.3.3.0. Newer versions stutter from time to time.

[sub]

Great.

[btothec]

This version rocks !!!!

Everything's working great. No lack of channel-information. All details are passed to vplug. I can see that in the info tab of vplug.

Tested with vplug v 1.3.3.0. Newer versions stutter from time to time.

Has it cleared up the EPG issues you were haiving? What sat are you pulling down?

B