I really appreciated this!

I’ll check this afternoon, if I get the chance. The way I wrote SoundSync (if I remember it right!) subsequent cues shouldn’t fire under the circumstances you describe. This is due to a timer inside the SoundSync class that checks the current position of the sound itself: while paused, the position doesn’t change. Are you using the AS2 version, or the AS3 version?

When I use your sound stop and start functions with SoundSync, the pause doesn’t stay paused … it fires at the next cue point, even though the sound has stopped.

Any ideas why?

SoundSync extends the native Sound class, so in theory, you’ll have to do whatever you would normally do with an instance of Sound. How are you trying to pause/play your SoundSync instance?

Or can you direct me to something that will work?

You shouldn’t run into any problems. Each class instantiates its own distinct objects. Glad you like the SoundSync class!

I just came across your tutorial for adding cue points to MP3 audio files – I wanted to think you for the excellent tutorial, it works great, and was exactly what I was needing.

An application I’m curently scoping uses both FLVs and MP3 files. I was wondering if you have come across any issues using the soundSync class with audio files in an app that also uses FLVPlayBack components with the usuall addASCuePoint for video?

Thanks in advance –

Michael

I have run into a bug with the AS2.0 version of the code and am wondering if you’ve encountered it before. It happens pretty randomly, when a cue point event triggers, it triggers twice.

I’ve used this same code a number of times myself. What you’re describing does sound familiar. I do recall discovering the occasional weakness while using this class in actual projects. The good news is, I also remember managing to fix each issue as it came up, so I hope that provides some encouragement!

For what it’s worth, here’s a snippet from a change I made to the pollCuePoints() method in one of my projects:

private function pollCuePoints():Void {
  // If current position is near the current cue point's time ...
  var time:Number = _cuePoints[_currentCuePoint].time;
  var span:Number = (_cuePoints[_currentCuePoint + 1].time) ?
    _cuePoints[_currentCuePoint + 1].time :
    time + _intervalDuration * 2;
  // HACK: hardwire span to 1 sec for single cue points under a sec
  if (_cuePoints.length == 1 && time < = 1000) span = 1000;
  if (position >= time && position < = span) {
  // Dispatch event
  if (_cuePoints[_currentCuePoint]) {
    dispatchEvent(_cuePoints[_currentCuePoint]);
  }
  // Advance to next cue point ...
  if (_currentCuePoint < _cuePoints.length) {
    _currentCuePoint++;
  } else {
    _currentCuePoint = getNextCuePointIndex(_secondOffset);
  }
}

I don't know if that will help you at all — I fear it may not — but you're certainly on the right track by tweaking _intervalDuration. If the above snippet doesn't change or correct the other issue, you may want to experiment with the span variable on your own. Those values work together and can probably stand to be tweaked for each situation. Which tells me I should have made them configurable.

First off, thanks for putting this tutorial together and for explaining how the code works so thoroughly. I am using this method in some eLearning I’m creating and it’s been a huge help.

I have run into a bug with the AS2.0 version of the code and am wondering if you’ve encountered it before. It happens pretty randomly, when a cue point event triggers, it triggers twice. I figured maybe it had something to do with the interval timer being too short, so I set _intervalDuration = 100; in the SoundSync.as file and that seems to be working so far.

I have also encountered another issue where if you set a cue point right near the beginning of the audio (like say 700 ms, the trigger never gets fired off. I work around that by never setting a cue point before the first second or two of audio, but I’d be interested to know if you’ve seen that behavior as well.

Ta,
Mark