similar to: [Flac-users] Re: detecting encoding parameters?

The Winamp3 hit the streets yesterday, so i gave the FLAC Winamp3 plugin a shot (dragged cnv_flacpcm.wac to the Wacs/ directory, yadda yadda) and received the following error message when starting Winamp3: --- Studio.exe - Entry point Not Found The procedure entry point_chkesp could not be located in the dynamic link library MSVCRTD.dll. -- It's unable to play .flac files, but still plays

2007/10/15, David W. Tamkin <dattier@panix.com>: > > Harry, > > > so i was wondering what advantages it could give me to make a ffp > > file, because there is already a internally stored md5 checksum on the > > decoded audio data inside the flac file? > > Testing the .flac file against its internally stored fingerprint lets > you know that you have a

Guys, i have icecast2 running on an opensuse 11.3 64 bit os. unfortunately, opensuse comes with ices2 which only does ogg streaming - - > hence my need for ices0.4 i got the source and ran ./configure . there was lots of console output and in the end i saw; .Features: XML : yes Python : yes Perl : yes LAME : yes Vorbis : yes MP4 : yes FLAC : yes Then i did

Solution file still contained the removed in_flac project causing unnecessary errors on load. -------------- next part -------------- --- FLAC.sln.orig Wed Mar 13 18:23:38 2013 +++ FLAC.sln Sat Mar 16 19:14:43 2013 @@ -57,14 +57,6 @@ Project("{4cefbc7c-c215-11db-8314-080020 {4cefbc89-c215-11db-8314-0800200c9a66} = {4cefbc89-c215-11db-8314-0800200c9a66} EndProjectSection EndProject

> The best approach would be for you to report this bug directly to the > developers of the WinAmp FLAC decoder, and also electriQ. Also postet it to the developers of electriQ, but it's a closed source project and there's not much activity in their forum, so i'm not sure if anybody is fixing this very soon. Furthermore I think the problem is more likely in the Winamp2 Flac

> The best approach would be for you to report this bug directly to the > developers of the WinAmp FLAC decoder, and also electriQ. Also postet it to the developers of electriQ, but it's a closed source project and there's not much activity in their forum, so i'm not sure if anybody is fixing this very soon. Furthermore I think the problem is more likely in the Winamp2 Flac

Hello, I'm not sure if this is the right place to post my problem to, i'm not a developer but a user experiencing a possible bug in the flac decoder. using winamp 2.81 + in_flac.dll (tryed different versions eg 1.12 and 1.21) + Electri Q Winamp DSP plugin (all versions affected) Winamp crashes just before flac track ends (next track is also flac track) does NOT crash when playing mp3

The following changes since commit b78d8e4db10e57b8d82bb82e4e3662d5dedd7255: FLAC__bitmath_ilog2,FLAC__bitmath_ilog2_wide,COUNT_ZERO_MSBS: add gcc specific optimizations (2012-03-28 15:43:48 -0300) are available in the git repository at: git://github.com/crrodriguez/flac.git master for you to fetch changes up to 3a060556772c5d6a6464afddfda7c3ad2f93a306: Remove winamp2 plugin.

Okay, I've done a bit of work on flacpcm.cpp and the Winamp3 component workspace. I updated the workspace & projects to use the SDK for build 488 (based on GenericWACTemplate). I also fleshed-out the MediaInfo callbacks, so that standard Vorbis comment fields are reported (author, album, genre, date/year, title, track, description), although id3 tag info takes precedence. So flac

--- "David W. Tamkin" <dattier@panix.com> wrote: > An enthusiastic FLAC user on another list to which I subscribe said > that FLAC > has a function to display on screen the stored fingerprint that a > FLAC file > has of its source WAV. That sounds wonderful, because it allows a > user to see > whether two differing FLAC files might come from the same WAV but

Two wavs I tried to encode tonight got errors near their ends, saying something like "skipped unknown sub-chunk 'LIST'." These occurred at 97% into one file and 98% into the other. If I hadn't brought the DOS command window to the foreground and hadn't been at the monitor watching before these warnings were scrolled away by the displays from work on other files in the

--- "David W. Tamkin" <dattier@panix.com> wrote: > Our Leader asked, > > | In any case, if you run flac -t and it passes, the only extra > | information you get from comparing the MD5 sum to the text > | file is to know if the original seeder put the right text file > | together with the right FLAC file. But if you don't need the > | contents of the text

This may be more a question about the pseudo-DOS command line than about flac itself, but at this point I don't really know. How can one direct the output of flac -t to a file instead of the screen? Often I'd like to verify a large number of flac files, and Speek's front-end is very good for writing up the batch file for that (flac -t itself doesn't seem to expand wildcards on

If one is running flac under Windows and invoking it at a command.com prompt, does flac -t return an exit status that command.com can use to determine its next move (such as logging whether the flac file being tested passed or failed)? Meanwhile, I discovered the pause command; by editing that into the batch file between invocations of flac -t, at least I won't miss any results before they

When I asked, | > If you're going to run flac -t later to test | > the .flac file, isn't it redundant to have verification on during | > encoding? Fearless Leader Ace Coalson responded, | yep. OK. | > If you know ... that -V was used | > during encoding and that flac reported "Verify OK," is there any | > reason to test the file? | nope, unless you suspect

--- "David W. Tamkin" <dattier@panix.com> wrote: > First, as long as you don't use the --cuesheet option when you > encode, are > .flac files encoded by 1.1.0 still readable by earlier versions? that's right. > Second, if the old default for seekpoints was -S100x and the new one > is -S10s, > does that mean that, if you encode a 44.1-ksps WAV that was

--- "David W. Tamkin" <dattier@panix.com> wrote: > Thank you very much for the explanations, Josh. > > | the seekpoints are not the only places in the stream that can > | be seeked to, they are just hints about regular locations in > | the stream. you can still seek to any sample. the number of > | seekpoints are just one factor in determining how fast the >

So the right way to do it -- it seemed to work when I tried it, at least -- is metaflac --remove-all --dont-use-padding filename.flac ? I guess that these features make it more imperative than ever to watch the timestamps and not to validate a FLAC with an MD5 that is older than the FLAC is.

Miroslav Lichvar wrote: > Ok, you need 0.04% improvement, that should not be a problem. Perhaps a little more than that, since the sizes I listed were after stripping out the padding and all metadata blocks except SEEKTABLE and STREAMINFO. > Try flac --lax -e -p -l 32 -r 10 --no-padding > and if it is not enough, increase -r up to 16. Thank you. I'll do that. What, though,