Falcosoft wrote on 2026-02-15, 18:32:

Hi,
If I remember correctly Bassmidi already supports setting individual drum key's chorus send level. The problem is not this, but the default state. For many years Bassmidi by default was compatible with the way Creative's SB HW SF2 synths handled chorus on drum channels (that is no restriction after a GS reset). Then suddenly it changed to be compatible with Roland GS hardware (and thus incompatible with SB HW SF2 synths).

You can restore the old behavior by applying new flags (and FSMP applies this flag when the 'No SysEx' reset option is enabled) but for me such changes would be more acceptable if they were intruduced as opt-in instead of opt-out...

Hi,
Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later).
The easiest way to test is with another MIDI by Kr.palto47, this time from touhou 19 (the 88pro version). It sets chorus for snare drum 1 (key 38 i believe), but Bassmidi does not apply any chorus to the note. You can confirm this with SC-VA or spessasynth's latest development branch. This MIDI also alters the pitch of the drums, but it does so via a sysEx command rather than NRPN and Bassmidi doesn't seem to recognize those either.
Another example is This MIDI file, which uses NRPN for chorus. More precisely, it sets the snare 2 drum chorus to 64:

(the software is GS Advanced Editor)
And Bassmidi doesn't apply any chorus to the snare.

What's also interesting is that SC-55 had the behavior matching SB2 synths:
When you choose the SC-55 drum map in GSAE, the drum editor shows that chorus is enabled for all drum instruments by default, which is not the case on any later drum map (88,pro,etc.).
Nuked-SC55 confirms this.

Now regarding the pitch tuning, it is very strange. For the sysEx version of the command, it specifies the amount in semitone steps, while for the NRPN version the amount is in 50 cent steps. I thought this was an SCVA bug, but I sent the a test file to someone who owns a real SC-D70 and the behavior is replicated there (and youtube recordings with an 88pro seem to match it as well). Very strange! And, of course, if you select the sc-55 drum map the pitch in NRPN does use the full semitone steps...

Spesek wrote on 2026-02-15, 18:55:

Hi, Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later). The easiest way t […]
Show full quote

Falcosoft wrote on 2026-02-15, 18:32:

Hi,
If I remember correctly Bassmidi already supports setting individual drum key's chorus send level. The problem is not this, but the default state. For many years Bassmidi by default was compatible with the way Creative's SB HW SF2 synths handled chorus on drum channels (that is no restriction after a GS reset). Then suddenly it changed to be compatible with Roland GS hardware (and thus incompatible with SB HW SF2 synths).

You can restore the old behavior by applying new flags (and FSMP applies this flag when the 'No SysEx' reset option is enabled) but for me such changes would be more acceptable if they were intruduced as opt-in instead of opt-out...

Hi,
Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later).
The easiest way to test is with another MIDI by Kr.palto47, this time from touhou 19 (the 88pro version). It sets chorus for snare drum 1 (key 38 i believe), but Bassmidi does not apply any chorus to the note. You can confirm this with SC-VA or spessasynth's latest development branch. This MIDI also alters the pitch of the drums, but it does so via a sysEx command rather than NRPN and Bassmidi doesn't seem to recognize those either.
Another example is This MIDI file, which uses NRPN for chorus. More precisely, it sets the snare 2 drum chorus to 64:

The attachment Screenshot_20260215_194809.png is no longer available

(the software is GS Advanced Editor)
And Bassmidi doesn't apply any chorus to the snare.

What's also interesting is that SC-55 had the behavior matching SB2 synths:
When you choose the SC-55 drum map in GSAE, the drum editor shows that chorus is enabled for all drum instruments by default, which is not the case on any later drum map (88,pro,etc.).
Nuked-SC55 confirms this.

Now regarding the pitch tuning, it is very strange. For the sysEx version of the command, it specifies the amount in semitone steps, while for the NRPN version the amount is in 50 cent steps. I thought this was an SCVA bug, but I sent the a test file to someone who owns a real SC-D70 and the behavior is replicated there (and youtube recordings with an 88pro seem to match it as well). Very strange! And, of course, if you select the sc-55 drum map the pitch in NRPN does use the full semitone steps...

