Runtime Shared Library

Hi,
I was trying to test a flash movie that I made, and an error popped up.
It said, "Your content will not stream. Runtime Shared Library preloading will require all of your content to download before the first frame can play."
It also says, "The Runtime Shared Libraries being preloaded are: textLayout_1.0.0.595.swz for TLF Text". After I click "ok", the movie runs, but I had created a mask effect for some text, but that text never appeared in the movie, as it was supposed to. How can I fix this?

Can u share the fla if possible

Similar Messages

How Do I Fix This Runtime Shared Library Preloading Error?

Hello,
I just finished up my site, and this is the only thing holding me back from publishing it. Whenever I "Test" my site, I get this error: " Your content will not stream. Runtime Shared Library (RSL) preloading will require all of your content to download before the first frame will play.
To prevent this you can change the Runtime Shared Library Library Settings, in the Advanced ActionScript 3.0 Settings dialog which can be raised from the Publish Settings dialog.
The Runtime Shared Libraries being preloaded are:
textlayout_1.0.0.595.swz for TLF Text"
Does anyone know how to correct this error? If you do, could you please walk me through it step-by-step. I am still very new to "Flash Professional (CS5)" & "ActionScript (3.0)"

Reference error is because the default linkage for textLayout.swc is Runtime Shared Library (RSL) with preload swf option so the reference will always be “RSLPreloader” if TLF is used.
There are 2 options that we can avoid the reference error:
1. Change default linkage to “Merged to code” which will add around 150KB to child swf file size.
2. Change preloader method to “Custom preloader loop”, move all contents and scripts to frame 2. And finally, in the Advance ActionScript 3.0 Settings, export classes in frame to 2.

Flash CS5: Runtime Shared Library

Hi,
I'm having a problem publishing my flash files. Everything was fine up until a few days ago and now all of a sudden I get an error message when I try to publish telling me that the file won't publish due to a RSL error. It advises me to alter my publish settings as follows:
Publish settings
Advanced AS3 settings
Runtime Shared Library settings
error: text_layout_1.0.0.595.swz for TLF text
I'm told that the swf will not run without a preloader. There are two options available: custom preloader and merge into code. I am inserting the animations into a captivate project. If I choose custom preloader the animations won't run in Cp. When I try to insert them Cp only recognises them as being 2 frames long. If I choose the merge into code option it makes my captivate project go completely haywire.
Any suggestions? Ideas? I'm pretty much just learning how to use authoring tools and have a deadline looming for this project in a few weeks.
Thanks for any and all help!
Maedhbh

a) do you absolutely need TLF text?
Merging the SWZ into code makes sense for your needs, what exactly happens in captivate with it?
Remember that Captivate 4 has been released before CS5, so I would say that there might be a few errors or workarounds when mixing these two.
You might want to check over on the captivate forums, if anyone there experienced similar.

Runtime Shared Library Preloading Warning

Hi there, I just finished a project and added a preloader to it (in Flash CS5 AS3) and I get this error:
Your content will not stream. Runtime Shared Library (RSL) preloading will requiere of your content to download before the first frame will play.
To prevent this you can change the Runtime Shared Library Library Settings in the...
The Runtime Shared Libraries being preloaded are:
textLayout_1.0.0.595.swz for TLF Text.
I am using this preloader on a different project and I dont get this error.

I have the exact same question.

URGENT: RSL Stopped Working - Need to compile with Runtime Shared Library

