similar to: new SEEKTABLE block

I first thought that it would be much better to create a single seek standard for FLAC. Then, I thought, why couldn't someone just create the optional SEEKTABLE data after an initial encode, if they need this data? Since the checksums are a part of the FLAC format (unlike Shorten), and these checksums are on the data stream, not the metadata, so any additional metadata shouldn't matter or

On my lists of things to do for 1.0 were 1) improve seeking; and 2) speed up both encoding and decoding. Seeking seems better now (I added the SEEKTABLE and tweaked the search algorithm). On the way, one of my encoding experiments worked. By taking advantage of a relatively unused area in the Rice parameter space, I added an escape code for switching to flat encoding within a partition.

This is a fantastic selling point, and one that I've never really thought of. Back in the early days of etree (a whole three years ago ;) ), before we learned the virtues of MD5 sums for SHN downloads, I downloaded a Hornsby show from someone. Of course, an MD5 wasn't available, but when I decompressed and Shoren didn't throw a sanity error my way, I figured all was well. I burned

Please excuse me, I haven't yet dug into the code too far. What I'd like to do: I'm using ecasound to record for 24 hour periods, which pipes the output directly to flac. I would like to be able to decode sections of this (using until/skip) during recording/encoding. I understand currently that flac can't do this, unless I pipe into dd to skip after decoding (which would be an

I have read FLAC's "--help", the man-page, and the HTML documentaion, but there are a few things that I don't understand. 1. I'll start with the thing I'm most confused about. The --best option is synonymous with -l 12 -b 4608 -m -e -r 6. Why is that? Is not -l 32 better that l- 12? And you can have -r 0,8 without using --lax, and -r 0,16 with --lax. 2. The --lax option

Hi! I've been using a little C++ program I've written to encode flac files. The program does this in the usual way (I think), by inheriting a class from FLAC::Encoder::File, and passing it chunks of raw samples through process_interleaved()... Anyway, the program works beautifully, and I've now decided to try and add some metadata to the encoded flacs. Eventually, there will be vorbis

Ok, the patch from 2003 about improving seeking still didn't make it to CVS, so here is another try. I made some benchmarking with the test_seeking utility from flac sources to show how bad the current seeking is, especially without seektable. Track used for the experiment had about 50 minutes. In the following table is average number of seeks and number of decoded frames required for one

As far as I can tell I've found a serious bug in the command line flac encoder :( I have created many hundreds of flac files and I was very annoyed to discover that the XMMS flac plug-in had intolerably long seek times, but since that had been mentioned on this list a bunch of times without anyone actually investigating, I thought I had better actually find the BUG which causes this. 1. I

When I was trying to find yesterday's xmms-plugin bug, i have noticed that seeking in stream without seek-table isn't very good. With attached patch it is much better. -- Miroslav Lichvar -------------- next part -------------- --- src/libFLAC/seekable_stream_decoder.c.orig 2003-02-26 19:41:51.000000000 +0100 +++ src/libFLAC/seekable_stream_decoder.c 2003-07-09 23:49:35.000000000 +0200

sorry about the delay... first, yes you are calling it correctly. if your encoded files have max_framesize == 0, then that should mean that either 1) you were using the command-line flac to encode to stdout; or 2) you are using libFLAC directly. if 2, you can replicate the functionality that is in src/flac/encode.c:metadata_callback() to write back statistics and seek table to the metadata in

The attached patch adds the missing FLAC__metadata_object_seektable_*() functions from FLAC's metadata object methods (FLAC/metadata.h) to FLAC++'s SeekTable class. Of the 11 functions in the C API, only 4 are currently in the C++ API, this patch adds the missing 7. If this patch is ok, VorbisComment will be next. A quick look tells me only 5 out of 13

Hi all, A few (possibly dumb) questions about decoding.. 1. Is it possible to know the total size of FLAC metadata blocks in advance? Do I really need to parse all metadata blocks until I see the METADATA_BLOCK_HEADER with last-metadata-block == 1? 2. Is there a generally accepted best-practice for seeking if there is no seektable present in the file? The format states *"It is possible to

According to http://flac.sourceforge.net/format.html#metadata_block_streaminfo : "FLAC supports from 4 to 32 bits per sample. Currently the reference encoder and decoders only support up to 24 bits per sample. " This is why I'm confused. I though one of the benefits of FLAC was it's ability to encode in word lengths longer than 16 bits. MW -----Original Message----- From:

On 12/11/06, Josh Coalson <xflac@yahoo.com> wrote: > --- Avuton Olrich <avuton@gmail.com> wrote: > > I'm attempting to decode part of a largefile flac whose seektable is > > broken or missing and the file is shorter then it's supposed to be, > > when I use 1.1.2 it decodes fine, when I use 1.1.3 it fails > > > > flac --decode --skip=719:58.0

> From: Cristian Rodr?guez <crrodriguez at opensuse.org> > Sent: Sunday, May 6, 2012 8:24 AM > > El 05/05/12 02:23, Bastiaan Timmer escribi?: >> The attached patch adds the missing FLAC__metadata_object_seektable_*() >> functions from FLAC's metadata object methods (FLAC/metadata.h) to >> FLAC++'s SeekTable class. Of the 11 functions in the C API,

Awesome, I'm psyched for 1.0.3.... the ID3v1 winamp2 support will be a neat addition, as is the faster decodes. Will 24-bit audio play nice with the final public version of 1.0.3? MW On Tue, 11 Jun 2002, Josh Coalson wrote: > One more thing... you will probably have to > > chmod +x flac-1.0.3_beta/test/test_streams.sh > > before doing the 'make check'. > >

Hello , you've been written that file format is frozen. does this mean that i'll be able to play files, commpressed today, say, 1-2 years after? thereby the next question is coming. what kind of strategy do you plan to enable fast seeking? to write new seeking algoritm, or to add some data to .flac file. i ask of it because i want to write files on cd-r and so i'd like to know can i

First, thanks to everyone for putting in their time to make the first truly "free" lossless audio codec. I'm co-founder of etree.org, the largest online community of lossless audio traders (currently 12,000 active members). We have been living in the shadow of Shorten for almost three years. Shorten, as most of you have come to realize, is extremely limited in terms of

OK, I made a few reorganizations to the code I've been wanting to do before 1.0. Nothing major, but if you are integrating libFLAC into another program it will be of interest: First, I made changes so that the encoder is now called a stream encoder everywhere. I was going to write a file encoder but realized the only use for such a thing would be if someone needed to seek through the input

I have noticed flac -S- isn't working correctly, '-' isn't handled in parse_option() nor in convert_to_seek_table_template(). It makes SEEKTABLE with one seek point. Similar options -V-, -e-, -p-, ... are not allowed since 1.0.4, I think best would be drop -S- from documentation too and use --no-seektable option only. -- Miroslav Lichvar