[Resolved] [Resolved] [Resolved] [Resolved] [Resolved] [Resolved] [Resolved] [Resolved] [Resolved] [

FYI : The new player is avaliable at our website now.

This release only fixed :

1. the streaming bug within ActiveX players on windows.
2. a related memory bug.

if you have downloaded the new player and think you are still experiencing the streaming bug:

1. make sure the new plugin is loaded.
2. reboot your machine (to be sure)

if you still think you are experiencing the issue, then feel free to email me OFFLIST, but make sure that you include:

browser version
OS
web page you are having a problem with.
steps to reduce the issue.

i might not be able to response directly to each post, but i will make sure that the appropriate people see them.

mike chambers

[email protected]

dope.

because this ended up on a new page,
so you all know:
I figured every one would be looking here for the resolution to this, so I posted a MovieClip.prototype method that determines the minor version of the player and returns it, so you can then check whether or not it's < 25 (or whatever really)
it's on the previous page (13)
usage is there too.
use at your free will,
I'd appreciate it if someone answered the request:
how and where to copy it so that it automatically gets included in every .swf published (without me having to code it every time)
tx.

Quote:

---

Originally posted by sonwah

I'd appreciate it if someone answered the request:
how and where to copy it so that it automatically gets included in every .swf published (without me having to code it every time)
tx.

---

thanks for the method. it will be useful.

couple of comments.

1. first, you probably shoulnd't attach it to the movieclip object, but rather place it in the _global name space like so:

_global.methodName = function()
{
}

this will still allow you to call the method from anywhere in your movie, and will not pollute the MovieClip object.

if you put the method in a include file (checkVersion.as), and then place it in the following directory:

Flash MX\Configuration\Includes

Then, in any movie you want to use the method in, just add this line to the first frame of your movie:

#include "checkVersion.as"

and the method will be avaliable to your entire movie.

hope that helps...

mike chambers

[email protected]

thanks for the tip on _global mike,
I knew the MovieClip object wasn't the best place but couldn't think of anywhere else it was relevant...

code is amended.

cheers :)

thanks Mike!

Will there be a MAC version of the update or did I miss something in the many threads, and the bug did only affect windows?

thanks

chris

Quote:

---

Originally posted by chris.sauber
thanks Mike!

Will there be a MAC version of the update or did I miss something in the many threads, and the bug did only affect windows?

---

the bug only affected ActiveX plugins on windows, so i do not believe there will be a Mac update.

mike chambers

[email protected]

Mike,
after performing a regsvr32 c:\winnt\system32\macromed\flash\flash.ocx /u

and manually deleting the flash.ocx,
rebooting, downloading the supposedly new plugin,
rebooting again, and checking..
I still get minor version 23.
I think we still might need to wait awhile.

i actually did all of the above.. delete the ocx. then install the new version 25, reboot. download again to be sure.

then go to "about macromedia flash player" link from the popup menu, and it says version 6.25 installed


the bug is still there, (which I've sent Troy an email an hour ago, FYI Mike), and when i used the script sonwah provided, do a

trace(minorVersion())

it comes out to be 21?

I updated the player and the 'stream bug' is gone!

PC Win98, IE5.

Thank you MM,

Now comes the task to announce the new release to everyone and their mothers.

I just this second tried again to install it a still get only (minor) version 23

the reason you're getting minorVersion 21 in your trace is that the test movie environment uses a different player - ie not the same one as your browser.

try using this, (in a browser of course)

Code:

---

getURL("javascript:alert('the full version is " + getVersion() + " and the minorVersion is "+_global.minorVersion()+"');");

---

Got mine working. Just deleted the c:\winnt\system32\macromed\flash\flash.ocx reinstalled new flash restarted the browser and problem solved. Whoa ya...

Thanks Mike

hmm. interesting. i wonder why i still have the streaming bug.

would any of you guys (who said the streaming bug is gone) test this out for me

http://www.the1stmovement.com/temp


1) click on a song on the background
2) then wait till it's streaming
3) click "unload" on the left

for me, the sound continues to stream, and i have version 6.0.25 installed (as said on the "about Macromedia Player" link at least)


thanks guys

Quote:

---

Originally posted by chanm7
hmm. interesting. i wonder why i still have the streaming bug.

would any of you guys (who said the streaming bug is gone) test this out for me

http://www.the1stmovement.com/temp


1) click on a song on the background
2) then wait till it's streaming
3) click "unload" on the left

for me, the sound continues to stream, and i have version 6.0.25 installed (as said on the "about Macromedia Player" link at least)


thanks guys

---

I just downloaded version 25 and it fixed my streaming problems. What exactly does your "UNLOAD" button do? Does the button stop the streaming MP3 using Sound.stop()? My understooding of the "streaming bug" was that aborted downloads would keep silently downloading in the background, not that streaming audio would keep playing after a stop.

the "unload" button unload the whole movie (the right mp3 player)

that's why you'll only see the white, cuz the mp3 player has been unloaded, so the sound should be stopped right?


hmm.. or did i misunderstood the "streaming bug"

I went to the download page:
http://www.macromedia.com/shockwave/...ShockwaveFlash

But, it still says 6,0,23,0 and when I downloaded it again, you betcha, it's version 23.

Am I missing something?

fyi:

i am going to post some more info on this shortly.

mike chambers

[email protected]

We have pulled the new player release 6,0,25,0 from the website and are now currently pushing the previous player 6,0,23,0.

After we initially pushed 6,0,25,0 this afternoon, we discovered (with help from the community) that there was still an issue with streaming sounds using LoadSound. Because of this we pulled the 6,0,25,0 player from the website. We are working around the clock to fix the issue, and will be releasing a new version of the player in the next couple of days.

I realize that this is not the best way that this could have transpired, but based on past community feedback, we decided it was best pull the new player until the issue was resolved.

As usual, if you have any comments or questions, please feel free to contact me directly.

mike chambers

[email protected]

thanks mike.

Thanks. Glad you recognized that there were still problems with the new plugin before it caused any havoc. Can't wait for 6.0.26.0!

fair enough.

Here's hoping the rest of the probs get fixed easily.
Cheers to the dev team!