the alsa sink implementation would have this bug. Another possibility is that while processing the rewind, some code somewhere requests another rewind. Requesting a new rewind from a rewind processing handler would be one possible cause, and another would be requesting rewind from a wrong thread, which sounds quite likely in this case, since you're moving a stream. > I got this failure when I killed a sink-input in its move-finish hook > to a new sink (is it safe?). I don't know if it's safe. Might be that it's not. -- Tanu