Thanks for the deep analysis! If this is the case then the GS chorus related changes in newer Bassmidi versions are more annoying than I thought 😀
According to this the new behavior of Bassmidi is not compatible with anything while the old one was at least compatible with SB HW SF2 devices and to some degree with SC-55.

Would you be so kind to make a bug report to Ian at un4seen.com?
You can explain the problem much better than me. I will follow your post and provide full support if it's needed.
Thanks in advance!

@Edit:
I have made a bug report to Ian but I have only mentioned the problems I could test. I think you can extend the bug report with the results of your analysis.
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

Falcosoft wrote on 2026-02-15, 19:46:

Thanks for the deep analysis! If this is the case then the GS chorus related changes in newer Bassmidi versions are more annoyin […]
Show full quote

Spesek wrote on 2026-02-15, 18:55:

Hi, Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later). The easiest way t […]
Show full quote

Falcosoft wrote on 2026-02-15, 18:32:

Hi,
If I remember correctly Bassmidi already supports setting individual drum key's chorus send level. The problem is not this, but the default state. For many years Bassmidi by default was compatible with the way Creative's SB HW SF2 synths handled chorus on drum channels (that is no restriction after a GS reset). Then suddenly it changed to be compatible with Roland GS hardware (and thus incompatible with SB HW SF2 synths).

You can restore the old behavior by applying new flags (and FSMP applies this flag when the 'No SysEx' reset option is enabled) but for me such changes would be more acceptable if they were intruduced as opt-in instead of opt-out...

Hi,
Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later).
The easiest way to test is with another MIDI by Kr.palto47, this time from touhou 19 (the 88pro version). It sets chorus for snare drum 1 (key 38 i believe), but Bassmidi does not apply any chorus to the note. You can confirm this with SC-VA or spessasynth's latest development branch. This MIDI also alters the pitch of the drums, but it does so via a sysEx command rather than NRPN and Bassmidi doesn't seem to recognize those either.
Another example is This MIDI file, which uses NRPN for chorus. More precisely, it sets the snare 2 drum chorus to 64:

The attachment Screenshot_20260215_194809.png is no longer available

(the software is GS Advanced Editor)
And Bassmidi doesn't apply any chorus to the snare.

What's also interesting is that SC-55 had the behavior matching SB2 synths:
When you choose the SC-55 drum map in GSAE, the drum editor shows that chorus is enabled for all drum instruments by default, which is not the case on any later drum map (88,pro,etc.).
Nuked-SC55 confirms this.

Now regarding the pitch tuning, it is very strange. For the sysEx version of the command, it specifies the amount in semitone steps, while for the NRPN version the amount is in 50 cent steps. I thought this was an SCVA bug, but I sent the a test file to someone who owns a real SC-D70 and the behavior is replicated there (and youtube recordings with an 88pro seem to match it as well). Very strange! And, of course, if you select the sc-55 drum map the pitch in NRPN does use the full semitone steps...

Thanks for the deep analysis! If this is the case then the GS chorus related changes in newer Bassmidi versions are more annoying than I thought 😀
According to this the new behavior of Bassmidi is not compatible with anything while the old one was at least compatible with SB HW SF2 devices and to some degree with SC-55.

Would you be so kind to make a bug report to Ian at un4seen.com?
You can explain the problem much better than me. I will follow your post and provide full support if it's needed.
Thanks in advance!

@Edit:
I have made a bug report to Ian but I have only mentioned the problems I could test. I think you can extend the bug report with the results of your analysis.
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

Hi,
I saw the report you made and I think you explained it pretty well. Feel free to use my analysis to explain what's wrong in BM.
If you want to test the drum pitch file for yourself, I used this file:
https://github.com/spessasus/spessasynth_core … ch_nrpn_test.ts
simply run it through tsx and it should produce the output MIDI file which firstly changes drum pitch via sysEx and then via NRPN. It's very easy to hear the difference in SCVA.

