JUNO-G

Patch Management

Patch Management

9 Aug 2011, 08:16
I have returned to the "world" of synths and production after a long hiatus. My original foray into workstation projects was with an Ensoniq SQ-80 purchased when they were among the first available workstations.

My struggles are numerous as I have volumes of sequenced original compositions on a device that uses a currently irrelevant MIDI interface. Any direction or guidance on mitigating that obstacle would be helpful.

While I recognize the Juno-G to be a pretty comprehensive workstation, the manuals leave a lot to be desired.

As an example, and to the point of this post, I recently purchased an SRX-03 Expansion Board. Now as I understand the language the word expansion means to "build on that which currently exists." You can't imagine my surprise when I opened the back of the unit and discovered that it is in fact a "swap" board, not an expansion at all, as I had to REMOVE the SRX-98 that was already installed . So I have to eliminate sounds I currently have in order to "expand" the unit? This doesn't qualify as an "expansion!"

The heart of the matter...

What is the most efficient way to move patches from the SRX-03 into the Juno-G memory for future use? I want to then remove the SRX-03 and return the SRX-98 to it's home :-).

~musiqman7

Re: Patch Management

10 Aug 2011, 04:41
Hi. Only a few Junos came with pre-installed SRX-98s. Most of them had empty SRX slots and so the "expansion" word is correct. The problem is that it only has 1 slot.

You can't move the patches from the SRX to the Juno. The Juno has its own set of multisamples and the factory patches are built on that base. The SRX card has an additional set of multisamples and the SRX patches are built of those. You can copy-paste the patches but as soon as you remove the SRX the machine won't find the relevant samples and the patches won't sound.

← Back to JUNO-G