is *GREAT* For Re-Arranging Your Channel Guide!
Originally Posted by Tirebiter
Hmm, the 4 major networks are duplicated in the 380 to 388 channel range so the situation isn't as "dire" as I thought. The fifth missing channel isn't important to me. I don't watch anything on it. But it is still inconvenient to have these channels separated from the rest of the local channels in the on-screen guide...
Do you use WiRNS
If yes, you can create up to three CUSTOM lineups for one ReplayTV, gathering your 'Missing Guide Data'. Then, you can REMAP those channels to be wherever you want them - i.e. back in the 800s, or even down in the single digits like the original NYC channels from the 50s:
- CBS: 2
- NBC: 4
- FOX: 5
- ABC: 7
- WOR: 9
- PIX: 11
- NET: 13
#Created by WiRNS Configuration
#IMPORTANT - the ReplayTV will automatically remap channels in the 8000-9000 range and may with others as well.
I resisted using WiRNS
for several years because, for me, it's always been temperamental, where DVArchive
has been pretty much 'Rock Solid'. But, with ~600+ channels in the cable lineup - the MAJORITY of which I either don't subscribe to or don't watch, I needed a way to trim that number down to something manageable. WiRNS
was the ticket.
Unfortunately, now that *ALL* of my ReplayTVs are using WiRNS
, it has decided to get moody once again - "WiRNS has unexpectedly closed. Send report?"
The DEBUG Log shows:
[2012-06-18 21:39:44] HTTPClient WebException: HTTP error connecting to 192.168.0.117
[2012-06-18 21:39:44] HTTPClient URI: http://192.168.0.117/Device_Descr.xml
[2012-06-18 21:39:44] Refresh(): System.Exception: Error parsing device description from 192.168.0.117! ---> System.ArgumentNullException: Value cannot be null.
Parameter name: s
at System.IO.StringReader..ctor(String s)
at System.Xml.XmlDocument.LoadXml(String xml)
--- End of inner exception stack trace ---
at WiRNS.Replay.ReplayDevice..ctor(String ip, String Port)
at WiRNS.Replay.ReplayType..ctor(String name, String ip, Int32 type, String color, String input1, String input2, String input3, String serial, String isn, String port, String ivsNickname, String lastNetConnect, Boolean proxyGuide, Boolean doPoopli, Boolean doIVSBase, Boolean includeReceived, Boolean doJIT, Boolean IVSIntercept, Boolean RemoteReplay, Int32 quality, Int32 keep, Int64 guaranteed, String category)
and entering "http://192.168.0.117/Device_Descr.xml
" into a browser results in a '404 Error' until I COLD BOOT the specific ReplayTV. It worked OK for a good month, so, it's another interesting puzzle to research and discover what's wrong now.
I changed DNS1 on the offending ReplayTV from WiRNS
to my Router and now the rest of my ReplayTVs can get Guide Data - their last update was 06/16/12 and I just noticed it when I was entering the new season of USA shows into the 'Schedule'.