similar to: vorbisfile for Mac Classic

Hi guys, I'm working doing the Java->JNI->OggVorbis thing. As a test to get me going, I've just written a quick routine that dumps info about the file test.ogg in the current directory. The problem arises when I call ov_clear. I get a segfault everytime. Note that I am *not* doing any decoding (ov_read) at all, just ov_comment and ov_info. Should I only call ov_clear if I have

Hello - I have two files which play back in VLC correctly. They were encoded using this command: ffmpeg -y -i '/tmp/2e905b981d30324f9a0664cbabb3f59a20170406-21128-r0neh9.wav' -acodec libvorbis '/tmp/2e905b981d30324f9a0664cbabb3f59a20170406-21128-r0neh920170406-21128-146yyex.ogg However ov_pcm_total reports a zero length for one of the two files. Is this a problem with my use of the

Hello - I have two files which play back in VLC correctly. They were encoded using this command: ffmpeg -y -i '/tmp/2e905b981d30324f9a0664cbabb3f59a20170406-21128-r0neh9.wav' -acodec libvorbis '/tmp/2e905b981d30324f9a0664cbabb3f59a20170406-21128-r0neh920170406-21128-146yyex.ogg However ov_pcm_total reports a zero length for one of the two files. Is this a problem with my use of the

Hello - I send this to the vorbis-dev list yesterday, but I’m working if it would not have been better targeted at this list. Sorry for the spam if you are on both :) > Begin forwarded message: > > From: Jim Credland <jim at credland.net> > Subject: [Vorbis-dev] Zero length reported. > Date: 6 April 2017 at 15:43:18 BST > To: vorbis-dev at xiph.org > Cc: Maciej Dudek

Okay - so I stepped through the code slowly this morning making notes as I went. And I can see what’s wrong. The last Ogg header of the troublesome file contains -1 as the granule position. The spec says this has a special meaning "A special value of '-1' (in two's complement) indicates that no packets finish on this page." 4F 67 67 53 00 04 FF FF FF FF FF FF FF FF 16 A2

OK, thanks to the help of another forum user, I got my app compiled and working, but I now need to precache the OGG to memory. My current method somehow winds up in a loop or freezes the application. Here is y source for the decode/precache function. Why is it just freezing? I've let it run for about three minutes, thinking it was doing some heavy decoding, but I was wrong. Once this is

Hi, I use the following code: if (ov_open(NULL, &vf, const_cast<char*>(reinterpret_cast<const char*>(get_data())), get_size()) < 0) error = 0x100; else { vorbis_info* vi = ov_info(&vf, -1); Cvirtual_file f; const int cb_samples = ov_pcm_total(&vf, -1); const bool seekable = ov_seekable(&vf); So all data is already in memory and passed to

Hello all. I'm new to this list. I'm also new to coding with libvorbis and things, so please bear with me. :) I've been having trouble with libvorbisfile. My use of it is fairly simple, but when I try to ov_clear the vorbis file, it segfaults. I can attach or otherwise make availible some demo source code, but for now I'll just pull out relevant lines: //BEGIN PSEUDO CODE

Some months ago I tried to get some answers (and didn't) for a problem I've had with ov_pcm_total for files 8kb or smaller. I have no idea whether it should make a difference, but I operate inside Visual Studio, with C++ 6.0 and MFC. The value returned by ov_pcm_total doesn't agree with ov_read. My solution had been to add 0.2 to the buffer size, so that ov_read would make it to

I am wondering if buffer size for my decoding to pcm can be predicted dependably as follows. So far, the one problem I have had is when I have played a file of only about 5k. The buffer was a little less than 10% too small. I "solved" that by padding the result with an extra 20 percent. However, I have been told that I should be able to rely on the value of ov_pcm_total. char*

Hello, I've been looking to the libvorbisfile and got into troubles when trying to use it: I need to compile it on a PalmOS and the libvorbisfile must be compiled in ARM whereas calling code is in 68K. This implies that the interface ov_open_callback is not usable because the OggVorbis_File *vf must point to something in the target architecture (ARM) whereas the caller cannot do that. As

Hi Folks, i implemented the required callback funktions to open an ogg file from memory. Now ov_pcm_total() returns always 0, strange thing about is that ov_pcm_total does not call any of the callback funktions. I also like to mention that ov_info (which uses the read and seek callback funktions) delivers correct values. Thats why i doubt that there's an error in (the rather simple) callback

I get an access violation when calling ov_clear(). I know ov_open() worked because I used ov_info to get the sampling rate and number of channels in the .ogg file. I also know the FILE pointer and the OggVorbis_File structure are still in scope (they're member variables of the same class my deconstructor is in (where ov_clear() is called)). Anyone have any ideas? I opened the file using

I'm getting a lot of these from TOT make: /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h: In instantiation of 'llvm::LoopInfoBase<llvm::BasicBlock>': /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h:886: instantiated from here /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h:573: warning: 'class

Why ov_open_callbacks(fd_, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) takes so long to open OGG file? The OGG file has just 210 MB. It takes a lot of time open the file. I am working on OGG audio recorder and player. Thanks in advance! With kind regards, Pavel

I've been playing around with using ov_test and ov_test_open as an alternative to ov_open in the xmms plugin's vorbis_check_file function. xmms never bothers to cache the result of a file check, so it tends to happen rather a lot. Unfortunately ov_test_open returns OV_EINVAL because ov_test seems to have left vf->ready_state to OPEN rather than PARTOPEN. I'm presuming this is

On Mar 17, 2008, at 5:46 PM, Dale Johannesen wrote: > I'm getting a lot of these from TOT make: > > /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h: In > instantiation of 'llvm::LoopInfoBase<llvm::BasicBlock>': > /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h:886: > instantiated from here >

On Mar 17, 2008, at 6:22 PM, Devang Patel wrote: > > On Mar 17, 2008, at 5:46 PM, Dale Johannesen wrote: > >> I'm getting a lot of these from TOT make: >> >> /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h: In >> instantiation of 'llvm::LoopInfoBase<llvm::BasicBlock>': >>

Hey guys, currently wrapping my head around the vorbisfile API. The stream callback interface is really nice ! Great work. I'm running into two snags using it though. a) getting ov_bitrate on a seakable stream returns a long. When I print it as %ld, I get Bitstream is 2 channel, 44100 Hz, 0 version, -2147483648 bitrate I get this same number for any vorbis file. I checked them with

I wonder if anyone would have a comment on an experiment I have pretty much completed in my MFC/C++ project. With my simple libvorbis implementation, ogg decoding works just fine for files that are 10kb or larger. For anything smaller (actually, I don't have a 9kb file, so <= 8), it seems that I get an inaccurate value for ov_pcm_total. Though ov_read returns zero, I overflow the buffer