PS: In your report you mentioned that SC-55 and SC-88 resets are different. How so? Can you explain please?

Spesek wrote on 2026-02-15, 22:32:

Hi, I saw the report you made and I think you explained it pretty well. Feel free to use my analysis to explain what's wrong in […]
Show full quote

Falcosoft wrote on 2026-02-15, 19:46:

Thanks for the deep analysis! If this is the case then the GS chorus related changes in newer Bassmidi versions are more annoyin […]
Show full quote

Spesek wrote on 2026-02-15, 18:55:

Hi, Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later). The easiest way t […]
Show full quote

Hi,
Bassmidi support pitch, but not chorus. (and the pitch support is also incorrect, but more on that later).
The easiest way to test is with another MIDI by Kr.palto47, this time from touhou 19 (the 88pro version). It sets chorus for snare drum 1 (key 38 i believe), but Bassmidi does not apply any chorus to the note. You can confirm this with SC-VA or spessasynth's latest development branch. This MIDI also alters the pitch of the drums, but it does so via a sysEx command rather than NRPN and Bassmidi doesn't seem to recognize those either.
Another example is This MIDI file, which uses NRPN for chorus. More precisely, it sets the snare 2 drum chorus to 64:

The attachment Screenshot_20260215_194809.png is no longer available

(the software is GS Advanced Editor)
And Bassmidi doesn't apply any chorus to the snare.

What's also interesting is that SC-55 had the behavior matching SB2 synths:
When you choose the SC-55 drum map in GSAE, the drum editor shows that chorus is enabled for all drum instruments by default, which is not the case on any later drum map (88,pro,etc.).
Nuked-SC55 confirms this.

Now regarding the pitch tuning, it is very strange. For the sysEx version of the command, it specifies the amount in semitone steps, while for the NRPN version the amount is in 50 cent steps. I thought this was an SCVA bug, but I sent the a test file to someone who owns a real SC-D70 and the behavior is replicated there (and youtube recordings with an 88pro seem to match it as well). Very strange! And, of course, if you select the sc-55 drum map the pitch in NRPN does use the full semitone steps...

Thanks for the deep analysis! If this is the case then the GS chorus related changes in newer Bassmidi versions are more annoying than I thought 😀
According to this the new behavior of Bassmidi is not compatible with anything while the old one was at least compatible with SB HW SF2 devices and to some degree with SC-55.

Would you be so kind to make a bug report to Ian at un4seen.com?
You can explain the problem much better than me. I will follow your post and provide full support if it's needed.
Thanks in advance!

@Edit:
I have made a bug report to Ian but I have only mentioned the problems I could test. I think you can extend the bug report with the results of your analysis.
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

Hi,
I saw the report you made and I think you explained it pretty well. Feel free to use my analysis to explain what's wrong in BM.
If you want to test the drum pitch file for yourself, I used this file:
https://github.com/spessasus/spessasynth_core … ch_nrpn_test.ts
simply run it through tsx and it should produce the output MIDI file which firstly changes drum pitch via sysEx and then via NRPN. It's very easy to hear the difference in SCVA.

PS: In your report you mentioned that SC-55 and SC-88 resets are different. How so? Can you explain please?

Hi,
1. I think the pitch issue is a separate one and currently I do not think I'm willing to deal with it.
2. SC-88 and later devices recognize special SC-88 mode set messages that also function as a (GS) reset. They can be tested with SC-VA:
F0 41 10 42 12 00 00 7F 00 01 F7

SC-88+ specific Midi files use them many times. Bassmidi also recognizes such messages as equivalent to a GS reset.

@Edit:
BTW, your SC-88Pro LCD Bitmap example files also contain such messages instead of classic GS resets:

Spesek wrote on 2026-02-15, 22:32:

...
And Bassmidi doesn't apply any chorus to the snare.

Hi,
Ian has responded to my report and regarding Bassmidi's SC-88(+) drum key chorus level emulation I think he is right. It seems even SC-VA resets drum key settings to default after a program change message.
https://www.un4seen.com/forum/?topic=20880.ms … 46255#msg146255

