I thought I had a test case exposing the bug, but I was mistaken...
Salem: mf_needed is hardcoded to 1904 at the moment. There's no particular reason to do mfbuf[0] and [1] separately, other...
Type: Posts; User: cecomp64
I thought I had a test case exposing the bug, but I was mistaken...
Salem: mf_needed is hardcoded to 1904 at the moment. There's no particular reason to do mfbuf[0] and [1] separately, other...
Dino: I haven't been able to reproduce it in a smaller example yet. I updated my original post with all the code relating to file I/O. In a sample program, I wrote about 1 MB to disk and then read...
Thanks for the quick reply! Unfortunately, that is just a typo. Please substitute gfc->mfbuf_p for fp at that point. The problem still remains.
On a side note, I am compiling with Visual...
Hi All,
I've got another sanity-questioning problem to pose for you. I am trying to read the contents of a file, but I'm only able to read a small fraction of the file (15232 / 2912998 Bytes). ...
Thanks for all the replies. It turns out my problem was a combination of stack issues and misinterpreting my debugging results.
Alright, that solves one mystery, but the basic problem still remains, even with a prototype of the form
func (unsigned char mp3buffer[16][16384]);
No warnings are generated corresponding...
Ah sorry, this is a typo in my haste to copy only relevant parts of the code. Please assume that this points to a previously instantiated, valid value.
Thanks.
Hi,
I'm new to this forum and was hoping someone could help me debug a sanity-questioning problem I'm having. Consider the following function declaration and call...
int...