similar to: possible format change

> JC> After doing a lot of automated seek testing on files, it looks like > JC> the length of the sync code (currently 9 bits) is not long enough to > JC> enable a really robust AND efficient seek algorithm. Lengthening the > JC> sync code will require a format change (i.e. FLAC <0.8 streams won't > JC> play back on FLAC >>0.9 decoders), so I'm

All, FLAC is nearing an official version. I am going to release a 0.9 version first with the winamp2 plugin fixes (and some other small inprovements). but I want to ask the question now: As a user, what do you think is left to do before 1.0? FLAC is bound to have incremental improvements but are there any fundamental format or feature changes/additions that you think that should be made? I am

On Tue, 11 Jun 2002 11:51:33 +0400 Andrey Astafiev <andrei@tvcell.ru> wrote: > flac-1.0.3_beta compilation breaks for me with message: I had the same experience, too. I think that a cause is in configure and configure.in files. Therefore, let's rebuild these files. I took the following, and solved the problem. $ cd flac-1.0.3_beta $ automake $ autoconf $ ./configure ;make --

when i try to build rpm package of 1.0.1 i get some error messages (in attach)... version 1.0 with the same spec builds fine... any ideas? -- andrei at tvcell d0t ru -------------- next part -------------- A non-text attachment was scrubbed... Name: flac_install_error.txt.bz2 Type: application/octet-stream Size: 1184 bytes Desc: not available Url :

JC> After doing a lot of automated seek testing on files, it looks like JC> the length of the sync code (currently 9 bits) is not long enough to JC> enable a really robust AND efficient seek algorithm. Lengthening the JC> sync code will require a format change (i.e. FLAC <0.8 streams won't JC> play back on FLAC >>0.9 decoders), so I'm sending this message out to

I have just released a source distribution which is the candidate for the 1.0.3 release. At this time I would ask anyone who is willing to help test it to do the following: 1. download the tarball and unzip it: http://prdownloads.sourceforge.net/flac/flac-1.0.3_beta-src.tar.gz?download 2. do ./configure && make && make check This will build all code and run all the tests.

> > when i try to build rpm package of 1.0.1 i get > > some error messages (in attach)... version 1.0 > > with the same spec builds fine... any ideas? > > The problem is likely with your spec file; > send a copy to the list and I'll look at it. thanks, i've found the error by myself. there was export LDFLAGS="-L$RPM_BUILD_ROOT/usr/lib" missing.

Dear all, I wonder what's special about spinograms {vcd} that prevents me from using it the way I do with other plots. I do: > spine(f.speaker.identity ~ x.log.lengthening, > data=ms,breaks=45,gp=gpar(fill=c("red","green")),xlab="length difference > (log ms)",ylab="speaker") > curve(0*x,add=T) Error in plot.xy(xy.coords(x, y), type =

i've tried to make rpm package of flac 0.10, but compilation fails near start, 'cause compilator couldn't find .h files in libFLAC directory, when it tries to build this library. generated makefile in this directory contains "-I.$(srcdir)" in compilator options, though it should be "-I.$(includedir)" strange, but ./configure; make; make install running from

Firstly, a big thank-you to Josh for FLAC. Someone mentioned it in a post on Slashdot, so I came over to sourceforge for a look-see. This is just the sort of thing I've been looking for. Can anyone relate any general tips for using flac on Windows for the purpose of archiving cd's? If I can nail down a solid, easy-to-use process, I'm happy to write it up and contribute it to the

Hi, I've been working writing some tools that deal with id3v2 tags on mp3 files. id3v2 is this really, really long specification with places for all kinds of metadata for media. I've looking at the sample vorbis encoder and a file I made from it I noted that you have some a comment field, and I was wondering if you had any plans to support more metadata, and if you would

> A good number have id3v2 tags... say 20-30%. Do you find that it's stuttering on id3v2 files? Since those contain data that is counted by the timing code, but not played the the player, that seems a likely suspect. Ie, you'll get _playable_ data too slow. Try a stream with _no_ id3v2 files and see if the problem persists. > > What version of linux? glibc? > > RH 7.2

Hi Josh, I found id3v2 didn't work on v1.1.0. I checked source codes, macros- (in such cases as FLAC_HAVE_ID3LIB) ware moved to config.h. That is good. But the place to do include is the after of #ifdef FLAC_HAVE_ID3LIB. The result of configure script isn't reflected. And it doesn't always have id3lib with this. Move place of 'include "config.h"' to the top. I

I'm moving my Ogg Vorbis collection off of my Linux server and onto my laptop. I plan on using iTunes to play my collection, but, that's a whole 'nother can of worms. I'm having trouble moving my complete collection over because dbPowerAmp (an application I used to love) made some dumb decisions about naming my files. For example, in track/album/artist names that contained a

I've been with FLAC since 0.7, and I've loved the FLAC files I've ripped with grip, converted from FLAC 0.8 to 0.9, and played constantly on my desktop. And then I noticed the truncated ID3 tags in my FLAC files. I at first thought the problem lied in FLAC; I posted to this list, hoping for a solution. But then I realized my trusty GRIP was the flawed program. Now re-ripping my

I tagged some FLAC files with ID3V2 information (by the id3v2 program), but their metadata does not show up in XMMS. Anyone else have this problem? Anyone have a solution? (I tested the tags using the --list option of id3v2; they are there. XMMS and the FLAC plugin just don't seem to respect them.) -- Asheesh.

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

I'm a bit confused about VBR with Opus. I see that the default is VBR, but I don't see any way to specify a quality setting. I can set a target bitrate, but that's definitely not what I want; I want a constant quality level, like "-q" in oggenc, and for the encoder to select bitrates based on the desired quality. For example, for playback through earbuds or laptop

> > What kidn of files are you streaming? > > MP3s and nothing but. Are they high bitrate? VBR? Do they have id3v2 tags? We could all guess they were mp3s :) <p>What version of linux? glibc? Icecast 1.3.11? jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

I have several data input functions that include a construct like the following: indat <- function(stuff) { [...] awkp <- paste("awk ...yada yada...", stuff, etc.) scan(pipe(awkp),quiet=TRUE) } I use these functions a lot, and as I do, a lengthening list of closed, but undestroyed, connections accumulates. Ultimately this appears to stuff things up and cause