similar to: Closed Source Releases (Ekk a LGPL problem)

> 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

Just got around to compiling RC3 under beos and came across an anomaly when using managed bitrates. I haven't changed the code for the beos encoder but I now get double the bitrates so vorbis_encode_init(&vi,mediaFormat.u.raw_audio.channel_count,(long)mediaFormat.u.raw_audio.frame_rate , -1, 128000, -1); now gives me vorbis files that average around 325 - 350. Is this now the correct

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

After fixing a 'bug' in libtool, I've finally got ogg compiling and producing a shared library. Now I'm trying to build vorbis but I'm falling over at the final step. While trying to produce libvorbisfile. The make file is trying to compile with gcc -nostart vorbisfile.o -L/boot/home/config/lib -logg -Wl,-soname - Wl,libvorbisfile.so -o .libs/libvorbisfile.so with

Tony Arcieri wrote : > I'm curious if anyone else is at all fed up with the current > state-of-affairs of media support under *IX. As things stand it's rather > a pain to add support for a new codec/framing format to an application, > and it seems like were someone to step up and design a system which > abstracts media support from end-user applications and

We spent a little time here taking a look at the Vorbis licensing scheme and ran into some possible issues. In particular, the Vorbis FAQ page here says that the LGPL license applies to Vorbis libraries and GPL applies to source code (at least that's what I gather). http://www.vorbis.com/faq.html#flic http://www.fsf.org/copyleft/lesser.html Reading the text of these Gnu

(Just a copy of the message I sent to Vorbis, better to send it here.) Hello, I'm just letting everyone know that I've begun the preliminary part of putting together a working comment system. I have a few idea's on how to implement this system. 1. What I would like to do is grab the General and Input SDK's for Winamp first. Then I would like to add to our existing Winamp

Seems we've gone back to the -L/path/to/libvorbis/ -lvorbis missing while building libvorbisfile :( it appears that. libvorbisfile_la_LIBADD = libvorbis.la and libvorbisenc_la_LIBADD = libvorbis.la have gone missing from vorbis/lib/makefile.am Dave --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list,

This one may be my fault.... I've put a temporary fix for libvorbis not linking, I altered libvorbis_la_LIBADD = to libvorbis_la_LIBADD = $(OGG_LIBS) in the makefile, hence the temporary and continued with the build. I'm now getting gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0.0\" -DHAVE_ALLOCA_H=1 - DHAVE_ALLOCA=1 -I. -I. -I../include

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

hi, I am working on a windows NT version of openssh. It's mostly working (ssh.exe, ssh-keygen.exe to be precise), except for some minor UI issues. however, i have a couple of questions about making the port available: 1. minor issue: My port is based on the openbsd ssh source (2.5.2). Is this acceptable, or should I base it on the portable source ? I think I know the answer to that one. If

http://bugzilla.mindrot.org/show_bug.cgi?id=368 ------- Additional Comments From mindrot at regs.nebcorp.com 2002-07-24 12:16 ------- Just make life easier: TeraTerm 2.3 http://hp.vector.co.jp/authors/VA002416/ttermp23.zip TTSSH 1.5.4 plugin http://www.cs.cmu.edu/~roc/ttssh154.zip ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the

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

Here's what we need for a BIG popularity boost: Good interfaces! Yeah yeah, i know, i'll be bitched at on how I should do it on my own, but one thing that always ticked me about MP3 - the lack of tools that do the job without the mess. What we need now is - an ID tag editor. Menu-driven, that means CLI or GUI. We need that, badly. Encoder - GUIs for X and MS Windows. Right now, encoding

HI, how do I get mods applied to Vorbis, I'm not a cvs guru and I don't know much about configure scripts. BeOS has this little quirk of being 99% POSIX compliant so these mods are required for vorbis to compile. To define int64_t in codec.h #ifdef __BEOS__ #include <inttypes.h> #endif run.c in vq needs 'changing' around line 141 becuase S_IFSOCK isn't

The merge of the format changes and new psychoacoustics is complete. There's still tuning work left to do (most notably there's a somewhat higher-than-acceptable level of background low-midrange/upper bass noise; this is due mostly to incomplete psychoacoustic modelling data in the 100Hz-500Hz range) however, at this point, pending bugfixes, the Vorbis 1.0 stream format is frozen.

In order to compile the latest Vorbis library on the Macintosh, the change appended to this message needs to be made to os_types.h.in. Then, anyone who wants to actually build it must first copy os_types.h.in to os_types.h by hand, since MacOS does not include a command line and thus cannot run configure. It really bugs me that the whole "platforms which don't support configure

David Mitchell <mitchell@ucar.edu> writes: > Ralph Giles wrote: > > > > On 15 Oct 2000, Maciej Stachowiak wrote: > > > > > I don't really know the details of the discussion, but I'd like to > > > present this issue from a user-oriented perspective, and from the > > > perspective of how Nautilus wants to use data files. > >

Hi everybody, I was just wondering if there is a DRM (Digital Right Management) solution to use with ogg vorbis. Any information welcomed. Thanx Chris <p>--- >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 'vorbis-dev-request@xiph.org' containing only the word

Hi everybody, I was just wondering if there is a DRM (Digital Right Management) solution to use with ogg vorbis. Any information welcomed. Thanx Chris <p>--- >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 'vorbis-dev-request@xiph.org' containing only the word