Falcosoft wrote on 2026-02-16, 16:36:

Hi, Ian has responded to my report and regarding Bassmidi's SC-88(+) drum key chorus level emulation I think he is right. It see […]
Show full quote

Spesek wrote on 2026-02-15, 22:32:

...
And Bassmidi doesn't apply any chorus to the snare.

Hi,
Ian has responded to my report and regarding Bassmidi's SC-88(+) drum key chorus level emulation I think he is right. It seems even SC-VA resets drum key settings to default after a program change message.
https://www.un4seen.com/forum/?topic=20880.ms … 46255#msg146255

Hi,
ndeed it looks like I overlooked that, sorry! GSAE and SC-VA's drum editor both show 64 there, but after listening indeed there's no snare there.
But the chorus issue from the th19 MIDI still applies. I just checked again with SC-VA and the chorus is noticeably applied to the snare 1 drum (and a pitch change). Neither are present in BASSMIDI's rendering.

Falcosoft wrote on 2026-02-15, 12:22:

Hi, Unfortunately I cannot help with such issues. You should tell such problems to Ian at https://www.un4seen.com/ (forum sectio […]
Show full quote

ColomboGMGS2 wrote on 2026-02-15, 10:56:

Update: Something fishy is going on with my new "Sub Aqua" preset I designed keeping step with the same named preset found in so […]
Show full quote

Falcosoft wrote on 2026-02-10, 10:00:

Hi, The term 'Midi Panic' was not too helpful since it was so radical that it suggested for me that you noticed something that w […]
Show full quote

Hi,
The term 'Midi Panic' was not too helpful since it was so radical that it suggested for me that you noticed something that was fundamentally broken.
Watching your video made it clear what your problem was. I introduced All Sounds Off instead of All Notes Off in case of Mute/Solo since All Notes Off messages simply cannot mute looped sustained notes.
But to tell you the truth this problem occurs rather rarely since most sustained notes are not looped and have a proper release phase.
I did not think that a little bit more abrupt muting of notes makes someone think of 'Midi Panic' 😀.
So OK, I reverted the change. You can try the new test version. You should simply overwrite the files in FSMP's folder with the new ones:
https://falcosoft.hu/midiplayer_66_test.zip

Update: Something fishy is going on with my new "Sub Aqua" preset I designed keeping step with the same named preset found in some Yamaha PSR.
probably this is just a bassmidi issue...

My tone is designed to go through a delayed filter envelope that goes like this (according to how I hear or at least imagine)
in the initial envelope delay of 0.05 seconds, the tone stays bright during that small time,
Then with a snappy attack (almost sounds like a cut) of 0.001 seconds the tone dips below a low-pass filter of -3100 cents.
When the note is released, then it gradually climbs (or Wahs) back up to the brightness as it quickly fades out.
The overall pattern sounds like an "AMmmmmwuA" rather than an "AWUummmuwuh"

Somehow the snappy attack I mentioned has now become slower.
Even when I remove the attack value entirely, the new bassmidi puts some high attack time value as a placeholder.
So there is a difference between how it sounded before on FSMP 5.8's bassmidi library and the current one.
The current bassmidi version had pretty much turned my sub aqua into nothing more than a "yet another synth bass preset" 🙁
*this same problem is also present in virtualmidisynth 2.12.8 as well.

Test video: https://youtu.be/tTHG1XxfSdg

...

Hi,
Unfortunately I cannot help with such issues. You should tell such problems to Ian at https://www.un4seen.com/ (forum section).
He is usually very helpful, but of course his and our vision of Bassmidi regarding compatibility sometimes differ and of course usually his version wins.

@Edit:
1. Regarding your ruined tone problem:
In FSMP there is an advanced setting that can only be changed using the registry (HKEY_CURRENT_USER\Software\falcosoft\MidiPlayer) or in the MidiPlayer.ini file. It's called

BassMidiFontInitFlags

. With the help of this flags field you can try/set any present or future values defined by BassMidi. That is:

