Displaying 20 results from an estimated 700 matches similar to: "FLAC StreamInfo Parsing"
2010 Jun 23
3
FLAC StreamInfo Parsing
Thank you very much! But how to deal with endianness in the case of
bit stream? Some blocks (for example MinBlockSize) require 16bits
(simply swap first and second), some block (e.g.MinFrameSize) require
3 byte-array to be reverted.
Finally totalSamples is stored in 5 bytes ( only last 4 bits from
first one byte are used). It was a real issue to make it little-endian
(here is how I did it:
2010 Jun 23
0
FLAC StreamInfo Parsing
On Jun 22, 2010, at 21:27, Ilia Ternovich wrote:
> Thank you very much! But how to deal with endianness in the case of
> bit stream? Some blocks (for example MinBlockSize) require 16bits
> (simply swap first and second), some block (e.g.MinFrameSize) require
> 3 byte-array to be reverted.
>
> Finally totalSamples is stored in 5 bytes ( only last 4 bits from
> first one byte
2010 Jun 22
2
FLAC StreamInfo Parsing
Hello Ilia,
The FLAC format by nature is not a byte stream, it's a bit stream.
Therefore, in order to parse it you need too build a bit-reading
infrastructure. Eg. a class that accepts a byte stream, implements
buffering, etc, etc, and supports reading a specified number of bits, not
bytes as you are used to. There is quite a lot of bit logic there, but
nothing too scary.
Best Regards,
2024 Oct 14
1
C API: How to get a seektable for very long files?
Op zo 13 okt 2024 om 22:33 schreef Stefan Oltmanns <stefan-oltmanns at gmx.net>:
>
> Is the seektable written at the beginning of the file in the metadata
> block or can there also be a second metadata block at the end?
>
Only at the start of the file.
>
> If it's at the beginning, would it possible to reserve space for N seek
> points and during encoding remember
2015 Jan 15
1
Max Sample Rate FLAC
Hi,
I would like to clear something up about Sample Rate, If the Frame header can look to the metadata block streaminfo for sample rate what (if anything limits it to 655350Hz)? Can all frame headers not just point to streaminfo and it be specified in streaminfo as all 1s ie 2^20-1 = 1,048,575Hz? It would be really good to be able to use 1MHz and beyond for some of my/our work. Does anything
2024 Oct 13
2
C API: How to get a seektable for very long files?
I think there is another major issue for me: In
METADATA_BLOCK_STREAMINFO the field for the length is only 36 bit,
that's not even half an hour at 40 MHz sample rate, resulting in that
the encoder sets it to 0 for longer captures. In the seekpoint the
sample number is 64 bit, which is more than enough.
But how does the decoder handle the seektable when the total number of
samples is unknown?
2009 Jan 27
1
frames number & compression level
If compression level is not default (!=5), is it stored?
If compression level is stored in some case, where I can find it?
Frames number works OK according to your instructions. Thank you
----- Original Message -----
From: "Josh Coalson" <xflac at yahoo.com>
To: "Santiago Jimeno" <sjimeno at ya.com>; <flac at xiph.org>
Sent: Tuesday, January 27, 2009 7:43
2024 Oct 14
1
C API: How to get a seektable for very long files?
Am 14.10.24 um 09:11 schrieb Martijn van Beurden:
> Op zo 13 okt 2024 om 22:33 schreef Stefan Oltmanns <stefan-oltmanns at gmx.net>:
>>
>
>>
>> The signal is the FM-modulated video signal of video tapes (like VHS).
>> The idea is to capture the signal directly from the video head amplifier
>> in the VCR and later demodulate/decode it in software, providing
2006 Jun 08
1
How can I recreate STREAMINFO metadata?
I have some FLACs that have STREAMINFO that looks like this:
METADATA block #0
type: 0 (STREAMINFO)
is last: false
length: 34
minumum blocksize: 4608 samples
maximum blocksize: 4608 samples
minimum framesize: 0 bytes
maximum framesize: 0 bytes
sample_rate: 44100 Hz
channels: 2
bits-per-sample: 16
total samples: 0
MD5 signature: 00000000000000000000000000000000
(This came
2010 Nov 16
2
How to handle multiple STREAMINFO blocks?
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
2012 Feb 20
0
Regain play analysis patches
Erik,
It turns out bc(1) is too accurate, and a little slow, for this purpose.
I've switched to using awk(1) which uses floating point.
Do you feel I need to test for the presence of awk(1) ?
It is specified as one of the standard commands in the LSB :
http://refspecs.linuxfoundation.org/LSB_1.0.0/gLSB/command.html
Earl
??? awk -- '
??? BEGIN {
??????????? samplerate = 8000;
2010 Nov 16
1
How to handle multiple STREAMINFO blocks?
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
2008 Oct 24
1
Decoding error: fingerprint unset in streaminfo block
Using Trader's Little Helper 2.4.1.160 when testing some 16/96 FLAC
files I run into the following error:
"file is decodable without error, but flac fingerprint cannot be
checked since it was unset in the streaminfo block."
Is there an automatic checksum verification when testing/decoding? Is
there any way to fix this, i.e. get rid of the error?
Martin
2006 Sep 07
2
Getting subframe type=verbatim on 16 bit files
Here's how I set up the data for processing:
// For moving data into 32 bit shape
uint8_t *buffer8 = NULL;
uint16_t *buffer16 = NULL;
uint32_t *buffer32 = NULL;
unsigned sample32;
unsigned sample, channel;
uint32_t bitsPerSample = this->get_bits_per_sample();
numFrames = inData.GetSize();
2005 Sep 30
2
Reg. FLAC decoding
I'm using seekable_stream_decoder, And., this is my write_callback. I'm
not getting the required output. The PCM i get is not the proper music.
Am I doing something wrong here?
FLAC__StreamDecoderWriteStatus
AFLACStreamPlayer::StreamWriteCb (
const FLAC__SeekableStreamDecoder *decoder,
const FLAC__Frame *frame,
const FLAC__int32 * const buffer[],
void *client_data)
{
int Channels,
2010 Jun 23
1
FLAC StreamInfo Parsing
Oops. I proofread my email a little too late. I corrected the
example. Hopefully what I am suggesting is clear.
Brian Willoughby
Sound Consulting
On Jun 22, 2010, at 22:15, Brian Willoughby wrote:
> What you need to do is write a bitStream function. It should only
> read each byte from the stream once and completely deal with all 8
> bits before reading the next byte. You
2005 Sep 30
0
Re: Reg. FLAC decoding
I can't be totally sure what 'short' is on your platform, but if
it's (probably) 16-bits, it looks like you're treating the samples
in buffer[] as packed 16 bit numbers.
but all samples in buffer[] are 32-bit signed integers in host
order, regardless of the bits-per-sample of the frame. so to get
them down to shorts (assuming they'll fit), do like:
FLAC__int32 *
2017 Jun 07
0
[Cellar] FLAC Markdown
Hi all,
> On Jun 5, 2017, at 11:52 PM, Andrew James Weaver <weevz at uw.edu> wrote:
>
> Hello all!
> (cc-ing the flac-dev list)
>
> I would like to give an update as to the recent CELLAR work on the FLAC specification.
>
> • Work has been done to make internal and external links more accurate and reliable.
> • 'Rice Coding' has been clarified as
2012 Feb 17
3
Regain play analysis patches
Earl Chew wrote:
> I'm a little reluctant to introduce another compiled program when there are
> so many other options that will work well enough out of the box.
>
> Here are two ideas:
>
> 1. Use bc(1) to compute the raw samples
> 2. Use perl(1) to compute the raw samples
>
> To generate raw unsigned samples using bc(1) for example:
>
> samplerate = 1000;
2015 Jul 16
0
WAVEFORMATEXTENSIBLE_CHANNEL_MASK is not described
Martin Leese wrote:
> Your proposed wording was:
> 0000-0111 : (number of independent channels)-1. The channel order
> follows SMPTE/ITU-R recommendations. The assignments are as follows:
>
> The channel order might not follow SMPTE/ITU-R
> recommendations, so this proposed wording
> seems misleading to me.
But this text describes only those 4 bits in frame header.
IMHO