Hi Falcosoft,

I just wanted to say how much I truly appreciate your MIDI Player. Many of the people I talk to feel the same, and the updates in version 6.5 are especially welcome.

I do have one question, though — MIDI Player seems to only let me sort through 16 channels and only displays 16 in the visualizer, even when there are more than 16 channels. Is there an option to expand this that I may have overlooked? Or do you have any plans to implement a feature that would allow viewing and sorting all channels, similar to the Sound Canvas or other VSTs?

This feature would be incredibly helpful for preparing arrangements, as I often use the chorus, reverb, and volume controls to shape the sound I’m aiming for — and it’s just a lot of fun to experiment with.

Again, thank you for creating such an amazing piece of software!

Best regards,
Stevacus

Stevacus wrote on 2025-08-15, 20:12:

Hi Falcosoft, […]
Show full quote

Hi Falcosoft,

I just wanted to say how much I truly appreciate your MIDI Player. Many of the people I talk to feel the same, and the updates in version 6.5 are especially welcome.

I do have one question, though — MIDI Player seems to only let me sort through 16 channels and only displays 16 in the visualizer, even when there are more than 16 channels. Is there an option to expand this that I may have overlooked? Or do you have any plans to implement a feature that would allow viewing and sorting all channels, similar to the Sound Canvas or other VSTs?

This feature would be incredibly helpful for preparing arrangements, as I often use the chorus, reverb, and volume controls to shape the sound I’m aiming for — and it’s just a lot of fun to experiment with.

Again, thank you for creating such an amazing piece of software!

Best regards,
Stevacus

Hi,
No, currently the visualization is limited to first 16 channels. Expanding this is not an easy task and I have been thinking about the possibilities for a while. Displaying and handling e.g. 4 x 16 channels is a UI nightmare.
So currently I cannot promise anything for the near future.

Falcosoft wrote on 2025-08-15, 20:43:

Hi, No, currently the visualization is limited to first 16 channels. Expanding this is not an easy task and I have been thinking […]
Show full quote

Stevacus wrote on 2025-08-15, 20:12:

Hi Falcosoft, […]
Show full quote

Hi Falcosoft,

I just wanted to say how much I truly appreciate your MIDI Player. Many of the people I talk to feel the same, and the updates in version 6.5 are especially welcome.

I do have one question, though — MIDI Player seems to only let me sort through 16 channels and only displays 16 in the visualizer, even when there are more than 16 channels. Is there an option to expand this that I may have overlooked? Or do you have any plans to implement a feature that would allow viewing and sorting all channels, similar to the Sound Canvas or other VSTs?

This feature would be incredibly helpful for preparing arrangements, as I often use the chorus, reverb, and volume controls to shape the sound I’m aiming for — and it’s just a lot of fun to experiment with.

Again, thank you for creating such an amazing piece of software!

Best regards,
Stevacus

Hi,
No, currently the visualization is limited to first 16 channels. Expanding this is not an easy task and I have been thinking about the possibilities for a while. Displaying and handling e.g. 4 x 16 channels is a UI nightmare.
So currently I cannot promise anything for the near future.

Thanks for your response. Regardless, it’s still a treasure of a tool, and I, along with many others, truly appreciate your work.

Hope you’re having a great one! 😀

Hi Zoltan )
I know what you make VST things , how about compile this plugins to VST versions ? https://github.com/Wohlstand/ADLplug Author said , what previous man not answered from 2022 year , also author said , what he can help you in make VST version if you want make VST version his and if you have questions to author )
His plugins https://disk.yandex.ru/d/U5268ZIzskaFbQ old versiuons )

Roland User wrote on 2025-08-20, 10:46:

Hi Zoltan )
I know what you make VST things , how about compile this plugins to VST versions ? https://github.com/Wohlstand/ADLplug Author said , what previous man not answered from 2022 year , also author said , what he can help you in make VST version if you want make VST version his and if you have questions to author )
His plugins https://disk.yandex.ru/d/U5268ZIzskaFbQ old versiuons )

There is already a VSTi plugin version of this.
https://github.com/jpcima/ADLplug

Yes , but you see date ? ) Date make is 2021 , but now available version from 2025 year ) , because I ask you )
https://github.com/Wohlstand/libADLMIDI/tree/master
sorry , I mistake before with link
also available https://github.com/Wohlstand/libOPNMIDI/releases/tag/v1.6.0 )

I can waiting what you will be caloborate with Wohlstand or VST version his synths not appear ?
I ask this only because of I very want ESFM 1868

Roland User wrote on 2025-08-23, 21:16:

I can waiting what you will be caloborate with Wohlstand or VST version his synths not appear ?
I ask this only because of I very want ESFM 1868