Copy code to clipboard

1// BASS_MIDI_FontInit flags
2#define BASS_MIDI_FONT_MEM			0x10000
3#define BASS_MIDI_FONT_MMAP			0x20000
4#define BASS_MIDI_FONT_XGDRUMS		0x40000
5#define BASS_MIDI_FONT_NOFX			0x80000
6#define BASS_MIDI_FONT_LINATTMOD	0x100000
7#define BASS_MIDI_FONT_LINDECVOL	0x200000
8#define BASS_MIDI_FONT_NORAMPIN		0x400000
9#define BASS_MIDI_FONT_NOSBLIMITS	0x800000
10#define BASS_MIDI_FONT_NOLIMITS		BASS_MIDI_FONT_NOSBLIMITS
11#define BASS_MIDI_FONT_MINFX		0x1000000
12#define BASS_MIDI_FONT_SBLIMITS		0x2000000
13#define BASS_MIDI_FONT_STEREO		0x4000000  

BassMidiFontInitFlags is a bit field which means you can combine all of the above flag values by logical OR operators (which in this case actually equivalent to an arithmetical addition) to get an overall value that you can set.
E.g. to test the BASS_MIDI_FONT_SBLIMITS flag together with the BASS_MIDI_FONT_LINATTMOD flag you can simply add them. That is:
0x100000 + 0x2000000 = 0x2100000 (34603008 in decimal).
I recommend to test the BASS_MIDI_FONT_SBLIMITS flag first since it changed recently (the default was the opposite).

2.

And also, there is this drum-chorus-prohibition facade I read from that discussion on Un4seen. I tried my best to ignore that difference until I played some old karaoke midi files.
In those tracks, every single channel including drums was set at a high chorus level.

I have already built in a workaround to circumvent this 'chorus on drum channels is always disabled in GS mode' limitation into FSMP.
To activate the workaround you should select the 'No SysEx' reset mode option instead of GS and then press the 'Reset' button. Then even in case of GS files you can adjust the Chorus level on drum channels.

Thank you. Should i paste those values into the said .ini file in my directory?

ColomboGMGS2 wrote on 2026-02-18, 09:47:

Thank you. Should i paste those values into the said .ini file in my directory?

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find the mentioned 'BassMidiFontInitFlags' key in MidiPlayer.ini file in FSMP's folder.
But If it's 'Store Settings in Registry' then you can find the mentioned 'BassMidiFontInitFlags' key in 'HKEY_CURRENT_USER\Software\falcosoft\MidiPlayer'.

BTW, We have got good news related to the 'disabled chorus effect on drum channels in GS mode' issue. It seems I succeeded in convincing Ian that disabling chorus effect on drum channels in simple GS mode was a bad idea:
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

So you can try the newest Bassmidi.dll version(s) that Ian posted at the end of the conversation. With these new versions chorus should not be disabled on drums in GS mode so you do not have to always use the 'No SysEx' reset option of FSMP to use chorus effect on drum channels in GS mode.
(Even if you do not want to test the new beta versions right now, grab that Bassmidi.dll files since in the end Ian can change his mind 😀 )

Falcosoft wrote on 2026-02-18, 11:16:

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find t […]
Show full quote

ColomboGMGS2 wrote on 2026-02-18, 09:47:

Thank you. Should i paste those values into the said .ini file in my directory?

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find the mentioned 'BassMidiFontInitFlags' key in MidiPlayer.ini file in FSMP's folder.
But If it's 'Store Settings in Registry' then you can find the mentioned 'BassMidiFontInitFlags' key in 'HKEY_CURRENT_USER\Software\falcosoft\MidiPlayer'.

BTW, We have got good news related to the 'disabled chorus effect on drum channels in GS mode' issue. It seems I succeeded in convincing Ian that disabling chorus effect on drum channels in simple GS mode was a bad idea:
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

So you can try the newest Bassmidi.dll version(s) that Ian posted at the end of the conversation. With these new versions chorus should not be disabled on drums in GS mode so you do not have to always use the 'No SysEx' reset option of FSMP to use chorus effect on drum channels in GS mode.
(Even if you do not want to test the new beta versions right now, grab that Bassmidi.dll files since in the end Ian can change his mind 😀 )

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast!

