search for: audiobanshee

I am hosting Mac OS X builds of flac 1.1.4 and 1.2.1, but my domain name changed earlier this year. So, those old links on flac.sourceforge.net for sounds.wa.com are now audiobanshee.com, e.g. http://www.audiobanshee.com/software/flac-1.1.4.dmg http://www.audiobanshee.com/software/flac-1.2.1.dmg I couldn't access SourceForge.net earlier today, maybe their site was down. My site is up, though. Brian Willoughby Sound Consulting

...for minimal file sizes without realizing that I could save another 40 bytes. Anyway, since metaflac can remove the Vorbis comment using the standard library, then you should be able to create a solution without modifying libFLAC. Brian On Feb 4, 2018, at 12:43 AM, Brian Willoughby <brianw at audiobanshee.com> wrote: > Gabriel, > > metadata_has_vorbis_comment is a FLAC__bool which defaults to false. There should be no reason to modify stream_encoder.c, but just modify the caller. > > The following command: > > metaflac —remove —block-type=VORBIS_COMMENT —don’t-use-padding...

Brian Willoughby <brianw at audiobanshee.com> ?????(?) ? ????? ?????? Sun, 31 Jan 2016 22:26:40 +0300: > My assumption is that the code was written to call flac_fopen() so that it is portable to every operating system, even those without fopen(). If you replace flac_fopen() with fopen(), then the tests won't compile on systems...

...e I don't expect it to be that significant in normal cases. > > Thanks for all replies, but I don't have the code at home. > I will create a patch with my changes for review. > > Regards, > Gabriel > > On Sun, Feb 4, 2018 at 9:57 AM, Brian Willoughby <brianw at audiobanshee.com> wrote: >> Correction, the flac command-line does create a 40-byte Vorbis comment by default. I just never noticed it before. I’ve been using —no-padding all these years for minimal file sizes without realizing that I could save another 40 bytes. >> >> Anyway, since metafl...

...ases it causes an 25% overhead! Of course I don't expect it to be that significant in normal cases. Thanks for all replies, but I don't have the code at home. I will create a patch with my changes for review. Regards, Gabriel On Sun, Feb 4, 2018 at 9:57 AM, Brian Willoughby <brianw at audiobanshee.com> wrote: > Correction, the flac command-line does create a 40-byte Vorbis comment by default. I just never noticed it before. I’ve been using —no-padding all these years for minimal file sizes without realizing that I could save another 40 bytes. > > Anyway, since metaflac can remove...

I am also philosophically opposed to changing the specification. That said, there's nothing wrong with adding a note to the specification about the common implementations, particularly the reference library. Then, future developers will know both the precise specification and still have the warning that they risk incompatibility by deviating from the reference implementation. I own devices

...ack, size: 146 [29.009834] read_callback, size: 146 [29.009844] read_callback, size: 146 [29.009855] read_callback, size: 146 ... <calls read_callback forever> I can send out some of the code fragments if needed. Thanks, Chris On Tue, Dec 12, 2017 at 4:44 PM, Brian Willoughby <brianw at audiobanshee.com> wrote: > Hi Chris, > > Have you tried the Standard C libflac option? Not that I have anything > against the C++ flavor, but I've only ever worked with the C API, to keep > things simple. Sorry for the brief response, but I wanted to reply quickly. > > Brian > &g...

...c_fopen() makes test_streams dependent upon libFLAC, but I do not understand why that is a problem. Doesn't the test software have to link to the flac libraries in order to test them? On Jan 31, 2016, at 1:01 PM, lvqcl <lvqcl.mail at gmail.com> wrote: > Brian Willoughby <brianw at audiobanshee.com> ?????(?) ? ????? ?????? Sun, 31 Jan 2016 22:26:40 +0300: >> My assumption is that the code was written to call flac_fopen() so that it is portable to every operating system, even those without fopen(). If you replace flac_fopen() with fopen(), then the tests won't compile on syste...

...ert flac -> wav -> mp3 -- it seems to work OK for me -- > > I guess if I get a high end player like the FiiO or PONY I might just use the FLAC files > directly > > thanks again > > fpe > > On Sun, Jun 5, 2016 at 6:14 PM, Brian Willoughby <brianw at audiobanshee.com> wrote: >> Hi Frank, >> >> On Jun 5, 2016, at 12:34 PM, Frank Esposito <fpesposito at gmail.com> wrote: >> > I have a flac file encode 92/24bit -- what tools are available to convert these files >> > to wave 44.1/16 bit so then I can convert to m...

