First guess: you're US based right ? SofaSMS configures the Playsoniq for RGB output, that could be an explanation (try to use NTSC instead).
I am US based, but I think my SCART to HDMI adapter is fairly versatile. I had the defaults enabled. Changing them to Video=Playsoniq, Freq=60hz, Mode=RGB, Standard=NTSC didn't really help... The only thing that changed something was selecting Video=Playsoniq, after which the Playsoniq's output became a solid empty steel blue instead of black when launching the game.
If that does not help, please post a snapshot of your settings in SofaRun, and the message displayed by SofaSMS before launching the game.
When I access these URL's manually, I get a Microsoft login. Max, better use something like msx.pics for image uploads 
VGMPlay can handle decompressed VGM data of up to 4 MB (and more by recompiling it), very few VGMs are larger than that. However it is the decompressed file size that counts, since the entire file is decompressed into memory before playback. If you rename the .vgz files to .vgm.gz and then decompress them with gunzip, you will see their actual size. E.g.:
01 Theme of Solid Snake (Opening BGM 1).vgz - compressed: 112 kB, decompressed: 1.3MB
02 The Art of Noise.vgz - compressed: 297 kB, decompressed: 1.0 MB
So not a bug in SofaRun of VGMPlay, it just doesn’t fit into the memory of your MSX, as the message says. As for why memory expansions in 2020 still come with a measly 512 kB or 1 MB… 
There are two items on the VGMPlay to-do list related to reducing the memory consumption here and here. They are high on my wish-list but technically complex to implement.
VGMPlay can handle decompressed VGM data of up to 4 MB (and more by recompiling it), very few VGMs are larger than that. However it is the decompressed file size that counts, since the entire file is decompressed into memory before playback. If you rename the .vgz files to .vgm.gz and then decompress them with gunzip, you will see their actual size. E.g.:
01 Theme of Solid Snake (Opening BGM 1).vgz - compressed: 112 kB, decompressed: 1.3MB
02 The Art of Noise.vgz - compressed: 297 kB, decompressed: 1.0 MB
So not a bug in SofaRun of VGMPlay, it just doesn’t fit into the memory of your MSX, as the message says. As for why memory expansions in 2020 still come with a measly 512 kB or 1 MB…
There are two items on the VGMPlay to-do list related to reducing the memory consumption here and here. They are high on my wish-list but technically complex to implement.
Thanks for the explanation, Grauw!
Sofarun really is great stuff. Nowadays I mainly use my MSX for gaming and listening to music. For the latter, I use many DOS utils such as vgmplay, nmp, muplay. For graphics, I use bls. Anyhow, all these utils require pressing ESC to exit. But there is no ESC button on my joypad. So I still constantly have to get out of my Sofa to press ESC.
So I thought, there should be some TSR program which maps for example the combination of DOWN and BUTTON B to the ESC button. This TSR program should also work within these forementioned DOS utils.
Then I read the Sofarun manual and discovered the SROM.INI in which this keymapping is present! But as it looks like, only for special controllers? And only to work within ROM images? How does this syntax work anyway?
Of course I know this keyboard matrix and I even thought of programming such a tsr myself, but I don't know where in memory something like that should be and whether it's just a matter of hooking this program to #fd9f?
Any help would be much appreciated. In short, in Sofarun, is it possible, with a regular joypad, to map the combination of e.g. DOWN and BUTTON B to keyboard ESC button? And does this then work in DOS utils? How?
Thanks
Louthrax, when I now select MGS-files from within Sofarun 7.0, the SCC is being detected and used. In Sofarun 6.1 this didn't work. You managed to look into this? Thanks a lot
And also, the temporarily files keeping their original extension, is much better! More thanks