btw, something fishy went down with a VST Effect that has an option to sync its LFO to the BPM, here I documented it in a video. more details in the description.
https://youtu.be/027AxawRXl4
(This video was uploaded before me getting to know the good news about chorus, so please disregard any chorus related rambling there.)

ColomboGMGS2 wrote on Yesterday, 16:45:

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast! […]
Show full quote

Falcosoft wrote on 2026-02-18, 11:16:

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find t […]
Show full quote

ColomboGMGS2 wrote on 2026-02-18, 09:47:

Thank you. Should i paste those values into the said .ini file in my directory?

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find the mentioned 'BassMidiFontInitFlags' key in MidiPlayer.ini file in FSMP's folder.
But If it's 'Store Settings in Registry' then you can find the mentioned 'BassMidiFontInitFlags' key in 'HKEY_CURRENT_USER\Software\falcosoft\MidiPlayer'.

BTW, We have got good news related to the 'disabled chorus effect on drum channels in GS mode' issue. It seems I succeeded in convincing Ian that disabling chorus effect on drum channels in simple GS mode was a bad idea:
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

So you can try the newest Bassmidi.dll version(s) that Ian posted at the end of the conversation. With these new versions chorus should not be disabled on drums in GS mode so you do not have to always use the 'No SysEx' reset option of FSMP to use chorus effect on drum channels in GS mode.
(Even if you do not want to test the new beta versions right now, grab that Bassmidi.dll files since in the end Ian can change his mind 😀 )

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast!

btw, something fishy went down with a VST Effect that has an option to sync its LFO to the BPM, here I documented it in a video. more details in the description.
https://youtu.be/027AxawRXl4
(This video was uploaded before me getting to know the good news about chorus, so please disregard any chorus related rambling there.)

Hi,
I have watched the video and read the description.
But ultimately I have a feeling that you misunderstood what was happening and why with your affected effect:

If the effect has an LFO sync option, just sync it to the given fraction of BPM and not precisely the current beat marker.

