Vorbis - Jul 2001 - Songs stopping early on my player

I suspect the stopping behaviour is my mishandling of either OV_EBADLINK or
OV_HOLE.
What should I be doing if either of these values are returned by ov_read?

Having experimented more Winamp has no trouble with the "jerky"
songs. But the songs where my player stops prematurely pause for a second or
two in Winamp. And with WMP they continue to play properly, but from the
point where they stop with my player, the position indicator of WMP goes
kinda crazy.
I found that somehow I ended up with a *really* old version of my player
code, where I wasn't actually calling ov_read repeatedly, so fixing that up
has fixed the jerkiness. Sorry for wasting ppls time with that one :)
----- Original Message -----
From: "Lance Paine" <lbp1@cs.waikato.ac.nz>
To: <vorbis@xiph.org>
Sent: Monday, July 02, 2001 12:01 AM
Subject: [vorbis] Jerkiness in player on some songs
> What could be causing my player to skip, and repeat (ie Jerky) with some
> songs and not others?
> I am just using a timer and checking the buffer. Could it be that with the
> troublesome files the are extra empty packets (or something) that cause
this
> timer approach to be inadequate?
> I usually have no, problems, just with one or two files, and they play
> correctly in winamp
> I'm using beta encoder, and plugin, and vorbisfile.
>
> TIA
>
> Lance
>
>
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is
needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

At 12:38 AM 7/17/01 +1200, you wrote:
>
>I suspect the stopping behaviour is my mishandling of either OV_EBADLINK or
>OV_HOLE.
>What should I be doing if either of these values are returned by ov_read?
OV_HOLE means "It looks like something was missing here". For a file, 
that's usually an indication it's corrupt. For a stream, it's
normal.
Either way, it's completely non-fatal. You may want to inform the user
in some way that it occurred, but other than that, just keep decoding.

OV_EBADLINK is, I think, a serious error which isn't recoverable. You 
should stop decode (I'm not certain about that, though, without checking
the code).

Michael

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

On Tue, Jul 17, 2001 at 12:38:40AM +1200, Lance Paine
wrote:
> 
> I suspect the stopping behaviour is my mishandling of either OV_EBADLINK or
> OV_HOLE.
These will never happen unless the file you're trying to play is
corrupt or the C code is corrupting heap/stack memory.

If you *are* debugging best possible playback of corrupt files, let us
know :-)
> What should I be doing if either of these values are returned by ov_read?
OV_HOLE: just continue.  
OV_EBADLINK: skip that link and begin decode at the beginning of the next link.

Monty

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.