Uno Synth Pro Editor?

[SacralReason1]

Hello everyone, when can I expect an editor for Uno Pro?

[Peter_IK]

I don't have a specific date but it is being worked on.

[ibisum]

Great to hear its in the works .. I'm wondering though, if anyone else out there has the inspiration to make an open-source editor, based on the MIDI chart .. wouldn't it be nice if we could extend it?

[IkUser09]

In case you're referring to ctrlr.org, an editor could be written based on the controller data. However, since such editors exist for other synths, they all suffer the ussue that they cannot visualize how the currently loaded preset was programmed. To achieve that, the Pro must be able to dump pathes as SysEx data. Unfortunately this feature was not implemented. So neither Ctrlr nor KnobKraft Orm (or any other tool) will ever be able to work as expected.

A decision was made by the product designers, and we should respect that. Which does not mean we are not allowed to mention we miss this feature .

ce

[mungewell]

To achieve that, the Pro must be able to dump pathes as SysEx data.

The original UNO Synth DID have the ability to read/write patches over SysEx, though this was somewhat custom/convoluted. Without having any evidence, it would suspect that the UNO Synth Pro might have the same ability.

If someone want's to investigate I would suggest that you try 2 tests.

1. Check SysEx enquiry message ('F0 7e 00 06 01 F7')... You can send this message through Midi-OX, or the like

Code: Select all

$ amidi -p hw:2,0,0 -S 'F0 7e 00 06 01 F7' -r temp.bin -t 1 ; hexdump -C temp.bin | head

2. Check IK's 'version inquiry' message. Original UNO Synth replied to/on ID '2 1' (UNO Drum's ID is '2 2'), the Pro might use ID '2 3' and the above enquiry should show you want to change it to.

Code: Select all

$ amidi -p hw:1,0,0 -S 'f0 0 21 1a 2 1 12 f7' -r temp.bin -t 1 ; hexdump -C temp.bin

28 bytes read
00000000  f0 00 21 1a 02 01 00 12  01 30 31 2e 31 34 20 23  |..!......01.14 #|
00000010  23 2e 23 23 20 23 23 2e  23 23 00 f7              |#.## ##.##..|
0000001c

[IkUser09]

Thanks a bunch. The Pro does not respond to the enquiry message:
F0 7e 00 06 01 F7
Response:
None

It does respond to the version inquiry:
f0 00 21 1a 02 03 12 f7
Response:
F0 00 21 1A 02 03 00 12 01 31 2E 30 2E 31 20 23 23 2E 23 23 20 23 23 2E 23 23 00 F7

Interestingly, the Pro emits SysEx when scrolling through presets, like this:
F0 00 21 1A 02 03 32 00 01 00 01 F7
F0 00 21 1A 02 03 32 00 02 00 02 F7
F0 00 21 1A 02 03 32 00 03 00 03 F7

Feeding those back results in the below response, though the device does not do any program change:

F0 00 21 1A 02 03 01 32 00 F7

Unfortunately, I'm not savvy enough about SysEx, so I have no clue what those messages are all about

ce

[IkUser09]

When sending something like
f0 00 21 1a 02 03 31 f7
which appearently caused the predecessor to dump the current patch, the response of the Pro looks like
F0 00 21 1A 02 03 01 31 00 F7

Feeding this one back results in
F0 00 21 1A 02 03 01 01 00 F7
Feeding this back results in the same response.

ce

[mungewell]

So that's really good news, but IK probably doesn't want us filling their forum up with a lot of speculation. I started a bug over on GitHub for anyone who wants to get technical.
https://github.com/mungewell/uno-synth-utils/issues/6

In the response 'F0 00 21 1A 02 03 01 31 00 F7' I believe the '01' after the ID is the synth saying 'error'. It does not understand the request...
Simon

[IkUser09]

Github is just fine. You'll find me as https://github.com/Christedge

ce

[SLiC]

I am amazed this wasn't available at launch, its such an important part of the original UNO and without an editor (and VST editor) the UNO Pro is less useful to me than the original UNO....hope it drop soon, very soon!

[Peter_IK]

I am amazed this wasn't available at launch, its such an important part of the original UNO and without an editor (and VST editor) the UNO Pro is less useful to me than the original UNO....hope it drop soon, very soon!

Everything is available directly on UNO Synth Pro, there are no hidden options that can't be accessed on the analog hardware itself (like with a classic analog synth, computers aren't considered part of the process except for recording the output for many/most hardware synth users).

Edit - That's in response to why it wasn't there on launch, I was typing/moving fast Of course people expressed interest in an editor so we're working on it!

[SLiC]

I’m happy enough now I have seen it in action

https://www.instagram.com/p/CPV_2JOHOlX/

Word on the street is that it is out next month….