Is AVAudioPlayerNode isPlaying flag set as soon as scheduleBuffer is called?

Question

I've got two AVAudioPlayerNodes.

I schedule one using scheduleBuffer.

I want to cancel it before it starts but not if it has already started.

How do I know if it has actually started?

The isPlaying flag appears to be set as soon as it is scheduled rather than when it actually starts at the scheduled time.

Are you calling play() or play(at:) on the nodes? – dave234 Jun 27 '17 at 21:33 — dave234, Jun 27 '17 at 21:33
I'm calling play() on the nodes. – Andrew Sage Jun 28 '17 at 10:12 — Andrew Sage, Jun 28 '17 at 10:12
Didi you get it figured out? – dave234 Jun 30 '17 at 14:37 — dave234, Jun 30 '17 at 14:37
I need it now! Did you get it ? – Fischer Jul 08 '19 at 09:52 — Fischer, Jul 08 '19 at 09:52

score 0 · Answer 1 · answered Jun 27 '17 at 21:44

AVAudioPlayerNode takes a render cycle after calling play() before actual audio starts playing. If you are trying to identify the time between play() and audio being played, you can get the playerNode's playerTime and look for negative (or less than specified with play(at:)) sampleTime values. But since you're on different threads than the audio being scheduled, there's still a chance that a render cycle's worth of audio can squeeze out before you stop the player.

let playerTime = playerNode.playerTime(forNodeTime: AVAudioTime.init(hostTime: mach_absolute_time()))
print("sample time \(playerTime.sampleTime)")

Is AVAudioPlayerNode isPlaying flag set as soon as scheduleBuffer is called?

1 Answers1

Linked