Im just guessing here, but it might be that the size
is vallid. If the size is set to 4 GB ww will not use the full file. That is also why ww sets the size to 0. A way to test this is to
unselect ignore invallid size, and then to drop the file. If it accepts it, then the size is vallid.
Im going to solve this "bug" by adding the options
- always ignore the size and
- automaticaly ignore the size when its larger then 2gb/4gb
If this is not the problem, it might be handy if you could post the first 100 bytes of the wav. Then ill can experiment with it myself.
it would look something like this:
Code:
52 49 46 46 44 CB 36 83 57 41 56 45 66 6D 74 20
10 00 00 00 01 00 06 00 44 AC 00 00 30 13 08 00
0C 00 10 00 64 61 74 61 20 CB 36 83 01 00 01 00
01 00 01 00 01 00 01 00 FF FF FF FF FF FF FF FF
FF FF FF FF 01 00 01 00 01 00 01 00 01 00 01 00
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
EDIT and i can confirm the bug in sonic surcode. I have to set the option to off to enable it
I think i will add an option to cb to invert the flag.
EDIT 2 and i got the same verion of surcode as you