I see I brought up an old thing here. My signal path was MoonSound -> Echo AudioFire 8 (back panel inputs) -> AKG K270 Studio mk II, and for OpenMSX the same except from Mac mini's line out to the AudioFire 8.
@yzi : as you are on Mac OS, maybe you can try CocoaMSX, it's the blueMSX port for Mac OS X version 10.6 (Snow Leopard) and higher.
https://github.com/melllvar/CocoaMSX/releases
https://plus.google.com/u/0/communities/104314701960403368876
Can someone help then to quantify this, with a recorded sample?
I have no idea what could cause the difference.
How about you install blueMSX and check the differences?
I'm sorry, but where exactly do I place the Moonsound stuff in CocoaMSX? Or do I have to activate it somewhere? The contents of Moonsound.zip downloaded from bluemsx.com (MOONSOUND.rom and README) are in both of these folders
/Users/yzi/Library/Application Support/CocoaMSX.app/Machines/Shared Roms/Moonsound
and
/Users/yzi/Library/Application Support/CocoaMSX.app/Machines/Shared Roms
and in the bluemsx.ini file, there's a row
sound.chip.enableMoonsound=yes
Soepfiskje2 says "Moonsound not found".
I tried with the newest 1.32beta and the stable 1.32. Moonsound not found.
Try to install a generic MSX2, 2+ or TurboR machine, almost all come with Moonsound rom.
It's the easy way with CocoaMSX.
Meits: blueMSX doesn't run on Linux.
mars200you: Do you mean that a Moonsound on/off setting must be specified in each individual machine description? It's not enough that it's activated in bluemsx.ini and the ROM file is in Machines/Shared Roms?
Each machine has a config.ini file.
If you use a specific machine, you need to add manually the Moonsound rom in this file (as there is not yet a Machine editor in CocoaMSX)
The line to be added in the Slots section of the config.ini file is :
0 0 0 0 79 "Machines/Shared Roms/MOONSOUND.rom" ""
I'd be interested in a double blind test of a real MSX, openMSX and blueMSX MoonSound song.... who can help to organize that?