Spesek wrote on Today, 14:42:

Falco, I can't seem to get presets to work. It always uses the last configuration preset I selected. […]
Show full quote

Falco, I can't seem to get presets to work.
It always uses the last configuration preset I selected.

I have a total of 6 presets, i believe that most are default:
- Default_000
- MuntVsti_001
- OPL3Vsti_002
- scvaRender_003
- syxg50Render_004
- WinMM_MultiPortVsti_005

The command i use with a random file (silent removed so i can see the gui):

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" "/preset 3" "/render" "/close"

for scva

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" "/preset 4" "/render" "/close"

for syxg.

If I had manually selected scva, both will render as scva. I tried 4 and 5 respectively as well, but that didn't work.

I attached the ini files here:

The attachment scvaRender_003.ini is no longer available

The attachment syxg50Render_004.ini is no longer available

They seem fine to me and have correct paths.

Ideas as for why it might not be working? The FSMP works with close, render and silenttray, so the arguments are definitely parsed.

PS: I forgot to mention but the new dark mode looks amazing!

The attachment Screenshot_20260622_164020.png is no longer available

Hi,
First you should check that your presets work through the GUI or not. That is double click them (or press Apply) on the configuration preset loading dialog and check that the proper VSTi plugins are loaded or not.

Falcosoft wrote on Today, 14:53:

Spesek wrote on Today, 14:42:

Falco, I can't seem to get presets to work. It always uses the last configuration preset I selected. […]
Show full quote

Falco, I can't seem to get presets to work.
It always uses the last configuration preset I selected.

I have a total of 6 presets, i believe that most are default:
- Default_000
- MuntVsti_001
- OPL3Vsti_002
- scvaRender_003
- syxg50Render_004
- WinMM_MultiPortVsti_005

The command i use with a random file (silent removed so i can see the gui):

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" "/preset 3" "/render" "/close"

for scva

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" "/preset 4" "/render" "/close"

for syxg.

If I had manually selected scva, both will render as scva. I tried 4 and 5 respectively as well, but that didn't work.

I attached the ini files here:

The attachment scvaRender_003.ini is no longer available

The attachment syxg50Render_004.ini is no longer available

They seem fine to me and have correct paths.

Ideas as for why it might not be working? The FSMP works with close, render and silenttray, so the arguments are definitely parsed.

PS: I forgot to mention but the new dark mode looks amazing!

The attachment Screenshot_20260622_164020.png is no longer available

Hi,
First you should check that your presets work through the GUI or not. That is double click them (or press Apply) on the configuration preset loading dialog and check that the proper VSTi plugins are loaded or not.

Yes, loading either syxg or scva manually works just fine. The VSTs load correctly. Then the cli version uses the vst i selected through the GUI, completely ignoring the passed argument.

@EDIT: An idea: maybe make FSMP write the arguments it received and the currently selected configuration preset to stdout for debugging? Wouldn't hurt, i think.

Spesek wrote on Today, 14:57:

Falcosoft wrote on Today, 14:53:

Spesek wrote on Today, 14:42:

Falco, I can't seem to get presets to work. It always uses the last configuration preset I selected. […]
Show full quote

Falco, I can't seem to get presets to work.
It always uses the last configuration preset I selected.

I have a total of 6 presets, i believe that most are default:
- Default_000
- MuntVsti_001
- OPL3Vsti_002
- scvaRender_003
- syxg50Render_004
- WinMM_MultiPortVsti_005

The command i use with a random file (silent removed so i can see the gui):

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" "/preset 3" "/render" "/close"

for scva

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" "/preset 4" "/render" "/close"

for syxg.

If I had manually selected scva, both will render as scva. I tried 4 and 5 respectively as well, but that didn't work.

I attached the ini files here:

The attachment scvaRender_003.ini is no longer available

The attachment syxg50Render_004.ini is no longer available

They seem fine to me and have correct paths.

Ideas as for why it might not be working? The FSMP works with close, render and silenttray, so the arguments are definitely parsed.

PS: I forgot to mention but the new dark mode looks amazing!

The attachment Screenshot_20260622_164020.png is no longer available

Hi,
First you should check that your presets work through the GUI or not. That is double click them (or press Apply) on the configuration preset loading dialog and check that the proper VSTi plugins are loaded or not.

Yes, loading either syxg or scva manually works just fine. The VSTs load correctly. Then the cli version uses the vst i selected through the GUI, completely ignoring the passed argument.

@EDIT: An idea: maybe make FSMP write the arguments it received and the currently selected configuration preset to stdout for debugging? Wouldn't hurt, i think.

Then make sure there are no other presets in the preset folder with the same suffix as the required ones. I have just tested again and I experienced no problems.
Also you should try to remove the double quotes around the arguments (except the filename). They are not required at least on Windows. That is:
MidiPlayer.exe "filename" /preset 1 /render /close

