Displaying 7 results from an estimated 7 matches for "ogg_stream_pageout_fil".
Did you mean:
ogg_stream_pageout_fill
2010 Nov 01
1
Xiph.Org releases libogg 1.2.1 and libvorbis 1.3.2
Xiph.Org is pleased to announce a full release of libogg 1.2.1
and libvorbis 1.3.2. This is not a coordinated release, it was
merely convenient to do a release cycle for both at the same
time.
Changes and fixes in the new libogg release include:
* Various build updates (see SVN)
* Add ogg_stream_pageout_fill() to API to allow applications
greater explicit flexibility in page sizing.
* Documentation updates including multiplexing description,
terminology and API (incl. ogg_packet_clear(),
ogg_stream_pageout_fill())
* Correction of a possible buffer overwrite in stream encoding on
32 bit when...
2010 Nov 01
1
Xiph.Org releases libogg 1.2.1 and libvorbis 1.3.2
Xiph.Org is pleased to announce a full release of libogg 1.2.1
and libvorbis 1.3.2. This is not a coordinated release, it was
merely convenient to do a release cycle for both at the same
time.
Changes and fixes in the new libogg release include:
* Various build updates (see SVN)
* Add ogg_stream_pageout_fill() to API to allow applications
greater explicit flexibility in page sizing.
* Documentation updates including multiplexing description,
terminology and API (incl. ogg_packet_clear(),
ogg_stream_pageout_fill())
* Correction of a possible buffer overwrite in stream encoding on
32 bit when...
2010 Nov 01
1
Xiph.Org releases libogg 1.2.1 and libvorbis 1.3.2
Xiph.Org is pleased to announce a full release of libogg 1.2.1
and libvorbis 1.3.2. This is not a coordinated release, it was
merely convenient to do a release cycle for both at the same
time.
Changes and fixes in the new libogg release include:
* Various build updates (see SVN)
* Add ogg_stream_pageout_fill() to API to allow applications
greater explicit flexibility in page sizing.
* Documentation updates including multiplexing description,
terminology and API (incl. ogg_packet_clear(),
ogg_stream_pageout_fill())
* Correction of a possible buffer overwrite in stream encoding on
32 bit when...
2010 Apr 04
1
Make check failure
Hi all,
I've just grabbed a copy of SVN head for libogg and 'make check'
is failing:
./test_framing
testing single page encoding... 0, (0), granule:0 ok.
testing basic page encoding... 0, (0), granule:0 1, (1), granule:6151 ok.
testing basic nil packets... 0, (0), granule:0 1, (1), granule:10247 ok.
testing initial-packet lacing > 4k... 0, (0), granule:0
2010 Dec 07
0
libOgg 1.2.2 released
Xiph.Org is pleased to announce a full release of libogg 1.2.2.
This is a spot release that contains only build and documentation
fixes.
Changes and fixes in the new libogg release include:
* Build fix (types correction) for Mac OS X
* Update win32 project files to Visual Studio 2008
* ogg_stream_pageout_fill documentation fix
This release contains no library code changes, only a type
correction in a header to allow successful builds on Mac OS X. A
similar type change without practical effect was made for correctness
purposes on BEOS.
Tarballs and zipfiles of the official release can be found in the...
2012 Oct 19
3
How to cross-compile opus-tools?
...rence to `ogg_stream_flush_fill'
/home/user/source/opus-tools/src/opusenc.c:830: undefined reference to `ogg_page_packets'
/home/user/source/opus-tools/src/opusenc.c:830: undefined reference to `ogg_page_granulepos'
/home/user/source/opus-tools/src/opusenc.c:879: undefined reference to `ogg_stream_pageout_fill'
/home/user/source/opus-tools/src/opusenc.c:798: undefined reference to `opus_strerror'
/home/user/source/opus-tools/src/opusenc.c:955: undefined reference to `opus_multistream_encoder_destroy'
/home/user/source/opus-tools/src/opusenc.c:956: undefined reference to `ogg_stream_clear'...
2010 Apr 05
6
Make check failure
Erik de Castro Lopo wrote:
>> I've just grabbed a copy of SVN head for libogg and 'make check'
>> is failing:
>The breakage happened in this commit:
>
> r17098 | gmaxwell | 2010-03-29 16:35:11 +1100 (Mon, 29 Mar 2010) | 1 line
> Firstly, is gmaxwell on this list?
[snip]
> Secondly should be be trying controvertial changes in HEAD? Surely thats
> what