sIFR 2.0.7: Fixed issue with CS4

posted December 1st, 2008, 21 comments

The sifr.fla file included in sIFR 2.0.7 could not be opened by CS4. This has now been resolved, thanks to Andrew Crowe who managed to open it in CS3 and re-save the file in a different format. Many thanks to Andrew, and also Nathan Strong, Todd O’Connor, Chris Peters and Lenny de Rooy for reporting the issue and testing a solution.

You can download the updated file from the sIFR 2.0.7 page.

(I would have done this myself, were it not for the fact that I’m still using Flash 8! Any help in getting CS4 would be much appreciated.)

21 responses

  1. I downloaded version 2.0.7 but the .fla still doesn’t open in Flash CS4. Is there any other place where can I download the updated .fla file?

    Thanks.

  2. Mark Wubben says:

    Gabriel, are you sure you got the latest version, and opened the sifr-cs4.fla file?

  3. Adam says:

    Hi the problem with “Unexpected file format” is still there with this release. I’m using Flash CS4 and Vista. I can’t edit the FLA..

  4. Adam says:

    Sorry, my bad. Opened the wrong file. It does work now :)

    Thanks for the fix!

  5. quack says:

    On the latest dev build of Google Chrome (2.0.156.1) transparency doesn’t appear to work.

  6. Mark Wubben says:

    Just tried with sIFR 3, build 2.0.157.0 and Flash 10 and it worked for me. Could you verify? Perhaps you have a link to the page that doesn’t work?

  7. Steven Douglas says:

    The fix worked for me as well (THANK YOU), but that doesn’t answer why this even happened in the first place. Isn’t Flash CS4 the big granddaddy, current latest and greatest? And it can’t open a file created in a LOWER version of itself?

    This isn’t the only file that gives me that same error from CS4. It happens to me frequently with other FLA files, and Adobe is very short on answers.

    Does anyone know what’s up with this?

  8. Steve says:

    We’ve been having trouble implementing sIFR 3. I have downloaded the file, opened it, made the necessary font changes, exported the movie file with all the correct settings, etc. I don’t think I’m doing anything wrong in the process.

    I’ve read that there were compatibility issues using different versions of Flash. I’m using CS4. I know there is an updated file for CS4 and sIFR 2.0.7 but we’ve implemented sIFR 3.

    Does anyone have any suggestions of what we can try? Thanks.

  9. Suleman says:

    Adobe has always been good with backwards compatibility but it does seem there are times when CS4 has some issues opening .fla’s created in previous versions of Flash. I’ve had problems opening a few files in CS4 too but as of yet have not been able to pinpoint the cause.

  10. I seem to have all sorts of problems with Flash Player 10 and ActionScript errors. I have a flash video and SIFR on my page, but that’s the only flash. Is this SIFR, or is it most likely my video player that’s causing errors?.

  11. mike says:

    Use SIFR 2 if you can. SIFR 3 is experimental.

  12. Mark Wubben says:

    Florida, hard to say. Perhaps you could ask at Stack Overflow?

    Mike, experimental or not, sIFR 3 is tons better than v2.

  13. Mok Seng Chai says:

    sIFR is new to me. Let alone sIFR needs the bulky Flash just to obtain the fonts, look at this code segment:

    if (typeof sIFR == “function”) {

    sIFR.replaceElement(named({sSelector:”body h1”, sFlashSrc:”./sifr/super_font.swf”}));

    };

    Why are there { } in the parameters list?

    sSelector:”body h1”, Why is there : not = ? Assuming it follows CSS, then why it ends with , not ; ?

    Why is there ; at the end of the code segment?

    Is such syntax JS or sIFR-specific? It violates every law in Pascal, C/C++, Java, PHP…. Such syntax kept on messing up the Open Source world.

    sIFR is a stupid idea. It should go to hell.

  14. Mark Wubben says:

    This is JavaScript syntax, basically passing an object literal to the function. Syntax is exactly the same as Python’s syntax for dictionaries, and the best solution for keyword arguments, which JavaScript does not support.

    And yea, it’s too bad sIFR is still necessary, but unfortunately the browser vendors and type foundries can’t figure out better solutions.

  15. Mok Seng Chai says:

    Thanks, Mark Wubben.

    I wrote Comment 13 in a fit of anger, out of my love of Open Source. All of us are for code quality. My apologies if Comment 13 does offend anyone.

    I made this comment several times: “Open Source is a mess put together by everyone.” I am happy to see someone actually attending.

    Open Source is not profitable. It needs spirit to keep going. We support it.

  16. Justin Byrom says:

    I too tried to open sifr.fla in FlashPro CS4 and no avail :(

    Looks like I bombed at the first hurdle.

    unsupported file format …

  17. Mark Wubben says:

    Justin, please make sure you’re using the version downloaded from this page.

  18. bas says:

    dear Marc,

    Im using sifr but im not able to get background transparant. im using version 2.0.7 but im not succesfully to get my parameters to set wright. do you have a working exmaple with the wmode wright?

    the code im using:

    //

    //

    WHERE DO IS SET THE PARAMETER WMODE.

    can you help me out.

    thank you, Sebastiaan

  19. Mark Wubben says:

    Sebastiaan, please do consult the documentation. It specifies the correct argument name – sWmode for sIFR 2 – and the argument order.

  20. Still not opening in CS4. This seems like a rather large issue to me.

  21. Mark Wubben says:

    Merrick, which file are you opening?