Problem with MLB.com IS NOT SWARMCAST!!!
I have been maintaining a thread documenting my testing of the problem with MLB.com. http://forums.adobe.com/thread/1010015?tstart=0 In response to my complaint that the thread is being ignored, Chris Campbell, who I actually find polite and helpful, posted this:
Sorry Wilbur, I didn't mean to ignore this thread. I thought I had communicated that we found the MLB problem wasn't due to Flash Player, but instead attributed to a technology that MLB is using called SwarmCast. It looks like Flash Player is responsible, but that isn't the case.
http://forums.adobe.com/message/4440073#4440073
I appreciate your detailed responses, but my video team is telling me that this isn't something we can fix (since we don't own SwarmCast.) Is there an action item you'd like to see us respond to?
Chris, because you are still ignoring that thread, you missed this detail:
I am having the same problem even when what you are calling "SwarmCast" is not running.
I realize that my posts are long and daunting to read. However, they contain a wealth of information and are worth taking the time over. Especially, the last several I posted with screen shots should be particularly interesting.
So you know, what I think is that there is an interaction between Flash player and the MLB container that is choking off the video data stream. My evidence is that when a game exhibits the pausing and spinning circle problem, the associated browser gets bad results from MLB's speed test, but another browser does not.
Could you please consider not giving up on us MLB.com subscribers? The problem is NOT SwarmCast (actually NexDef) and my posts on that thread clearly show that.
Thanks.