Skip navigation
hometown rival
Currently Being Moderated

Cue Point Rounding Issue

Sep 16, 2013 7:45 AM

Tags: #cue_point

Greetings all,

 

I recently upgraded from CS5 to CC, and I'm have a devil of a time with cue points. With the videos I produce, I set various cue points that are used as chapter markers. On the video's player I include simple buttons that, when clicked, advance to the corresponding cue point. Pretty straight forward. I should also note that I convert and set the video's cue points using Media Encoder.

 

So, when I went through my same routine using Media Encoder CC and Flash Professional CC I came across an issue in which the cue points were not in line with the timecodes I set up. A typical cue point would be along the lines of 13:13;17, but it appears that when Flash is rounding the time code up to the nearest second (13:13;17 would be listed as 13:14;00 in Flash). So, then I tried setting up cue points on exact seconds thinking it would correct the issue, but it hasn't. If I set the cue point at 13:13;00, it rounds up to 13:14;00 more often than not.

 

Has anyone else encountered this issue, and if so, knows how it can be corrected? Thank you

 
Replies
  • Currently Being Moderated
    Sep 16, 2013 8:04 AM   in reply to hometown rival

    Knowing you can't seek to anything but a keyframe in progressive playback it seems like the encoder may not be properly setting a keyframe on a cue point (it's supposed to).

     

    When you receive the metadata have you run a loop on the received cue points and trace()d them out to see if they're correct?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 17, 2013 12:19 PM   in reply to hometown rival

    I'm wondering if the cue point time rounding is some byproduct of cuepoints creating a keyframe. You can't seek to a point in a video unless it has a keyframe embedded at that exact time. Otherwise it seeks to the nearest keyframe.

     

    When making cuepoints using Adobe Media Encoder, it should be setting a keyframe at every cue point you enter. I've had Adobe Media Encoder fail to set the cuepoint exactly where I set it before. It doesn't happen when I encode using Sorenson Squeeze, or programmatically set the AS cuepoints though.

     

    Is programmatically setting the AS cuepoints a possibility for you?

     

    On the second part I mentioned, NetStream needs the client property set so it knows where to look for the public functions it expects to find. One of those functions is "onMetaData". When that function is fired you're given information about the video. One part of that data is all the cuepoints the video contains. You can loop through them, printing out their name and exact time they're set to. You should see what your cuepoints are set to.

     

    e.g.

     

    function onMetaData(infoObject:Object):void

    {

         // trace cue point name:time values

         var key:String;

         for (key in infoObject.cuePoints)

         {

              trace(infoObject.cuePoints[key]['name'] + ' = ' + infoObject.cuePoints[key]['time']);

         }

    }

     

    It should trace something like this:

     

    cuePointName1 = 0.142

    someOtherCuePoint = 25.17

    etcCuePoint = 38.259

    Check to see what the cuepoints times actually are in code.

     

    Here's more info on the subject:

    http://help.adobe.com/en_US/ActionScript/3.0_ProgrammingAS3/WSD30FA424 -950E-43ba-96C8-99B926943FE7.html

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points