S2 in 4.8

[PerryM]

I've just got a new card to enable reception of S2 format for Ch4 HD in Freesat. I did a complete new scan in my host HTPC running 4.8 and the CH4 HD station comes up bright blue in the Channel List. Is this because it is S2? It is the only channel so coloured but I think it is also probably the only S2 currently broadcasting. It seems to be working OK. My slave DVBViewer is still on previous version and that doesn't come up blue but also seems to work OK.

[PerryM]

It was all going too well!

I updated the slave PC to 4.8 and it all went well for about a week. Today I turned on the PC, did a Windows update and one for the Adobe Flash stuff used for BBC iPlayer, and suddenly I have no live TV - it says 'No Hardware'. I can see the host PC on the network and the slave DVBViewer plays back recorded programmes from it. The local DVBViewer on the host machine is working fine so I assume the Unicast Devices are OK. I can also get live TV fine on my Popcorn Hour type Media Player at the same location as the slave. I tried System Restore on the slave PC but no change.

Any ideas?

[majstang]

DVBViewer-->Options-->Hardware-->Highlight your Unicast device/s--> Press "Settings" button-->Check if server is present in "Autodiscovery Serverlist"-->Doubleclick on the servername in same window-->OK-->Close and restart DVBViewer and live-tv should work.

 

If not working redo the unicast setup by following http://en.DVBViewer.tv/wiki/Recording_Service_Installation_Guide

[PerryM]

This is the sort of thing that drives me potty!

I came home from work tonight to find my host PC with the Recording Service Tray Icon red even though there was nothing scheduled for that time. I could not get into the R/S to see what it was doing so I had to reboot the PC. Everything came good and (you've guessed it) I now have my slave back working again. Now earlier this evening the R/S had successfully recorded a programme so there couldn't have been a lot wrong with it! When I was trying to cure my lost slave (see above) I rebooted the host PC at least twice!

In retrospect the R/S clearly suffered some form of corruption which has taken several PC reboots to get back to normal. Earlier in the week we did have some severe power fluctuations which maybe started off the chain of events.

PCs - don't you just love/hate them!!!