similar to: Libvorbis documentation.

In the example decoder it writes data in varying lengths to stdout, is it possible to alter the decoder to write the same length data to stdout every time? Rather, how would you alter the decoder to do that. It seems to be writing everything from 512 to 4096 bytes each time and i cant really see why this is and how to change it. <p><p>--- >8 ---- List archives:

Greetings, I thought this was supposed to be a list for educated people to discuss serious development of the ogg vorbis project. In light of that, it is amazing to see the level Mr. Segher Boessenkool drops down to in the last posts. More or less calling people insane and accusing them of being on crack and what not. I didn't want to post this on the list, for there is no reason to

The latest CVS update of libvorbis fails to compile on SuSE Linux 6.4. The error is below. Also, what happened to the xmms plugin directory in cvs? It complains that it is missing when I do a 'cvs update'. gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0beta3\" -DHAVE_ALLOCA_H=1 -DHAVE_ ALLOCA=1 -I. -I. -I../include -O20 -ffast-math -mno-ieee-fp -D_REENTRANT -fs

Hiya, I sent the enclosed email to linux-kernel before realizing that it would, perhaps, be more proper to send it here, which I hereby do. I shall be happy to try out any and all patches. Best regards, Sune M?lgaard -------- Original Message -------- Subject: [bisected] nouveau failure with 3.9-rc1 and ongoing Date: Tue, 12 Mar 2013 19:57:55 +0100 From: Sune M?lgaard <sune at

Actually GM108 is not one of the recognized chips. Someone needs to go through and check that its goldens didn't change. Nobody's done that. See https://bugs.freedesktop.org/show_bug.cgi?id=89558 On Thu, Mar 31, 2016 at 4:57 PM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Hello, > > Acceleration support for GM107 was merged in kernel 4.1, and modesetting > support

Audacity is preparing to release version 2.0.6 shortly, so I have been doing numerous test builds. Since the last Audacity release, my development system (Gentoo Linux) has updated to libvorbis-1.3.4 and libogg-1.3.1. As a result (I think) of this, I now get link errors when trying to compile Audacity against the system copies of libogg and libvorbis (standard dynamic linkage to the system

https://bugs.freedesktop.org/show_bug.cgi?id=62351 Priority: medium Bug ID: 62351 Assignee: nouveau at lists.freedesktop.org Summary: Segfault in nouveau_dri.so Severity: major Classification: Unclassified OS: Linux (All) Reporter: sune at molgaard.org Hardware: x86-64 (AMD64) Status: NEW

Hiya, Is there any change for Quadro K620M support at some point in time, and what can I do to help, apart from the info below? Best regards, Sune Mølgaard dmesg |grep -i nouveau [ 1.164919] nouveau 0000:08:00.0: unknown chipset (1183a0a2) [ 1.164943] nouveau: probe of 0000:08:00.0 failed with error -12 lspci|grep -i nvidi 08:00.0 3D controller: NVIDIA Corporation GM108GLM [Quadro

I've used libvorbis many times in linux and windows <= 7 applications without any major problems, and wanted to know if that translates the same to the sandboxed windows 8 store app environment. I'm playing around with it right now, and was able to get the library to compile fine (static), and was able to get it to compile within my project. So far, no problems, but I was almost

Just wondering... Would it be possible for the list software to set the reply-to: field to compiz@lists.freedesktop.org? Best regards, Sune M?lgaard -- I can resist everything except temptation. - Oscar Wilde (1854-1900)

In file vorbisfile.c, function int ov_pcm_seek_page(OggVorbis_File *vf,ogg_int64_t pos) the calculation of the approximate seek point causes an overflow for very large files and on pure 32 bit architectures. /* take a (pretty decent) guess. */ bisect=begin + (target-begintime)*(end-begin)/(endtime-begintime) - CHUNKSIZE; The temporary expression (target-begintime)*(end-begin)

Hi, this is my first post, I hope it's the right mailing list (or should it be vorbis@xiph.org?) I just downloaded "SDK for MacOS9" and tried to compile the "vorbisfile_example.c" sample with CodeWarrior for Mac 8 on a Mac OS 9.2 machine. I included the libOgg and libVorbis libraries in my project, but the linker cannot file ov_clear(), ov_read(), ov_pcm_total(),

ltconfig placeholder shoud be removed. Makefile.am : some stuff copied from branch_beta3 ogg lib must be added only where necesary. vq subdir Makefile.am'ized, (but installs nothing) made distclean target slightly more clean -- check it by hand first, please --- also you'll want to remove vq/Makefile if the ...am passes inspection ------------------------------------------------- diff

I'm forwarding this mail, since thomasvs on #vorbis can't seem to subscribe/send to the list. Please Cc: thomas@apestaart.org when you answer, or write directly to him. ----- Forwarded message ----- Hi, I've been asked by Vakor to help out on the packaging of the 1.0 release (for Red Hat). (For some reason xiph.org is refusing any mail from our server, urgent.rug.ac.be, so I

I have made a patch to support libvorbis to allow parsing a vorbis bitstream in an ogg bitstream containing additional bitstreams. The patch is attached in the given ticket http://trac.xiph.org/ticket/925#preview from my experiment it successfully decodes a normal vorbis file and a vorbis+skeleton+cmml file. thanks in advance for reviewing it. -------------- next part -------------- An HTML

I am having one frustrating time trying to decipher why ov_read is failing in my MFC/C++ application, and I see in Google results that others have had difficulty as well. These google discussions generally involve libraries, dll's and linking options, as though there are perhaps some basic incompatibilities between ogg vorbis and win32 and/or MFC/C++. Very confusing. If I pass fopen a

Hi Ralph, Two diffs. One for vorbis.def and the other for vorbisfile.def. Hope they work!! regards John -------------- next part -------------- A non-text attachment was scrubbed... Name: vorbisdef.diff Type: application/octet-stream Size: 256 bytes Desc: vorbisdef.diff Url : http://lists.xiph.org/pipermail/vorbis-dev/attachments/20031001/3b7df5ad/vorbisdef-0001.obj -------------- next part

Hi all. New to the list, so my apologies, if I am out of line. I was told, that window shading (rolling them up into the title bar) is on the TODO-list. As I normally rely heavily on this feature, I just wondered which priority it has, i.e. when I can expect it. I rely solely on your kindness for this, as I am neither versed in C nor graphical effects, and thus cannot provide code of my own.

My thanks still stands, however, when one reloads compiz, any shaded windows are closed. Just wanted to let you know Best regards, Sune M?lgaard -- The best way to accelerate a Macintosh is at 9.8m sec sec. - Marcus Dolengo

Is there anything I can do in this regard? /smo On 2016-03-31 23:12, Pierre Moreau wrote: > Oh, hum, GM108 is NV118 and not NV108 which is Gk208… My bad! > > SMF from the bug report seemed to have some working setup, and since he didn't > pinged back, I guess it's working nicely. But some more checking might still be > needed? > > On 04:59 PM - Mar 31 2016, Ilia