BTW, GUI applications have no standard stdout on Windows. You have to explicitly open and attach a console window to the application to use stdout.
You can use OutputDebugString but you have to get a special app (like SysInternals's Dbgview.exe) to watch the output.

I removed all other presets, the config window nly shows syxg50 and scva now,
I tried 0, 1, 2, quotes and no quotes, it's always scva since i set it to that before.

So another approach: where does FSMP store the last selected config? I suppose i can just change that file if the options aren't recognized.

Falcosoft wrote on Today, 15:02:

BTW, GUI applications have no standard stdout on Windows. You have to explicitly open and attach a console window to the application to use stdout.
You can use OutputDebugString but you have to get a special app (like SysInternals's Dbgview.exe) to watch the output.

Then maybe in the "about" window? A small line with passed command line options.

Spesek wrote on Today, 15:22:

I removed all other presets, the config window nly shows syxg50 and scva now, I tried 0, 1, 2, quotes and no quotes, it's always […]
Show full quote

I removed all other presets, the config window nly shows syxg50 and scva now,
I tried 0, 1, 2, quotes and no quotes, it's always scva since i set it to that before.

So another approach: where does FSMP store the last selected config? I suppose i can just change that file if the options aren't recognized.

Falcosoft wrote on Today, 15:02:

BTW, GUI applications have no standard stdout on Windows. You have to explicitly open and attach a console window to the application to use stdout.
You can use OutputDebugString but you have to get a special app (like SysInternals's Dbgview.exe) to watch the output.

Then maybe in the "about" window? A small line with passed command line options.

Here is a debug a 32-bit version that opens a console windows and prints the found presetnum and preset file name:

For me it only shows "Found PresetNum:" with the correct number. So it sees the argument correctly, but doesn't find the ini file? Strange, given that the configuration preset window shows the list correctly.

Spesek wrote on Today, 15:34:

For me it only shows "Found PresetNum:" with the correct number. So it sees the argument correctly, but doesn't find the ini file? Strange, given that the configuration preset window shows the list correctly.

Here is another debug version that prints more detailed info about the findfileFirst/FindfileNext API calls (and the found preset folder)

I'm starting to suspect that this is another Wine quirk...

CMD shows:

1Found PresetNum: 2
2Preset Folder: Z:\home\spessasus\Desktop\clutter\MidiPlayer x86\Preset\
3Im in FindfirstFile
4Im in FindNextFile

Also, I think you can test wine without dualbooting linux via WSL2. It supports GUI apps. I don't do anything special, just:

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" /preset 2

And it's a normal wine install on arch, which is supported through wsl2

Spesek wrote on Today, 15:47:

CMD shows: […]
Show full quote

CMD shows:

Copy code to clipboard

1Found PresetNum: 2
2Preset Folder: Z:\home\spessasus\Desktop\clutter\MidiPlayer x86\Preset\
3Im in FindfirstFile
4Im in FindNextFile

Also, I think you can test wine without dualbooting linux via WSL2. It supports GUI apps. I don't do anything special, just:

Copy code to clipboard

1wine MidiPlayer.exe "Z:\home\spessasus\htdocs\spessasynth_core\tests\midi_file\generated\auto_wah.mid" /preset 2

And it's a normal wine install on arch, which is supported through wsl2

I'm using a SoundBlaster Audigy 2 ZS so I'm on Windows 10 1809 where there is no WSL2 ...
BTW, Is the Preset Folder: "Z:\home\spessasus\Desktop\clutter\MidiPlayer x86\Preset\" the expected one?

@Edit:
Last debug version that also prints the found ini file names. Please, run it the last time 😀

1Found PresetNum: 2
2Preset Folder: Z:\home\spessasus\Desktop\clutter\MidiPlayer x86\Preset\
3Im in FindfirstFile
4INI name: scvaRender_003.ini
5Im in FindNextFile
6INI name: syxg50Render_004.ini

So it does see them!

@Edit: About the audigy, I found quite a few mentions of it in the linux kernel, so i think it has a driver for it. Maybe you'll join the penguin side? :-]

Spesek wrote on Today, 16:01:

So it does see them! […]
Show full quote

Copy code to clipboard

1Found PresetNum: 2
2Preset Folder: Z:\home\spessasus\Desktop\clutter\MidiPlayer x86\Preset\
3Im in FindfirstFile
4INI name: scvaRender_003.ini
5Im in FindNextFile
6INI name: syxg50Render_004.ini

So it does see them!

@Edit: About the audigy, I found quite a few mentions of it in the linux kernel, so i think it has a driver for it :-]

1. The problem is that the found presetNum is 2 but there is no INI file found with _002 suffix !
2. I was talking about Windows 10 😀 Windows 10 versions after 1809 kills my Audigy in different ways...

Welp, yeah. The suffix was it, it works now.
And I know that you meant windows breaking the driver in the new versions, so I mentioned that linux has essentially timeless drivers (because they are source code, not compiled) which always work on the latest version! For example i got 5.1 through spdif working out of the box on linux, while on windows it either requires an ancient sound card or shady realtek drivers. It's an old codec called DTS Interactive and modern sound cards don't really support it.

Spesek wrote on Today, 16:15:

Welp, yeah. The suffix was it, it works now.
And I know that you meant windows breaking the driver in the new versions, so I mentioned that linux has essentially timeless drivers (because they are source code, not compiled) which always work on the latest version! For example i got 5.1 through spdif working out of the box on linux, while on windows it either requires an ancient sound card or shady realtek drivers. It's an old codec called DTS Interactive and modern sound cards don't really support it.

1. OK, I'm glad it finally worked.
2. OK, But on Linux there is no Creative's SoundFont Bank manager (sfman32) and this is the most important component for me because of SF2 engine related testing .

https://sourceforge.net/projects/qsfm/

😉

@Edit: This is the first result thatcame up, I don't actually have a sound blaster to test.

@Edit 2: There's also this https://flaterco.com/kb/audio/Semi_MIDI_Linux.html

Spesek wrote on Today, 16:22:

https://sourceforge.net/projects/qsfm/ […]
Show full quote

https://sourceforge.net/projects/qsfm/

😉

@Edit: This is the first result thatcame up, I don't actually have a sound blaster to test.

@Edit 2: There's also this https://flaterco.com/kb/audio/Semi_MIDI_Linux.html

It does not seem to use the same API as creative's driver 😀
For me sfman32 is important because of compatibility testing of my Midi Player that uses the API of sfman32.