Displaying 20 results from an estimated 10000 matches similar to: "FLAC: decoding to WAV in the future"
2007 Apr 01
0
Re: FLAC: decoding to WAV in the future
Hi Harry,
First of all, if you keep a copy of flac 1.1.4 then you will always
be able to decode the files. Why not make a backup of flac 1.1.4?
Second of all, flac is open-source, so somebody will always be able
to compile flac 1.1.4 for any new platform.
There are never any guarantees about the future. Some day, MP3 won't
decode on a new computer, AIFF and WAV might be unheard of.
2007 Apr 01
3
FLAC: decoding to WAV in the future
What Brian Willoughby means is that even though the future is
uncertain, you may trust FLAC. The format is mature enough so that
you won't see major changes preventing playback of files encoded by
older encoders, but even if that comes to happen, the playback
libraries on most software will be backwards-compatible, and FLAC is
lossless meaning that you may convert FLAC 1.1.4 to a possible
2007 Apr 01
0
FLAC: decoding to WAV in the future
2007/4/1, Ivo Emanuel Gon?alves <justivo@gmail.com>:
>
> What Brian Willoughby means is that even though the future is
> uncertain, you may trust FLAC. The format is mature enough so that
> you won't see major changes preventing playback of files encoded by
> older encoders, but even if that comes to happen, the playback
> libraries on most software will be
2008 Feb 06
4
wav to flac corruption
So some research and experimentation I think I found the problem, but I'm
not sure how to go about fixing it.
If I import one of the wav files into Audacity then export them as "16 bit
PCM" then they encode to flac and play fine. The files bitrates are
currently at 24. If I export them from audacity as a 24 or 32 (anything
higher than 16), flac fails on me. With a bitrate of 24, the
2008 Feb 07
5
wav to flac corruption
I have exactly the same problem.
I encoded a BWF file to flac and then then decoded back to wav, using
--keep-foreign-metadata, and I ended up with a bit-perfect copy of the
original BWF. So I was fairly confident that the flac encoding is
working correctly, the problem definitely appears to be with the flac
players.
Unfortunately it seems that the majority of flac players cannot play
24bit
2009 Aug 05
2
FLAC 1.2.1 on OS X 10.4.11
hi,
according to the FAQ flac supports multichannel formats. i had no
luck with 1.1.4 though ( "Untitled.aif: ERROR: unsupported number
channels 8 for AIFF" ), i guess that feature was added in 1.2?
unfortunately, the binary for 1.2 does not run on OS X 10.4 (says
libiconv is too old). i removed libiconv and reinstalled that from
source, but then flac 1.2.1 just prints
2009 Aug 05
1
FLAC 1.2.1 on OS X 10.4.11
yes that is what i did. got the "requires version 7.0.0 or later, but
libiconv.2.dylib provides version XYZ" (forgot which version i had
before). removed libiconv, downloaded compiled and installed the new
one (libiconv-1.13.1), then i just get
$ flac
Bus error
i reinstalled flac 1.1.4, still runs fine (but doesn't support
multichannel).
cheers, -sciss-
Am 05.08.2009 um
2008 Feb 06
2
wav to flac corruption
Thank you for the reply! I know that my system can play flac files, I've
played others I've managed to convert using both of those programs. I'm
only running into difficulty when it comes to these large WAV files. By
"Does not work" I mean that they do not play, and instead I receive the
errors I mentioned in my original post. I wasn't actually intending to use
2013 Dec 02
3
Encode wav to uncompressed flac
I thought that an uncompressed FLAC file provides better sound quality than
a compressed FLAC file.
To Erik: How to grab the revision before this one
https://git.xiph.org/?p=flac.git;a=commit;h=fc360735ce4d1aa88a94bfccdd3bea5bdd19a8d6?
Regards,
Maciej
----- Original Message -----
From: "Erik de Castro Lopo" <mle+la at mega-nerd.com>
To: <flac-dev at xiph.org>
Sent:
2008 Feb 05
2
wav to flac corruption
Hello,
I'm attempting to convert fairly large WAV files (90 - 800 MB each) using
flac but the files do not work after the encoding. (The play fine in wav
format)
Command I'm using:
flac --verify -8 file.wav
Attempting to run the file with either flac123 or the default player for
Ubuntu (Movie Player?) results in the extremely terse messages:
Default Player: "An Error Occurred:
2014 Dec 15
2
[PATCH] for flac/decode.c
On Dec 14, 2014, at 10:02 AM, lvqcl <lvqcl.mail at gmail.com> wrote:
> Currently the header of a decoded WAV file can be different to the
> original WAV file because FLAC doesn't preserve 'fmt ' chunk.
>
> For example: create a 24-bit stereo .wav file with WAVEFORMATEXTENSIBLE
> header with channel mask == 3. Encode it to .flac then decode back to .wav.
> FLAC
2008 Feb 08
1
how to get flac fingerprint from a wav?
Thanks for all the responses to my question.
I think I can use shntool hash option for my project
I did not find in the shntool documentation or flac documentation that the
hash or st5 always would match the flac fingerprint. But at least in a
couple tests I did they matched. And I found some more comments around the
internet indicating they were the same.
-----Original Message-----
From:
2008 Feb 08
2
how to get flac fingerprint from a wav?
Great info. I found some descriptions of st5 (md5 fp) and ffp, where
I assume that "fp" is just a Taper abbreviation for "fingerprint" -
or signature as it's called in the flac header. However, I could not
find these utilities or source code. What I found looked like
instructions for a gui-based program. I think it would be easier to
support Mac if st5 were
2007 Mar 29
4
Re: FLAC: same features as WavPack
Hello FLAC list.
As far as I know 24 bit FLAC support is broken. It often doesn't
compress the audio at all, but instead stores the chunks as verbatim
type (although the FLAC format supports 24 bit). Perhaps this is fixed?
If so, do let me know. I agree that perhaps 32 bit float/pcm isn't
entirely necessary when it comes to storing different qualities. But
when wanting to preserve
2008 Feb 07
4
how to get flac fingerprint from a wav?
In windows command line:
I have a wav file and would like to see what the flac fingerprint would be.
To do this I run flac to encode the wav file and write the flac file to the
hard disk. I then run metaflac to read the flac file and display the
fingerprint.
Is there an existing way or other utility to do this without generating the
flac file on the hard disk. I would think it could be quicker
2007 Feb 21
1
Re: Is FLAC fully cooked for OS X yet?
On 2/21/07, Brian Willoughby <brianw@sounds.wa.com> wrote:
>
> The key to Arek comment is that the project files only work with 1.1.2 FLAC.
> Even in those days, the Xcode project was not fully operational. I gave up
> on using it, and I think everyone else did. You basically have no hope of
> just pulling it out of the repository and expecting it to work.
Brian, you
2007 Jan 02
4
Is FLAC fully cooked for OS X yet?
On Jan 2, 2007, at 5:15 AM, Arek Korbik wrote:
> The XCode project files you found are meant to be used with FLAC
> 1.1.2. The FLAC repository now contains version 1.1.3 files, and there
> have been interface changes in that latest revision
> (http://flac.sourceforge.net/changelog.html#flac_1_1_3). That could
> explain your problems with compilation.
Well, now, no, I did download
2007 Mar 29
2
Re: FLAC: same features as WavPack
On Thu, 2007-03-29 at 12:53 -0700, Brian Willoughby wrote:
> > Hello FLAC list.
> >
> > As far as I know 24 bit FLAC support is broken. It often doesn't
> > compress the audio at all, but instead stores the chunks as verbatim
> > type (although the FLAC format supports 24 bit). Perhaps this is
> fixed?
> > If so, do let me know.
>
> Hi
2011 Apr 11
1
24 bit flac decoding efficiency
I am trying to decode 192k/24 bit flac on 542 MHZ risk processor, and I am
having problems. I seem to be right at the edge of what this processor can do.
So I am wondering what functions would be canidates for assembly code
optimization? Any suggestions? Or could an older version of code be a batter
candidate to use?
Dennis Kerrisk
720-542-8504
303-668-0736
dennis_k85 at yahoo.com
2007 Mar 30
2
Re: FLAC: same features as WavPack
Harry Sack wrote:
>
>
> 2007/3/29, Brian Willoughby <brianw@sounds.wa.com
> <mailto:brianw@sounds.wa.com>>:
>
> There actually is no problem with 24-bit support, as I stated
> earlier. So before people start chiming in with "me too" - I'd
> like to request that you actually say what problem you're seeing,
> along with a few