[vorbis-dev] ov_read() reading too little.

[Monty]

> Ah.  You might want to update the online documentation.  If you click
> "documentation", "api reference" then "ov_read", you get to this page:
> 
> http://www.xiph.org/ogg/vorbis/doc/vorbisfile/ov_read.html
> 
> it says:
> 
> n indicates actual number of bytes read. Within a logical bitstream, the
> number should equal length. At the end of a logical bitstream, the
> number of bytes read will equal the remaining number of bytes in the
> bitstream.

I'll fix it.

> I don't need to fill up my buffer every time, but I do need to read at
> least 1/10 of a second on average.  I can put the call to ov_read() in a
> loop, decreasing the "available buffer size" after each iteration by the
> amount read.  But what happens when the buffer size gets too small, e.g.
> < 1K?  Will ov_read() refuse to read any bytes?  If so, then "0" doesn't
> always mean EOF.

It will fill the available space.  There is internal buffering for
unrequested data.

> Just curious, are there plans to change this or document it?

I just need to fix the one doc-bit you found.  No plans to change it
unless folks convice me to do otherwise (it would complicate error
handling/buffering)

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-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.