search for: vorbis_packet_blocksize

..., what i have achieve :) let's see logical vorbis stream (actually i have no stream, coz i have rid of ogg). first three packets - identification, comments and codebooks. then goes a packet, which, as i understood, is just auxiliary for the next one. In addition, it holds (it can be found via vorbis_packet_blocksize) size of pcm data, that the next one holds. In general every packet holds part of size of pcm data in next packet, i.e.: ? ? ? cur = vorbis_packet_blocksize(&m_vorb_info, &m_packets[cur_packet_num]); ? ? ? if ( cur <= 0 ) ? ? ? ? ?m_packets_real_lengths[cur_packet_num] = 0; ? ? ? el...

...o added an ov_test() function as a fast partial open that verifies the vorbis-ness of a file (and loads the headers for perusal), but doesn't seek to learn the chain structure or total length. A partially open file can then be fully opened using ov_test_open(). Libvorbis now has an official vorbis_packet_blocksize() function to learn the block size of a packet without decoding it. Libogg also has one new function, ogg_stream_packetpeek(), which fetches the next packet in a logical stream without removing it from the stream head. None of these changes should affect binary compatability with prebuilt applicat...

...dicate that it doesn't know. For the last packet on a page, it uses the page's granulepos. Q1. Is this accurate? ---- I want to know the granulepos of individual packets. It appears that Ogg cannot provide me this information. Glancing at vcut, it appears that I can use the function vorbis_packet_blocksize() to determine the number of samples contained in a given vorbis packet. But I have no idea why the vcut function get_blocksize() adds the packet's block size to the previous packet's blocksize and divides by 4. Q2. How does vcut's get_blocksize() work? ---- The spec says that the...

...orry for the somewhat-overkill nature of explaining this bug, but some people have been doubting it so I'm going to give the evidence nessesary to prove the nature of it. If you send page-aligned data to libshout (via shout_send) it segfaults on the first page containing vorbis data within the vorbis_packet_blocksize function. Gdb traceback as follows: #0 0x282da38a in vorbis_packet_blocksize () from /usr/local/lib/libvorbis.so.2 #1 0x28419827 in blocksize (vd=0x8234400, p=0xbfbff54c) at vorbis.c:61 #2 0x28419aa4 in send_vorbis (self=0x81c6a80, data=0x827d014 "OggS", len=8153) at vorbis.c:124 #3...

...orry for the somewhat-overkill nature of explaining this bug, but some people have been doubting it so I'm going to give the evidence nessesary to prove the nature of it. If you send page-aligned data to libshout (via shout_send) it segfaults on the first page containing vorbis data within the vorbis_packet_blocksize function. Gdb traceback as follows: #0 0x282da38a in vorbis_packet_blocksize () from /usr/local/lib/libvorbis.so.2 #1 0x28419827 in blocksize (vd=0x8234400, p=0xbfbff54c) at vorbis.c:61 #2 0x28419aa4 in send_vorbis (self=0x81c6a80, data=0x827d014 "OggS", len=8153) at vorbis.c:124 #3...

Hi, I have a question regarding vcut. In the man page, it says: DESCRIPTION vcut reads an Ogg Vorbis audio file and splits it at the given cutpoint, which is a sample number. <p>What I want to do, is to cut an Ogg Vorbis file at a given time. Say, I have an Ogg Vorbis file, which is 1 hour long, and I want to cut it into two half hour parts. With a fixed bitrate