[BC] XDX Receivers

KNCN674 at aol.com KNCN674 at aol.com
Mon Feb 9 10:41:12 CST 2009


XDS / Premiere
 
This conversion seems very poorly planned. As of 2-6-09 they were still  
making more software revisions. They are following the Microsoft method of  
letting the customers identify and solve their problems. I could not get a firm  
"drop-dead" change over date and we now await more changes. ' Probably working  
with a very short staff too.
 
Rich KRDE
 
In a message dated 2/6/2009 10:06:47 P.M. US Mountain Standard Time,  
chad at lotusradio.com writes:

The only  issue we are having with Fox Sports is the new Dan Patrick clock
that is  now in play when the XDS receiver is left on FSR and not switched to
The  Dan Patrick Show. According to Premiere, it was strongly recommended
that  we move to the FSR since the length of time Dan Patrick will be on  a
separate channel is limited. Guess there is a 40 second delay issue with  the
show and Fox only allows for a :30 break at the top of the hour, that  is it,
not an additional :10 for a legal. Other than that, we have not had  issues
with Jim Rome and the rest of the Fox Sports lineup. Guess FSR just  changed
the entire lineup for hosts.

Chad Owens
Lotus Radio Corp  RENO

On Fri, Feb 6, 2009 at 11:46 AM, Kevin Trueblood  
<kevin at neptuneradio.net>wrote:

> I can't speak specifically  for Fox Sports, but I can tell you that we've
> had
> some  problems with missed closures on Delilah and Glenn Beck.  I've  talked
> to the folks at Premiere a couple of times who have admitted  the mistake
> and
> I know they'll fix it.  They've always  been very reliable, in my
> experience.
>  Just bugs in the  new system, I guess.
> I definitely found a "gotcha" at the end of the  hours on XDS-captured
> shows.
>  For us, we delay Glenn Beck  by one hour.  Two days in a row we missed what
> would have been  the 9:58:50 closure.  Come to find out that they sent the
> closure  2 seconds late each day.  Well, our XDS didn't catch it because  
the
> "feed time" ends at 58:50, thus not capturing the closure that  came in 2
> seconds later.  So our automation sat there waiting  until someone caught
> the
> missed break and moved it on  manually.  We put in a failsafe by
> hard-syncing
> the 58:50  break to 58:52, so if the closure is missed the automation will
> move  on by itself.  If the closure is received the automation will  already
> have moved on beyond the sync point.
>
> Kevin  Trueblood
> Engineer
> Mid-West Family Broadcasting
>  Madison,  WI
>

~_____________________________________________________________________~
The  BROADCAST [BC] list is sponsored by www.SystemsStore.com
The Preferred  Source For PLATINUM TOOLS - EZ-RJ45 & Lots More!
Tools & Supplies  To Build and Maintain A Technical  Infrastructure



More information about the Broadcast mailing list