User Name
Tags:
bold
: [b]bold[/b]
italics
: [i]italics[/i]
emphasis
: [em]emphasis[/em]
underline
: [u]underline[/u]
small
: [small]small[/small]
Link
: [url=http://www.google.com]Link[/url]
[img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message
Oh, I meant in vgmstream. To clarify: - I re-implemented vgmstream's H4M using your 'expansion' algorithm (converts nibble to sample with big [89][8] tables, like v0.5 line 379). Now vgmstream creates files that are byte-exact vs h4m_audio_decode v0.5 - Then as a test, I swapped the algorithm with the 'classic IMA' one (converts nibble to sample using shifts-and-adds, like v0.3 line 192) This also creates files that are byte-exact. Since (I think) the big table is just the output of all possible classic-IMA combinations of steps/indexes, makes sense both ways decode the same. It's fun to know they opmitized it like that tho. *** Checking v0.3 source (line ~160), I think the actual problem is that it doesn't understand frame format 0x03 (introduced in RE0 I pressume?), unlike v0.5. At 0x57CD8 it should read: 0xFDD4,0x30 + 0xFC36,0x2F (0x03*2). Instead it reads 0xFDD4 + 0x30FC (0x02*2) > a.k.a. 0xFDD4&0xFF80=0xFD80, 0xFDD4&0x007F=0x54 + 0x30FC&0xFF80=0x3080, 0x30FC&0x007F=0x7c = 124 = error!
HCS Forum Index
Halley's Comet Software
forum source