New Engine & DVB-S in North America? (1 Viewer)

[switzch]

The holygrail of TV in NA is a pointing at Dish or BEV and using a program like media portal. I have heard some rumbling of the new tv engine supporting North American satellite's.

Is this true? Does MP support plugins like Vplug? Can I use my cheap twinhan 1020?

Thanks.

 

[ASiDiE]

MP is very close... in fact, I was able to scan 1 transponder on Dish just today. It came up with about 18 channels. There were several FTA channels on this transponder, but I was unable to view any of them. I guess a little more work needs to be done... but at least we can scan.

MP does not support and never will support plug-ins like vplug so please to not ask about them.

I am 99% sure you can use your Twinhan.... Check the wiki for supported cards.

 

[smokeman]

running build tvengine3-05-28-2007--01-22h--Rev14720, I am able to scan echostar 110, and 119(legacy lnb's, on diseq port 1, and 2), worked great, except one annoyance. half the channels show the correct channel name. hgtv, food, etc..
I am near Litte Rock, AR so my locals come in, katv, kark, kthv, etc...
the annoyance is that a ton of channels scanned with very strange hex channel names. I haven't taken the time to figure out what channels those are, but when I tune to the ones that scanned correctly, it works just fine.

I'm using a skystar2.

 

[jdugas]

running build tvengine3-05-28-2007--01-22h--Rev14720, I am able to scan echostar 110, and 119(legacy lnb's, on diseq port 1, and 2), worked great, except one annoyance. half the channels show the correct channel name. hgtv, food, etc..
I am near Litte Rock, AR so my locals come in, katv, kark, kthv, etc...
the annoyance is that a ton of channels scanned with very strange hex channel names. I haven't taken the time to figure out what channels those are, but when I tune to the ones that scanned correctly, it works just fine.

I'm using a skystar2.

I have the same problem with my Skystar 2... I am now using a Hauppauge Nova-S Plus and only get a couple channels with this problem whereas the Skystar 2 had a ton of bad channels.

 

[CommGuru]

Those getting hex info for channel names should try increasing the timeout settings. In TVE3 under General Settings try setting PMT to 30 and SDT/VCT to 60 and then rescan. This resolves the issue for myself and many others.

This increases the time required for scanning but also makes it much more accurate.

CG

 

[smokeman]

this did not work

adjusting the timeouts did not work for me.
I see this problem popping up in other threads.
frodo worked on dvb-t

https://forum.team-mediaportal.com/...up-t22117p10.html?highlight=hex+channel+names

https://forum.team-mediaportal.com/...5703.html?t=25703&highlight=hex+channel+names

https://forum.team-mediaportal.com/...3430.html?t=23430&highlight=hex+channel+names

so, fyi this is still an issue. I might add I've tried on a amd 1200+, with 512 megs of ram. Then I tried on a slightly faster pc, pentium 4 2.3 ghz, with 1.5 gigs of ram, and sata.

 

[CommGuru]

Increasing the timings doesn't completely clear up the issue as there are still several channels that come in with hex names but for the most part, I can live with it.

 

[smokeman]

New Thread:

I started a new thread to detail all scanning problems with setup details, and log files:
https://forum.team-mediaportal.com/definitive_channel_scanning_thread_setups-t26786.html

 

[smokeman]

sorry to be running 2 threads,
but possible fix in sight,
see above link...