Embedded swf using external video (FLVPlayback) error #2035 / #2044

[Liathus]

I've been struggling quite a lot with this recently and I'm not even sure if it is possible at all.

I'm currently working on a project where I'm embedding a .swf inside another .swf.

The embedded .swf file however also uses the FLVPlayback component loading external videos, this is where the problem starts.

When publishing the .fla project I get the #2035 IOErrorEvent and when tracing the problem I get the #2044, this is to be expected though.

The embedded swf is still looking for the external videos but since the new ROOT is the swf it is embedded in, it won't find those videos.

I need to know if there is a way I can specify or link those external videos required by the embedded swf file's FLVPlayback component.

I really don't feel like redoing all the video content and embedding them in the timeline.

Thanks.

[sinious · Accepted solution]

The code in the inside SWF is going to fire off so those errors will continue to happen if you do not have the source for the SWFs to stop it.

If you do then you can simply access the loaded SWFs from the parent/stub SWF you have and control anything that has an instance name or on the display list with code, like the FLVPlayback components. You can then tell them the proper path.

Otherwise it'd take something like an apache mod rewrite to redirect the incorrect movie paths to the correct path.

[Liathus]

Thanks for the info.

I don't know why I didn't think about it earlier, I simply included the FLVcomponent and objects in the parent swf and it seems to work fine now. The child swfs are using the class objects as a path now.

I just don't fully understand how this is actually working. Aren't the embedded swfs looking for directory paths instead of a class objects, why are the embedded swfs using class objects as directory paths now?

Thanks for the help, much appreciated.

[sinious]

If I understand you correctly, you've embedded the FLVPlayback inside the parent and the children are instantiating it from the parent instead of their own copies, meaning the children also still contain FLVPlayback components? That would make the FLVPlayback operate from the SWF it originated in, or exactly where you wanted it to. The classes may simply collide and in reverse to CSS the class that was first declared will most be ignored by the runtime to avoid unnecessary collisions (the FLVPlayback embedded in the child SWFs).

A class is just a bunch of code that's given a name. The purpose of a package is to keep that name from colliding with other code with the same name. When the situation arises where the package and class name collide, something still needs to happen. In this case it can be that the runtime errors or simply doesn't accept the package+class that collides.

It's not the best workaround, I'm more of a fan of an apache mod-rewrite rule, but at the end of the day whatever meets the deadline works . Getting the source to the child SWFs if possible to remove the extra colliding code would be most optimal. And just as a concept, parents and children can reach into each other under the same application domain and use each others public facing properties and classes (like FLVPlayback).

[Liathus]

Ah I see. Thanks for explaining that.

In the future I'll look into using an apache mod rewrite, I've never attempted something like that.

I'm just glad the current workaround actually managed to fix the issue.

Thanks again.    

[sinious]

You're welcome and good luck!