similar to: format & seeking

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

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.

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

I've checked in code that supports a new metadata block called SEEKTABLE. Basically, it is an optional, arbitrarily-long list of seek points, by sample number and stream offset. I also added command-line options to flac so you can specify seek points by specific sample number and/or a specific number of evenly-spaced seek points. The table cost about 18 bytes per seek point. This seems to

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'. > >

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:

Josh Coalson wrote: > yeah, flac doesn't have a 'gzip' fallback method > so any non-audio data will probably get stored > verbatim. I'm kind of reluctant to add a generic > compressor. If you wan't, you could come up with a > FLAC metadata block to store a gzip'ed chunk and I > could add that to the format. > I had the same thought when I was

Which plugins do you mean? I thought I remember Winamp, for instance, being able to do word-length reduction on the fly. The only place I can find this feature is in the Monkey's Audio codec plugin, though. Anyway, great news Josh! Thanks for making 24-bit audio support in FLAC a priority. :) MW On Tue, 11 Jun 2002, Josh Coalson wrote: > --- Mike Wren <mikew@etree.org>

> Any thoughts to perhaps integrating a quick sector-boundary check of the > wav file before encoding? Does this functionality extend beyond the scope > of FLAC? A quick check, and a "this wav file is not cut on a sector > boundary, continue y/n" warning would do the trick. Perhaps, an > option to > silence this check would be useful also. > it's easy to

Hi I wrote a function implementing an algoritm for simulation of spatial sampling plans (using geoR). I'm using a range of parameters to perform several simulation and sometimes this parameters create function errors wich cause the algoritm to stop. How can I avoid this ? Below there's a small example that I made to study the problem but I was not able to solve it. I've tried

Hi there, I'm the process of centralizing user authentication for a medium-sized network with a few Linux servers, some of them runnng samba. The idea is migrating all user definitions from both /etc/{passwd,shadow,groups} and samba tdb to a central LDAP directory. Most servers had the same set of users, but as each one was administered in isolation (no NIS not all samba servers were part of

On Mon, Nov 25, 2019, 11:15 Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Nov 20, 2019 at 03:06:55AM +0200, Nir Soffer wrote: > > diff --git a/v2v/v2v.ml b/v2v/v2v.ml > > index 03590c9e..58bb06c3 100644 > > --- a/v2v/v2v.ml > > +++ b/v2v/v2v.ml > > @@ -739,7 +739,9 @@ and copy_targets cmdline targets input output = > > | TargetURI

I'm moving this over to flac-users... Anyway, are you using Mike Wren's installer? I'm not familiar with that yet. Josh --- C&K Slagle <ckslagle@earthlink.net> wrote: > have winamp installed on a partitioned drive. > I installed the most recent version of Flac which includes the plugin > for > winamp. However, .flac files are not recognized in winamp.. Is it

FLAC 0.8 is out. This version has gone through and passed the new (larger) test suite, so I'm much more confident in the encoder and decoder for all kinds of input. FLAC is much closer to an official version now. There are also some new features: I have added two metadata blocks: 1) a PADDING block, and 2) an APPLICATION block so third-party app developers can register for an ID and write

I know this is probably a really stupid question, but why is FLAC's MD5 checksum different than the MD5 checksum of the original (input) .wav? I was under the impression that since each FLAC file contains metadata that can be changed without changing the audio (thus changing the MD5 checksum of that FLAC file) that the checksum of the original .wav file would instead be used. If that's

The Winamp3 hit the streets yesterday, so i gave the FLAC Winamp3 plugin a shot (dragged cnv_flacpcm.wac to the Wacs/ directory, yadda yadda) and received the following error message when starting Winamp3: --- Studio.exe - Entry point Not Found The procedure entry point_chkesp could not be located in the dynamic link library MSVCRTD.dll. -- It's unable to play .flac files, but still plays

Just an FYI... On my RH8 Duron 800MHz box, after running ./configure --enable-3dnow && make && make check && make install I received the following errors: =================== 2 of 8 tests failed =================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/home/mw/flac-1.0.5_beta1/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory

When I asked, | > If you're going to run flac -t later to test | > the .flac file, isn't it redundant to have verification on during | > encoding? Fearless Leader Ace Coalson responded, | yep. OK. | > If you know ... that -V was used | > during encoding and that flac reported "Verify OK," is there any | > reason to test the file? | nope, unless you suspect

When using oVirt >= 4.3, we can enable the NBD based backend in imageio by specifying that we transfer raw data when creating a transfer. With the NBD backend, we can specify qcow2 disk format. I think we need a way to expose the capabilities of the output to the user. For example, can we use qcow2 format. Issues: - I hacked qemu-img convert command line to always use -O raw instead of

Hello there! I'm creacting a loop for(i in 1:n){...}within which I build a nls model at each iteration. for some of the values of i, the algoritm in the nls function doesn't converge or cannot find a solution and consequently an error message is produced, and so my loop is interupted. The errors don't really matter to me as all the other values might still be useful and therefore I