Steven Seeger wrote:
> Well, the thread suspends when it's done playing, and when new data arrives
> in the buffer via /dev/dsp, the thread is then resumed. I just wonder what
> the point of suspend/resume is, then, if we're supposed to just use
> rt_task_set_periodic to create a new timeline. Right now I am doing this,
> and then suspending, and then before I resume, I make another timeline.
> 

Well, and this is racy in case the resume - for what reason ever - takes
place before the suspend. It will get lost then, and your player will
miss a job. One should better model this via an event (don't count
multiple wakeups) or a semaphore (each wakeup counts and is paired with
a wait in the player task).

Jan