similar to: gcc 3.2 warnings

Hi all, Those of you uninterested in classic MacOS as a target will probably want to skip this email. I'm revisiting this platform, trying to get music going for the game I'm working on. We're obviously using OggVorbis on the other platforms we support (osx, linux, win32). The problem is that our classic MacOS build is currently under MPW/MrC. I can compile libogg/libvorbis fine

Well, I've "fixed" two problems so far with getting things built on OS X. If whoever did the OS X work is reading this, feel free to tell me where/how I've screwed up =) The first problem is that it couldn't find MacTypes.h in the path. MacTypes.h is simply a one line file that includes <CoreServices/CoreServices.h>, so I just replaced the MacTypes.h with that. In

Hello list, (PC Windows 2000, R 1.2.3) i want to compile C source file for R on windows 2000. I'm working with Metrowerks CodeWarrior for creating and compiling C files. I've see that R.lib file must be obtain with R.ddl by Visual C++. I don't have Visual C++ (and i don't want to buy it !!) but i want to obtain R.lib file. Is there a solution to my problem ??? Any help would

--- Stephane wrote: VP3 codec uses a lot of CPU for decoding. We will need some optimization because now this codec is way too slow for home uses. --- end of quote --- Actually, the Windows VP3 QuickTime codec runs just fine on a 400MHz Pentium II box, with only occasional glitches on some dodgy Celeron systems. At work, we routinely test 320x240 full-color, full-motion video on low-end boxes.

pls let me know if/when you have theora compiling & running on Windows. -----Original Message----- From: Tabuleiro [mailto:beta@tabuleiro.com] Sent: Tue 10/22/2002 3:13 PM To: theora-dev@xiph.org Cc: Subject: [theora-dev] compglobals.c I believe this file is no longer used and contains functions that are no

Well, I've been slamming my head against this all night, so it's time to ask for help... Having gotten together a reasonably decent port of what I thought was the whole API to the Ogg Way, complete with Ogg mem management and bitpacking, I started digging deeper in the code... only to find that it looks like I only have a middle stream handler. The encode and decode code both assume that

it appears your encoder/player do not yet reflece the changes rillian introduced wrt theora headers, which have been split into three parts -- header proper, comment, and tables (see toplevel.c). It's strange that your code works at all linked against the new libs; presumably since the tables still have the hard-coded values, if you encode & decode from the same lib compile you won't

Thanks for the http://vorbis.com link. That worked. But I looked in the download area and there is no SDK for Mac OS 9. So I am compiling the vorbis code directly into my app. The problem I am having now is that the CodeWarrior 5.0 compiler has a bug with alloca(). It allocates the area on the stack but, under some circumstances, it does not restore the stack pointer at the end of the routine.

Hey, I ran across this while building vorbis on the Mac: In libvorbis RC2, file info.c, line 65, there's a call to strdup(). strdup() isn't portable, and it looks like the code should use the internal memory functions to create the memory for the string anyway. Actually, on further inspection, it looks like the memory for the user comments is never actually freed. I'm not subscribed

I have a zip file containing updated Macintosh support for Vorbis on my company's web site at the following URL: http://bDistributed.com/projects/vorbis-mac/MacVorbisUpdatesBeta3.zip I used Metrowerks ClassWrangler to build the file because StuffIt insisted on MacBinary-encoding the project files. StuffIt Expander seems to have issues with expanding it, so I'm not sure if it's

Well, I updated the player to work with the branch_postbeta2, but it contains some nasty kludges to the project files that probably shouldn't be finalized. I'm going to put it in a separate file (http://oscar.the-rileys.net/programming/vorbis_pb2.tar.gz) for now. Unfortunately, this release doesn't seem to fix the "tearing sound" problem. I think this might be related to

On Jul 30, 2013, at 12:41 PM, Stephen Lin wrote: >> Right. What's the point of all the effort devoted to MSVC++ ABI >> compatibility when Clang doesn't need it for being a top-notch C++ >> compiler on Windows? > > I brought up a similar point a little bit earlier, too.... > > It seems like the only necessary condition for being a first-class >

--- "Tabuleiro" wrote: Hi, guys. I was working with the VP3 code, planning to integrate it with Ogg for a self-contained solution for video playback, platform independant, no installation required, no QT, no AVI runtimes. My main interest is CD-based work using local files and portability/performance, not really into streaming or anything fancy (network error correction, prediction,

First, an introduction: I work in a group that makes educational software. In the coming months, we're planning to release our entire Mac/Windows runtime under the GPL. We currently encode our audio with MP3 and our video with VP3. For playback, we rely on QuickTime 5 on MacOS and Windows. In the short run, we'd like to help maintain the VP3 QuickTime codecs, preferably without

good question. I would think beta means the bitstream is more or less stable. Monty? >If June is the goal for public release, is the second milestone the first beta/rc1? Guess what I'm asking is, whats a good estimate for when the codec will be frozen as far as backwards compatability.. -----Original Message----- From: Arc [mailto:arc@indymedia.org] Sent:

Question: is it permissible to put more than one frame packet into a page? At 30 fps, Ogg page overhead is on the order of 8 - 10 kbits/sec. At low datarates, this is going to be unacceptable. If I shove a few frames into a page, how does this affect the granulepos stuff? ___ Dan Miller (++,) Founder, On2 Technologies <p>--- >8 ---- List archives: http://www.xiph.org/archives/

Full_Name: Martin Gansser Version: 1.5.1 OS: hp-ux 11.00 Submission from: (NULL) (195.145.22.147) cc -Wp,-H16000 -I. -I../../../src/include -I../../../src/include -I/opt/gnome/include/gnome-1.0 -DNE ED_GNOMESUPPORT_H -I/opt/gnome/lib/gnome-libs/include -I/opt/gnome/include/glib-1.2 -I/opt/gnome/lib /glib/include -I/opt/gnome/include/orbit-1.0 -I/opt/gnome/include/gtk-1.2

> Right. What's the point of all the effort devoted to MSVC++ ABI > compatibility when Clang doesn't need it for being a top-notch C++ > compiler on Windows? I brought up a similar point a little bit earlier, too.... It seems like the only necessary condition for being a first-class native-code development tool on Windows is to support the platform C ABI and the subset of the

Colin Farrow <C.Farrow@geology.gla.ac.uk> writes: > Peter, > > Cautiously sticking my neck above the water line here. I have been > wondering about the Mac version for a while now. I may be able to get > an MSc IT student to work on this as a project for about 3 months > June-Sept. Before putting up the proposal some idea of the scale of the > task would be useful. Do