feature request on VideoLoader

[Ahrengot]

I'm playing around with the VideoLoader now. It seems like a really cool add-on, and i like how you added basic playback control. It makes a lot of sense those methods are there, without making it too complicated for a loader class. This is really becoming a great asset management tool!

 

I do have two feature requests though. Since there's a smoothing property in the vars object of the ImageLoader, wouldn't it make sense to add that along with deblocking to the vars object of the VideoLoader?

 

btw, I love how you just made the following this easy:

1 - loading a video, setting up NetStream, NetConnection etc. etc. etc.

2 - fitting it proportionally, centered in a container

3 - Handling complete and error events

var videoLoader:VideoLoader;
videoLoader = new VideoLoader("assets/video/website.f4v", { container:this, 
																			width:stage.stageWidth, 
																			height:stage.stageHeight,
																			scaleMode:"proportionalOutside",
																			onError:handleErrors,
																			onComplete:handleComplete} );
videoLoader.load();

[GreenSock]

Absolutely! A silly oversight on my part - smoothing is added in the most recent version (it's enabled by default). Good catch.

[Ahrengot]

Great! that was fast

 

How about deblocking? Also, there's an autoPlay property, i think it would make sense to add an autoLoop/loop property as well.

[GreenSock]

Wish(es) granted. Snag the latest version.

[Ahrengot]

You are awesome!

[Ahrengot]

Sorry i just thought about this now, but how about renaming the loop property in VideoLoader and MP3Loader to repeat and define it as an integer instead(where -1 = infinite repeat) - That way it would be consistent with the way loops are handled in TimelineMax and TweenMax.

[GreenSock]

Yeah, that was my first thought (use "repeat") but the down side is that it's inconsistent with the Sound object's "loop" property from Adobe's API. And using a certain number of repeats for VideoLoader adds a little more kb because of the additional logic required. I dunno - "loop" seemed slightly cleaner in this case but I do like "repeat" being consistent with TweenMax/TimelineMax.

 

Thoughts? Anyone else wanna chime in?