This could make sense indeed. I suppose this is not a libFlac feature and that I should end up using libogg and or adding myself basic ogg support in order to support that ? Thanks ! 2017-01-28 7:37 GMT+01:00 Brian Willoughby <brianw at audiobanshee.com>: > Don't overlook the FLAC in Ogg container solution. That's established as a > standard for some time now, as far as I know, and would probably be better > than a new, proprietary multi mono bundle. I haven't used it myself, but > people have been talking about it...

test_streams currently depends on grabbag and (on Windows) on win_utf8_io libs. It depends on win_utf8_io only because it uses flac_fopen() function. It will become to depend on libFLAC when all file functions will be moved from win_utf8_io to libFLAC. Not a big problem, but it is possible to avoid this dependency by replacing flac_fopen() with fopen(). test_streams doesn't open/create

stream_encoder.c has the following code: /* try to keep qlp coeff precision such that only 32-bit math is required for decode of <=16bps streams */ if(subframe_bps <= 16) { ... But FLAC can convert 16-bit input to 17-bit if mid-side coding is used. So, does it make sense to compare subframe_bps with 17? (The patch is attached. What do you think about it?) -------------- next part

...t, as of now, it gives a nice demo application that just runs quickly in every browser, independently from any platform and has nearly zero maintenance cost.) -- Rillke > Subject: Re: [flac-dev] FW: flac (encoder, analyzer, decoder) tool now (also) available in JavaScript? > From: brianw at audiobanshee.com > Date: Tue, 20 Jan 2015 10:25:31 -0800 > CC: flac-dev at xiph.org > To: rillke at wikipedia.de > > I'm not sure that I understand your goal. In a browser setting, I would think that you want to decode a stream, not a file, because streaming should have less of a memory impa...

...en't done the analysis to say whether it's safe or not. I do recall discussions that might have been referring to this sort of thing, so look at the change log to see why the change came about. Brian Willoughby Sound Consulting On Apr 18, 2015, at 12:20 PM, Brian Willoughby <brianw at audiobanshee.com> wrote: > Hmm, I don't know the history of the code, but flac 1.2.1 stream_encoder.c has > > min_qlp_coeff_precision = FLAC__MIN_QLP_COEFF_PRECISION; > /* try to ensure a 32-bit datapath throughout for 16bps(+1bps for side channel) or less */ >...

Security is quite important, but I believe that audio quality and lossless performance trump security for nearly all users of flac. In other words, unless the bugs affect the lossless quality of flac, then those old downloads should remain available. Of course, place a notice about the potential for security issues, but let the users make their own decisions. Personally, I find it important to

On Jul 18, 2015, at 10:46 AM, Martijn van Beurden <mvanb1 at gmail.com> wrote: > Op 16-07-15 om 07:50 schreef Brian Willoughby: >> On Jul 14, 2015, at 8:18 AM, Declan Kelly <flac-dev at groov.ie> wrote: >>> Can anyone on the list (possibly someone who works for MSFT) get this >>> fixed before Win10 is released? >> What size differences are we talking

Hi, are there any plans for FLAC to implement spatial audio? Or maybe Atmos on FLAC? renatas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/flac/attachments/20170810/57a79181/attachment.html>

Don't overlook the FLAC in Ogg container solution. That's established as a standard for some time now, as far as I know, and would probably be better than a new, proprietary multi mono bundle. I haven't used it myself, but people have been talking about it for a while, and I believe that some "FLAC" users are actually working with FLAC in Ogg container files. Brian

Hi List! On flac--l I was advised to cross-post to this list. So here is an extended version: After compiling opusenc.js to JavaScript [1], now the flac tool is also available [2][3], too. s/Check out/Clone/ https://github.com/Rillke/flac.js ! I am slightly nervous about its license, the GPL and what CloudFlare is doing: It's melting a lot of content together into one file (but not

I'm trying to use libflac++ on a live internet audio stream. I don't see anything mentioned in the documentation that suggests this should not be possible, so I hope I'm not chasing down the wrong path (two weeks in). The encoder seems to be working fine and creates data for the write_callback, which I have coded to packetize that data and send it across the network. The question is