Is this working in an update of the software yet? I downloaded the latest release and noticed it's still not working for me. Any news on this?

Hi there,

any news when this bug will be fixed? I have the same problem and can't switch back to CS 5.5, because the serial was used to update to CS6. This is really unfortunate, because I am working on a tight schedule project where there's only few ammendments to be made. The only solution would be to install CS 5.5 as trial which leaves out vital additional features.

I have this CS6 bug too, I can't believe it!

Adobe please fix

Really unbelievable. It still isn't working.

Ok, after several hours experimenting, I have found out that the cue points are completely messed up in CS6, also in Flash and the Media Encoder. Here is the problem (besides the known AE issue):

- Take any video in the Media Encoder, set it to FLV, open the export settings.

- Add somewhere a navigation and an event cuepoint and render.

- Open flash, create a new AS3 scene and import the rendered video.

- If you look at the properties, everything seems fine: It has a navigation and an event cuepoint.

- Add an actionscript tracing all metadata.cuePoints.type and test the movie.

- Result: It traces every cuepoint as event cuepoint. Therefore all tries to use commands for seeking to navigation cuepoints result in invalid seek errors.

Please, could somebody at Adobe fix this?

Oh yes, I agree. Especially considering that it already has been working just fine for years...

At least for the people who are as desperate as me I have found a tedious work-around:

I have written an AE-script that exports all markers as a Flash cue point XML (see below, it sure is not perfect and parameters are not considered, but it works). This XML-file can be used in Media Encoder to encode the AE composition with cue points.

Use the RichFLV App (http://richapps.de/?p=66) to change these cue points to navigation which should be of that type.

Here is the code, you need to check in the preferences that scripts are allowed to write files:

var comp = app.project.activeItem;

var XMLStart = "<?xml version='1.0' encoding='UTF-8' ?><FLVCoreCuePoints>";

var XMLEnd = "</FLVCoreCuePoints>";

var XMLTemp = "";

var XMLFinal = "";

var layerCount = comp.numLayers;

var layer = new Object;

var layerMarkers = new Object;

var markerCount = 0;

var curMarkerTime = 0;

var curMarkerName = "";

var curMarkerType = "";

var curMarkerXML = "";

//Layer markers

for(i=1; i<layerCount+1; i++) {

    layer = comp.layer(i);

    layerMarkers = layer.marker;

    markerCount = layerMarkers.numKeys;

    for(j=1; j<markerCount+1; j++) {

        curMarkerTime = layerMarkers.keyTime(j) * 1000;

        curMarkerName = layerMarkers.keyValue(j).cuePointName;

        if(layerMarkers.keyValue(j).eventCuePoint) {

            curMarkerType = "event";

        } else {

            curMarkerType = "navigation";

        }

        curMarkerXML = "<CuePoint><Time>" + curMarkerTime + "</Time><Type>" + curMarkerType + "</Type><Name>" + curMarkerName + "</Name></CuePoint>";

        XMLTemp += curMarkerXML;

    }

}

//Comp markers

var tempText = comp.layers.addText("");

var tempSrc = tempText.text.sourceText;

tempSrc.expression = "thisComp.marker.numKeys";

markerCount = Number(tempSrc.value);

if(markerCount > 0) {

    for (i=1; i<=markerCount; i++) {

        tempSrc.expression = "thisComp.marker.key(" + i + ").time;";

        curMarkerTime = Number(tempSrc.value) * 1000;

        tempSrc.expression = "thisComp.marker.key(" + i + ").cuePointName;";

        curMarkerName = String(tempSrc.value);

        tempSrc.expression = "thisComp.marker.key(" + i + ").eventCuePoint;";

        if(tempSrc.value == "true") {

            curMarkerType = "event";

        } else {

            curMarkerType = "navigation";

        }

        curMarkerXML = "<CuePoint><Time>" + curMarkerTime + "</Time><Type>" + curMarkerType + "</Type><Name>" + curMarkerName + "</Name></CuePoint>";

        XMLTemp += curMarkerXML;

    }

}

tempText.remove();

//create output string

XMLFinal = XMLStart + XMLTemp + XMLEnd;

//Write file

var cueFile = File.saveDialog("Save the XML file", "XML:*.xml" );

cueFile.open("W");

cueFile.write(XMLFinal);

cueFile.close();

Ran into this bug just today. Never thought that I would use flvtool2 again:

* https://gist.github.com/4088555

flvtool2 is a command line tool to manipulate flv files. The source in the gist is actually a small Ruby script which takes all *.flv files in a folder and injects the cue points defined in the xml file. Afterwards all files are zipped into an archive. I used this script to inject cue points into multiple videos after rendering them in After Effects. I needed the videos to contain cue points because they were used to trigger some actions in an ad campaign (Adobe Flash).

(1) Define your cue points and save them to an xml file, eg. cuepoints.xml

<tags>

  <metatag event="onCuePoint" overwrite="true">

    <name>myFirstCuePoint</name>

    <timestamp>3015</timestamp>

    <type>event</type>

  </metatag>

  <metatag event="onCuePoint" overwrite="true">

    <name>mySecondCuePoint</name>

    <timestamp>4018</timestamp>

    <type>event</type>

  </metatag>   

</tags>

(2) Fire up a command line and run flvtool2

flvtool2 -APUt cuepoints.xml input_file.flv output_file.flv

The output_file.flv should now contain two cue points. The first one named "myFirstCuePoint" at roughly 3 seconds and another one ("mySecondCuePoint") at 4 seconds in the video. This only works for the flv container! I am working with Ubuntu. But there should be some Windows binaries for flvtool2 as well.

Adobe, please fix this…

Hi Guys

I have made a little guide explaining the workaround:  http://kim.thoeisen.dk/ae-cs6-flv-cue-point-export/

Thanks a lot for the info and helping posts! I just hope Adobe will fix the bug soon!

Regards Kim

Well, I believe it when I see it, talk is cheap. To me the bug remains unfixed until an update is actually released. It is nice to hear that something happened behind the curtains - but this unfortunately does not change a thing so far for all the users who are already waiting for a very long time to get this fixed. So please, put it out there, the sooner the better!

Excuse me, I am a little late: Happy birthday, dear cue point bug! May you live long and stay just the way you are... NOT! Still no update, still no bugfix. I still need it. I still waste time working around it. And I am sure I am not alone. That it is even a question, whether the fix for a one-year-old bug gets released or not, tells a lot about how much Adobe cares about customers. Why did you wait with fixing it until the new version arrives in the first place?

Anyway, I guess that you, Mr. Kopriva, are only the messenger. Since you cannot make the release decision, could you please tell me, who is in charge of this and how I can contact this person?

Thanks,

Bob