ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
<TD-Linux>
ej5, don't forget MOV and MP4
<ej5>
ahh right
<Lord_Nightmare>
IFF is big endian, RIFF is little endian; riff technically requires there to be an outer container, while MID, being a RIFF format, doesn't have one. so .rmi exists, which is a MID file placed as (more or less) a subsection of a file, which allowed for embedding .dls samples, karaoke info, and other stuff inside a single file
<Lord_Nightmare>
then microsoft got annoyed with the .rmi format and created a very short lived format called .sgt which is like midi on crack, which is used by la mulana, final fantasy 8, and maybe a dozen other games
<Lord_Nightmare>
its basically a more convoluted version of .rmi
<Lord_Nightmare>
and of course completely incompatible, and very annoying to play back
<Lord_Nightmare>
i assume it was created to allow a singular file to have loop points, an intro, and an outro, and still be a midi file
<Lord_Nightmare>
sgt files also can use external .dls sample files relative to their own path, and not have to embed them
<Lord_Nightmare>
la mulana uses this extensively for its "SCC++" mode
<Lord_Nightmare>
and this is why its so difficult to play back the ff8 and la mulana musics accurately outside their respective programs
<Lord_Nightmare>
if you can find the directx sdk that's old enough you can use the directmusic headers/etc in there to play them
<Lord_Nightmare>
but since so few games actually USE .sgt, there's very little 3rd party/open source support
<Lord_Nightmare>
its a very complex format. probably not as complicated as yamaha's .smaf format (which is IFF, not RIFF! big endian) but pretty complex
<Lord_Nightmare>
i don't even want to get in to the .smaf format. its very poorly preserved, meant for ringtones in the early 2000s
<Lord_Nightmare>
but its spec documentation is out there and it seriously scares me
<Lord_Nightmare>
its probably not the worst out there but one of the worst designed-by-committee file formats i've ever seen
m4t has quit [*.net *.split]
ValleyBell has quit [*.net *.split]
m4t has joined ##yamahasynths
ValleyBell has joined ##yamahasynths
<cr1901_modern>
ej5: That fake USBC connector is very deep into Poe's Law territory
<Lord_Nightmare>
you missed an opportunty to make the connector have 2 prongs the exact distance apart as a standard us 2 prong wall jack
<Lord_Nightmare>
and width
<ej5>
yeah i know lol
<TD-Linux>
I've used a table at a hotel where USB-A was perfectly the right width and plugged my laptop right in
<Lord_Nightmare>
maybe it could be a documented 'fast charge' mode :P
<TD-Linux>
ej5, come to the dark side of magnetic deflection
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Xyz_39808 has quit [Ping timeout: 245 seconds]
cr1901_modern1 has joined ##yamahasynths
cr1901_modern has quit [Ping timeout: 245 seconds]
<ValleyBell>
It boots into test mode when some checks during the init phase fail.
<Lord_Nightmare>
what i'm fearing is that emulating the dsp on the mt32 will be much harder than expected. I know sergm figured out how it worked but he wasnt' able to explain it well, just pulling the various IIR factors out of its code
<Lord_Nightmare>
its a fixed function BOSS 'reverb' dsp, intended for the BOSS(roland sub brand) rv-2 pedal
<Lord_Nightmare>
it ended up getting used in a lot of mt-32 series stuff; the d-50 uses a different reverb chip, which might be a similar dsp but with on-chip mask rom; that one is NOT dumped
<Lord_Nightmare>
but the mt-32, cm-32l, d-10, d-110, d-20, d-220 all use the BOSS chip
<Lord_Nightmare>
its a weird dsp: it uses 256-word, 32(?) bit wide opcodes read in an endless cycle from the ROM
<Lord_Nightmare>
or maybe its 64 word 'programs' each 256 bytes long
<Lord_Nightmare>
i forget
<Lord_Nightmare>
i know when you're changing the dsp parameters you're literally changing the upper address bits of the reverb ROM
<Lord_Nightmare>
it has i think 64k of its own DRAM which its responsible for refreshing
<Lord_Nightmare>
if i recall correctly it uses a similar 'approximation' for multiplication to the la32 itself internally
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]