similar to: [Flac-users] questions about 1.1.0 release

--- "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

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 | decoder can find any particular sample. I did a lot of testing | before deciding on -S10s. So

Hello, I managed to insert cuepoints from a cue sheet and check them with metaflac. I witnessed that the FLAC headers then had additionnals sections (one for cuepoints and one for seekpoints), but i could not find documentation how the format used to store them (frame counts for both ?). Anyway it seems that cuepoints must be specified in MM:SS:fr format. It would be nice if those could be

--- "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 >

Thank you Josh, the link clearly explains FLAC's philosophy and it souds quite logical: "For FLAC the intention is that applications can calculate the CDDB or CDindex ID from the CUESHEET block and look it up in an online or local database just like CD rippers and players do. But if you really want it in the file itself, the track metadata should be stored separate from the CUESHEET, and

Dear list Sorry to ask a user's question on developer list. I didn't find the user list. I am experimenting with --cuesheet and encoded a flac file with a cuesheet. Result is: * Totem on opensuse 10.2 opens the flac file with no meta data, no play list. "Next" button doesn't work; * Mplayer on opensuse 10.2 opens the flac file with no meta data,

Hello, metaflac provides exporting CUEpoints, but not SEEKpoints. As i understand, cuepoints represent gaps beetween tracks (inserting pause), whereas seekpoints merely describe a list of seekable points. Can cuepoint be used just as seekpoints (in the end, the only thing which matters is that some classic media players will recognize them). In the script i have just posted before (joining

Hello, I have used --import-cuesheet-from= to insert the cue points, which are OK according to "--export-cuesheet-to=-". The points I invoke are: - the possibility to specify them as frame count instead of time - the doc: i would not find in which format cue/seekpoints are stored in the headers - titles: apparently they get lost with this option. I guess they would be preserved if put

--- On Mon, 4/20/09, porte64 at free.fr <porte64 at free.fr> wrote: > From: porte64 at free.fr <porte64 at free.fr> > Subject: [Flac] cuepoints: accuracy, titles and players > To: flac at xiph.org > Date: Monday, April 20, 2009, 10:07 AM > Hello, > > I managed to insert cuepoints from a cue sheet and > check them with metaflac. I witnessed that the FLAC >

Is it possible to place track markers that will be reflected in a cue sheet within a long FLAC file? I have a label who want to offer FLAC downloads of complete albums - but there have to be track points designated within the FLAC file How can I do this please? Many Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

Is it possible to place track markers that will be reflected in a cue sheet within a long FLAC file? I have a label who want to offer FLAC downloads of complete albums - but there have to be track points designated within the FLAC file How can I do this please? Many Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

--- doc/html/documentation_tools_flac.html | 8 +++++--- doc/html/ru/documentation.html | 2 +- man/flac.1 | 6 ++++-- man/flac.sgml | 5 +++-- src/flac/main.c | 4 +++- 5 files changed, 16 insertions(+), 9 deletions(-) diff --git a/doc/html/documentation_tools_flac.html b/doc/html/documentation_tools_flac.html

Sorry for the somewhat off-topic post, but while we are on the subject of flac, here's my question: Is the current version of ogg flac (encoded with flac.exe from the official flac website) some kind of beta implementation or is it a fully compatible release that will continue to be supported by future applications? The reason I'm asking is because I get the following error message when

are internal structures, unexposed to the end-user as you suggest. For me, a seekpoint describes an offset in the audio file, and enables any player to jump to instantly jump to that position. For instance, if you pack up an a collection of audio tracks into a single FLAC file, there is a strong need for seeking ! It is common, typically in classical music, to have up to 40 tracks on a single CD

Hi List, Is there a way to correctly use the replay-gain feature on flac files that contain an entire album (i.e., multiple tracks with seekpoints added from a cue sheet)? -- Chris

Hiya, will it be possible to add single song playback support like Monkey's Audio Image Link File to FLAC+CUE? This will allow the playing of single songs from 1 large FLAC file. Since FLAC can already embed the cuesheet inside the FLAC itself, the next step will be to allow the playback of the songs individually, allowing them to be added to playlists when playing singles. Please make

Ok, the patch from 2003 about improving seeking still didn't make it to CVS, so here is another try. I made some benchmarking with the test_seeking utility from flac sources to show how bad the current seeking is, especially without seektable. Track used for the experiment had about 50 minutes. In the following table is average number of seeks and number of decoded frames required for one

Hello, Apologies if this has already been covered. I'm trying to compile FLAC 1.2.0 under FreeBSD without ogg support: when I run gmake, I get: encode.c: In function `convert_to_seek_table_template': encode.c:2181: error: structure has no member named `use_ogg' the following appears to fix the problem for me, although I've not checked it fully: ---

Hello, Here's a script i use to join multiple PCM source files and feed them to FLAC. In the future i plan to add tag support from static CDDB (files). It would be nice if this feature could be incorporated to the native encoder. Another idea is to have flac/metaflac support joining FLAC files themselves (but this is much heavier to implement) -- and may pose issues with meta info like

Dear Friends, I am new to this mailing list. I am with the National University of Rosario, Argentina, and I am writing a book on software-based acoustical measurements, which includes a chapter on FLAC for archival and streaming purposes from an remote embedded system including a sensor. I would like to ask why the seekpoint information in the seek table metadata block reserves 64 bit for