Fix the possibly wrong assumption that we're able to accurately
calculate latency using GETOSPACE
(buffer size - available bytes to write).

New code uses GETODELAY to get latency directly but falls back to
GETOSPACE calculation should GETODELAY fail.
Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>