This is Korg's popular keyboard workstation.
It's a synthesizer, sequencer, and sampler all in one.
Please contact me if you have tips or comments you would like me to post on here.
I purchased the 61 key "Triton Classic" on 2000-05-27 for $2220.
I'm currently using OS version 2.5.3.
In May 2000 I bought a Triton as a "modern" replacement for my Yamaha SY55.
My hope was to use the Triton's built-in sequencer (as I did with the SY55), and not have to be around computers when I was making music.
Unfortunately, after I brought it home, I found out that the Triton's sequencer memory doesn't get saved internally;
it needs to be saved to floppy or external SCSI disk.
This was confusing and aggravating at first, because this meant that, despite being 10 years newer,
the Triton was actually less convenient to use than the SY55.
Long story short...
I ended up abandoning the Triton's sequencer and any hopes of making music without computers.
It took me almost two years and lots of hours of research and testing, but eventually I settled on Cakewalk/Sonar.
I now sequence my songs in Sonar, but use the Triton as my "master keyboard" (MIDI controller, sounds, and effects).
I also plug my mic into it, so it acts as a mic pre-amp and effects processor too.
Here I had problems:
I quickly got frustrated with the default Triton.ins that I got from Korg or TritonHaven.
The Triton's patches are not organized by category within the banks.
It's very difficult to find, say, a bass patch, just by looking at the patch and bank numbers.
I therefore created my own instrument definition file, which sorts the patches by category.
You can download it here: EasyTriton.zip.
Note: I've included 2 versions: one uses category numbers and the other uses abbreviations (e.g., "ke" for keyboards).
I created lots of songs using the Triton's sequencer that I later wanted to finish using Sonar.
Here's the steps I took to finish each Triton-started song on Baby Steps and Baby Talk
(and some tracks on other albums):
Even though Sonar comes with lots of audio effects, I prefer using the Triton's effects, for the following reasons:
The Triton's effects can't be manipulated within Sonar.
This means we need to use the Triton's touchscreen and knobs.
Once we're done tweaking the Triton's effects, we need a way to save them.
Sure, we could save them as a .SNG file to a floppy or SCSI disk, but it's more convenient to store them as Sysx data within a Sonar project.
This way, the project will always "remember" the state of the Triton effects.
To do Sysx dumps, you first need to tell Sonar how to request a Sysx dump from the Triton.
This is a one-time thing, and is pretty easy:
01 Triton Sequencer Dump=F0 42 30 50 18 00 F7
That should be it.
Note that I prefix my dump request's name with "01" to force it to the top of the list.
If you want to add more dump request macros, you can find a bunch at
These give me a "what channel" prompt in Sonar.
To get rid of that prompt, you can replace FC 30 FD 50 with 30 50 in each dump.
I hacked the TritonHaven list to create these simplified macros (which I haven't tested thoroughly):
Triton All Arpeggios=F0 42 30 50 34 00 00 00 F7
Triton All Combi=F0 42 30 50 1D 00 00 00 F7
Triton All Data=F0 42 30 50 0F 00 F7
Triton All Drumkits=F0 42 30 50 0D 00 00 F7
Triton All Programs=F0 42 30 50 1C 00 00 00 F7
Triton Combi Bank A=F0 42 30 50 1D 10 00 00 F7
Triton Combi Bank B=F0 42 30 50 1D 11 00 00 F7
Triton Combi Bank C=F0 42 30 50 1D 12 00 00 F7
Triton Combi Bank D=F0 42 30 50 1D 13 00 00 F7
Triton Global Data=F0 42 30 50 0E 00 F7
Triton Sequence Data=F0 42 30 50 18 00 F7
Triton Program Bank A=F0 42 30 50 1C 10 00 00 F7
Triton Program Bank B=F0 42 30 50 1C 11 00 00 F7
Triton Program Bank C=F0 42 30 50 1C 12 00 00 F7
Triton Program Bank D=F0 42 30 50 1C 13 00 00 F7
Triton Program Bank E=F0 42 30 50 1C 14 00 00 F7
Triton Program Bank F=F0 42 30 50 1C 15 00 00 F7
Before I tell you about how to request and save an actual Sysx dump, I need to tell you about a bug (or "undesirable feature") in the Triton.
This bug requires you to perform a few semi-tedious steps in order to prepare the Triton for the dump.
You need to perform these steps each time you do a Sysx dump.
Since this bug might be fixed in later versions of the Triton OS, and since someone might find workarounds for it, I'll cover it in a separate section: Preparing the Triton for a Sysx dump.
Read that section first, then come back here and I'll tell how to do the Sysx dump.
Okay, here are the steps we need to perform whenever we change effects on the Triton and are ready to save our Sonar project (before turning off the Triton):
The Sysx data should now be saved within your actual Sonar project file.
What I like to do is auto-send the Sysx data to the Triton whenever I open a project.
To do this, you need to:
This should put a checkmark in the Auto column.
Since almost all my projects use Triton effects, I include a Sysx dump in my default Sonar template.
I also set it to auto-send, so that every time I start or load a project, the Triton's effects are automatically setup for me.
Sysx dumps are super-convenient, but there's a slight catch.
For some reason, the Triton has two sets of SEQ data, which I'll call X and Y.
Here's what I've noticed:
As soon as you start changing settings on the Triton, the Y data gets out of date.
This means you won't be dumping the current (X) settings.
To force the Y data to be the same as the current (X) data, you need to save and load the current "song" data.
Just follow these steps:
At this point, the Y data matches the X data, so your Sysx dump will work as expected.
Yes, these steps are annoying, and no, I don't know of any workarounds.
However, you'll get used to it, and soon you will be enjoying the ability to save Triton effects inside Sonar projects.
This page is managed by Travis Emmitt
Last updated: 2008-05-21
Note: This is a fan-based site, and is not meant to be considered an "official" resource.