similar to: Vorbize.c

Hey all...I'm trying to use the decoder_example.c in the examples directory to decode a .ogg file that was encoded by using the binary encoder ogglame.exe and encoded via the encoder_example.c. I'm running into a problem with the decoder though. It plays FINE under the WinAmp plugin but I when I try and use the decoder_example.c to decode the file it says "End of file before finding

Hey all...for whatever reason when opening up the vorbis_vc6 project in Dev Studio bitwise.c and framing.c are still in the project. From my understanding these files are only in the ogg library now. If I try to compile the project as is, it fails because it can't find the files. Simple solution: Delete the two files. I just thought I'd give somebody a heads up.... Keep up the great

Hey all...I'm getting "Missing header in logical bitstream." error when trying to decode a Ogg file stream. I know the file is good because it plays fine in WinAmp etc, etc. The funky part to this is that I'm wrapping my own headers around each "packet" and now I'm trying to de-wrap them and I'm running into this problem. What I'm wondering is if vorbisfile

Can anybody tell me where I can find some info on the new books? I noticed there are now A-E. What exactly does this mean? How does it translate to higher and lower sampling frequencies and bit rates? Ideally I'd like something in the 11kHZ, 8bit mono area... I also noticed this struct: /* CD quality stereo, no channel coupling */ vorbis_info info_B={ /* channels, sample rate, upperkbps,

Hey. Last night I hacked grip so that it'd allow me to use vorbize and comments with grip. It's very ugly because grip'd need a bit of rearrangement in order to facilitate the way the vorbis comments work (that is, the comments are not added in after the encoded file has been written). Any one who wants to use it should patch grip-2.94 (http://www.nostatic.org/grip), and make sure you

I've been trying to tackle the vorbis source. I ran across what I think is a missing dependency in the vorbis-tools directory. Since ogg123 and vorbize are staticly linked to libvorbis and vorbisfile, when those file change, the executables should be rebuilt. Below I've attached a patch. (I hope it works. I am sort of new to patch and diff.) BTW, I've been trying to find a good

Howdy.. I've got a couple little patches here. 1. vorbis-tools needs getopt. Since it's already sitting in the source tree for cmdline I set up cmdline to make a getopt.a that gets used for both. Also, since mp3tovorbis is a shell script, it needs to be installed 755 not 711 (unless I'm missing something). 2. I've found that both tru64 and irix 5.3 won't give int64_t

Hi! I want to pipe stdout/stderr from vorbize for wrapper scripts. But as it doesn't send any "\n"s it doesn't work correctly. I solved it by adding if (param.verbose == 1) { fprintf (stderr, "\n"); } into appropriate position in vorbize.c. Could somebody please implement this nicely? Something like "-e" option in cdparanoia. Thnx. Bye, Peter Surda

I've fixed a heck of a lot of stuff in the time frame of just over ten minutes. And you all care... right. I actually ran Vorbize, and discovered some stupid bugs (e.g., segfault???). Fixed. Both Vorbize and Ogg123 should now speak fluently in Monty's comment-eese. I'll be working on getting both to implement all the comment tags; I'm seriously considering dropping all comment

Hello, I've been trying to compile some things but have run into some problems. I've have the vorbis directory inside of /usr/src. I have compiled vorbis itself with no problems. I've also copied the results to their respective directories as per the README file. I've also compiled the XMMS plugin with no problem. However when it is installed in the

Here is patch with manpages for ogg123(1), mp3tovorbis(1) and vorbize(1). Manpages are in pod format, because it is the most readable man source, and are compiled by pod2man. all and clean for man/ work. Install and uninstall for man/ seem to work. Manpages are GPLed of course. <HR NOSHADE> <UL> <LI>text/plain attachment: manpages.diff </UL> -------------- next part

Hi All trying to compile asterisk under linux kernel 2.6.6. Currently under zaptel get the following error make linux26 Link /usr/src/linux-2.6 to your kernel sources first! make: *** [linux26] Error 1 as going from the readme. is 2.6 not compatiable with asterisk and should I go back to 2.4.26. Also has anyone got the sipura 3000 working with asterisk, both fxo and the fxs ports on the

I finally got around to getting this to a more-or-less working state. Right now, it does most of what vorbize does, plus support for encoding multiple files (this works, but needs some additions to sanely handle titles, etc. for multiple files). The name is temporary, until I think of something better. http://www.labyrinth.net.au/~msmith/oggenc-0.1.tar.gz Hopefully, it's mostly portable,

Folks, Has anyone successfully compiled the Vorbis source code on Windows 98 with Visual C++ 6.0?? FR __________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/

Hi, I have just signed up with Voxee.com and have attached my Asterisk server to dial them via IAX2. Below is the start of the log which dials the number and promply hangs up when the call is answered, with the logs saying that the channel is not compatiable. I have traced this down to the g.729 codec which I don't have installed. Any ideas on how to force that the codec not be used?

Hi R-Experts, I have a huge data file of size over 100MB, and this is in .dat format. Is it possible to work with this in the current version of R in Windows-XP machine? If not, please let me know the remedy of this. Can R handle large dataset like this? I know SAS is compatiable for this. But i want to try it in R. -- SUMANTA BASAK. [[alternative HTML version deleted]]

------- Forwarded Message The following patches should fix vorbis-tools to build on NetBSD. I'm not including the diff to the configure scripts, so you'll need to rerun autoconf in the toplevel and libao directory after applying these patches to the configure.in files. It also appears that vorbis-tools/libao/ao_libs.inc is automatically generated by a configure script but checked into

I just commited my modifications: vorbis-tools is back in the main build, but ogg123 is out of the vorbis-tools build. I am investigating the cross-platform libraries suggested. ogg123 silences "Clipping in frame x", can now play multiple files at once, and has a new stream handling format (resolves the get_stream() bug mentioned earlier). Vorbize has options for no comment and

Hi, In the last few days I''ve been working a lot on rewriting the dragdrop.js code. I''ve made changes for what I think is stronger object-oriented design and made more parallels between how Droppbables and Draggables are coded and instantiated. I have multiple selection and dragging of draggables working and droppables can accept multiple draggables in one drop. There are some

virt-v2v is not an option for me as all I have are the VMDK images and don't have the VMware software to covert to OVA first. I really don't understand what is going wrong. I also found https://access.redhat.com/site/solutions/20511 and that still doesn't work. Both /etc/fstab and grub.conf refer to the LABEL and not any device name. In the boot process I see it explicitly says it