I do not understand why you think that the better option is to convince me to write a new plugin from scratch instead of convincing the authors of the existing plugin to release a new version based on the changes.
Wohlstand fork of the VSTi plugin is only 3 months old (the last commit has a date of May 26, 2025).
https://github.com/Wohlstand/ADLplug/commits/master/

So no, I will not do this.
I write plugins because I have the mood, free time and I'm genuinely interested in the topic, not because someone else 'very wants it'. Just so you know.

BTW, If you 'very want' ESFM 1868 why have you linked the libOPNMIDI library ? OPN2 (YM2612) has nothing to do with ESFM. OPN2 is not even OPL3 compatible.

As I see it the problem is that you always want things without researching and learning even the basics and you very much like to delegate all the work to others. That's not how it works in the real world...

PS:
As for me this conversation is over. Please, do not force me to ban you again by not accepting my final answer (that is no).

Bye.

Good ) but I think what I can answer you )

Falcosoft wrote on 2025-08-23, 21:59:

I write plugins because I have the mood, free time and I'm genuinely interested in the topic, not because someone else 'very wants it'. Just so you know.

This I known , becuse offer you learn this synth

Falcosoft wrote on 2025-08-23, 21:59:

BTW, If you 'very want' ESFM 1868 why have you linked the libOPNMIDI library ? OPN2 (YM2612) has nothing to do with ESFM. OPN2 is not even OPL3 compatible.

Because author sayd what want add ESFM in new version

Falcosoft wrote on 2025-08-23, 21:59:

As for me this conversation is over. Please, do not force me to ban you again by not accepting my final answer (that is no).

Good , I understand you ) thank you )

Simply before we friend-friend did not understand , you finded old version in which absent ESFMu , and I offered to you link with author for refresh VST version )

Roland User wrote on Yesterday, 01:28:

...
Because author sayd what want add ESFM in new version

It seems that the author (Wohlstand) added ESFM support to libADLMIDI library not to libOPNMIDI.
https://github.com/Wohlstand/libADLMIDI
It's more logical since libADLMIDI uses OPL3 emulation while libOPNMIDI does not.
libADLMIDI and libOPNMIDI are 2 different libraries and you mixed them up.

Roland User wrote on Yesterday, 01:28:

Good , I understand you ) thank you )
Simply before we friend-friend did not understand , you finded old version in which absent ESFMu , and I offered to you link with author for refresh VST version )

I still do not understand why you want me to do this when Wohlstand has already forked the VSTi plugin's repository (and the VSTi plugin is based on Wohlstand's own libADLMIDI and libOPNMIDI libraries ) so he can add his own latest changes easily.
Why do you think that I'm needed for this?

Because Wohlstand do driver version , and VST version before make Jean-Pierre Simalenda , and Wohlstand say to me in discussed with him :

Wohlstand (15:34:46 20/08/2025)
https://github.com/Wohlstand/ADLplug чутка освежил штуку, но не полностью
Wohlstand (15:35:16 20/08/2025)
Жан-Пьер Сималёнду с сентября 2022 года вообще не выходит на связь ни с кем, даже свои его потеряли
Wohlstand (15:35:30 20/08/2025)
Именно он и занимался этими VST-штуками

and translate to english :

Wohlstand (15:34:46 08/20/2025)
https://github.com/whlstand/adlplug a bit refreshed the thing, but not completely
Wohlstand (15:35:16 08/20/2025)
Jean-Pierre Simalenda since September 2022 has not come in touch with anyone at all, even lost his
Wohlstand (15:35:30 08/20/2025)
It was he who was engaged in these VST-slats

and I don't know anyone but you who make VST plugins from sources other authors

Roland User wrote on Yesterday, 08:43:

... Wohlstand (15:34:46 08/20/2025) https://github.com/whlstand/adlplug a bit refreshed the thing, but not completely .... […]
Show full quote

...
Wohlstand (15:34:46 08/20/2025)
https://github.com/whlstand/adlplug a bit refreshed the thing, but not completely
....

That's the point: Wohlstand has already refreshed the repository and made modifications to the existing VSTi plugin but he is not ready yet.
So you only have to be a little more patient instead of nagging me to write a new one...

If I right understand Wohlstand , him not do VST version , he do only driver version , and convert from driver to VST other developer , and I assumed what you can linked with Wohlstand and maybe if you this do Interesting , so will new versions VST solutions ) , but before that I mistake link and because you thinked what this already exists

Roland User wrote on Yesterday, 09:01:

If I right understand Wohlstand , him not do VST version , he do only driver version , and convert from driver to VST other developer , and I assumed what you can linked with Wohlstand and maybe if you this do Interesting , so will new versions VST solutions ) , but before that I mistake link and because you thinked what this already exists

