search for: pocision

Hi, I intend to use Ogg+Speex for voice recording/playback in a VoIP app. I am experimenting with liboggz to get acquainted with its API. As test files I am using some Ogg-Speex files converted from WAV files with speexenc.exe. I wrote a little testing app in Visual Studio 2010 under Windows 7. I defined OggzReadPage and OggzReadPacket callbacks with oggz_set_read_page()

I'm no expert, but it sounds to me like normal variable bitrate stream behaviour. With variable bit rate, you cannot calculate exact byte address from time reference. So, in general you estimate and get close to time reference requested. Whenever you need precise pocision, you should use constant bit rate or a byte offset (instead of time/milliseconds). FYI, in my apps, I use time to show progres to the user, but when I save a bookmark or pause, I record exact sample offset, and restart from there. So, time for UI, samples/bytes for hidden/underlying code. Miki....

...blems seeking with liboggz I'm no expert, but it sounds to me like normal variable bitrate stream behaviour. With variable bit rate, you cannot calculate exact byte address from time reference. So, in general you estimate and get close to time reference requested. Whenever you need precise pocision, you should use constant bit rate or a byte offset (instead of time/milliseconds). FYI, in my apps, I use time to show progres to the user, but when I save a bookmark or pause, I record exact sample offset, and restart from there. So, time for UI, samples/bytes for hidden/underlying code. Miki....

...gt; > > I'm no expert, but it sounds to me like normal variable bitrate stream > behaviour. With variable bit rate, you cannot calculate exact byte > address from time reference. So, in general you estimate and get close > to time reference requested. Whenever you need precise pocision, you > should use constant bit rate or a byte offset (instead of time/milliseconds). > > FYI, in my apps, I use time to show progres to the user, but when I > save a bookmark or pause, I record exact sample offset, and restart > from there. So, time for UI, samples/bytes for hidde...

...gt; > > I'm no expert, but it sounds to me like normal variable bitrate stream > behaviour. With variable bit rate, you cannot calculate exact byte > address from time reference. So, in general you estimate and get close > to time reference requested. Whenever you need precise pocision, you > should use constant bit rate or a byte offset (instead of time/milliseconds). > > FYI, in my apps, I use time to show progres to the user, but when I > save a bookmark or pause, I record exact sample offset, and restart > from there. So, time for UI, samples/bytes for hidde...