Re: U-Verse Realtime v1.2.1.0

wiltshp · ‎10-20-2008

SomeJoe7777 wrote:
I will add those two channels (195 and 233) to the database. By the IP addressing, 233 looks to be a local channel/feed, while 195 appears to be national. I get neither of these channels here in Houston.

The QVC/HSN thing, I think I know what's going on there. The feeds on 3/9 and 12/11 are actually duplicates of the same feeds that are on 420/422. 420 (QVC) and 422 (HSN) have as part of their contract that they appear in the local channel list as well, but the channel number they get put on down there varies with what your local channels are. 3 and 12 are not used in the Houston area, but probably are in Columbus, so they're on 9 and 11 there.

What I'll probably do is remove the local mapping from the channel database and just leave 420/422 in there. Thus, if you're tuned to QVC, then the program will show you're on 420 even if you're on the local channel remapped feed.

The same thing will happen if you tune in to one of the AT&T barker channels (like AT&T Buzz on 300). That same feed is on 1000 and 1300, so no matter which one you're on, UVRT will always show 300.

For the oddity you're seeing with the DVR, I'm working on a new version of UVRT that completely changes how it gathers the channel information, and it will be more reliable and robust.

Great, thanks again for your help. As I get more time I will continue to verify the rest of the channels here in cbus.

cheer · ‎10-20-2007

Joe:

This app is amazing. Finally took the time to install it/check it out...how did I ever live without it?

Two minor comments/suggestions:

(1) The elements on each screen appear "anchored" (meaning resizing the window doesn't move/resize them), which is fine...except the date/time. If you expand the window to the right, you'll see the date/time move too, which (A) looks odd, and (B) can end up clipping the "Connected" light. (Hey, I said these were minor.)

(2) I had an issue after enabling stream gathering. The default interface listed in the Network Interface dropdown was 'Network adapter "Microsoft" on local host.' (In fact, when I looked later, there were three of those listed.) I didn't pay any attention to this. Once I enabled stream gathering, I got an unhandled exception error in U-Verse Realtime. Simple error text was "Failed parsing as mac addresses. Expected 6 hexes and got 1 hexes. Parameter name: address."

Now I'm not sure what those Microsoft network adapters represent; the only other item listed was my GigE interface, so I'm guessing one of those must be my wireless, but who knows. The issue is that once I had done that, I got the unhandled exception every time I launched the app, after which the app wouldn't actually work (though it wouldn't close if I clicked "Continue"). Took me a minute to figure out I could still go to Configuration and change the selected adapter.

If you need the full text from the unhandled exception, let me know. You might want to toss some error handling code around the MAC address parsing. Also, if those "Microsoft" adapters are never valid, you might want to filter them out altogether. (Just suggestions, obviously.)

OK, sorry to immediately jump into issues, but figured you might want to know. Now...channel info. I could've just listed them here, but it was easier for me to create an Excel spreadsheet, and that's probably easier for you, too. (If it's not, just let me know and I can paste here, or get you a comma-delimited or tab-delimited file, or whatever you like.) You can get it here, or here if you need it in the older Excel binary (.xls) format.

I did notice some weird channel identification going on for the "national" channels that are remapped locally (QVC and HSN, for example) but I see you've already looked at that, so I didn't bother to include any of those in my list.

--chris

SomeJoe7777 · ‎01-30-2008

Thanks for the feedback, cheer!

I have a new version that I'm going to release soon (v1.3.0.0), I'll address your concerns here:

1) Ya, I saw that the date/time wasn't anchored properly. That's already fixed in the upcoming version.

2) Ya, currently, selecting an invalid interface produces this error/crash. This will be fixed in the next version such that a friendly error message will be displayed.

I can't tell just from the descriptions which network interfaces are going to be valid selections or not unless the code attempts to communicate with all of them at program startup. I'm afraid that this will take too much time and may delay the startup more than it already is.

3) Ya, will fix the QVC/HSN channel mappings as discussed above.

Awesome, thank you for the Chicago locals, I'll get them in the database. I need your zip code also so I can pull the official channel descriptions off the AT&T site.

cheer wrote:

Joe:

This app is amazing. Finally took the time to install it/check it out...how did I ever live without it?

Thanks very much for the compliment. Just wait until you see the new one (v1.3.0.0).

cheer · ‎10-20-2007

SomeJoe7777 wrote:
Awesome, thank you for the Chicago locals, I'll get them in the database. I need your zip code also so I can pull the official channel descriptions off the AT&T site.

60031.

And I should've figured you were already on top of the issues I saw.

--chris