Preset Doesn't Send to Alpha Juno 2

Question

Was "I am having the same problem with 1.4.5 Build 1450 - doesn't save though it seems to."

Comments

Hi and thanks for your question. Can you make this a comment on the question, please?

Also: please try force-quitting MIDI Designer and restarting. I'm looking forward to squashing this bug ASAP.

Thanks for your patience as we work this out.

---

Dan,  thanks for replying so soon. I did try force quitting and restarting the app, no difference. I am using Rainer's Alpha Juno 2 layout. It doesn't seem to be sending all the sysex parameters in the layout when I select the preset, but I can't figure out whether it's just sending the parameters I changed recently, or what. Any help would be appreciiated. Thanks, Andy

---

So first off, just to clarify, it's not that the preset is not saving to the slot. It's that the sysex parameters seem not to be sending. Is that correct? Thx!

---

Yes, this is what I mean when I say it seems to save a preset. Preset 1 is lit up and some parameters are sent, but apparently not all.

---

The reason this is so important is that we're trying to figure out where the problem is. The preset is probably saving and might even be sending. We're probably overwhelming the synth. Are the output lights lighting up on your interface when you send a preset?

Thanks for working through this.

---

Also check the log (More -> Log) and see if the sysex's are sending, or at least seem to be.

---

I checked the log and it seems to have no activity. This is all it says:

Welcome to MIDI Designer
Pro Version 1.4.5 Build 1450
No NSZombies

---

Log only shows activity once it's showing, meaning that you'd have to hit the preset while you're showing the log.

In the meantime, I spoke with Rainer, the creator of the layout. It's VERY likely that no-throttling is the issue.

Note: presets don't send if the value is already where it's supposed to be, so if you don't see any knobs move, you've got no data sending out.

---

As for parameters, the behavior is puzzling. I am not in my studio now, but was able to repeat what happened earlier without the Juno 2 present. I called up Preset 1, then altered 2 parameters, T4 (release time) and the Chorus rate.  I then saved the changes into Preset 1. I  altered T4 again, then called up Preset 1 again. T4 moved back to the position where I had saved it, but the Chorus rate reverted to where it had been before the save. So the problem is in how it saves data, possibly in addition to how it sends. When I was at my studio earlier this evening, I tried loading a patch manually on the synth, then calling up Preset 1 on the layout. Only certain parameters changed - it wasn't a complete set by any means.

Make of all this, what you will. Thanks!

Andy

---

Oh, I see - so I would have to tweak every knob in order to get a complete patch saved in a Preset that could take the synth back to my sound from anywhere, yes? That would make sense. What doesn't is the mysterious parameter that doesn't save...

---

Hi Andy,

There's always config -> send all to send all parameters. From what I can see, the problem is on the synth's side, but the solution will be on our side ;)

In any case, in the future I'll do throttled connections and probably an option to have presets send all values.

Thanks for your patience as the App advances and we solve a lot of these problems.

Best!
Dan

---

I just opened the log and looked at what was being sent.  The Chorus Rate parameter changes get sent as I move the knob. However, after I save the change and call up the Preset, it just sends one system message - resetting the Chorus rate to the same spurious value it had before the save, as though I hadn't made any changes.

FWIW -
Andy

---

Appreciate your attentiveness. Looking forward to a solution. Really glad to have purchased such a well-supported product!

---

So we're not overwhelming the synth with these presets. So are you able to send a sysex in a preset--assuming the knob is set to the wrong value--to the Roland midi target?

---

If you mean does the synth get all the sysex messages that appear in the Log, the answer is apparently yes. The T4 value that I altered and saved in the Preset, was sent back to the synth as it should have. So was the spurious Chorus rate, which kept coming back at a value of 65 no matter how many times I tried to change it and save it.

Hope this answers you succinctly -

Andy

---

"However, after I save the change and call up the Preset, it just sends one system message - resetting the Chorus rate to the same spurious value it had before the save, as though I hadn't made any changes."  If I'm reading this correctly, I'll have to check out how presets work with sysex, I think.