I need this target to compile using the “Use Runtime Shared Library” option such that Flex libraries will be not included IN the swf, however I cannot get it to work. No matter what, mxmlc includes them. Oddly it DID work briefly for short time, however suddenly stopped again and unfortunately going through subversion revision history yields no insight whatsoever to what evoked this breakage.
<target name="compile" depends="replace_build_version">
            <exec executable="${FLEX_HOME}/bin/mxmlc.exe" dir="${basedir}">
                  <arg value="${basedir}/src/Main.mxml"/>
                  <arg value="-output=${basedir}/bin-release/Main.swf"/>
                  <arg value="-static-rsls=false"/>
                  <arg value="-debug=false"/>
                  <arg value="-include-libraries=${basedir}/libs"/>
                  <arg value="-source-path=${basedir}/src"/>
                  <arg value="-creator=me"/>
                  <arg value="-source-path=${basedir}/locale/en_US"/>
                  <arg value="-source-path=${basedir}/locale/ru_RU"/>
                  <arg value="-locale=en_US" />
                  <arg value="-include-resource-bundles=en_US,ru_RU"/>
                  <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/framework.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/framework_4.1.0.16076.swz,http://fpdo wnload.adobe.com/pub/swz/crossdomain.xml"/>
                  <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/textLayout.swc,http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz,http://fpdownlo ad.adobe.com/pub/swz/crossdomain.xml"/>
                  <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/osmf.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/osmf_flex.4.0.0.13495.swz,http://fpdo wnload.adobe.com/pub/swz/crossdomain.xml"/>
                  <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/spark.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/spark_4.1.0.16076.swz,http://fpdownlo ad.adobe.com/pub/swz/crossdomain.xml"/>
                  <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/sparkskins.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/sparkskins_4.1.0.16076.swz,http://fpd ownload.adobe.com/pub/swz/crossdomain.xml"/>
                  <arg value="-external-library-path=${FLEX_HOME}/frameworks/libs/flex.swc"/>
                  <arg value="-theme=${FLEX_HOME}/frameworks/projects/spark/MXFTEText.css"/>
                  <arg value="-theme=${FLEX_HOME}/frameworks/themes/Spark/spark.css"/>
                  <arg value="-verbose-stacktraces"/>
            </exec>
      </target>

I really hate to do this, but I very much need someone from Adobe to chime in here. It is causing some serious headaches. Ant nor the straight Flash Builder 4 will build with RSLs properly enabled now and this is really a very urgent situation for me. It has doubled file size and made the application absolutely unbearable for users.
Thanks!

Error Message: Your content will not stream. Runtime Shared Library preloader will require...

Please help. I am receiving an error message and I don't know what I need to do to fix my file. I'm working in Flash CS5.5. I've created an animated web banner. When I go to test movie, I receive the following error message:
Your content will not stream. Runtime Shared Library (RLS) preloader will require all of your content to download before the first frame will play.
To prevent this you can change the Runtime Shared Library Library Settings in the Advanced ActionScript 3.0 Settings dialog which can be raised from the Publish Settings dialog.
The Runtime Shared Libraries being preloaded are:
textLayout_2.0.0.232.swz for TLF Text
I don't know what any of this means or what I need to do to ensure that my web banner will load correctly once it's uploaded to a website. Please help. I'm fairly new to Flash. Thank you in advance for any advice you can provide.

Mr Benrud,
This window means you've used TLF Text Format and before all of your content download, it requires to be proloaded. To get rid of this message, just remove TLF Text Format (if you really don't require it) or else goto Publish Settings -> Flash -> Actionscript Settings and just remove it.

Runtime shared library in Flash CS5

I'm trying to use OSMF as a runtime shared library in Flash CS5, but Flash keeps on crashing all the time I'm trying to change that swc from Merged into code to runtime shared library. Whatever URL / policy file Im using, Flash always crashes at compilation, and then after that there's no way to reopen the FLA without Flash crashing. Very annoying. I'm glad it's just a test project and not production files... Anyone already experienced the same kind of bug?
UPDATE: just tested it on Win XP SP2, same behavior, same nasty result

Funny, I have the same problem with a shared library (documentation on this site makes no sense to me, that is). And the Adobe Help desk refers me to this forum!
What I know is that an item in a shared library cannot have names with spaces, so should be like "btn-up" and not "btn up".
Further you should while activating the item in Libraries look for "Properties" (on the right hand side of the pull down of the Library) and define them as "Export for sharing" (my version is in Dutch and for Mac so these labels are named differently and in a different place).
Then in the movie you want to use them in, you open import (under file) and open the .fla of your first document as external library.
In the beginning it is as easy as that, but then creating a library in movies that are in use for an extended period of time (using spaces in their names, etc.) is a whole new ball game.
Lucie

[ERROR] - Runtime Shared Library Preloading Warning

