similar to: Normalize?

--- Matt Zimmerman <mdz@debian.org> wrote: > Date: Thu, 29 Mar 2001 22:05:48 -0500 > From: Matt Zimmerman <mdz@debian.org> > To: flac-dev@lists.sourceforge.net > CC: Josh Coalson <xflac@yahoo.com> > Subject: Re: [Flac-dev] Normalize? > > On Thu, Mar 29, 2001 at 01:39:32PM -0800, Josh Coalson wrote: > > > --- "Jesse W. Hathaway"

I have been following flac development for some time now, but with the release of 1.0.4 I thought I would finally start the task of encoding my entire cd collection into flac format. After looking through the list archives and the webpage I still have a few unanswered questions. 1. What is the best method tagging method to use? Josh mentioned that id3v1 was preferred over id3v2 since it

Hi, My wife who has thousands of IMAP boxes keeps getting errors when moving mailboxes in Thunderbird in Windows. I am using the same server (dovecot test 77) with Thunderbird in Linux and don't see the problem. What happens is she moves the mail box and Thunderbird comes up with an error saying it can't access the old box (odd!?). It has however completed the move. The following

Hi there, I've finally had a deeper look and found the Lollipop routing issues root cause: Lollipop uses several routing tables instead of the default one for previous Android versions. The main routing table is used with lowest priority per default: root at hammerhead:/ # ip rule show 0: from all lookup local 10000: from all fwmark 0xc0000/0xd0000 lookup legacy_system 13000: from all

Hi, I was wondering if there have been any conversations with backup vendors like Veritas or EMC regarding better integration with ZFS. While I understand they can use the "native" mode of reading files from the filesystem, it would be great if there were agents that had options like making a snapshot and storing a "zfs backup" datastream that could be used for zfs restore.

I've been implementing Ogg FLAC support in an editor I'm working on, and I must admit to being frustrated by the lack of support for the codec on the Ogg layer... and this is more than lacking granulepos. The codec's I've worked with, and my own (Writ), use Page 0 for general information about the codec. Specifically, the samplerate, bitrate, quality, number of channels, all

Monkey's Audio lossless compressor (currently win32 only, free but not open-source except decoder) author is thinking to implement a kind of audiophile-quality lossy compression which would filter "noise bits" that are hard to encode lossless but which are (or should be) inaudible and thus improve lossless compression (avg. 300-450kbps). I think that implementing something like this

Thanks for reply.. I'll try and then i'll advise you if it woks Andrea Squeri Il 30/mar/2015 11:38 "Vil Brekin" <vilbrekin at gmail.com> ha scritto: > Hi there, > > I've finally had a deeper look and found the Lollipop routing issues root > cause: Lollipop uses several routing tables instead of the default one for > previous Android versions. The main

On Mon, 2003-11-17 at 11:04, Josh Coalson wrote: > could you clarify your plan... are you thinking about > 1) encoding to a FLAC container and using metadata blocks > for everything that is not data? > 2) writing your own container? > > 1) seems kind of impractical to do in a general way. > I'm starting to also think that 2) is the best route. I was originally

Yes, it's finally here. See the homepage for details, but here's a summary: - 10-15% decoder speedup - 24-bit input support restored - more robust plugins - new metadata block for Vorbis-style tags - vastly improved metadata editor - fixed bug with pipes and Windows - new libFLAC++, a C++ object wrapper around libFLAC - new metadata editing interface in libFLAC and libFLAC++ - and

I think it's more of a routing issue than anything explicitly blocking it, they use a new 'ip rule list' and per user settings that aren't well documented yet either, but where exactly to point I don't know. I haven't messed with android 5 much yet, it seems not ready enough yet for daily use, there isn't a single snapshot in the cyanogenmod repos, for example. So maybe

I thought some here may find this interesting... There has been discussion in Monkey's Audio forum about creating a new open source format for lossless audio compression with the intent of creating a *standard* for lossless compression, similar to what Xiph is trying to do with Ogg Vorbis. Some have even been tossing around the idea of trying to work in conjunction with Xiph on this, and a

I'm writing a program that plays FLAC files using the libFLAC API's. Is there a specific way I'm supposed to handle multiple STREAMINFO metadata blocks? For example, should I ignore all but the first, or all but the last? The format spec doesn't mention anything. Thanks, - Brian Waters

Hey, I've compiled DarkIce 0.6 dynamically linked to LAME 3.89. I'm running Slackware 8 and using gcc 2.95.3. Running DarkIce yields the following output: DarkIce 0.5 live audio streamer, http://darkice.sourceforge.net Copyright (c) 2000-2001, Tyrell Hungary, http://tyrell.hu Using config file: darkice.cfg Using POSIX real-time scheduling, priority 98 LAME version 3.89 (beta

It's certainly best to honor what the specification says. My assumption is that a "stream" could also be a continuous broadcast, not just a file. With a hypothetical server streaming FLAC bitstreams, I would assume that the most recent STREAMINFO is valid until another one comes along. If you're writing a file player, then perhaps you can trust the spec and assume

SELinux is considered as the biggest problem. On Thu, Mar 26, 2015, 22:37 Andrea Squeri <andrea.squeri at gmail.com> wrote: > Yes. The problem is lollipop. I tried to install tinc on my brother's > device which mount a cyano 10.1( android 4.2.2) and it works. > I don't understand which is the problem with lollipop. Is there a > firewall that block the packets? >

I posted to this list a couple years back and then again sometime a year ago about using Flac to compress SoundFont instrument files. I never got around to finalizing the specification for that project, and I have since realized that a more generic approach would be better. I registered the "SFFL" Sound Font FLAC application meta data ID. I would like to remove that, since it was never

Samuel, I had the same problem. I think it's because the port in darkice does not match the port icecast or shoutcast is listening on. I thought it was 8000 but it was actually 8001. Check that. Matt -----Original Message----- From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org]On Behalf Of Samuel Hathaway Sent: Friday, October 05, 2001 2:43 PM To: icecast@xiph.org Cc:

I switch to lollipop 4 months ago and I never had issue. So for my opinion it is ready for daily use. Before try tinc I had my vpn implemented with openvpn, and it works great on lollipop. I switch to tinc because i prefer a mash vpn topology versus a client/server topology. -- Andrea Squeri Inviato con Sparrow (http://www.sparrowmailapp.com/?sig) Il giorno venerd? 27 marzo 2015, alle ore

On 14-03-13 20:02, Declan Kelly wrote: > The next official release of the FLAC command line should really have > a "-9" option for absolute maxed-out big-memory CPU-burning compression. No. If you want such things, try TAK, OptimFROG, Monkey's Audio or even LA, you'll lose hardware compatibility anyway and they do much better than FLAC will with a -9 option. FLAC 1.0