Mixed loaders and not getting great progress when loading

[junky]

Have a Queue of imageLoaders and videoLoaders, and I've defined the estimatedBytes, but I still get very poor progress reports. It starts at 0 then jumps to .2 then .9 and then the remaining progress reports .9945413412, .9956341435. Here's the trace:

 

trace(event.target.name, "progress: " + event.target.progress);

 

returns:

why progress: 0.8593410590073448

why progress: 0.8594171019451604

why progress: 0.859893932453896

why progress: 0.8673481144808071

why progress: 0.8675188586030212

why progress: 0.9898047009946656

why progress: 0.9899934945196937

why progress: 0.9957593552804853

why progress: 0.995928129077478

why progress: 0.9961149535479457

why progress: 0.9962897743205523

why progress: 0.9964796674055109

why progress: 0.9966514195636268

why progress: 0.9968322873118477

why progress: 0.9970191117823154

why progress: 0.9971939325549221

why progress: 0.9973838256398806

why progress: 0.9975555777979965

why progress: 0.9977364455462174

why progress: 0.997926338631176

why progress: 0.9980980907892919

why progress: 0.9982909622353737

why progress: 0.9984597360323663

why progress: 0.9986406037805872

why progress: 0.9988214715288081

why progress: 0.999002339277029

why progress: 0.9991832070252499

why progress: 0.9993640747734708

why progress: 0.9995449425216917

why progress: 0.9997258102699126

why progress: 0.9999066780181335

why progress: 1

 

What do I need to do to get better results? Is it the videoloaders? Here's what I'm doing for the video loaders.

 

var v0_loader:LoaderCore = LoaderMax.parse(xml.page.video[0].@src.toString(), {volume:0,bufferMode:false,container:v0_mc, noCache:false, estimatedBytes:Number(xml.page.video[0].@estimatedBytes)});

parentQueue.getLoader(QUEUE_NAME).append( v0_loader );

v0_loader.addEventListener(VideoLoader.VIDEO_COMPLETE, loopVideo);

 

Anyone have any ideas? HELP!

[GreenSock]

A few questions:

 

1) Are you using the latest version of LoaderMax?

 

2) Are you sure that your estimatedBytes values are accurate?

 

3) Can you provide a very simple example FLA (and support files) that demonstrates the issue? No need to post production files.

 

4) Did you clear your Internet Explorer cache before testing your movie? Flash caches files (including NetStream video stuff) in IE's cache. That'd explain why it might jump ahead initially (if the file or part of it was cached).

 

You could also consider using the rawProgress of the LoaderMax if you want. See an explanation at http://www.greensock.com/loadermax-tips/#8

[junky]

http://flash.dev.axis41.com/axis41/_test/_loader.zip

 

I'm not using IE. I'm just testing in the flash IDE bandwidth profiler (which usually seems to work). Take a look and let me know what you think. Thanks Jack.

[GreenSock]

Aha, that's just because Flash's bandwidth profiler treats NetStreams differently than all other file types - it doesn't throttle them at all. So, in your example, you've got 2 videos and 1 image (in that order) in your queue. So it loads the first video VERY quickly (that's the first jump), then it loads the second video almost instantaneously too (the second jump) and then the final image does indeed get throttled by Flash, so it slowly loads over time. But remember, your videos are MUCH bigger in terms of file size than your image. That's why you get to 98%+ very quickly and then it inches towards 100% as the image finishes loading. This isn't a bug in LoaderMax at all - it's a bug in Flash's bandwidth profiler. You can verify this by moving your .flv to a remote server and load it that way instead of a local file. Again, make sure you clear your IE cache each time you test, though, because that's where Flash caches things.

[junky]

Ah, excellent. I'm an idiot.

 

Thank you for the reply I really appreciate it. I'll upload the file and see if that fixes it. Thank you again.