Teach me about Galaxy

[Syntho]

As a convert to Studio Vision, I'd like to start using Galaxy instead of my old copy of Sounddiver. The SVP manual took a while to digest and it's looking like I'll have to do the same with Galaxy. Especially since I plan to integrate Galaxy with SVP.

To get me started, can someone explain the difference between bundles, banks and libraries? I understand that Banks are like Program bank A, Program bank B on a synth, and that a bundle can hold any/every type of data bank that that synth has (patch bank, combi or multi bank, FX bank etc). But where do Libraries come in?

Any tips or tricks I should know of generally? I can't wait to see how it integrates with SVP.

[IIO]

if it is the same as in sounddiver the library is simply "all you ever saved" in the form of single patches.

[GaryN]

It's simple.

BANKS are exactly what you imagine they are. Exactly like a bank of patches in a synth. You upload and download them as such.

BUNDLES are well, bundles of BANKS you gather together for organizing. They may be all from one synth and maybe organized into types like Piano, Horns, Strings etc. BUT they can also be multiple BANKS for different / multiple synths too. Galaxy can load/reload ALL of your synths simultaneously from a BUNDLE of patches of their corresponding BANKS. You can imagine say, a "smooth jazz" BUNDLE where all your synths get loaded with soft keys, Rhodes-type stuff etc; maybe an EDM BUNDLE with lots of perc and bass stuff.  Got a couple of devices you gig with? You can make a "Gig" BUNDLE to easily load those and then go back to whatever you were working with afterwards.
You can make song BUNDLES where all of the patches used on a recording can be recalled for a remix or such. Lots and lots of possibilities.

LIBRARIES are the final way to sort out and file patches. They hold unlimited numbers of patches and are intended for sorting types: A library of Pianos of all types, of orchestral sounds of whatever. Say, you're looking for just the right patch for something; you step through ALL of the patches of a type one-at-a-time till you find it. Every time you select one, Galaxy will load it into the synth in a blink.

Once you get stuff organized into BANKS, SVP will "subscribe" to whichever one you use on a project. The patch names will be stored with and appear in the song file. SVP will prompt you to load the necessary banks when you load the songfile.

Yes, it's like Logic and Soundiver, but Opcode was first.

The main "tip & trick" you need is patience. The initial sorting and organizing is critical. If you have lots of patches and/or lots of devices, it's a BIG task.
Just naming / renaming patches, weeding out duplicates, testing them etc. is a LOT of work. BUT at least you only have to do it once.
If you put in the time and effort to sort it all out though, that time will pay dividends forever as long as you use the software.

[Syntho]

I read the entire Galaxy manual (much shorter than expected) and now I'm getting the hang of it. The manual wasn't as clear about sending/receiving patches as I'd like. The example it gave said that with an editor window open, the Send/Receive menu performs slightly different actions than if a library or bank is open.

On page 143 it says, "if you choose store patch or send bank, the current edit will be saved first. Then the patch will be stored or the Bank sent.". "Store Patch"? Do they mean Send Patch? Because the closest thing to Store Patch is in the Program Menu where it says "Store Current Edit", and that saves it, but doesn't send it, and Send Patch doesn't save it, but it does send it. That line in the manual is confusing.

