similar to: Bug: end-of-line in FLAC console output

> I was wrong about it going up to 11 - it actually goes up to 12. Too bad. I thought for a minute there that it goes up to eleven because... "Well, it's one louder, isn't it? It's not ten. You see, most blokes, you know, will be playing at ten. You're on ten here, all the way up, all the way up, all the way up, you're on ten on your guitar. Where can you go from

On Tue, Dec 27, 2016 at 04:13:28PM +0000, oresteszoupanos at hotmail.com wrote: > > That's great! I reckon when the release happens someone should also make a Hacker News post and maybe also certain sub-reddits would like to know about it. This might be overkill, but we could also set up a Facebook Event for the next release. It would be of absolutely no benefit to FLAC, but it might

On Wed, Nov 16, 2011 at 05:41:21AM -0800, avuton at gmail.com wrote: > Hate to be Capt. obvious here, but there's a lot of development going > on here that should be encouraged. If the FLAC project isn't going to > open up, it would make a lot of sense for someone to take over > maintenance on a github account with the git-cvsimport or such. I > don't see anyone

Hi all, Quite some time ago, it became clear that Windows 10 would feature out-of-the-box decoding support for the FLAC format. However, I discovered today that Windows 10 will feature FLAC encoding support as well, in the CD rip feature of Windows Media Player. It seems that Microsoft decided to take the reference implementation, as the generated files have "reference libFLAC 1.3.0

I don't think you guys should worry too much about messing up old decoders, but no matter what you choose to do FLAC MUST REMAIN LOSSLESS. On Thu, Mar 14, 2013 at 5:06 PM, <flac-dev-request at xiph.org> wrote: > Send flac-dev mailing list submissions to > flac-dev at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit >

Hi all, The latest version of FLAC has been releases. See: https://xiph.org/flac/index.html https://xiph.org/flac/changelog.html The source tarball and Windows binaries are available (with md5 and sha256 checksums) at: http://downloads.xiph.org/releases/flac/ The source tarball is also available at: https://sourceforge.net/projects/flac/files/flac-src/ and similarly the

On Jul 14, 2015, at 8:18 AM, Declan Kelly <flac-dev at groov.ie> wrote: > On Mon, Jul 13, 2015 at 01:28:22PM +0200, mvanb1 at gmail.com wrote: >> FLAC is not the only one though, Apple Lossless has been added >> to the mix in the same way, but (properly) creates smaller files. > > Can anyone on the list (possibly someone who works for MSFT) get this > fixed before

On Jan 7, 2011, at 18:08, Declan Kelly wrote: > On Fri, Jan 07, 2011 at 05:11:26PM -0800, brianw at sounds.wa.com wrote: > [NIN 24/96] > >> Thanks! That's interesting to note. I think that I ended up with >> the true 24/96 files, but I am curious: How do you tell whether you >> have the full 24/96 or not? > > Extract to WAV, do a hex dump, and look for

Lots of comments throughout this one... On Jan 7, 2011, at 15:28, Declan Kelly wrote: > On Fri, Jan 07, 2011 at 02:22:51PM -0800, brianw at sounds.wa.com wrote: >> However, you should be aware that many modern producers use software >> to create their music, and when the software stores sound clips in >> MP3 format, what you end up with is music that sometimes looks like

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

Hi Justin, Are you saying that 24-bit support does not work for you? Which version of FLAC are you using? What platform? What kind of files are you trying to compress? I am not any kind of official spokesperson for FLAC, but this alleged report about 24-bit problems surfaced in Aug 2006. However, I have been successfully using 24-bit FLAC since June of 2004, and I have never seen a

On Mon, Sep 22, 2014 at 06:39:43PM +1000, mle+la at mega-nerd.com wrote: > Martijn van Beurden wrote: > > > I dropped -e because > > it's compression improvement isn't worth the slowdown, but it is > > easy for the user to add this anyway. > > I think we should keep -e but may print a warning. The reason to keep it > is so that we do not break some

Hi all, Google Security Team member, Michele Spagnuolo, recently found two potential problems in the FLAC code base. They are : CVE-2014-9028 : Heap buffer write overflow CVE-2014-8962 : Heap buffer read overflow For Linux distributions, the specific fixes for these two CVEs are available from Git here:

Hi, I meant that it seems problematic to write an updated file to itself, because the operation could erase the data before it is read. Unless you read the entire file first, or write to a temporary file which is then renamed. I deal with FLAC files that are over a gigabyte, meaning that this could easily exceed normal buffers. Just curious. I guess I could go test it myself... or

On 5/13/07, Brian Willoughby <brianw@sounds.wa.com> wrote: > If we ever reach this 64 GigaSample limit, the fact that FLAC is a > stream should allow multiple FLAC headers to be concatenated in a > single file - although that might be tricky. I believe you can do this with Ogg FLAC. The Ogg container manages the multiple FLAC streams. Theoretically, we'll never see limit

Hi Neil, I think you have a misunderstanding or two. What you want to do does not require "code." In fact, you might want to move your question from the FLAC-Dev list to the FLAC (User) list. I'm on both lists, so I did not realize that you were basically asking in the wrong place. No "coding" skills whatsoever are required to create seekpoint markers in a

On Jan 7, 2011, at 17:18, Paul Davis wrote: > On Fri, Jan 7, 2011 at 7:36 PM, Brian Willoughby > <brianw at sounds.wa.com> wrote: >> I'd like to borrow these ideas, or at >> least similarly-inspired ideas, and have FLAC streaming designed such >> that the stream can tell the playback software when to reset. > > the internals of the slim protocol does

i'ld just like to have a car unit that you can put a USB stick in, a friend has one for mp3 and it is just what i want (but w/ flac support)- now that 4GB USB sticks are around you can get a lot on there in flac! > --- Brian Willoughby <brianw@sounds.wa.com> wrote: > > > are there any car stereo flac players?

---------------------------------------- > CC: flac at xiph.org > From: brianw at sounds.wa.com > Subject: Re: [Flac] Build FLAC source on Mac OS X without Xcode? > Date: Sun, 22 Mar 2009 14:33:36 -0700 > To: jensiragh at hotmail.de > > I don't have time to look through error codes, but I can tell you > that I have always compiled FLAC the Unix way, via the command

I would also add that the "level" is only relevant to the reference encoder, as it is an alias to quickly set a number of parameters. Other encoders might make different choices. Also, I haven't looked in details at how the encoder works, but I think it is based on heuristics to decide which is the best compression method for a set of samples, and I'm not sure that it would give