similar to: C++, Python wrappers for libogg and libvorbis

Hi, I've been working on a competing Python wrapper for ogg, vorbis, and theora, and if you are someone who knows about boost.python and would like to test my package for me I would appreciate it. Especially re: compiler errors and how to get it to reliably work on other's computers. The wrapper should be advanced enough to add comments or show comments on a theora stream, and to

[Sorry if this is a duplicate post. My original didn't appear to have gotten through.] I had previously installed libao, libogg, libvorbis, and vorbis-tools, as linked from the RC3 download page at vorbis.com -- I downloaded and installed the latest versions of these four libraries from the vorbis.com download page, at which point my pyogg/pyvorbis Python bindings broke. I reinstalled the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://dingoskidneys.com/~dholth/oggzcomment-0.0.1.tar.gz This is a program that is capable of altering vorbis and theora comments in a combined stream. It requires python, libogg, and liboggz. Compile thusly: gcc oggzdc.c -o oggzdc -logg -loggz gcc oggzrc.c -o oggzrc -logg -loggz 1. Dump comment headers to a simple comments-only (now:

I compiled and installed pyogg followed by pyvorbis, running: $ ./config_unix.py $ python setup.py build and as root: # python setup.py install for pyogg and pyvorbis in turn. This completed without error, however upon trying to import ogg.vorbis in IDLE I get an import error: ImportError: libvorbisfile.so.3: cannot open shared object file: No such file or directory I was told this may have

Dear List, I'm just creating a little application for my openmoko freerunner, unfortunately in python, so that I have to use pyogg and pyvorbis(http://ekyo.nerim.net/software/pyogg/index.html) as wrappers around the C-functions and objects. I've got it all installed, after applying some patches and trying to run an example of encoding a wave-file I just get an empty ogg-file, the

I'm having trouble getting libvorbis to cut the beginning of a bitstream when I instruct it to do so with granulepos. I have constructed a file which I believe should have its beginning truncated. I have attached it to this mail. Here is a picture of what the bitstream looks like, as output by a python program that uses pyogg/pyvorbis to read the stream and print a representation:

If FLAC is to be streamed over http, it makes sense that ogg123 ought to be able to recognize flac on http when it sees it. http://dingoskidneys.com/shoutpy/httppeek.patch It seems to work. - Daniel Holth --- >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

Hello everybody! I'am just leaning Python and wanted to write something useful for me, an recursive masstagger for ogg-vorbis files. My script uses pyvorbis 1.3 from the Debian testing tree. so far here is my Problem: The pyvorbis bindings aren't documented. As i understand the pyvorbis package, this is a simpe 1:1 mapping to libvorbis. dir(pyvorbins-oject) gives me an refernece to an

Hi everybody: Here is the latest issue of Ogg Traffic. The HTML version is at http://www.vorbis.com/ot/20030715.html. Enjoy! Carsten. <p>Ogg Traffic for Tuesday, July 15, 2003 Author: Carsten "Purple" Haese Contact: [1]carsten@xiph.org Date: July 15, 2003 Table of Contents 1 Status Updates 1.1 Stan Seibert 1.2 Ed Zaleski

Hi. I'm working on a very simple C++ wrapper for parts of libogg and libvorbis; I thought I would expose it for initial comments and the generally curious. No conveniences, no frills. No helpful higher-level abstractions. Just a translation from ogg_method_foo(ogg_method* data) to classes that hold the ogg_stream_state etc., so you may type mypage.bos() instead of

Anyone who wants to see what bugs might not have made it into xiph bugzilla may want to look at the urls below. Be sure to check the bugs marked as fixed in NMU since they may have patches that aren't in cvs yet. I'll try to be around to help verify the bugs are fixed before release tomorrow/monday. Thanks, Chris Cheney http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libao

So, I abandoned the hope of using the ogg python bindings to do pure ogg container encoding. I started looking at the libogg in the hopes of retooling the bindings to follow a better object model and it actually looks like the problem is down in libogg, not the bindings. Am I crazy or does libogg rely on libvorbis to return ogg_packets, and that there are no functions that will build an ogg_packet

hi list.. did anyone of you ever try to play mono files with pyvorbis (1.0)? when i try such a file, generated from a mono wave file with oggenc, with ogg123.py, it sounds like being on speed. i believe, it plays with double speed, because pyvorbis always assumes a stereo file to be read, though i did not measure it. playing the same file with ogg123 (the c program), it works fine. i also

Hello All, Somewhat offtopic, but pertinent for my Ogg app. I'm very happily using pyogg and pyao in a python script to serve as my ogg decoder. It's working very well! I'd like to add support for MP3s in a fashion similar to what I already have for oggs. However, I'm unaware of any such module. Anyone know of a python decoder wrapper for MP3s? Closest thing I can find is the

Zen (and everyone else), I finally had time this weekend to review the libogg and libvorbis release status. I think both are ready to go on the linux side. There are quite a few vorbis issues open, but I don't think anything is release critical, and we should get the gcc4 aliasing bugfix out there. How are things looking with your build? Is current svn is building for you? As soon as

Hi folks,. I'm working on a project on Irix 6.3 using CC (not GCC) and the .o32 object format (not n32) and would like to incorperate ogg-vorbis. Is there any way to configure the libogg/libvorbis makefiles to work with CC? (Or does anyone know how to arm-twist GCC under Irix 6.3 into producing o32 object files?) Thanks super-much for any help, Mike <p>--- >8 ---- List

I'm pleased to announce the release of new versions of our Ogg and Vorbis reference implementation libraries. These are bug fix releases, with no new features. Particularly important is a fix for a pointer aliasing bug triggered by the new gcc 4.x optimizer. Because of this we strongly recommend that all gcc-based users upgrade, i.e. those on GNU/Linux and MacOS X, for example. The new

I'm pleased to announce the release of new versions of our Ogg and Vorbis reference implementation libraries. These are bug fix releases, with no new features. Particularly important is a fix for a pointer aliasing bug triggered by the new gcc 4.x optimizer. Because of this we strongly recommend that all gcc-based users upgrade, i.e. those on GNU/Linux and MacOS X, for example. The new

I am using libogg, libvorbis, and libvorbisfile in my most recent project. One of the build environments that my project must build on is MinGW. http://www.mingw.org/ Unfortunately, it seems that there are a few (possibly) minor problems with the libogg and libvorbis build processes which prevent me from building them under MinGW. One is that both of them reference header _G_config.h which

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. *