I think it would be useful if there was a mode after recalling a patch that you could go into and it would show you the level a parameter has been set to, utilizing the row of 16 LEDs similar to how you view the modulation depth. There would have to be some way you enter this mode, a button combo or some other way that someone smarter than me could figure out. Once you are in that mode, if you move a knob or slider, the 16 LEDs would give you an idea of where that parameter is actually setup in the patch. Since there are only 16 LEDs, this might not be fine enough to show exactly where a parameter is at, but it would help get close. Alternatively, the LEDs could simply point you into the right direction, up or down, until the slider gets to the same position as the recalled patch. This would give you a way to reverse engineer patches and even set the state of every physical parameter to the state of a recalled patch if you go through every single parameter.
A software editor/programmer would be even cooler, with graphic and/or numeric representation of where everything is set.
I posted the same thought some time ago, but it seems to no longer be on the forum. My idea is different, but might be more useful than TheRosskonian’s. Let me explain again: Why not a App that merely can read every setting of a patch file that is loaded into the Super6 over USB. So not on the Super6, but on the computer, displaying settings as a spreadsheet? No elaborate button codes to learn on the Super6. It would allow me to at-a-glance de-construct a patch. What do other Super6 players think of this?
That’s what I said in the post above yours! 
Just claiming I posted the idea before you. Brownie points and all that. Also, editor programmes usually control the synth in real time, (which is what I understand you are suggesting). My suggestion would not. So my App merely let’s you view a patch in the Super6 folder that is on your computer. I’m not a computer coder, though as I understand it, an actual editor would need to be revised for every computer OS version, whereas mine would run in html or a spreadsheet. As I say, that is just my limited knowledge, so please do not turn this into a big angry storm.
I think we are agreeing to agree, haha. But if you go to all the effort of making a cross platform “read out” program, by using USB MIDI, you might as well make it a full visual editor/librarian, IMO.
I am not a programmer. I could not write a line of code to save my life. Many IT products, including synths, became “abandon ware”, due to relying new Drivers. It happens when Drivers are no longer made available from a manufacturer. To remain current, new drivers are needed for each upgrade of each operating system. UDO and Roland appear to have side-stepped this, making their products longer-lasting, (in the sense of still able to link to a computer). Editor software would need regular updating, which is an ongoing cost to UDO. I may have mis-understood this, as I am computer illiterate. This is my final comment. THE END.
I am also not as programmer, but am still failing to see what the difference would be between a patch readout program and a full editor librarian, WRT to drivers being needed etc. They are usually needed for audio, I am just talking about a two way USB MIDI link between the S6 and a computer. Full graphical and numerical readout of all S6 parameters, and if you change a slider, the editor/librarian updates in real time, and if you change an editor parameter onscreen, the S6 sound engine updates in real time etc.
Anyway, I think we are in agreement, as I stated before. No big angry storm here, smiles all round, just enjoying the weekend and hope you are too! 
While a software editor/programmer would be useful, that would not solve the issue where you are trying to find where a parameter is at in the middle of using it. The way I worded my post, especially the last part, didn’t paint my perspective very well:
“This would give you a way to reverse engineer patches and even set the state of every physical parameter to the state of a recalled patch if you go through every single parameter.”
Although having the ability to see the state of a parameter means you could get the entire state of a patch, I rarely do this with synths that do allow you to see the state of a parameter from a recalled patch. But, it is much more handy to quickly view the state of a couple of parameters and tweak it to taste in the heat of the moment.
Having a way to view the state of a parameter directly on the synth is way more immediate for me than a software solution would be as I tend use my favorite synths away from the computer most of the time. Not to discredit the merit of wanting a software editor, but it’s a different use case for each in my case.
At the end of the day, I bought the Super 6 not expecting either of these features, so it would not be a dealbreaker if it never happened.
I’ve had some ideas for a web-based utility for the Super 6. Spent my sunday sketching a gui and trying to get midi to work. W3C is working on a Web MIDI API and it is already partly supported in Chrome and Edge. A bit unsure about sysex yet so I’ll have to investigate more.
update: tool can be discussed at Working on a web-based companion tool for Super 6
This is awesome! Can’t wait until it’s finalized and would love to try it out.
I sent this suggestion to UDO in October and they thought it sounded like a good idea and made a note of it, who knows if it will be implemented though…
On the DSI/Sequential OB-6 and P6, when you are on a saved patch, and you change a knob, if you rotate it back to the actual parameter setting of that patch, a little red dot shows up on the patch number display to signify you have matched that setting amount of that saved patch.
Obviously, the Super 6 has no display, but! Since the “Manual” LED is only ever fully lit when you are not tweaking a saved patch (hence Manual), it is essentially free for a similar task. For example, if I had been messing with the filter cutoff, but want to go back to the actual setting of the patch, as I move the cutoff slider, when I arrive at the setting of the saved patch, the Manual LED would flash for a second, or flash twice quickly, or something else of that nature.
@trond.olsen: if I load a patch to the editor, how would you visualize the hidden modulations? Or just list them in a text field?
Currently it wonˋt do anything I first have to get it working with midi messages. If the S6 will support controlling all parameters with midi messages then the modulation could be set in a separate table with modulation parameters.
As there is no specification for how to parse patch files I won´t be able to include that now. Also, there was mention of an official patch librarian so maybe that will cover that functionality.
Actually I think I like your idea better than mine, would not require to get into a specific mode to display the parameters, would always be available.
Glad this is sparking two different discussions though, that web interface also looks cool.
Got MIDI working now Translated all the midi specification from the manual but currently only keys and bender can be received/transmitted. A bit unclear if I can support the modulation matrix as the specification is currently. As everyone else I really look forward when the firmware fully enables MIDI.
update: tool can be discussed at Working on a web-based companion tool for Super 6
This is looking fantastic, Trond
I would love to see this implemented the way the Prophet 6/OB-6 do it, where a little dot shows in the corner of the LED screen when whatever knob/slider you’re moving lands on the value that’s saved to the preset. Being that the Super 6 doesn’t have an LED screen, I’d vote for the MANUAL button’s LED to light when you hit that value. It’s a simple, easy way to do it, imo.
edit: so much for my reading comprehension, @four_corners posted the same idea above 
Second that. I think implementing this kind of “Sequential/DSI” parameter marker would benefit both Super 6 and Gemini. Super 6 can be extremely simple if you want it to be, but then, almost modular structure (I quite often use this synth as I would my modular system) that allows for the complex modulation, recursive modulation, many different sources and destinations makes it really hard to remember what I actually did in some patches, that went into evolving and experimental grounds. Granted, maybe this wouldn’t solve all the patch recall issues but it would greatly help - there is a simple way of doing this - each time slider/pot is being moved, once the saved value is reached, any specified button would blink.
Just a thought. What if you supplied a .jpeg of the Super6 with each patch? It’s virtually impossible to “see” how a patch is made, once controls were changed to tweek another patch. It’s not going to cover everything e.g. not Mod Matrix. They used to take Polaroids of mixer desk states, didn’t they?