The most important thing to realize is that it's not true that Midi Player itself makes the effects sync to anything.
It's entirely the effect's business to sync to anything if it wants to. The only thing that newer Midi Player does (actually it's rather the newer versions of Bass_VST ) that older versions did not is sending the correct VstTimeInfo structure, but only when it's asked by the effect!
So it should be set on the VST effect's side to ask for VstTimeInfo or not. And it also depends entirely on the effect how it reacts to the given timing info.
This decision is made on the effect side not on the host side (in this case the host is Midi Player/Bass_VST).
Older versions of Bass_VST always sent fake/invalid timing info to effect plugins for such requests. In the newer versions you can set a callback so the effect plugins can get real timing info from the host's side. But that's all, the host does not make the effect sync to anything.
https://github.com/Falcosoft/BASS_VST/commit/ … 7be34334deb19ac

Falcosoft wrote on Yesterday, 19:23:

Hi, I have watched the video and read the description. But ultimately I have a feeling that you misunderstood what was happening […]
Show full quote

ColomboGMGS2 wrote on Yesterday, 16:45:

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast! […]
Show full quote

Falcosoft wrote on 2026-02-18, 11:16:

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find t […]
Show full quote

It depends on the 'Main menu -> Storage of Settings -> Store Settings in...' option. If it's 'INI File' then yes, you can find the mentioned 'BassMidiFontInitFlags' key in MidiPlayer.ini file in FSMP's folder.
But If it's 'Store Settings in Registry' then you can find the mentioned 'BassMidiFontInitFlags' key in 'HKEY_CURRENT_USER\Software\falcosoft\MidiPlayer'.

BTW, We have got good news related to the 'disabled chorus effect on drum channels in GS mode' issue. It seems I succeeded in convincing Ian that disabling chorus effect on drum channels in simple GS mode was a bad idea:
https://www.un4seen.com/forum/?topic=20880.ms … 46246#msg146246

So you can try the newest Bassmidi.dll version(s) that Ian posted at the end of the conversation. With these new versions chorus should not be disabled on drums in GS mode so you do not have to always use the 'No SysEx' reset option of FSMP to use chorus effect on drum channels in GS mode.
(Even if you do not want to test the new beta versions right now, grab that Bassmidi.dll files since in the end Ian can change his mind 😀 )

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast!

btw, something fishy went down with a VST Effect that has an option to sync its LFO to the BPM, here I documented it in a video. more details in the description.
https://youtu.be/027AxawRXl4
(This video was uploaded before me getting to know the good news about chorus, so please disregard any chorus related rambling there.)

Hi,
I have watched the video and read the description.
But ultimately I have a feeling that you misunderstood what was happening and why with your affected effect:

If the effect has an LFO sync option, just sync it to the given fraction of BPM and not precisely the current beat marker.

The most important thing to realize is that it's not true that Midi Player itself makes the effects sync to anything.
It's entirely the effect's business to sync to anything if it wants to. The only thing that newer Midi Player does (actually it's rather the newer versions of Bass_VST ) that older versions did not is sending the correct VstTimeInfo structure, but only when it's asked by the effect!
So it should be set on the VST effect's side to ask for VstTimeInfo or not. And it also depends entirely on the effect how it reacts to the given timing info.
This decision is made on the effect side not on the host side (in this case the host is Midi Player/Bass_VST).
Older versions of Bass_VST always sent fake/invalid timing info to effect plugins for such requests. In the newer versions you can set a callback so the effect plugins can get real timing info from the host's side. But that's all, the host does not make the effect sync to anything.
https://github.com/Falcosoft/BASS_VST/commit/ … 7be34334deb19ac

So I should change the vst plugin dll. Shame on me for being not that much of a programmer.

ColomboGMGS2 wrote on Today, 06:09:

Falcosoft wrote on Yesterday, 19:23:

Hi, I have watched the video and read the description. But ultimately I have a feeling that you misunderstood what was happening […]
Show full quote

ColomboGMGS2 wrote on Yesterday, 16:45:

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast! […]
Show full quote

Thanks for the heads-up. I downloaded the updated bassmidi test versions and had a blast!

btw, something fishy went down with a VST Effect that has an option to sync its LFO to the BPM, here I documented it in a video. more details in the description.
https://youtu.be/027AxawRXl4
(This video was uploaded before me getting to know the good news about chorus, so please disregard any chorus related rambling there.)

Hi,
I have watched the video and read the description.
But ultimately I have a feeling that you misunderstood what was happening and why with your affected effect:

If the effect has an LFO sync option, just sync it to the given fraction of BPM and not precisely the current beat marker.

The most important thing to realize is that it's not true that Midi Player itself makes the effects sync to anything.
It's entirely the effect's business to sync to anything if it wants to. The only thing that newer Midi Player does (actually it's rather the newer versions of Bass_VST ) that older versions did not is sending the correct VstTimeInfo structure, but only when it's asked by the effect!
So it should be set on the VST effect's side to ask for VstTimeInfo or not. And it also depends entirely on the effect how it reacts to the given timing info.
This decision is made on the effect side not on the host side (in this case the host is Midi Player/Bass_VST).
Older versions of Bass_VST always sent fake/invalid timing info to effect plugins for such requests. In the newer versions you can set a callback so the effect plugins can get real timing info from the host's side. But that's all, the host does not make the effect sync to anything.
https://github.com/Falcosoft/BASS_VST/commit/ … 7be34334deb19ac

So I should change the vst plugin dll. Shame on me for being not that much of a programmer.

The only thing that can be done on the Host/Midi Player's side is a compatibility setting not to send real timing info. Actually there is already a compatibility setting for Midi devices namely 'Send Start/Stop/Clock messages'. Such messages are not relevant for effect plugins since they do not get Midi messages at all but the purpose is the same. So sending VST timing info could be linked to the same compatibility setting.