with the same browser open, I went to buy.com -- still downloading 184KB/s -- I keep hoping this is just an illusion or some kind of snafu -- If aI had any less of a connection i would be dead in the water
Printable View
with the same browser open, I went to buy.com -- still downloading 184KB/s -- I keep hoping this is just an illusion or some kind of snafu -- If aI had any less of a connection i would be dead in the water
jhb: Any files that are started downloading will continue downloading until they are complete or the browser is closed
I wonder if the media will pick up on this before too long, since it effects sites that have no Flash content on them.
what do you mean 196 kb/s? Are you using a dsl. I only ask because my monitor download rate averages about 5-10kb on a 56k modem. Sorry for the unrelated post here, just curious about it.
I have an OC-48 line -- its fiber -- to concentric's backbone
So basically it does affect any user, IF they go to a site that has the Flash 6 player and then go to a different site they will experience a longer load time. I am not sure if most users will connect the load time with the flash 6 player, but certainly it is something to be fixed. Perhaps MM can disable the download of the player until these issues are worked out. I think for many users they may just think the internet is running slow?
http://www.actionscript.com/archives/00000256.html
We have our first real word from a Macromedia official. Check the reply at the bottom of the article.
It seems finally someone has noticed our concern. Although the he's not particularly helpful and doesn't seem to fully understand the issue yet this is at least a start. There is hope :)
that was very nice corporate double speak in that article -- Pinged his radar -- I don't have it wired yet --
Why is it that tech support people have such a hard time understanding a problem? I am not trying to knock the guy, but the statement he made was not exactly a helpful one. I understand it's probably not a big concern to him -- he probably doesn't mess with Flash all day- and all the nuances of the program are probably not a big part of his consciousness, but don't try to sound like you know what you are talking about if you don't.
It's good to so-- that MM is aware of the problem and has decided to grace us with a response - whatever the quality.
If that guy knows about it, I am sure the developers will probably know about it -- and that makes me feel a nice warm fuzzy for Macromedai again.
I guess wiring up the core issue will be his primary action item at this juncture.
Excuse me for jumping in this thread, just had a complete readthrough... And just wondering if reverting to the Flash 5 player would temporarily solve the problem for the average user.
Guess some new features outputed through MX woudn't be available, but for the time being, would it solved this continuous streaming problem?
It would indeed solve the problem, but it's a bit of a hastle for normal users and I suspect most would be reluctant to do it.
Really Macromedia should pull the new player from the website to stop this spreading further, but I doubt they will, it would be bad publicity
And what about this new member from Macromedia...
http://board.flashkit.com/board/show...hreadid=290156
Doesn't he have anything to say about this?
I do think we need to keep things in perspective. We posted the original problem over a weekend which happened to coincide with the biggest week in Flashworld - the Flash Forward conference. It would make sense that many of the developers will be at Flash Forward as will the Macromedia Developers who would usually monitor the bug reports. I am sure Macromedia has listened and hopefully the speed we have escalated this problem will ensure its treated with the due urgency it requires.
We now have an official Macromedia response to say its being looked at - what would now be nice NOW is to have a ball park timescale for when a fix would be available presuming Macromedia have gone through their internal procedures and confirmed our findings - which they will do however they wish to word it.
How this rogue player got into live circulation though is a question mark and I think this proves one thing - the beta testers for flash need to include some narrow band streamers!
Its NOW however in all our interests to keep this thing low key and let Macromedia do their stuff and get a fix out with as little fuss as possible. Putting people off the Flash plugin is kissing our clients goodbye. There are enough anti-flash html pussies out their who would love to do some scrare mongering - lets not give them more rocks to throw at us.
Goes without saying that if we can provide any further information or resources to help Macromedia provide the fix quicker so be it - they have but to ask.
Well, guys. I closed comment posting options on the Actionscript article concerning this issue. Looks like John Dowdell from MM Support is aware of the issue and is going to be dealing with it.
That's good enough for me. I think they'll do it in a timely fashion now.
I do believe this is a serious issue and Mike Chamber's comments did not help the situation of a bunch of developers freaking out.
Soon we'll all have the chore of updating all those buggy Flash 6 Players in the world.
-scott
http://www.scottmanning.com/
alls well that ends well
That was a lively debate though.
Let's hope we did more than ping his radar and he rings some bells with the higher-ups.
Yes, you can download and install the old Flash 5 player here:
http://www.macromedia.com/support/fl...oldplayers.htm
But, it's a nasty solution for the average user. Download the player installer, find where you saved it, run it, choose the options, and then restart. Try it for yourselves.
I, too, think we should try and keep this a little quiet. Most people won't be able to associate the slowdown to the flash content. I wouldn't have if I hadn't seen this thread.
ok, sorry i haven't been back on this thread, but i have been travelling a lot the past week between toronoto and san francisco.Quote:
Originally posted by nocrapchurch
I do believe this is a serious issue and Mike Chamber's comments did not help the situation of a bunch of developers freaking out.
second, we are very aware of the issues, and our engineers are working on it.
third, i just reread my previous post in this thread, and realize how flippant it sounded. sorry about that. we take these sorts of issues very seriously, but at least on my radar, this is one that fell through because of everything going on (flashinthecan, flashforward, continued heavy traffic on all of the flash community lists).
mike chambers
[email protected]
[Edited by MikeChambers on 04-03-2002 at 03:08 AM]
Thanks Mike, that's exactly what we wanted to hear. Do you have any idea what kind of timescale it will be before a fix is released? We need something to tell our clients.
i don't have an eta right now, but i can say that we understand how important an issue this is. (after we fix it, we have to QA it to make sure it is fixed, and that the fix didn't break anything else).Quote:
Originally posted by C4_Tom
Thanks Mike, that's exactly what we wanted to hear. Do you have any idea what kind of timescale it will be before a fix is released? We need something to tell our clients.
when / if i get an eta, i will post it here.
mike chambers
[email protected]
Excellent, that's great news. Hopefully this will be resolved soon. You guys at Macromedia had us worried for a while there :)
no problem. in the future, if something like this comes up (and I obviously miss it like i did this time), please email me directly.
mike chambers
[email protected]
Righto, I'll add that email to my address book for future issues. That would certainly save time in the future