Displaying 20 results from an estimated 10000 matches similar to: "Possible bug"
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
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
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
0
Bug with FLAC raw encoding
On Fri, 2 Feb 2001, Josh Coalson wrote:
> this is probably a good point to remind everyone that FLAC is still
> beta so don't delete your originals! everyone here has been good
> about it but I'm dreading that message from someone who lost all their
> stuff.
You mentioned that one update was to include an md5 signature of the
compressed stream to detect errors? Could you
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
2
Bug with FLAC raw encoding
On Fri, 2 Feb 2001, Josh Coalson wrote:
> sounds great. I've been thinking about adding a
> 'what uses FLAC' set of links to the web page...
> please keep me posted.
The latest version of my cue+wav splitter supports .flac files. Hope to
get it released this weekend. Will eventually be at:
www.lameb.fsnet.co.uk
It also supports .shn and .ape. I've seen shorten
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
1999 Dec 06
0
Fwd: Re: openssh on a non-PAM system?
FYI. Maybe ppl with access to Solaris can look at this.
Niels.
From: mark at salfrd.ac.uk (Mark Powell)
Newsgroups: comp.security.ssh
Subject: Re: openssh on a non-PAM system?
Date: 6 Dec 1999 14:10:21 -0000
Message-ID: <82gg4d$15ta$1 at plato.salford.ac.uk>
In article <x7zovrqhrv.fsf at bombadil.nic.net>,
Dan Lowe <dan at bombadil.nic.net> wrote:
>mark at salfrd.ac.uk
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
0
Auto-detecting wav input
Hi,
I notice that this still doesn't work:
$ shorten -x a.shn - | flac -V - a.flac
You have to put the -fw in there:
$ shorten -x a.shn - | flac -fw -V - a.flac
Could wav format not be the default. Or even better could flac not
auto-detact wav input, which is relatively easy?
Cheers.
Mark Powell - UNIX System Administrator - The University of Salford
Academic Information Services,
2004 Sep 10
0
0.6 release
Josh,
Those speed improvements are great. Quick test on an 365MB wav of Neil
Young's eponymous 1st album on a PIII 650E (Coppermine) under FreeBSD 4.2:
User Sys MB
shorten23 0:46s 4.0 208.3
shorten31 1:24s 5.3 208.6
flac CVS 4:21s 7.5 199.2
It's getting near to be a useful replacement for shorten. Only 3x slower.
Any idea why it uses so much more sys time? I would've thought
2004 Sep 10
0
0.6 release
--- Mark Powell <M.S.Powell@salford.ac.uk> wrote:
> Josh,
> Those speed improvements are great. Quick test on
> an 365MB wav of Neil
> Young's eponymous 1st album on a PIII 650E
> (Coppermine) under FreeBSD 4.2:
>
> User Sys MB
>
> shorten23 0:46s 4.0 208.3
> shorten31 1:24s 5.3 208.6
> flac CVS 4:21s 7.5 199.2
>
> It's getting near to be
2004 Sep 10
1
Monkey Audio Open Source?
--- Mark Powell <M.S.Powell@salford.ac.uk> wrote:
> Thought this may be of interest to this list:
>
>
http://66.96.216.160/cgi-bin/YaBB.pl?board=general&action=display&num=995374789
>
> Down the bottom the author of Monkey's Audio claims he's going Open
> Source.
that would be great... the list of usable OS audio codecs
is pretty small and more sharing of
2004 Sep 10
0
Bug with FLAC raw encoding
On Fri, 2 Feb 2001, Josh Green wrote:
> 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?
> I'm excited about FLAC!! I've been looking for a good GPL lossless RAW
> audio compressor for
2004 Sep 10
0
flac can occasionally be worse than shorten
On Thu, 15 Feb 2001, Josh Coalson wrote:
> well, I took a look at the files. from my
> knowledge of shorten there are two things it does
> that flac doesn't do:
>
> BUT, you have stumbled on some recordings where the
> LSB is 0 for much of the file. as a matter of fact,
> in
> the worse track (track 6) almost the entire signal in
> both channels is like that.
2004 Sep 10
0
beta 10 candidate checked in
On Fri, 25 May 2001, Josh Coalson wrote:
> 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
0
beta 10 candidate checked in
On Tue, 29 May 2001, Josh Coalson wrote:
> > AM_INIT_AUTOMAKE(flac, 0.9)
> >
> > I've never had to run autoconf manually before so I'm not really sure
> what
> > I'm doing.
> >
> hmm... not sure what the syntax error is; did you run aclocal first?
No. Had no idea I had to. I've gleaned from someone else's message that I
should be doing
2004 Sep 10
0
Re: beta 10 candidate checked in
On Wed, 6 Jun 2001, Josh Coalson wrote:
> > > my hunch is that your version of either automake or possibly
> > > autoconf is not recent enough.
autoconf v2.13
automake v1.4
I've upgraded to autoconf v2.50 and updated flac from cvs. The error is
being generated by aclocal anyway and that's part of automake v1.4.
> > No. He simply doesn't have xmms installed.
2009 Aug 08
0
floating point
Yes, WavPack is second in my list.
FLAC doesn't preserve every chunk? I thought it did. I only gave a quick try
but it seemed to have preserved even the most obscure chunks.
Let me check: it even seems to preserve "MIDI note associated to marker",
which is a very unknown metadata used by SoundForge (& even defined in a
buggy way), so I assumed it was saving them
2007 Nov 02
0
Re: Welcome to the "Flac" mailing list
That's a handy command, but I'm certain it won't work 100% for the
file in question. The chunks in that bad file claim the extra two
bytes are part of the file, so a wav format parser could come up
short. You have to edit existing data in the file in two places
before shortening the file - truncating the file is not enough by
itself.
The real problem is that the file was