TWC Today Forums

Present - The Weather Channel 2000 => WeatherSTAR Tech Support => Topic started by: Tyler on November 13, 2013, 06:06:43 PM

Title: Update-Related Issues
Post by: Tyler on November 13, 2013, 06:06:43 PM
Please use this thread to report specific issues with this weeks IntelliStar and IntelliStar 2 update. This thread is not to be used for speculation, only for reporting bugs.

Known issues (please do not report):



Another widespread issue is with the radar products. A lot of reports of cities missing, out of place, or locator dots missing. Example, here is my metro radar:

http://i40.tinypic.com/14dklkh.jpg (http://i40.tinypic.com/14dklkh.jpg)

There are a few issues with it:

1. Cranberry Twp is out of place. It's actually in Butler County, not Allegheny.

2. Wexford is out of place. It's along I-79, not I-76.

3. Penn Hills has no locator dot.

4. Several cities are kind of far from their locator dots (see: Beaver Falls, South Fayette). Though my map isn't as bad as some maps are.

Radar with correct location of Wexford and Cranberry: http://i43.tinypic.com/e06h79.png (http://i43.tinypic.com/e06h79.png)

Please also report radar issues like these here. If you STAR info isn't in your profile, please include the following: STAR ID, cable company and city. Screenshots and/videos help.
Title: Re: Update-Related Issues
Post by: Trevor on November 13, 2013, 06:24:51 PM
I places the cities in the correct location and also suggested a few changes for a few cities (hope that's ok). Red indicates that the city needs to be moved, orange is just a suggestion.

Top is showing the current map with corrections, bottom is showing what it would look like after the changes.
Title: Re: Update-Related Issues
Post by: toxictwister00 on November 13, 2013, 06:47:12 PM
Macon, GA is missing on the regional radar map, however the black indicator dot is there. (red arrow points to where I'm talking about)
Title: Re: Update-Related Issues
Post by: Zach on November 13, 2013, 07:08:23 PM
Two issues on 24629:

- Ocala is cut off on the regional radar map
- MacDill AFB is misplaced
Title: Re: Update-Related Issues
Post by: TWCJim on November 13, 2013, 07:22:10 PM
On Astoria's STAR (23550) there are issues with both of the radar maps.

On the regional map, the labels for Olympia and Hoquiam are cut off at the top.

(http://i1213.photobucket.com/albums/cc475/TWCJim/23550regionalradar_zpsab7cc2d7.jpg)

On the metro map, Vernonia shows the dot but its label is cut off at the bottom (black arrow points toward Vernonia).

(http://i1213.photobucket.com/albums/cc475/TWCJim/23550localradar_zps69bd3650.jpg)
Title: Re: Update-Related Issues
Post by: beanboy89 on November 13, 2013, 09:18:32 PM
  • Severe weather crawl: Crawl no longer has beeps - this is intentional. Also, all crawls are now red no matter if they are a warning, watch or advisory
I could be mistaken, but I thought the beeping (or some kind of audible tone) was required by the FCC. Isn't that the reason the Weather STAR III was discontinued?
Title: Re: Update-Related Issues
Post by: Tyler on November 13, 2013, 11:06:05 PM
  • Severe weather crawl: Crawl no longer has beeps - this is intentional. Also, all crawls are now red no matter if they are a warning, watch or advisory
I could be mistaken, but I thought the beeping (or some kind of audible tone) was required by the FCC. Isn't that the reason the Weather STAR III was discontinued?
I thought that was the case too. I guess we were wrong.
Title: Re: Update-Related Issues
Post by: Mike M on November 13, 2013, 11:15:28 PM
AFAIK, the only thing the FCC requires is that if there IS a tone it has to repeat when the message replays.

Also has anyone's IntelliStar SD been having issues with constant lagging when transitioning between the hourly and 7-day forecast, as well as the 7-day's icons rerendering towards the end of the duration of the product? Been seeing this issue on Xfinity's intellistar in Burlington, New Jersey.
Title: Re: Update-Related Issues
Post by: Charismatic Applesauce on November 13, 2013, 11:23:19 PM
I've been seeing the 7-day rerendering issue on both the SD IS (21813) and the IS2 (ID unknown) on Xfinity in Chicago.

Also, that same IS2 had an issue in the LF today at 10:18 PM CT when it didn't render the background at all, so all the data was superimposed on the national LF.
Title: Re: Update-Related Issues
Post by: beanboy89 on November 13, 2013, 11:27:17 PM
Also has anyone's IntelliStar SD been having issues with constant lagging when transitioning between the hourly and 7-day forecast, as well as the 7-day's icons rerendering towards the end of the duration of the product?
Yep. I've been noticing that, too. IS 22608.
Title: Re: Update-Related Issues
Post by: texasstooge on November 13, 2013, 11:33:18 PM
Also has anyone's IntelliStar SD been having issues with constant lagging when transitioning between the hourly and 7-day forecast, as well as the 7-day's icons rerendering towards the end of the duration of the product?
Yep. I've been noticing that, too. IS 22608.
Noticed it on my end as well on IS 22105. In addition, when the transition to the 7-day forecast takes place, I kept hearing the buzzing sound.
Title: Re: Update-Related Issues
Post by: micvachon on November 14, 2013, 12:00:51 PM
Just wanted to inform you that my Local Forecast still is stuck on the desert theme. I live on the Chesapeake Bay in Maryland, so it's not very fitting  :P

I don't know how to find my STAR info since it no longer says it... but my cable provider is Atlantic Broadband and my city is Chester, MD but I get the forecast for Centreville, MD.
Title: Re: Update-Related Issues
Post by: Eric on November 14, 2013, 05:48:24 PM
Just wanted to inform you that my Local Forecast still is stuck on the desert theme. I live on the Chesapeake Bay in Maryland, so it's not very fitting  :P

I don't know how to find my STAR info since it no longer says it... but my cable provider is Atlantic Broadband and my city is Chester, MD but I get the forecast for Centreville, MD.

This is a known issue, and the technical folks behind the scenes are said to be working on it.  It's a brand-new system, so let's just give them some time.  :)  It's not as if they ignore the problems.  They know what's going on.
Title: Re: Update-Related Issues
Post by: Dj0287 on November 16, 2013, 01:08:14 AM
New Orleans, LA. Is missing from the metro radar the location dot is there but the city name is missing I think it is just cut off at the bottom. Also Gulfport, Bay St. Louis, Long Beach, and Picayune seem removed well off from their location dot.

Cable One
Gulfport, MS.
23299
Title: Re: Update-Related Issues
Post by: beanboy89 on November 18, 2013, 12:37:34 AM
Currently under a Severe Thunderstorm warning and I heard the beeping and narration for the warning on my IS.

Edit: I just now heard the beeping and narration for the Severe Thunderstorm Warning, but the crawl is NOT on the screen. Only the LDL.
Title: Re: Update-Related Issues
Post by: curtjr4 on November 18, 2013, 07:10:23 PM
Not to step on Tyler's toes (heh), I have a friend in Glassport, PA who says that his headends IntelliStar would report for Penn Hills, PA. He told me after the updates, his IntelliStar stopped displaying an LDL and the locals. So essentially all he sees is the national feed.

IntelliStar SD
Penn Hills (or Glassport?), PA
Comcast - Channel 16

Tyler, if you know much could you lemme know? I know your on FiOS so I don't expect you to know much about it on Comcast.
Title: Re: Update-Related Issues
Post by: GolfDude on November 21, 2013, 06:40:43 AM
i came across something odd

i have a tv tuner that lets me tune on multiple tvs, so using that i tuned to the weather channel in hd on 1 tv, and the weather channel's SD FEED on the other (both have updated system).. both LOT8's are shown with the same location used, however both seem to have slightly different forecasts/data on them, even current conditions i have seen have been different between the sd and hd feed (temperatures being different, slightly different todays weather description/forecast).. and i noticed that the SD feed has a more detailed radar  than the hd feed does..)

no need for me to bring up the ever popular issue of the  too bright backgrounds causing the weekend forecast  to sometimes be near invisible to read in the extended forecast  b/c its white on top of brightness
Title: Re: Update-Related Issues
Post by: texasstooge on November 23, 2013, 02:26:38 AM
During the LOT8s, as a weather alert slide came in to inform of a "Winter Storm Watch", it started to lag severely, causing a 5-second delay for the rest of the presentation.

Local WX ID: 22105
Title: Re: Update-Related Issues
Post by: Al on November 25, 2013, 02:33:51 AM
On the San Angelo, Texas IS2 sidebar, for the airport area, it shows SAT - which is the airport code for San Antonio. Not San Angelo.

I'm not sure if this is intentional, but the airport code for San Angelo is SJT.
Title: Re: Update-Related Issues
Post by: Charismatic Applesauce on December 01, 2013, 02:01:36 PM
On the Xfinity Chicago SD IntelliStar (21813), the basemap is still green, and there is still buzzing on the 7-day forecast.
Title: Re: Update-Related Issues
Post by: Mike M on December 01, 2013, 06:59:42 PM
21884. On the regional raadar, the city identifier for Baltimore is missing. On the local radar Wilmington's identifier is missing, Bryn Athyn is a bit far from its point, and Marlton should be moved just a tad to the southeast so it's in Burlington County and not Camden.
Title: Re: Update-Related Issues
Post by: twcfan on December 01, 2013, 11:59:53 PM
Anyone else getting moon icons (e.g., clear instead of sunny) during the evening/overnight for tomorrow's forecast, or is this only an issue for those of us out West?
Title: Re: Update-Related Issues
Post by: gt1racerlHDl on December 02, 2013, 08:00:30 AM
Anyone else getting moon icons (e.g., clear instead of sunny) during the evening/overnight for tomorrow's forecast, or is this only an issue for those of us out West?

It happened on the New Bedford, MA IntelliStar recently, i'll take a pic tonight if it happens again.
Title: Re: Update-Related Issues
Post by: Al on December 21, 2013, 06:21:59 PM
The San Antonio IS2 (Time Warner Cable) apparently did not receive the graphics update. During Local on the 8s, it shows the old IS2 graphics, but it does have the correct LDL during segments and commercials.

Did I miss something? Did all units revert back to their old graphics or just this one?

Edit: Nevermind, it mysteriously changed back to the new graphics. That was weird.
Title: Re: Update-Related Issues
Post by: colonieweather on December 21, 2013, 07:01:57 PM
The San Antonio IS2 (Time Warner Cable) apparently did not receive the graphics update. During Local on the 8s, it shows the old IS2 graphics, but it does have the correct LDL during segments and commercials.

Did I miss something? Did all units revert back to their old graphics or just this one?

Edit: Nevermind, it mysteriously changed back to the new graphics. That was weird.

Hey Al.  I noticed the same thing with the IS2 up here in Albany, NY. I agree that it was weird.  So you're not the only one who saw that.
Title: Re: Update-Related Issues
Post by: viper87 on December 21, 2013, 08:37:16 PM
I caught the same thing on the Farmingdale, NY IS2
Title: Re: Update-Related Issues
Post by: WeatherWitness on January 11, 2014, 10:13:21 PM
9:08 CT: OKC IS2 was overlaid on top of the satellite feed.  Will need to check again to see if this was a one-time thing or not.  Has anyone else been having this issue recently?
Title: Re: Update-Related Issues
Post by: Charismatic Applesauce on January 11, 2014, 10:16:38 PM
9:08 CT: OKC IS2 was overlaid on top of the satellite feed.  Will need to check again to see if this was a one-time thing or not.  Has anyone else been having this issue recently?
I've seen that a few times on my IS2.
Title: Re: Update-Related Issues
Post by: WeatherWitness on January 11, 2014, 10:22:27 PM
9:08 CT: OKC IS2 was overlaid on top of the satellite feed.  Will need to check again to see if this was a one-time thing or not.  Has anyone else been having this issue recently?
I've seen that a few times on my IS2.

Yeah, it was no longer an issue on the 9:18 LF.  Guess it was just a glitch.