Displaying 3 results from an estimated 3 matches for "flacced".
Did you mean:
  faced
  
2004 Sep 10
1
[Flac-users] more front-end trouble
...re these
warnings were scrolled away by the displays from work on other files in the
batch, I wouldn't have known: the front-end reported nothing about the errors.
The wavs were ripped by EAC, and I couldn't imagine what might be troublesome
about them.  I resaved them with GoldWave and re-flacced them, but FLAC gave
the same warnings.  The resulting .flac files played properly in WinAmp, and
the wavs I decoded from them matched exactly (according to EAC's Compare Wavs
function) to the originals from which they had been encoded.
Was there a problem or wasn't there?
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();
   
2006 Sep 06
2
Getting subframe type=verbatim on 16 bit files
I'm using libFLACC++ and libFLAC and I think that I'm using the calls in the
typical order (see code below).  But every monoe or stereo file that I send
thru I get files that are the same sze as the orginal wave files.
Doing a flac -a on the flac files I see that I get:
frame=9 blocksize=4608  sample_rate=8000        channels=1
channel_assignment=INDEPENDENT
        subframe=0