similar to: libvorbis on Classic MacOS

> In fact I am compiling as C++. Under BeOS, these functions will > eventually end up inside of a C++ class. So, I'm kind of stuck. > It's not the end of the world. Couldn't you just compile the vorbis files as vanilla C, and then implement a thin C++ wrapper if you need to access it that way? There's nothing in BeOS which *requires* code to be C++. Sorry if I'm

Looking through the archives I have seen talk of making CPU specific optimisations for Vorbis, a la MMX/3DNow!/SSE. The feeling I gather is to wait until something is working well in C before committing to any kind of specific optimisation. What if oft used and needed DSP functions were identified and standardised DSP functionality be written for Vorbis? This would seperate the basically

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'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

This is mostly for derf, but others may be interested too. Attached are the warnings (stderr log) from compling theora under gcc 3.2.3 (Debian). There quite a few. Many of them are spurious, but some indicate real bugs. In particular it seems likely we have more unitialized variables since Dan reports differing encoder output depending on the compiler used. In general, we need to go through

Hi all, This is to say hello to all of you as we are starting the project Ogg on a Chip for our master thesis. More information can be found at http://oggonachip.sourceforge.net/. Cut from the homepage: "The Ogg Vorbis Player (http://www.xiph.org/ogg/vorbis/index.html) shall be implemented in form of a system-on-a-chip by using hardware/software co-design techniques. A prototyping board

Hi I'm getting frequent segmentation faults (on the order of one every hour) while listening to the stream at http://62.93.224.180:15000/radio404.ogg . This is on FreeBSD 5.3 with everything installed from the FreeBSD ports (this means libvorbis-1.0.1), but I had the same issue with an older FreeBSD 5.1 installation. The backtrace looks like : (gdb) bt #0 0x28741d88 in

Hi all, I recently noticed that Vorbis shlibs export several symbols which are not present in it's public header (for a total of 85 symbols, see attach). Would it make sense to filter them via -fvisibility=hidden and -Wl,--version-script? I attached a draft patch. Best regards, Yury Gribov -------------- next part -------------- _book_maptype1_quantvals _book_unquantize __bss_start

https://bugzilla.mindrot.org/show_bug.cgi?id=2497 Bug ID: 2497 Summary: Add debugging information to ga_match() to show each attempted match Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

Sorry, majordomo mistriggered on the word 'which'. Sigh. Monty ------- Forwarded Message From: "Timothy Wayper" <timmy@r3.co.nz> To: <vorbis-dev@xiph.org> Subject: Re: [vorbis-dev] BeOS (was Parallelism) Date: Fri, 18 Aug 2000 10:17:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority:

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

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

---------- Forwarded message ---------- Date: Mon, 18 Dec 2000 15:50:05 -0500 (EST) From: Erik Kruus <kruus@on2.com> Reply-To: vorbis-dev@xiph.org To: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] what script or command makes the codebooks? I've been through the entire vq table process during the last week. Some folks have already suffered through listening to .ogg files encoded with a

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 >

Greetings. In looking through the mail archives, I don't see any mention of parallelism of the vorbis code (particularly the encoder). I was wondering if anyone was looking into this at all? Either with threads, and/or on some kind of parallel machine (e.g., a Beowulf cluster)? I see very little mention of threads in the source code, which leads me to believe that they are only there for

Charles Davis <cdavis5x at gmail.com> writes: > Huh? Intel CC supports the MSVC++ ABI. Zortech (Digital Mars) supports > it, too (though the guy who wrote it isn't too proud of that fact--or > the fact that he even wrote that compiler to begin with). Heck, even > CodeWarrior supported it (as Howard Hinnant might well remember), > before Metrowerks sold off their x86

[* The word xSUBSCRIBE so early in your posting made it bounce. MMae] v I 0subscribe to R-help (not R-devel) but thought this was more relevant to R-devel, and the future of R's imaging model and cross-platform support. If this has already been under discussion I apologize. I've no connection with the product, business or its people. Gerry Begin forwarded message: We, at

First of all, GREAT WORK! I now have my very own Windoze domain thanks to Samba :) Now, getting Samba to work fully on OpenBSD was harder than I'd think it would be. To get smbd to compile somewhat cleanly, I had to hack ./source/include/config.h thusly: remove USE_SETREUID, add USE_SETEUID. Then, I hacked sec_ctx.c like the attached diff shows, to get rid of some assert_gid panic when

I need libvorbis-devel to build another app. I have been trying to resolve this dependency failure for several days with no luck. I hope someone here can help me. uname -a Linux 2.6.10-2.1.ll.rhfc3.ccrma #1 Thu Dec 30 03:08:13 EST 2004 i686 i686i386 GNU/Linux rpm -q libvorbis libvorbis-1.0.1-1 rpm -ivh libvorbis-devel-1.0.1-1.i386.rpm error: Failed dependencies: libvorbis = 1.0.1 is