Make your SWFs profilable with Scout

Scout logoI wanted to post a quick note about enabling your SWFs for Adobe Scout. There has been lots of discussions on Twitter and forums about that. Actually, this is something we have not really documented entirely and we will fix that very soon. Don't forget you can ask your questions on the Adobe Scout forum, we will be happy answering all your questions! Make sure you also check the Adobe Scout Vimeo channel, with video tutorials!

As you know, to get full profiling working with Scout, the SWF needs to be enabled for profiling. So to make it quick, today there are three ways to enable your SWFs with Scout.

The first way, is by using Flash Builder 4.7 and use the Telemetry option in the ActionScript compiler tab in your ActionScript project properties:

Telemetry UI

The second way to enable your SWF, which most of you probably don't know is to use the -advanced-telemetry compiler argument when using ASC 2.0. This is useful if you are using a tool like Flash Develop or any others for instance.

As a reminder, ASC 2.0 is the new compiler for ActionScript that is provided inside the AIR SDK bundled with Flash Builder 4.7 and the Gaming SDK. The UI above in Flash Builder actually just does that and appends this string to the arguments passed to the ASC compiler:


Finally, the third way to do it, is by using the post processing script. Which is useful in a scenario where you don't want to recompile the SWF, or cannot, because you don't have the sources anymore. Or if you are using Flex, because the -advanced-telemetry argument is only available in ASC 2.0 and not MXMLC. In this scenario, you just process the SWF and inject the specific tag required. We have a little Python script for that available here.

But this script requires Python and we have seen people having issues with this, so recently Renaun created this little app called Scout Enabler, which is all AS3 based, so no dependencies at all and has a nice GUI on top:

Scout Enabler

I hope this clarifies things. We will integrate that in the Getting Started document for Adobe Scout, so that it is clear to everyone and easy to find.

Comments (5)

  1. ben w wrote:

    Just out of curiosity, was there any reason not to build this into the tool itself?


    Friday, December 14, 2012 at 11:57 am #
  2. mizi_sk wrote:

    I know there was a discussion how to enable advanced telemetry (opt-out vs opt-in), but I just thought about it now… With this post-compilation enabling you can get telemetry for all swf files, even for those whose publishers didnt want that in the first place (didnt opt-in)

    All you need is some proxy server that can map remote address to local file which is advanced telemetry enabled.

    Or you can just make this opt-in script ran automatically for all swf files that passes through the proxy.

    Friday, December 14, 2012 at 3:29 pm #
  3. Thibault Imbert wrote:

    Hi Ben,

    We did not build this in the tool, cause it is really SWF related and we expect most people to use the compiler option, or automate this (by using the script). Having it inside the tool is a possibility too. Thanks for the feedback!


    Friday, December 14, 2012 at 8:42 pm #
  4. deryost wrote:

    Is there a way to add this with the ANT task. I’m compiling all my project with ANT and I would like to automate the process. Good job by the way.

    Monday, December 17, 2012 at 7:24 pm #
  5. Jason wrote:

    Just in case it helps anyone, I made a ruby version of the script to enable telemetry data in case anyone has Ruby installed and not the proper Python version installed.

    Monday, April 8, 2013 at 3:41 am #