Hey there guys, I have a question that probably has a very easy answer, but after searching online for a while I couldn't figure out just how to fix it.
Anyways the problem is this, when I run it, it gives me this warning and then the when i click "OK" it startes playing the movie..but when i upload the content i dont see it woking
I assume I'm receiving this warning because I'm using Adobe Flash Professional CS5 if this helps.
Thanks very much for any advice you guys have.
-=-=-=-=-=-=-=-
The warning:
Runtime Shared Library Preloading Warning
Your content will not stream. Runtime Shared Library (RSL) preloading will require all of your content to download before the first frame will play.
To prevent this you can chane the Runtime Shared Library Library Settings in the Advanced ActionScript 3.0 Settings dialog which can be raised from the Publish Settings dialog.
The Runtime Shared Libraries being preloaded are:
textLayout_1.0.0.595.swz for TLF Text

Since my presentation requires hiding a text field behind "revealer bars", unlayering was not going to make it in my situation. By some kind of good fortune I had another FLA file that behaved properly. I found that it had the "Merge with code" switch set, but making that change to my current file did not correct the problem. It appears that the flash data base became corrupted and I had to re-build the entire file from scratch.
Here is something that hints ( but doesn't admit ) that you can corrupt the fla file:
Home / Using Flash Professional CS5 / Text
Working with Text Layout Framework (TLF) text
Converting between Classic and TLF text
When you convert a text object from one text engine to the other, Flash preserves most of the formatting. However, because the text engines are different in their capabilities, some formatting may be slightly different, including letter spacing and line spacing. Inspect the text carefully and reapply any settings that have been changed or lost.
If you need to convert text from Classic to TLF, try to do so only once rather than converting back and forth more than once. The same is true for converting TLF text to Classic text.
When converting between TLF and Classic text, Flash converts text types as follows:
TLF Read Only> Classic Static
TLF Selectable > Classic Static
TLF Editable > Classic Input
Until I become very certain that I am on the right path, I am saving a new sub-version of the file after every small advance in the restoration. If something I go breaks the "streamability", I Quit without saving then start up again with the last successfully saved version. ( I haven't yet found the "Revert to Last Saved State" menu pick. )
Hope this helps.

CS3 Runtime shared library linkage

I'm new to runtime shared libraries, so figured someone will
see what obvious thing I'm doing wrong.
Given:
1. Created a Assets.swf with one exported MovieClip symbol
with a linkage name called "Symbol1". "Export for actionScript",
"Export for runtime sharing", and "Export in first frame" are all
checked. URL: "Assets.swf"
2. Created a Movie.swf that imports "Symbol1" from
Assets.swf (using the Open External Library dialog).
3. Attached a Document class to Movie.swf that contains the
attached Movie.as code below.
Result: Two compiler errors:
Movie.as,Line 9 1046: Type was not found or was not a
compile-time contant: Symbol1
Movie.as,Line 9 1180: Call to a possibly undefined method
Symbol1.
Movie.as code:

I wonder why Adobe even enables the "export for runtime
sharing" checkbox if it doesn't do anything for AS3? This
definately lead me down the wrong rabbit hole trying to get that
approach to work.
Anyway, I made the suggested code changes to Movie.as
(attached). Unchecked the "export for runtime sharing" box on
Symbol1 in Assets.fla. Removed the Symbol1 import from Movie.fla.
And, sure enough, the Symbol1 import now works. Thanks, kglad.
So in summary, the two points that I missed were:
Every exported symbol must have as
associated class definition in a corresponding .as file. so that
symbol can in imported using the AS3 "import" directive.
Ignore the "Export for runtime
sharing" mechanism entirely and use the Loader class
instead.

How do you change the "Runtime Shared Library"?

Hello Everyone,
I recently began using CS5 with AS3.0 and I encountered this error -
I can not find where I can edit the AS3.0 settings nor do I know what to change. Can someone please help me with this?
Thanks for your time and assistance,
Todd

click file/publish settings/flash/actionscript 3.0 settings/library path/default linkage: merged into code.

Runtime shared library? maybe getting too tricky?

Hi team,
I am still owrking on my project and was trying to be tricky by using TLFtextfield for a roll over to vertically centre the text, but now that I am using that class I am getting this message when I publish
So now because this project os goign to be on CD-rom and may be going out to people who have very limited computer knowldge and probably no access to the internet, should I not use this class, is this going to require a new version of Flash Player than these people psoobily have? Should I just stick to dynamic text box and not worry about the text being vertically centered? Any advice would be greatly appreciated,
Cheers
Sub

If you are worried about your users not having a new enough version of Flash, which can be a legitimate concern, then you should target your publishing for as far back as is feasible for your design needs. Using dynamic textfields remain the better bet. There are other ways to vertically center things if it is important to your design.

Content will not stream - Runtime Shared Library Settings

Hello Everyone,
I recently began using CS5 with AS3.0 and I encountered this error -
I can not find where I can edit the AS3.0 settings nor do I know what to change. Can someone please help me with this?
Thanks for your time and assistance,
Todd

Mr Benrud,
This window means you've used TLF Text Format and before all of your content download, it requires to be proloaded. To get rid of this message, just remove TLF Text Format (if you really don't require it) or else goto Publish Settings -> Flash -> Actionscript Settings and just remove it.

How can I use a shared library made with the application builder?

Hi,
I am using LabVIEW 7.1 running on Slackware 10.1 (kernel 2.4.29) and I am trying to call a graph display from a C program that I use for debugging VME access from a VMIVME controler. So using the application builder I built the VI as a shared library (graph.vi -> graph.so) containing a function called "graph". In my main program the call to the dlopen fails with the error: "graph.so: undefined symbol: UninitLVClient". When I examin graph.so with nm I see that UninitLVClient and other LabVIEW functions are indeed undefined and using ldd shows that graph.so has dependencies only on libc.so.* and *linux*.so.* but not on LabVIEW related stuff. Those functions are defined in the liblv.so that's in the cintools directory but I have no idea if the user is supposed to use that.
So I think I am missing an important concept here. Can somebody help or direct me to some documentation (I found lots of information about how to link external code to LabVIEW but nothing about how to link LabVIEW code to an external program)?

Thanks Watermann,
your message has been very useful so now I am linking to the proper library but I still have problems when trying to load dynamically the shared library produced with LabVIEW. It is strange that I could successfully load the lvrt library at loading time but it does not work when I am loading the library at execution time.
I made a small LabVIEW program that prints a hello window and I am calling it from a C program. In the first program main.c I am linking to the lvrt library at loading time and it works but in the second one I am linking dynamically at execution time and it does not work. For my work I need to be able to load code done in LabVIEW at execution time. Any help is appreciated!
Program main.c:
// small program to call a LabVIEW shared library
#include
#include
#include "hello.h" // got this from the LabVIEW builder, i.e. when I made the hello.so
int main(void)
printf("Hello from C!\nLets call LabVIEW now\n");
hello();
printf("Bye ... \n");
return 0;
The command to compile main.c, i.e. linking shared library lvrt when loading main program:
gcc -Wall -I /usr/local/lv71/cintools/ -o main main.c hello.so -l lvrt
The LD_LIBRARY_PATH has been defined and exported:
$ LD_LIBRARY_PATH=$PWD
$ export LD_LIBRARY_PATH
IT WORKS!
Program main2.c:
// small program to call a LabVIEW shared library
#include
#include
#include
int main(void)
void * h_lvrt;
void * h_hello;
void (* hello)(void);
char * error;
printf("Hello from C!\nLets call LabVIEW now\n");
// open LabVIEW RunTime shared library
// in my computer located at /usr/local/lib/liblvrt.so
h_lvrt = dlopen("/usr/local/lib/liblvrt.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
printf("error : could not open LabVIEW RunTime library\n");
printf("%s\n", error);
return 1;
// open hello shared library
// in my computer located at /home/darss/lv_call/hello.so
h_hello = dlopen("hello.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not open hello library\n");
printf("%s\n", error);
return 1;
// get function hello from library hello.so
hello = dlsym(h_hello, "hello");
// check for error
error = dlerror();
if (error) {
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not get the hello function\n");
printf("%s\n", error);
return 1;
// call hello function
hello();
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("Bye ... \n");
return 0;
The command to compile main2.c, i.e. dynamically linking library lvrt at execution of main2 program:
gcc -Wall -o main2 main2.c -l dl
The LD_LIBRARY_PATH still defined and exported.
IT DOES NOT WORK!
Program output:
Hello from C!
Lets call LabVIEW now
error : could not open hello library
/home/darss/lv_call/hello.so: undefined symbol: WaitLVDLLReady

CS5.5 Import for runtime sharing and preview problem

Hello
I'm having a strange issue with CS5.5 and the import for runtime sharing settings. Here's what I'm doing: I create two .fla's, Export.fla and Import.fla. In Export.fla, I create a shape, select it, press F8 and tick export for runtime sharing, to create a really simple exported movie clip. I click the exported symbol in the library, press Ctrl-C, switch to Import.fla and press Ctrl-V. Everything ok so far, the symbol is imported for runtime sharing.
The first problem I have at this stage is that changes I do to the exported symbol in Export.fla are not reflected in Import.fla, only in the final .swf's I can see the changes. Also, unlike in CS4 and CS5 I cannot "Update" the imported symbol in the library right-click menu, to make changes to Export.fla visible in Import.fla. The menu entry is just greyed out...
So I tried to use Authortime sharing, in the Symbol Properties for the imported symbol in Import.fla. I link the source to the symbol in Export.fla, and once I do that, everything is completely borked. The previously imported symbol is no longer imported. Whenever it is changed in Export.fla, it gets an "Export for Runtime Sharing" tick in its Properties in Import.fla, and worst, it is not shared at runtime, like I need it to.
Can anyone tell me how to get the "normal" CS/4/5 behaviour in CS5.5: a runtime shared symbol, that can be updated in Import.fla (I dont care if manually or auotmatically) when I change it in Export.fla, and which also is runtime shared?
Cheers
Ulf

Hi, JonnyDiamond
Thank you for reporting the issue for runtime sharing settings affected by authortime sharing. It is fixed for parent symbols in Flash Pro CS6, but we just recognized it is not for nested items.
As an alternative to deleting and re-copying the symbol, we see the following steps restore the original settings of the nested bitmap symbol (png in your case) for importing runtime shared library. After you open Bitmap Properties dialog of the bitmap symbol, go to ActionScript section and:
1. Uncheck Export for ActionScript
2. Check Import for runtime sharing
3. Input the path to Library.swf in URL
4. Click OK twice
Please try these steps to see if they work for you. If they do, the simalr steps can be processed via JSFL script. It would be something like this:
//// To restore the settings to import runtime shared library //////
// Get Library items
var myItems = fl.getDocumentDOM().library.items;
// Store an item from myItems
var myItem;
// Path to runtime shared library. Change this to your path
var pathToRSL = "Library.swf";
// Go through Library
for (var i = 0; i < myItems.length; i++)
          myItem = myItems[i];
// Change the condition to suit to your Library
          if(myItem.itemType == "bitmap" &&
             myItem.name.split(".").pop() == "png" &&
             myItem.linkageExportForRS == true )
    switchRSSettings(pathToRSL);
// Disable Export for runtime sharing and
// enable Import for runtime sharing
function switchRSSettings(path)
          myItem.linkageExportForRS = false;
          myItem.linkageExportInFirstFrame = false;
          myItem.linkageExportForAS = false;
          myItem.linkageImportForRS = true;
          myItem.linkageURL = path;
///////////////////////// End of Script ////////////////////
We hope this would help you workaround the issue. Again, thank you for your report!
Thanks
Toshi

XFL-Based Author-Time Shared Library Workflow

I'm creating a large project with many different FLAs using symbols pulled from a shared library FLA at author time. It works great, however, the workflow could be simplified (possibly) if the shared library were saved in XFL format.
I saved a copy of the shared library FLA as XFL. Then, I tried to import a symbol to another FLA from the XFL as author-time symbol references. Flash recognized the XFL document as an accepted source, but did not offer a menu giving a selection of symbols.
Has anyone tried this at all? Any luck? Is it a bug in CS5?

Im having the same issue. With an FLA, hitting the browse button brings up the symbol browser. With an XFL, the symbol browser does not come up. Nothing happens.
Also, if you copy/paste from an FLA library, it will maintain the "Source" reference and have the option to Update the symbol. If you copy/paste from an XFL, it loses its reference and the ability to update. It looks like a bug with CS5...
However,
If you use runtime shared libraries it works. This is probably the better approach anyways, since you only need to change and recompile a single shared asset.
Watch out though, i've found a bug with CS5 and RSL...using the new TLF text fields will cause shared library swf files to fail to load! So stay away from TLF in shared libraries.
So for you, just take the symbols that you want to link from one XFL to another, and split them into their own shared assets XFL. Now go to the symbol properties, and export as runtime shared library. Enter the swf name as the URL. Comp
Now copy/paste the symbol into the second XFL or use the Import / Open External Library.

Runtime Shared Library

Similar Messages

Maybe you are looking for