search for: gab91c8b020a1da37d7524051ae82328cb

...FLAC__metadata_object_seektable_template_*(). If the client does not > support seeking, the SEEKTABLE will have inaccurate offsets which will > slow down or remove the ability to seek in the FLAC stream. Also, take a look at this: https://xiph.org/flac/api/group__flac__metadata__object.html#gab91c8b020a1da37d7524051ae82328cb Hope that helps. Also, as I'm always extra curious when FLAC is used for non-audio purposes: could you perhaps say a little bit about what kind of signals you're compressing? Kind regards, Martijn van Beurden

...table_template_*(). If the client does not >> support seeking, the SEEKTABLE will have inaccurate offsets which will >> slow down or remove the ability to seek in the FLAC stream. > > > Also, take a look at this: > https://xiph.org/flac/api/group__flac__metadata__object.html#gab91c8b020a1da37d7524051ae82328cb > > Hope that helps. Thanks, I have looked at the wrong place (at the encoder documentation, not the metadata). Is the seektable written at the beginning of the file in the metadata block or can there also be a second metadata block at the end? If it's written at the end could I just c...

Hello, I'm using flac to compress s signal data during capture. The sample rate is almost a thousands time higher compared to audio (40 MHz), resulting in a lot of data very quickly. I'm using the C API in my capturing application (mostly copy&paste directly from the example) and it works so far, but unfortunately for longer captures there is no seeking information. How can I tell

...does not >>> support seeking, the SEEKTABLE will have inaccurate offsets which will >>> slow down or remove the ability to seek in the FLAC stream. >> >> >> Also, take a look at this: >> https://xiph.org/flac/api/ >> group__flac__metadata__object.html#gab91c8b020a1da37d7524051ae82328cb >> >> Hope that helps. > > Thanks, I have looked at the wrong place (at the encoder documentation, > not the metadata). > > Is the seektable written at the beginning of the file in the metadata > block or can there also be a second metadata block at the end? > >...