everal of us are individually working on specific software solutions to solve the Kronos backwards compatibility gap. Michel's PCG Tools are available, while cynkh and I are working on program and combi conversion respectively. It would be nice to somehow incorporate all of these tools into a common framework.
There are two back doors into the program. If a DLL file is written to query a SysEX file or a PCG file, the program will suck all the data from that and populate the KRONOS UI. The function for running the DLL already exists.
The other option is simply text. If someone else’s program was to output the parameters of a PCG to a text file, a filter can be written to populate the KRONOS UI. That function already exists too. I just didn't write the filter.
I wish that would work for Triton family programs too.
The approach makes it possible to use anything. So long as the KRONOS UI is complete, then it’s only a matter of making the connections to it from the UI of some other keyboard. Let people then try it and based on the feedback, it's only a matter of then writing in the offset values so things match up sound wise better.
So how did you do it? Did you have to create that UI from scratch? Or did you have some existing M1 code base to build on?
Yes and no… I took screen shots of the VSTi and using Photo Shop I removed all the controls. I then placed my own controls in over the background layer.
To make it look like the KORG buttons are still real, I’ve placed invisible buttons over them that recall different graphics and the correct controllers I’ve mapped.
This is a Windows program, and not something that is native to the Kronos?
There will be 2 Windows versions.
1: An online version where up to 50 people can access the system at the same time. You can pool your efforts into populating the program with sounds, and then you can all use it, or download copies of the database to populate option two.
2: A normal standalone version.
Regards
Sharp.