I think in general to store a single patch on my synth, I have to send it to the buffer first (if it's not already there from the Editor window), then manually save on the synth itself. And to get everything reflecting what I see in Galaxy, I've got to send the whole bank, or save one patch at a time manually which is time-consuming.

PS: The manual is slightly different than the actual program. For example, there is no 'keyboard echo' (I'm taking it they mean Keyboard Thru?) and the midi keys window is in the Windows section and not the Play menu.

The other thing I'm gonna have to reread is about how Galaxy and SVP integrate - inserting sysex data for patches and all of that into SVP.

[GaryN]

On page 143 it says, "if you choose store patch or send bank, the current edit will be saved first. Then the patch will be stored or the Bank sent.". "Store Patch"? Do they mean Send Patch?

I think so. You're right - "Send Patch" makes sense. It's a typo.

PS: The manual is slightly different than the actual program. For example, there is no 'keyboard echo' (I'm taking it they mean Keyboard Thru?) and the midi keys window is in the Windows section and not the Play menu.

Correct again. "Keyboard thru" is the intended term. (In fairness, when this stuff was written, waaay back when, much of the terminology was not yet settled)
Also, I think you're referring now to "MouseKeys" not "MIDIKeys" and that is in the Windows Menu section.

The other thing I'm gonna have to reread is about how Galaxy and SVP integrate - inserting sysex data for patches and all of that into SVP.

Now we're heading into the weeds for sure. I think you'll find that the general expectation back then was that SVP handled the sequence and Galaxy handled the synth data - you would just send patch changes and controllers etc from SVP during sequence playback as needed.

SVP can capture and store sysex as a sequence that you can later trigger if needed. You can see it, edit it if you're familiar with the format, but there's no special "sysex editor" function in either app.

[Syntho]

"if you choose store patch or send bank, the current edit will be saved first" - using Send Patch doesn't save it though, it just sends it over to your synth. That's why I thought there might be some other command called Store Patch somewhere.

[Syntho]

I'm thinking that the final revisions of Galaxy didn't ever come with updated manuals. The manual I have (hard copy and pdf) is for version 1 it seems, and the software version that I have is 2.5. I'm guessing the Store Patch or Send Patch thing functions slightly differently because of that. And that would also explain the Menu options not matching up.

[Syntho]

For some reason I can't get Galaxy to launch in System 7. It gives me an error type 1 no matter what I do. It works in OS8 though.

EDIT: Turns out, it was some files in the Librarians folder that was making it crash. It doesn't do that in OS8 with the exact same set. I only added what I needed and it works fine now.

PS: After years of fooling with these machines, I STILL find these weird idiosyncrasies that I have to maneuver around and tweak to get it solid and stable. It never ends... but I'm almost there too.

[GaryN]

I'm thinking that the final revisions of Galaxy didn't ever come with updated manuals. The manual I have (hard copy and pdf) is for version 1 it seems, and the software version that I have is 2.5. I'm guessing the Store Patch or Send Patch thing functions slightly differently because of that. And that would also explain the Menu options not matching up.

You know, I don't think there ever were updated manuals. There weren't any major revisions to the app other than the integration of Editors and System / PPC stuff.
Oddly though, you have a menu options issue that I don't. Is your "Opcode part #" on page one  110-0206-02 ?

For some reason I can't get Galaxy to launch in System 7. It gives me an error type 1 no matter what I do. It works in OS8 though.
EDIT: Turns out, it was some files in the Librarians folder that was making it crash. It doesn't do that in OS8 with the exact same set. I only added what I needed and it works fine now.

Not surprising. One thing I've found is that Opcode apps (being as wide ranging as they are by the time you have MIDI, Digital Audio recording, Synth Libraries and Editors) generate, store and refer to lots of individual files that are kept in specific folders in a specific hierarchy so that they can be found as needed.
When an app goes looking for a file, if it doesn't find it where expected, or if there's an improper version with the same title, or whatever…SPLAT!

The Opcode Motto should have been "Neatness Counts"

[Syntho]

Is your "Opcode part #" on page one  110-0206-02 ?

Yep, that's mine. Under the Windows menu, I see MouseKeys. In the manual it says it's under the Play menu.

[GaryN]

You missed your calling. You should be a proofreader.
You're correct. On page 55 it says Play>MouseKeys. That's an error. BUT…
It also correctly shows MouseKeys under the Windows menu on page 127

Oh well…

[Syntho]

I'm pretty good at studying manuals  The thing that bothers me most is how it said Store (Send) patch saves the patch before sending. Hmm...

[Syntho]

How would one go about hacking a Galaxy editor to display custom names of multisamples? For example, some drum modules have both mono and stereo samples. It would be convenient to edit the list of multisamples and add a (ST) trailer on the name so I know what I'm working with. There's a programming tool for the editors but I haven't looked at it yet.

[GaryN]

How would one go about hacking a Galaxy editor to display custom names of multisamples?

You don't. You store the mono and stereo versions as two different patches in the Librarian and name them there.

[Syntho]

I'm having trouble with the Cross Reference Bank command. It freezes when I try it on some synths, and with others it jumbles the names of the patches. It won't work on either System 7 or OS8.

There are also some weird idiosyncrasies with certain editors, like how when you click to edit a multi/combi (parent patch), it mutes the timbres that are supposed to sound. You have to unmute them hear anything. Hmm...

I wish this were the 90s again. I could actually get answers to this software that no one is using 

[GaryN]

Hmmm… honestly, you're now further into the weeds here that I ever go, but I can make an educated guess.
I think you're probably trying to use the app on synths that are newer revisions than Galaxy and it doesn't understand something in the data formats - hence the freeze. Remember: there were no updates after a certain point. And: this is just a guess; don't hold me to it.

As for the timbre muting, I can't begin to theorize without a lot more info. If you like, you can .sit a couple of problem patches and send them to me. I'll open them here and see what happens.

[Syntho]

Open the bundle. Double click the Combi bank. Sending the patches to my synth works fine. When I double click them or click the Edit button though, when the editor comes up the programs are muted. I have to unmute them to hear anything. It does this for every single combi.


I don't believe you need the synth to see what I'm saying here.

[GaryN]

Wow golly gee whiz!

You're absolutely right, they come up muted.
I played around and theorized, even twisted one up for inspiration and I came up with…

Squat, nada, zip, zero.

I think if this was intentional for some reason, they would have pointed it out and explained why in the manual.  So…
I guess it's a bug…probably unique to the Korg Editor, or maybe not, but most likely.
I personally don't have any other synths that create similar "combi" patches to compare, so I guess you gotta live with it.
I mean, it could be a LOT worse. At least everything works and it's just a minor inconvenience.

Sorry I couldn't be more helpful.

[Syntho]

Well at least it's not me. The version of the editor I'm using is 1.0.9 I believe. I don't know if there's a newer one or not.

[GaryN]

Well at least it's not me. The version of the editor I'm using is 1.0.9 I believe. I don't know if there's a newer one or not.

Are you sure about the version? I've have "Korg X/N Series Editor" ver 1.0.3 "Shipped with Galaxy 2.5" Created 4/6/95