Thanks, guys. Your answers helped and I think I have some ideas now on what to
do.
On Wednesday, March 6, 2019 Miroslav Lichvar wrote:
On Tue, Mar 05, 2019 at 10:26:54PM -0800, Brian Willoughby wrote:
> Frames start with a 14-bit sync code, which is 13 “one" bits and 1 “zero"
> bit. Subframes s
On Tue, Mar 05, 2019 at 10:26:54PM -0800, Brian Willoughby wrote:
> Frames start with a 14-bit sync code, which is 13 “one" bits and 1 “zero"
> bit. Subframes start with a 1-bit padding of “zero." Keep in mind that FLAC
> is a bit stream, not a byte stream, so that 14-bit frame sync can happen
>
Hello Dave.
Frames start with a 14-bit sync code, which is 13 “one" bits and 1 “zero" bit.
Subframes start with a 1-bit padding of “zero." Keep in mind that FLAC is a bit
stream, not a byte stream, so that 14-bit frame sync can happen anywhere in a
pair of bytes. You can’t simply scan memory by
Hello,
I've set up and have been reading through the FLAC reference implementation
source code on Windows and stepping through it in the debugger. I've been
trying to understand how the protocol knows where the subframe and frame
boundaries are. Is there a good tutorial that discusses the in