I do not think you are right. This is the repository of the VSTi plugin on Wohlstand's account and it is fresh (only 3 months old):
https://github.com/Wohlstand/ADLplug
Why has he forked it and made modification to it if he wants some other developer to maintain it?
The plugin's code is based on Wohlstand's libraries so no one is better suited for this task than Wohlstand himself.
But actually it does not matter. I'm not interested so I definitely will not be the one who maintains it.
If it's true that Wohlstand does not want to maintain the plugin then you have to find someone else for this task.

Good ) I understand you )
But here you look only to date repository , and not look to :
Author: Jean Pierre Cimalando
and missing what Author: Jean Pierre Cimalando
and I not have link with Jean Pierre Cimalando

Roland User wrote on Yesterday, 09:24:

Good ) I understand you ) But here you look only to date repository , and not look to : Author: Jean Pierre Cimalando and missin […]
Show full quote

Good ) I understand you )
But here you look only to date repository , and not look to :
Author: Jean Pierre Cimalando
and missing what Author: Jean Pierre Cimalando
and I not have link with Jean Pierre Cimalando

You are really tiresome. Do you know what does a fork mean? I have seen the original author but why does it matter?
Wohlstand already has its own fork of the repository so he has free hands to do whatever he wants with it.
The question is why do you think that maintaining this plugin would be better suited for me than for Wohlstand.
At least he knows the base libraries since he wrote them. I have nothing to do with either of the plugin or the libraries.
So you had better convince Wohlstand than me.

I hope what you not angry to me , simly I originally gave no right link , excusme )

Hmm appeared question ) when I speak with Wohlstand , he say what in GS reset do so :
9, 0, 1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 12, 13, 14, 15
this from https://github.com/Wohlstand/libADLMIDI/blob/ … cpp#L1028-L1128
if not difficult , tell why Roland start reset from 9 channel and next 0,1,2 etc ? What is the cause this solution ?

Roland User, dude, you explained a total mess. Let me clarify about the stuff so no longer misunderstandings should be.
- I develop MIDI synthesizer core libraries such as libADLMIDI and libOPNMIDI, and I have bundled tools like cross-platform terminal players, plugins for VLC player and WinMM drivers.
- My friend JPCima developed powerful VST plugins over my libraries and we worked together.
- Unfortunately, my friend is gone at September 0f 2022 and nobody can find him, even his close friends (I unexpectedly received one of such letters) and since that all his projects became unmaintained.
- I took the maintenance over his ADLJack repository that implements the MIDI daemon that I actively use on Linux to make music using Sekaiju MIDI editor.
- His ADLplug repository that contains VST plugins were left without write access for me at all.
- I made my fork 3 months ago to just apply minor fixes, but later I just didn't touched it for a long time since any VST modules aren't in my priority.
- What actually Roland User wanted from Falcosoft: he wants Falcosoft to pick up the most recent version of ADLplug (my fork is right now) repo and continue its maintenance so let new updates with the most fresh libADLMIDI's and libOPNMIDI's cores being available in VST/LV2 plugin format too.
- By myself I am not super-interested in VST since I don't use any of such stuff on my end and across of my users it's very small demand on VST/LV2 plugins (or isn't just users of JPCima's ADLplug/OPNplug are fine with existing stuff?). I do use DAWs very rarely, just because I am fan of pure MIDI and I use my libADLMIDI and libOPNMIDI directly in game projects to play musics from MIDI files directly. But if anybody greatly wants a VST - feel free to assist me to maintain such overlays. While JPCima was available, we worked very good, and his ADLplug received my updates rapidly.

Roland User wrote on Yesterday, 14:13:

Hmm appeared question ) when I speak with Wohlstand , he say what in GS reset do so : 9, 0, 1, 2, 3, 4, 5, 6, 7, 8, […]
Show full quote

Hmm appeared question ) when I speak with Wohlstand , he say what in GS reset do so :
9, 0, 1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 12, 13, 14, 15
this from https://github.com/Wohlstand/libADLMIDI/blob/ … cpp#L1028-L1128
if not difficult , tell why Roland start reset from 9 channel and next 0,1,2 etc ? What is the cause this solution ?

That sequence of numbers has nothing to do with GS reset messages. If you inspect the code more carefully you can notice that the sequence belongs to the 'Percussion channel' setting part.
Moreover the order of the numbers does not mean at all that Roland synths 'start the reset' from that channel. The order of these numbers can be explained simply by the syntax of the SysEx messages that can switch channels to be either melodic or drum/percussion channels.
This is the format of such a message: F0 41 10 42 12 40 10 15 00 1B F7
The bold part denotes the channel. In this case '10' in hexadecimal means channel 10, but '11', means channel 1. The sequence is up to '1F' that means channel 16.
FYI: In the Midi protocol channel numbering starts from 0 not from 1. This explains why all the numbers in the code have a -1 offset compared to everyday channel numbering convention.