Hi Jessie,

I've removed the transition code that was corrupted by the last edit you mentioned, and the project now opens fine. I'll send a copy to you via email or ftp.

Eric

Hi Christian,

My apologies for the late reply. The best way to do this is to import the file into Flash Builder 4.5. Once imported, Builder will automatically generate a list issues in its Problems panel. If you hit a similar snag as the other user in this post, look for a corrupted Transitions tag (e.g. missing code and improper closure of the tag in MXML). In this case deleting the damaged transitions code will result in a need to rebuild transitions in Catalyst, but the rest of the project will be intact. Once done, export the project from Builder to a new FXP.

Re-opening the project in Catalyst requires use of Catalyst CS 5.5, as the earlier version won't open Builder-edited projects. If you don't have Catalyst CS 5.5 and you'd rather not deal with editing in Builder, let me know. It's possible to manually edit files inside an FXP (which is similar to a ZIP archive). I can take a look at the project's content this way and send you an updated FXP that will still open in Catalyst CS5.

Eric

Hi Shane,

Sure, I'd be happy to check out the project file. If you'd like, send me an message with the location of the file off-thread, via the forum's email service. Attachments here are limited to 5MB.

Thanks,

Eric

Hi Shane,

I researched this a bit and discovered the limitation to the simple solution of using a SWFLoader tag in FlashBuilder: you will not be able to re-open the project in Catalyst CS 5.5 once such a tag exists in the project.

If re-opening the project in Catalyst isn't a concern (e.g. adding the video is the very last thing you'll want to do), then I'd suggest these steps:

1. In Catalyst, drag/drop a Video placeholder from the Common Library panel onto the artboard, so you know where you'll know where to revise code in Flash Builder.

2. Save out the FXP

3. In Builder, choose File>Import Flash Builder Project to import your FXP from Catalyst

4. Find the placeholder video code, which will be:

<s:VideoDisplay x="276" y="85" autoPlay="false" scaleMode="stretch"
                        source="assets/media/fpo_video.flv"/>

5. Replace the instance of VideoDisplay with an instance of SWFLoader:

<s:SWFLoader x="200" y="200" source="http://www.youtube.com/v/hPUGNCIozp0?version=3"/>

Note the above example points to a video on YouTube who's video ID is hPUGNCIozp0

When you initially copy the URL from YouTube that points to you'll end  up with one like this:

http://www.youtube.com/watch?v=hPUGNCIozp0

Per Google's suggested embedded Player parameters (see: http://code.google.com/apis/youtube/player_parameters.html), the URL must be modified to call out the version of ActionScript in use; ActionScript 3. So you end up adding: /v/VIDEO_ID?version=3, where VIDEO_ID is the ID of your particular video. See the completed SWFLoader example URL above.

To preview the project in Builder, right-click its folder in the Package Explorer and choose Run As>Web Application

Hope this helps. I know it isn't ideal, but it's the most straightforward way of solving the problem if the video needs to be accessed straight from YouTube.

Eric

Hi Shane,

No problem, glad to help. Yes, simpler integration in the future for a common use case like this one would be good (fingers crossed).

Eric