Thank you so much, my friend!

Falcosoft wrote on 2025-03-15, 19:04:

Hi, I have added a new command line option (/vstdelay ms) to new test version: https://falcosoft.hu/midiplayer_65_test.zip After […]
Show full quote

Abu Brandino wrote on 2025-03-14, 23:41:

Hi mate, I just wanted to put forth an issue from Roland's end that maybe you could be able to mitigate on your program. The SCVA needs to authenticate every time it runs on a computer and if you have the MidiPlayer to run at startup with the VST autoloading the VST doesn't see the authentication ticket until the computer has been on for a bit. Since MidiPlayer starts up pretty quickly it always thinks it's unauthorised unless you stop the VST and restart it. Do you have an idea on how to mitigate it, it becomes a hassle to keep rebooting the VST on startup which kind of negates the whole idea of having the Player start on Log-in. Thanks mate.

Hi,
I have added a new command line option (/vstdelay ms) to new test version:
https://falcosoft.hu/midiplayer_65_test.zip
After starting the new exe you should try to disable and re-enable the 'Main menu -> Start with Windows (System Tray)' option.
This will add a new parameter (/vstdelay 1000) as startup option to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\MidiPlayer.
This change will result in a 1 sec. (1000 msec.) delay of loading VSTi plugins which most likely will not be enough on your system. But you can try to increase the delay value step by step until you find a sweet spot (use Regedit to find and edit the value).

Still getting an RCM service not found on startup.

Abu Brandino wrote on 2025-03-29, 04:01:

Still getting an RCM service not found on startup.

What delay values have you tried? Have you tried e.g. 5000 ?
Remember what I wrote:

This will add a new parameter (/vstdelay 1000) as startup option to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\MidiPlayer.
This change will result in a 1 sec. (1000 msec.) delay of loading VSTi plugins which most likely will not be enough on your system. But you can try to increase the delay value step by step until you find a sweet spot (use Regedit to find and edit the value).

Hi.
It's passed a while since my last request.
I was trying to listen to some mod files through your software. Conversion works great with few track/instruments mod but I'm having some issue with complex mod files with 21 tracks (and 30 instruments). Could it be possible to arrive to channel 32 with midi created (and maybe to avoiding percussion channel as some editor has issue with this)? I was trying to record Deus EX Ost.
Thank you for your help.

RetroGC wrote on 2025-03-29, 09:33:

Hi. It's passed a while since my last request. I was trying to listen to some mod files through your software. Conversion works […]
Show full quote

Hi.
It's passed a while since my last request.
I was trying to listen to some mod files through your software. Conversion works great with few track/instruments mod but I'm having some issue with complex mod files with 21 tracks (and 30 instruments). Could it be possible to arrive to channel 32 with midi created (and maybe to avoiding percussion channel as some editor has issue with this)? I was trying to record Deus EX Ost.
Thank you for your help.

Hi,
OK, here is a new version that supports 16+ channel modules by converting them to multi-port (16+ channel) Midi files. The converted Midi files work automatically in Midi player but in other software most likely you will have to manually adjust the tracks where ports are set bigger than 0.

As for using Midi drum channels during module conversion: There has been an option to disable this behavior for a while. If you run mod2midi.exe without any parameters you can get the options:

1Usage: mod2midi <source_file> <destination path> <use drum channel[0/1]> <by inst[0/1]> <by track[0/1]> 

Using drum channel stays enabled as default since Midi player has no problem with this setting and this way you will need one less port for 16 (and 32, 48 etc.) channel module files.

BTW, mod2midi active development has been stopped for a long time. My motivation for fixing more bugs and problems has been reduced even more since Ian at un4seen has released his 2MIDI software for free and it is much more polished than mod2midi.
So if you experience further problems with mod2midi then you should use 2MIDI instead:
https://www.un4seen.com/2midi.html

I'm not sure why but on Wine 10.4 the program doesn't have any window decorations and as a result I can't snap the window anywhere on my desktop environment. I don't think this is intentional is it?

Atleast; I don't see a option anywhere in the drop down menus that would cause it to not permit window decorations. Seems like a Wine regression maybe?

DracoNihil wrote on 2025-03-30, 20:14:

I'm not sure why but on Wine 10.4 the program doesn't have any window decorations and as a result I can't snap the window anywhere on my desktop environment. I don't think this is intentional is it?

