similar to: Uncompressed size in bytes

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

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

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

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

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

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

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*

I have a wav file which has been converted to an ogg file with libvorbis via ffmpeg. However I've tested a few files just to make sure. I run a standard while loop to using ov_read to pull all the data out of ogg file. Using 4096 as the size to read each call. Watching my debug logs it is reading 2048 bytes each call. When I load the wav file the data chunk for the pcm data is 167680

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

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

I seem to have run into a slight problem in my decode/cache routine. For some reason, my ov_info struct is saying that the channels in the bitstream are zero. Is this normal for certain files, and zero signifies something, or is something wrong? The ov_info struct DOES get filled (it isn't NULL), but channels gets set to zero. This of course can cause problems while calculating the buffer

I am deeply sorry about the corrupt message just being sent; there seems to have been a compatibility issue with my mailer and my browser. This is an identical copy of the previous message: Hello Martin, Vorbis encoders are lossy, which is in a sense equivalent to converting the sample size of the raw PCM stream into something that would result in the desired bitrate. The "sample size"

Hi Thomas. On Thu, Oct 15, 2020 at 02:38:06PM +0200, Thomas Zimmermann wrote: > At least sparc64 requires I/O-specific access to framebuffers. This > patch updates the fbdev console accordingly. > > For drivers with direct access to the framebuffer memory, the callback > functions in struct fb_ops test for the type of memory and call the rsp > fb_sys_ of fb_cfb_ functions. >

Hi, this is my first post, I hope it's the right mailing list (or should it be vorbis@xiph.org?) I just downloaded "SDK for MacOS9" and tried to compile the "vorbisfile_example.c" sample with CodeWarrior for Mac 8 on a Mac OS 9.2 machine. I included the libOgg and libVorbis libraries in my project, but the linker cannot file ov_clear(), ov_read(), ov_pcm_total(),

On Tue, Oct 20, 2020 at 02:20:46PM +0200, Thomas Zimmermann wrote: > At least sparc64 requires I/O-specific access to framebuffers. This > patch updates the fbdev console accordingly. > > For drivers with direct access to the framebuffer memory, the callback > functions in struct fb_ops test for the type of memory and call the rsp > fb_sys_ of fb_cfb_ functions. Read and write

On Tue, Sep 29, 2020 at 05:14:36PM +0200, Thomas Zimmermann wrote: > At least sparc64 requires I/O-specific access to framebuffers. This > patch updates the fbdev console accordingly. > > For drivers with direct access to the framebuffer memory, the callback > functions in struct fb_ops test for the type of memory and call the rsp > fb_sys_ of fb_cfb_ functions. > > For

Hi Thomas. On Thu, Oct 15, 2020 at 02:38:06PM +0200, Thomas Zimmermann wrote: > At least sparc64 requires I/O-specific access to framebuffers. This > patch updates the fbdev console accordingly. > > For drivers with direct access to the framebuffer memory, the callback > functions in struct fb_ops test for the type of memory and call the rsp > fb_sys_ of fb_cfb_ functions. >

Hi Thomas. On Tue, Oct 20, 2020 at 02:20:46PM +0200, Thomas Zimmermann wrote: > At least sparc64 requires I/O-specific access to framebuffers. This > patch updates the fbdev console accordingly. > > For drivers with direct access to the framebuffer memory, the callback > functions in struct fb_ops test for the type of memory and call the rsp > fb_sys_ of fb_cfb_ functions. Read