VOGONS

Common searches


Search results

Display options

Re: Decoding Roland PCM ROMs

Thanks for all the help, I reckon the results are close enough and it's not known how the decoded data from the VST was derived anyway a you say. I had originally assumed they'd have access to the original data before encoding for the ROM rather than having to decode their own ROMs but you never …

Re: Decoding Roland PCM ROMs

Could you please elaborate to what extent do you observe differences from the reference samples? P.S. If you care about portability, rows #4 and #5 could be slightly improved. Thank's for the portability tip. It's really just a personal project but I may as well improve it where possible. Hopefully …

Re: Decoding Roland PCM ROMs

I noticed that on line 18, the "32767.0f" part is actually "32787.0f" in MUNT. Try to change it and see if it gets bit accurate now? Though tbh, that kinda looks like a typo in the MUNT code. EDIT: Most likely not a typo! I see the same value in the integer LA32 code too. Also how do you know if …

Decoding Roland PCM ROMs

Hello, New around here. I'd like to decode some Roland PCM ROMs in a perfect, bit accurate way. I'm currently using this code which is a combination of code posted on this forum modified a little: for (int i = 0; i < file_size / 2; i++) { int16_t raw_sample; *(((int8_t *) &raw_sample) + 1) = fgetc( …

Re: Munt Reloaded - Development

That's interesting, thanks. I have MT-32 ROMs here, would be interested to know which ROMs have the lookup tables and their address and size if it's convenient. An idea of how to make use of them would be great too. I can code fairly well in C but maths is not a strong point at all.

Re: Munt Reloaded - Development

I'm still looking at how Roland compresses the samples. That's how I stumbled on this thread. Because I hope that the algorithm Roland used to compress samples for the MT-32 would be the same as for the D-110, and maybe also the U-110/U-220. They are all from the same time period. And as the MT-32 …

Munt - possible bug in code

Hello. Complete outsider here. Just looking through munt mt32emu source code and in Synth.cpp noticed in Synth::loadPCMROM it has: int order[16] = {0, 9, 1, 2, 3, 4, 5, 6, 7, 10, 11, 12, 13, 14, 15, 8}; with the loop: for (int u = 0; u < 15; u++) { ... } so it's only accessing index 0-14 rather than …

Page 1 of 1