Atleast; I don't see a option anywhere in the drop down menus that would cause it to not permit window decorations. Seems like a Wine regression maybe?

Hi,
All I can say is that nothing related has changes in Midi player. So if it worked with previous Wine versions then it is definitely a Wine regression.

Falcosoft wrote on 2025-03-29, 07:09:

What delay values have you tried? Have you tried e.g. 5000 ? Remember what I wrote: […]
Show full quote

Abu Brandino wrote on 2025-03-29, 04:01:

Still getting an RCM service not found on startup.

What delay values have you tried? Have you tried e.g. 5000 ?
Remember what I wrote:

This will add a new parameter (/vstdelay 1000) as startup option to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\MidiPlayer.
This change will result in a 1 sec. (1000 msec.) delay of loading VSTi plugins which most likely will not be enough on your system. But you can try to increase the delay value step by step until you find a sweet spot (use Regedit to find and edit the value).

5000, 10000, 300000

Abu Brandino wrote on 2025-03-30, 23:24:

Falcosoft wrote on 2025-03-29, 07:09:

What delay values have you tried? Have you tried e.g. 5000 ? Remember what I wrote: […]
Show full quote

Abu Brandino wrote on 2025-03-29, 04:01:

Still getting an RCM service not found on startup.

What delay values have you tried? Have you tried e.g. 5000 ?
Remember what I wrote:

This will add a new parameter (/vstdelay 1000) as startup option to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\MidiPlayer.
This change will result in a 1 sec. (1000 msec.) delay of loading VSTi plugins which most likely will not be enough on your system. But you can try to increase the delay value step by step until you find a sweet spot (use Regedit to find and edit the value).

5000, 10000, 300000

300000 means 5 minutes so if you look at Midi player by opening it from the system tray after a system restart you should see that the plugin is not being loaded at all for 5 minutes. Is this what you see?

Falcosoft wrote on 2025-03-29, 15:27:

BTW, mod2midi active development has been stopped for a long time. My motivation for fixing more bugs and problems has been reduced even more since Ian at un4seen has released his 2MIDI software for free and it is much more polished than mod2midi.
So if you experience further problems with mod2midi then you should use 2MIDI instead:
https://www.un4seen.com/2midi.html

Well, I think I can not agree. I've found a complicated user interface, instead of an easy command line.
Still have to figure out if this other software works on a complete file or just on channel, and inside user interface I could'nt select above 16 channel...
Your is a great piece of software.

Falcosoft wrote on 2025-03-31, 00:26:

Abu Brandino wrote on 2025-03-30, 23:24:

Falcosoft wrote on 2025-03-29, 07:09:

What delay values have you tried? Have you tried e.g. 5000 ?
Remember what I wrote:

5000, 10000, 300000

300000 means 5 minutes so if you look at Midi player by opening it from the system tray after a system restart you should see that the plugin is not being loaded at all for 5 minutes. Is this what you see?

No, the VST launches straight away.

Abu Brandino wrote on 2025-04-03, 09:32:

Falcosoft wrote on 2025-03-31, 00:26:

Abu Brandino wrote on 2025-03-30, 23:24:

5000, 10000, 300000

300000 means 5 minutes so if you look at Midi player by opening it from the system tray after a system restart you should see that the plugin is not being loaded at all for 5 minutes. Is this what you see?

No, the VST launches straight away.

Then your Midiplayer.exe is not the right version or you must have done something wrong. So:

1. Check that you really downloaded and using the right version. The file version should be 6.5.0.8.
2. Then check if the vstdelay parameter works for you locally with the help of the attached midiplayer.bat file. Its content is midiplayer.exe /vstdelay 10000 so it simply sets a 10 sec. delay. The bat file should be copied to and then should be started from the same folder as midiplayer.exe.

Test video:
https://youtu.be/9IrhOpL6kYM
3. If it works the same way as shown in the test video then you should check if you modified the vstdelay parameter properly in the registry.

Falcosoft wrote on 2025-04-03, 10:37:

Then your Midiplayer.exe is not the right version or you must have done something wrong. So: […]
Show full quote

Abu Brandino wrote on 2025-04-03, 09:32:

Falcosoft wrote on 2025-03-31, 00:26:

