similar to: the road to 1.0...

Displaying 20 results from an estimated 1000 matches similar to: "the road to 1.0..."

2004 Sep 10
5
flac command line usage (was: the road to 1.0...)
> > > It would be easier if FLAC understand the following command: "flac *.wav > > > *.flac" or "flac -d *.flac *.wav" > > > > > > for now I have to use some shell "tricks". > > > > > I assume you're using the DOS shell? because all unix shells I know will > > expand the globs first so this syntax cannot
2004 Sep 10
2
flac worse than shorten
I've found a wav of an entire album that shorten compresses better than flac. Is this supposed to be possible? wav 388,374,044 flac-6 239,109,203 shn 236,457,697 Cheers. Mark Powell - UNIX System Administrator - The University of Salford Academic Information Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888
2004 Sep 10
1
xmms-plugin problem
ok, I tried a few songs and it seems to me, that the seek problem appears only with some songs. Also I have songs where is no problem. Josh, should I mail you a problematic song? Jan On Tuesday, 15. January 2002 15:38, you wrote: > --- Jan Suhr <jan.suhr@freenet.de> wrote: > > hello! > > I use flac 1.0.2 with xmms 1.2.5 . The problem appears when I use > > the scroll
2004 Sep 10
4
the road to 1.0...
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
2004 Sep 10
3
FLAC status
Hi, How's the testing going? I compressed 194 individual .wav files (totaling 8.54GB) which contained tracks ripped from many varied albums. I unflacced them and compared their md5 signature with the same from the original .wav. They were all perfect. I didn't use the -V option just in case of any chance of mis-reporting. I hope to test it with the complete collection of ~41GB
2004 Sep 10
2
Bug with FLAC raw encoding
> > I found a bug with FLAC v0.6 raw encoding. It > appears that the file > > pointer in the source file is not reset after > seeking to the end for > > checking the size. I've attached a patch. > > What's the impact? Do I have bad .flac files? > If you are piping raw samples in, no. The bug only occurs when you give an input file AND use -fr. In that
2004 Sep 10
2
flac worse than shorten
On Wed, 7 Feb 2001, Josh Coalson wrote: > Mark, if it's possible, can you do me a favor... > Try encoding the album as individual tracks and > compare sizes. The reason I ask is because of > the way FLAC frames are numbered in the frame > headers (if you check the format page you'll see > what I mean). Sorry, I don't :( I've split into individual files and
2004 Sep 10
1
Re: flac and pipes problems (was: Possible bug)
I'll rearrange a little and respond: --- Mark Powell <M.S.Powell@salford.ac.uk> wrote: > Also, when flac takes input from stdin it fails to > fill in the wav size > fields correctly, whereas shorten has no problems > with this: i.e. >... > You can see it puts a data chunk size of zero in > there. > OK, this has been fixed in CVS. > Flac refuses
2004 Sep 10
2
corrupt/invalid wav
I posted the bug at http://sourceforge.net/bugs/?func=detailbug&bug_id=130992&group_id=13478 . Since all my other discs were encoding fine I thought that the wav file may be corrupt/invalid/or something. I opened them with cool edit and "saved as"ed them to my drive. These files encoded fine and the extraced/converted files have the correct md5sum. Is there a program that can
2004 Sep 10
1
flac worse than shorten ON SOME FILES
had to fix the subject... was getting under my skin! yeah, could you put up the FLAC version of the worst track that is less than 20 megs compressed? (I'll have to grab it with a 56k modem). by worst I mean the one where shorten beats flac by the most. also: 1. what version of shorten are you using? 2. what command-line options for flac and shorten did you use on this track? thanks, Josh
2004 Sep 10
6
beta 10 candidate checked in
I have checked in all the latest into CVS and am going to start the test suite again. if all goes well I will probably release this as beta 10. this one should have all the configure stuff working with the new assembly infrastructure. I have tried to make it as easy as possible to port routines to assembly. all that's really needed now is to write the corresponding routine for a specific
2004 Sep 10
1
problem with file.wav > 700MB
hi. 1. I tried to encode some wav files with a size of 700MB - 1.1GB and got the message: "ERROR: no data sub-chunk". I used flac version 0.8 and 0.9. 2. It would be nice if flac displays the filename of the current used file. the reason: I started flac with a command like this: "flac -d 1.flac 1.wav; flac -d 2.flac 2.wav; flac -d 3.flac 3.wav; flac -d 4.flac 4.wav; flac -d
2004 Sep 10
1
Fwd: [Bug 468] New: - seg fault when change the playing FLAC file; FLAC plugin
Fine! I tried 1.0.2 and It works! thank you very much! Jan On Tuesday 04 December 2001 05:43, you wrote: > Jan, > I'm not sure that you've seen the messages go by in > the mailing list, but I think I fixed that bug and have > checked it into CVS. Could you try either CVS or > 1.0.2 which will be released this week an let me > know if it is fixed? Thanks, > >
2004 Sep 10
2
problem with file.wav > 700MB
On Mittwoch 09 Mai 2001 02:53, you wrote: > > > first I should say that it MIGHT not be because the file is > > > large. the wave reader in flac is pretty rudimentary and if there > > > is any sub chunk between the wave header and data sub chunk flac > > > will give you that error. could you inspect the wav file to see > > > if that's the case?
2004 Sep 10
4
beta 10 candidate checked in
> > I have checked in all the latest into CVS and am going to start the > > test suite again. if all goes well I will probably release this as > > beta 10. > > > > anyway, try it out and let me know if anything bad happens! it > > should be a short jump from beta 10 to 1.0. > > I've just checked out the latest from scratch. There is no configure
2004 Sep 10
2
flac can occasionally be worse than shorten
well, I took a look at the files. from my knowledge of shorten there are two things it does that flac doesn't do: 1. it estimates the mean of the signal for each block, subtracts it out and stores it separately. but this is pretty useless for the predictors that shorten uses as they are pretty insensitive to the mean (try different values of -m from 0 to whatever and note practically no
2004 Sep 10
1
Fwd: [Bug 468] New: - seg fault when change the playing FLAC file; FLAC plugin
---------- Forwarded Message ---------- Subject: [Bug 468] New: - seg fault when change the playing FLAC file; FLAC plugin Date: Fri, 23 Nov 2001 20:16:08 +0100 From: bugzilla-daemon@bugs.xmms.org To: jan.suhr@freenet.de http://bugs.xmms.org/show_bug.cgi?id=468 Summary: seg fault when change the playing FLAC file; FLAC plugin Product: XMMS Version: 1.2.5
2004 Sep 10
5
Bug with FLAC raw encoding
I found a bug with FLAC v0.6 raw encoding. It appears that the file pointer in the source file is not reset after seeking to the end for checking the size. I've attached a patch. I'm excited about FLAC!! I've been looking for a good GPL lossless RAW audio compressor for use with sound fonts. Sound font files contain 16 bit samples that are word aligned, so just treating it as raw
2004 Sep 10
0
flac command line usage (was: the road to 1.0...)
> > I think the easiest way to make all of this "just work" would be to > provide > > a default output filename for both encoding and decoding, e.g.: > > > > flac file.wav > > > > would produce file.flac, and > > > > flac -d file.flac > > > > would produce file.wav. That way, flac *.wav and flac -d *.flac > are >
2004 Sep 10
2
flac can occasionally be worse than shorten
> > I've never come across a sample like this which is > > why I thought it wasn't useful to add that > > functionality to FLAC... maybe if this is a common > > practice I should put it in. > ... > I've > compressed around 50 albums with flac and found 1 > where the LSB is 0. Even > if it's 1 in 200, that's going to be lots of cases >