Displaying 20 results from an estimated 8000 matches similar to: "Bug in oggz-validate with small files"
2009 Aug 24
2
oggz reading & seeking
??????? I've rewritten my theora player using liboggz. I've stumbled upon a few issues though. First of all liboggz exposes oggz_read and oggz_run, but how can i read only sound data, or only video data using liboggz, say something like this: oggz_read_sound(1024), oggz_read_video(1024).
? ? ? ?? Second of all i tried using liboggz's seek function. Immediately after the seek i get some
2009 Feb 13
1
Decoding from memory using libfishsound
Hi,
I have a problem. I've started to develop crossplatform sound
receiving application using qt4/openal/libfishsound. Server is
streaming audio coded with speex in ogg container throuh http. I'm
receiving packages and when I write them to file application example
from libfishsound is properly decoding it. Problem starts, when I want
to decode from memory, for example: receive few
2008 Jul 31
1
liboggz and packets versus segments ...
I'm doing some work where narrowband speex audio capture is happening and
being written to file in the ogg container format. Later retrieval for
reading will occur too.
I've been using liboggz to do the file reading and writing and have
obviously come across some things I don't seem to follow or have just got
wrong.
I can happily generate an ogg file using liboggz with some test
2008 Nov 10
2
oggz-validate does not seem to check for correctly framed headers
While testing the new vcut, some of the early results had badly framed
headers. I actually didn't notice it at first, because I was testing
with oggz-validate, but ogginfo does identify the problem:
"WARNING: Vorbis stream X does not have headers correctly framed.
Terminal header page contains additional packets or has non-zero
granulepos"
Conrad (or someone else) may want to
2008 Nov 11
0
oggz-validate does not seem to check for correctly framed headers
2008/11/11 Ivo Emanuel Gon?alves <justivo at gmail.com>:
> While testing the new vcut, some of the early results had badly framed
> headers. I actually didn't notice it at first, because I was testing
> with oggz-validate, but ogginfo does identify the problem:
>
> "WARNING: Vorbis stream X does not have headers correctly framed.
> Terminal header page contains
2008 Jul 04
2
Oggz 0.9.8 Released
Oggz 0.9.8 Release
------------------
Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump,
oggzdiff, oggzmerge, oggzrip, oggz-chop, oggz-comment, oggz-scan, oggz-sort
and oggz-validate. oggz-chop can be used to serve time ranges of Ogg media
over HTTP by any web server that supports CGI.
liboggz is a C library providing a simple programming interface for reading
and writing Ogg
2008 Jul 04
2
Oggz 0.9.8 Released
Oggz 0.9.8 Release
------------------
Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump,
oggzdiff, oggzmerge, oggzrip, oggz-chop, oggz-comment, oggz-scan, oggz-sort
and oggz-validate. oggz-chop can be used to serve time ranges of Ogg media
over HTTP by any web server that supports CGI.
liboggz is a C library providing a simple programming interface for reading
and writing Ogg
2009 Jun 09
2
oggz mingw
When I try to 'make' oggz (0.9.9), I get the following compile error
make[4]: Leaving directory `/c/liboggz/src/tools/oggz-chop'
make[4]: Entering directory `/c/liboggz/src/tools'
/bin/sh ../../libtool --tag=CC --mode=link gcc -g -O2 -Wall -Wextra -g
-std=gnu99 -Wdeclaration-after-statement -Wno-unused -o oggz-info.exe
oggz-info.o skeleton.o oggz_tools.o dirac.o
2008 Jul 15
3
oggz-chop crash
Hi,
while playing around with oggenc, I used oggz-chop, and got it to crash
consistently on one set of input and parameters (cutting a file I'd encoded
(Vorbis+Kate) between (IIRC) 120 and 150 seconds. GDB showed a NULL
pointer access (can't recall where, sorry). When I came back to it though,
with a new input file, I couldn't repro it, though it had previously happened
several times
2009 Apr 10
0
Oggz 0.9.9 Release
Oggz 0.9.9 Release
------------------
Oggz comprises liboggz and the tool oggz, which provides commands to
inspect, edit and validate Ogg files. The oggz-chop tool can also be
used to serve time ranges of Ogg media over HTTP by any web server that
supports CGI.
liboggz is a C library for reading and writing Ogg files and streams.
It offers various improvements over the reference libogg,
2009 Jun 15
2
oggz-chop gives segmentation fault
Hi,
I am using oggz-chop in the ubuntu jaunty, am I doing something wrong?
$ oggz-chop -o yt1.ogv -s0 -e500 ondrej.ogv
Segmentation fault
gdb session doesn't reveal much, since it isn't compiled with debugging symbols:
(gdb) bt
#0 0x00007f9e5d2f0092 in memcpy () from /lib/libc.so.6
#1 0x0000000000403698 in ?? ()
#2 0x000000000040262e in ?? ()
#3 0x000000000040285d in ?? ()
#4
2008 Nov 23
2
ogg dirac granulepos in oggz tools
2008/11/24 David Flynn <davidf+nntp at woaf.net>:
> On a slightly unrelated note, i keep hitting the following error in
> liboggz when using the oggz tools on an ogg dirac stream:
>
> /home/davidf/project/liboggz/src/liboggz/oggz.c:202: oggz_close:
> Assertion `oggz_dlist_is_empty(oggz->packet_buffer)' failed.
>
> I'll supply an example file tomorrow if that
2009 Oct 08
0
Oggz 1.1.0 Release
Oggz 1.1.0 Release
------------------
Oggz comprises liboggz and the tool oggz, which provides commands to
inspect, edit and validate Ogg files. The oggz-chop tool can also be
used to serve time ranges of Ogg media over HTTP by any web server that
supports CGI.
liboggz is a C library for reading and writing Ogg files and streams.
It offers various features over the reference libogg, including
2009 Sep 14
0
Oggz 1.0.0 Release
Oggz 1.0.0 Release
------------------
Oggz comprises liboggz and the tool oggz, which provides commands to
inspect, edit and validate Ogg files. The oggz-chop tool can also be
used to serve time ranges of Ogg media over HTTP by any web server that
supports CGI.
liboggz is a C library for reading and writing Ogg files and streams.
It offers various features over the reference libogg, including
2009 May 04
1
[PATCH] oggz: inefficient seeking
I have a 1.1G Ogg file with vorbis and theora. oggz_seek_units() takes 14
seconds to find a position in the file towards the end. Now, the function
guess() in oggz_seek() guesses a position at about 1.5G and then slowly
searches back until it finds the end of the file (continously seeking
beyond the end of the file and then calling read which returns 0). Then
it does a linear scan from the
2008 Jul 16
0
oggz-chop crash
2008/7/15 ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com>:
> Hi,
>
> while playing around with oggenc, I used oggz-chop, and got it to crash
> consistently on one set of input and parameters (cutting a file I'd encoded
> (Vorbis+Kate) between (IIRC) 120 and 150 seconds. GDB showed a NULL
> pointer access (can't recall where, sorry). When I came back to
2007 Dec 04
1
patch for oggz-comment
Hi,
It seems the oggz-comment on your computer has more features than the
one you sent in August :-) Any chance you could send a more recent
copy?
In any case, I've updated the --help output for the -s option, and
also added a manual page with the same info, in
doc/oggz-comment.1.sgml (in svn.annodex.net changeset:3280).
cheers,
Conrad.
On 07/11/2007, Kangyuan Niu
2007 May 02
2
libogg++ release 0.1.1
On 02/05/07, Elaine YueLien <et@ihear.com> wrote:
> Hi,
>
> Several months ago, I asked a question about seeking without a metric.
> You can find one answer in this beta release, demonstrated in the
> example program multiThreadSeek. There is also an example demuxer, and a
> rewriter.
Hi Elaine,
congratulations :-) that's a nicely designed API you've got there.
2012 May 16
2
Problems seeking with liboggz
Hi,
I intend to use Ogg+Speex for voice recording/playback in a VoIP app.
I am experimenting with liboggz to get acquainted with its API.
As test files I am using some Ogg-Speex files converted from WAV files
with speexenc.exe.
I wrote a little testing app in Visual Studio 2010 under Windows 7.
I defined OggzReadPage and OggzReadPacket callbacks with
oggz_set_read_page()
2008 Nov 13
5
ogg dirac granulepos in oggz tools
Hi,
I'm wondering if the Dirac granulepos parsing in liboggz and display
in the oggz tools is currently correct, as I'd like to do a release of
these soon.
A couple of days ago David Schleef mentioned there were some problems.
David, is that currently true (ie. since David Flynn's recent updates
to support Dirac), and if so could you please explain what the
problems are, or point me