Hey folks,

There used to be a website where this could be done before, but it died. I made a Python script to do this instead, but it turned out to not be so user-friendly to non-programmers. So I ported it to a Flask web app which I'm hosting here:

https://scala2mts.vercel.app

With this form you can upload a Scala tuning file and get a MIDI SysEx file back. You can upload this to your hardware, such as Cirklon or Prophet rev2 with SysEx Librarian.

Thank you so much for Scala2MTS!!! I am so happy to have this capability now. I used to use the website you mentioned that allowed this, until it disappeared. I tried out Scala2MTS today and it worked perfectly. I tested it by creating a sysex file from a scala file using Scala2MTS and then sending it using Bome SendSX to my Novation Summit. I tested it with that synth because while it will receive tuning files via sysex, it also allows creating tunings directly on the instrument. Therefore I could carefully check the file in detail after sending it via sysex. It worked fine and checked out perfectly.
I will use Scala2MTS to create tuning files to send to my Sequential Pro 3, which will receive the files by sysex, but that synth does not allow creating tunings directly on the instrument. I already sent a bunch of tuning files to the Pro 3, back when the old Scala to MTS converter was still available online, but when it disappeared, that was the end of my ability to send tuning files to the Pro 3. Now I am so glad to have the capability back, and I will soon be creating and sending more tuning files to my Pro 3.
Again, my thanks to you for creating this app and making it available online for free. It is much appreciated!

i was wondering if the Filter envs are actually analog or digitally created? Do we have any verified info about it?

I bought this editor last week.  So far, pretty happy with it, but there are a few things that I think would be a huge benefit for users:

1.  Ability to drag/drop programs from the 'Database' section to the 'Export' section (instead of clicking arrow one-by-one), and the same drag/drop functionality within the 'Export' section itself to re-order patches without starting over.

2. Ability to delete unused tags.  I started with one naming convention, but switched all programs to a different tag and can't figure out how to delete the old unused tags.

3.  Ability to save/open different program databases.  I have spent quite a bit of time organizing sounds, but I want to start over completely with a new tagging structure and new programs without losing my previous work or co-mingling two different datasets that use different methodology. I know you can copy the Documents folder contents somewhere else, but it'd nice to be able to select from within the window which one to reference.

A few additional things that would be real improvements:

1a. Deleting Patches:  Any time you delete a patch (mouse click only), the programs list jumps back to the the very beginning.  This is very annoying for people trying to clean up large banks because we have to scroll to find our place every time we delete a patch.
1b. It would be great if users could just press the  'delete' key on their keyboard to delete a patch while still staying where they are in the list (load next patch immediately after the deleted one instead of going back to the beginning of the list).

2. Unable to export more than 128 patches at a time.  I understand the Rev2 only allows 128 patches to be loaded into a bank, but I wish there wasn't a limit on exporting as many as we want into a sysex file.  I'm at a point where I'm just trying to export every patch I have so I can manage them in a different library.  My only options seems to be to export 128 patches times __ number of banks and then combine them into a single sysex file using a different tool (f0f7). More hassle than it should be.

Hope all of this is taken as constructive feedback from a paying customer.

My wife and I were recently back in Berlin and went to Schneidersladen. They've moved and are now split across three locations. We stopped first in the keyboard shop and I finally got to mess with the Trigon. Loved it, as I'd imagined I would, though I didn't spend enough time with it to be able to say more about it here.

The scary and surprising thing, though, happened in the modular shop, which was a block or two away. Not sure how or why, but suddenly, after being resistant all these years, both Julia and I got hit with the "let's get a modular system" bug! We didn't purchase anything, but we did go back a second time to follow up on a few things. I think, for me, anyway, the sudden appeal of modular is that it seems to lean in the opposite direction to where I've been with musical gear for a while. I've been so practical and pragmatic, and everything I buy or record has to have a purpose. With modular, I'm picturing pointless generative meanderings! Basically, I'm dreaming of meditative drones that have no bearing on my pop music mind. Not that all things aren't One, man, but you know what I mean.

I still want a Trigon, but it would probably mean letting go of my Prophet 6. The P6, speaking to my earlier point, is probably the most "practical" synth. It fits well on my desk, serves as a great controller etc. Its sound is familiar  and I know my way around it well, but practicality is starting to wear on me and I need more mystery in my head. We'll see where the modular bug leads, meanwhile...

Thanks, it works! Greetings!