300000 means 5 minutes so if you look at Midi player by opening it from the system tray after a system restart you should see that the plugin is not being loaded at all for 5 minutes. Is this what you see?

No, the VST launches straight away.

Then your Midiplayer.exe is not the right version or you must have done something wrong. So:

1. Check that you really downloaded and using the right version. The file version should be 6.5.0.8.
2. Then check if the vstdelay parameter works for you locally with the help of the attached midiplayer.bat file. Its content is midiplayer.exe /vstdelay 10000 so it simply sets a 10 sec. delay. The bat file should be copied to and then should be started from the same folder as midiplayer.exe.

The attachment Midiplayer.bat.zip is no longer available

Test video:
https://youtu.be/9IrhOpL6kYM
3. If it works the same way as shown in the test video then you should check if you modified the vstdelay parameter properly in the registry.

So I just turned it off, restarted, then turned it on and the regedit value works now just like the .BAT did.

Unfortunately that doesn't fix the issue. It's definitely on Roland's end because always on first launch of the VST now it has a stupid error about RCM service not being connected or running or something, then once you get past those boxes it runs as usual. The delay helps the authentication issues I think but in terms of preventing the boxes at startup, I don't think there's anything you can do...unless you know what's causing it.

Abu Brandino wrote on 2025-04-04, 12:48:

Falcosoft wrote on 2025-04-03, 10:37:

Then your Midiplayer.exe is not the right version or you must have done something wrong. So: […]
Show full quote

Abu Brandino wrote on 2025-04-03, 09:32:

No, the VST launches straight away.

Then your Midiplayer.exe is not the right version or you must have done something wrong. So:

1. Check that you really downloaded and using the right version. The file version should be 6.5.0.8.
2. Then check if the vstdelay parameter works for you locally with the help of the attached midiplayer.bat file. Its content is midiplayer.exe /vstdelay 10000 so it simply sets a 10 sec. delay. The bat file should be copied to and then should be started from the same folder as midiplayer.exe.

The attachment Midiplayer.bat.zip is no longer available

Test video:
https://youtu.be/9IrhOpL6kYM
3. If it works the same way as shown in the test video then you should check if you modified the vstdelay parameter properly in the registry.

So I just turned it off, restarted, then turned it on and the regedit value works now just like the .BAT did.

Unfortunately that doesn't fix the issue. It's definitely on Roland's end because always on first launch of the VST now it has a stupid error about RCM service not being connected or running or something, then once you get past those boxes it runs as usual. The delay helps the authentication issues I think but in terms of preventing the boxes at startup, I don't think there's anything you can do...unless you know what's causing it.

I'm sorry it could not help. Unfortunately I have no idea what can cause the problem on Roland's side.

Falcosoft wrote on 2025-04-04, 15:16:

Abu Brandino wrote on 2025-04-04, 12:48:

Falcosoft wrote on 2025-04-03, 10:37:

Then your Midiplayer.exe is not the right version or you must have done something wrong. So: […]
Show full quote

Then your Midiplayer.exe is not the right version or you must have done something wrong. So:

1. Check that you really downloaded and using the right version. The file version should be 6.5.0.8.
2. Then check if the vstdelay parameter works for you locally with the help of the attached midiplayer.bat file. Its content is midiplayer.exe /vstdelay 10000 so it simply sets a 10 sec. delay. The bat file should be copied to and then should be started from the same folder as midiplayer.exe.

The attachment Midiplayer.bat.zip is no longer available

Test video:
https://youtu.be/9IrhOpL6kYM
3. If it works the same way as shown in the test video then you should check if you modified the vstdelay parameter properly in the registry.

So I just turned it off, restarted, then turned it on and the regedit value works now just like the .BAT did.

Unfortunately that doesn't fix the issue. It's definitely on Roland's end because always on first launch of the VST now it has a stupid error about RCM service not being connected or running or something, then once you get past those boxes it runs as usual. The delay helps the authentication issues I think but in terms of preventing the boxes at startup, I don't think there's anything you can do...unless you know what's causing it.

I'm sorry it could not help. Unfortunately I have no idea what can cause the problem on Roland's side.

Don't stress man, you're doing an awesome job. Roland just being typical Roland making it hell for their own users. They discontinued the SCVA and yet their "offline" installer still requires the RCM Service and constant checking the authentication servers that you're still logged in.