I mean, it is very likely there is some problem in my UI code, but VST format is extremely badly documented, and almost no one programming UIs directly as I did, most VSTs created with SynthEdit-alike constructors. So I can't even know for sure.
]]>the trouble is with the UI, when i click in the plugin UI to another midi channel, all the envelope settings stay the same. i cannot set custom envelopes per channel.
in other words, the plugin UI is forcing me to use the same envelope settings for every midi channel. is there a way to fix this?
]]>It was the last mass produced device of such kind in the USSR. There was a similar but 8086-powered MK-98 follow up in the works, a few production quality fully functional prototypes were found, but it was never available to the mass market.
]]>https://github.com/linuxmao-org/shiru-plugins
LMMS can "natively" load and run windows VST (even from Linux, using Wine and their own engine called VeSTige), and it can also run LV2 and native linux VST with the Carla Engine (it's an external project but it runs well).
]]>A while back, way before I took the VST route, I had a desire to support LMMS, which was the best free FL-style DAW out there. I come to their IRC channel and started to ask questions, like, how to make native plugins, are there people who would want it. They said - nah, do VST instead. So I did eventually, and I guess it has been a good advice, after all.
]]>I've briefly looked into VST in the past, and indeed it seemed like a huge mess. Sadly Steinberg's stance and actions don't help to advance open source development in that field either.
In regards to DAW plugins in general, the situation is hardly better on Linux & Co. This is from the LV2 documentation:
What not to do: If you are new to LV2, do not look at the specifications and API references first! These references provide detail, but not necessarily a clear high-level view.
And then they wonder why adoption of this standard is so slow (even though the standard itself if quite good imo). And the API reference actually isn't bad, but it indeed provides no overview whatsoever.
]]>I'm sure up to making software more accessible and to supporting more platforms, but only if it does not take too much effort/resources that could be otherwise spent to other developments (or to make damn music, I got a dozens of music tools already that I have never used myself). Unfortunately, for VST it is anything but easy. The original framework documentation is exceptionally bad, VST3 is exceptionally over engineered, there is tons of compatibility quirks between hosts, none of numerous VST wrappers out there are easy to setup or use, possibility of hooking up Qt or SDL is a total mystery, etc. No wonder most of VSTs out there were made with the SynthEdit, and you can barely find a properly programmed open source one.
]]>- MS is now one of the biggest sponsors of the Linux Foundation
- WSL2
- dropping Chakra for Chrome
While the latter has no direct connection to Linux, but it shows that the company philosophy is shifting away from doing everything in-house.
Anyway, let me just say I still very much appreciate that you took the time to make 1tracker build smoothly on Linux, even more so considering the story you told.
]]>A true story: in 2002 or so I had to break any interaction with a friend, because he moved to Linux completely (he's a web designer, so GIMP and a text editor was all he needed) and developed a habit of calling me even so often and spend long hours simply repeatedly telling me that I should drop Windows ASAP, and start to program for Linux, because Linux is the new greatest thing in universe and Windows is shit and going to die out soon anyway. This kind of advertising worked very well in alienating me from this stuff up to this day.
]]>Also yup, I guess 32-bit is on its way out. Not a big fan of this development, but I don't have 32-bit compatibility on my main machine anymore either, as it mainly just increases the number of packages that need to be updated. Then again you should just come over to the dark side and develop for *nix 
Guess in a few years Microsoft will to switch to a Linux kernel for Windows anyway.
This one got x64 support (comes in two versions). It starts to be the main issue with all of my plugins, people are always asking for 64-bit support. So it seems you have to have 64 bit to promote 1 bit technologies these days. Going to update all of my synths to x64 support sometime soon, as well as some maintenance for PCSPE.
]]>I've also finished my previous track, but I might expand it in the future: https://battleofthebits.org/arena/Entry/The+Ride/29099/
]]>I'll try to use it with chipwave in my next tune!!
]]>