Channel aftertouch and poly aftertouch are two separate sources in the opsix mod matrix, and all the default patches are configured to use only channel aftertouch. If you set your Hydrasynth to transmit channel aftertouch then it will work with the default patches on opsix, but then you are losing the benefits of poly aftertouch. If your Hydrasynth is set to transmit poly aftertouch, you would need to edit every opsix patch changing any mod matrix settings from channel aftertouch to poly aftertouch, or the opsix will completely ignore the poly aftertouch messages you are sending. There are some mod settings outside the mod matrix (in other opsix screens) where channel aftertouch is an option but poly aftertouch is not, so that might be a problem when an existing patch used channel aftertouch and you can't fully convert it to poly aftertouch.
Korg ought to have either had only one multipurpose aftertouch source capable of receiving both types, or at least make it an option that when receiving poly aftertouch it can use the highest current poly aftertouch value as the input to any opsix modulations that were configured for channel aftertouch, but Korg have not done so, and it is very annoying.

UPDATE: firmware v3 has added a solution, see posts below...

Have you updated your opsix to 3.0.2 or later? (Current version is 3.1.0.)

As many here will know, my group at Korg works on the wavestate and modwave. The opsix is from a separate group, but shares much of the underlying structure as the other two instruments. Over the last year, all three instruments have added an "Aftertouch Source" parameter. The modwave release notes describe the new parameter this way:

Added Aftertouch Source parameter on Utility/Controllers page. This allows you to use Poly Aftertouch to control existing Aftertouch modulation routings, without needing to create new, dedicated Poly AT routings.
Off: All aftertouch will be ignored.
Channel: The mod source "Aftertouch" receives Channel Aftertouch. Poly Aftertouch can still be used via the dedicated Poly AT mod source.
Poly: The mod source "Aftertouch" receives Poly Aftertouch. Channel Aftertouch is ignored.
Channel+Poly: The mod source "Aftertouch" receives both Channel and Poly Aftertouch. If both are sent simultaneously, the most recent value is used.

The opsix version 3.0.2 release notes are less descriptive, but note:

The following parameters have been added: SEQ > SEQUENCER > ACTIVE, SEQ > MOTION > SYNC, GLOBAL > MIDI > Aftertouch Src, GLOBAL > CTRL > Aftertouch Curve, and GLOBAL > SEQ > Key Trig Velocity.

I'm going to suggest to the opsix team that they add a little detail here. That said, the GLOBAL > MIDI > Aftertouch Src parameter is what you're looking for.

Hmmm... that may also be part of the problem, I`m only on V2.01

So far I have managed to get the Chan AT working on some patches by altering my Hydrasynth though, I guess I need to update my Opsix now.

Oh great! the updater is windows 10 and above

anyone know of a win7 version or am I stuck with 2.01 forever now?

Can't you borrow a laptop to update?

I hope so!

Thanks Dan, I hadn’t seen the new version and was still on 2.0.1
Google took me to the product page for my mk1 opsix at https://www.korg.com/uk/products/synthesizers/opsix/ which rather makes it look as though version 2.0 is still the new thing.
Tonight I went to the Support screen from the left, Downloads > Synthesizers/Keyboards > Discontinued products > opsix, and downloaded the System Updater 1.0.3 which appeared from that screen to be the latest.
Bizarrely despite having just been obtained from the current support downloads page, 1.0.3 does not seem to actually be the latest version of System Updater, and when I installed it, opened it and connected usb to opsix, it immediately told me to download System Updater 1.0.5. So I let it download that, installed it and reopened it, then let it download and run the opsix 3.1.0 firmware update over usb and it worked.

Katherine_Alicia, if you manage to use someone else’s Mac or Windows 10/11 to update to firmware 3.1.0, these are the settings I would recommend, and will work with the unedited default patches:

Opsix:
Global Parameters > MIDI > Aftertouch Src > Both
When creating or editing patches, in the mod matrix (virtual patch) screen, you will probably be better to use “AFTER TOUCH” instead of “POLY AFTER”, so the mod will still also work from channel aftertouch without having to reconfigure anything, in case in future you ever have to use your opsix with a channel aftertouch master keyboard. In other screens like filter you can only choose “AFTER TOUCH” anyway as there is no “POLY AFTER” option there.

Hydrasynth System Setup:
MPE > OFF
At TX > Poly

OMFG!

so I borrowed my daughters laptop, installed the 1.03 was prompted to update to 1.05 and that seemed to work when installed.

put the Opsix intousb boot mode (Seq-Rec-Dup then power up) that works but the update s/ware keeps waiting for a device for me to select, it`s not "seeing" the Opsix at all. the laptop makes no sound when I plug the USB in like it does on win7
Aaaaaand now I can`t even turn the opsix off (unless I pull the power plug).

What am I doing wrong???

Honestly, it sounds to me like you need to read the instructions carefully before proceeding, To start with, why are you using the USB Boot Mode method? Always start with the normal method first. USB Boot Mode should only be used in special circumstances. Use the Korg System Updater, and read its manual carefully (I wrote it!).

I got past that wall anyway, I realised that when I did the driver thing it was on my win7 machine and not this one
so now it`s seeing the Opsix fine, and I ran the installer and that picked it up too (SO FAR SO GOOD!)

but now it`s saying...

Download Failed

Failed to download from:
https://storage.korg.com/korgms/korg...date_3_0_1.zip

so I`m not sure what that means?

It looks like the updater is referencing an out-of-date link as it seems that file doesn't exist in that location.

What version of the System Updater are you running? I'm running 1.0.5 on my Mac, but the Korg downloads only has v1.0.3 so you'd need to do an in-app update.

1.0.5 as well, it auto updated from the 1.0.3 on it`s own.
turns out that with Opsix plugged into the USB it was turning the wi-fi off? and into airplane mode and every time I turn it back on a second later it would turn back off.
I had to do 2 resets for it to work again.
Now I remember why I use Win7 and not 10

But... it`s all working now the update to the opsix was fine and now I have the Poly AT turned on to "Both".
When I catch my breath I`ll install the Librarian on the win10 laptop as well, it`s always good to have a backup since I bought all those new soundbanks for it.

Can`t wait to get it back in the studio and try it out!

What instructions, where? also it was the "System Updater" that I was trying to get working, I can only use that After I`d gotten the driver working (thanks to a reddit post).

Eitherway, it`s all done now, and wasn`t really much harder than some other gear I own, it would just be nice to have all the info up-to-date and in one place, like someone said earlier, I honestly thought that 2.01 WAS the latest update, if you do a search there`s little to no mention of this new version 3, which is a pity really because it`s such a lovely sounding synth.
still.. it`s no worse than trying to find a decent manual/ up-to-date video tutorial on Jupiter XM or trying to update the Kordbot for the first time! LOL

A link to the manual appears during the installation for the Korg System Updater. See the screen-shot below; this is from macOS, but it's similar on Windows.

While you're running the application, the Help menu also includes a link to the online manual.

As long as you follow the instructions - which include troubleshooting steps, for relatively rare situations - the driver should work properly. (It's a Microsoft driver - nothing custom from Korg, just a config file.)

I'm glad that it's working now. It would have been much more straightforward, though, if you'd read the directions and not done extra stuff such as putting the system into USB Boot Mode, which as you discovered doesn't work at all with the normal updater. I say this only because you've posted several messages about how difficult this was for you. It didn't need to be!

I'll let the opsix team know.

Well the "hard part" was actually forgetting that I hadn`t altered the driver on the Win10 machine in Device Manager and then going looking around the internets for advice.

But, since you`re here, also tell the Opsix team to make a Youtube video or two featuring the new 3.1.0 and also the new updater, there`s nothing on there at all (absolutely nothing!), and it`s too good to remain hidden, Especially for those with Poly AT controllers.

That sounds like a screwed-up version of Win10!

and then some!

Yes it's well worth updating, the default patches feel much more expressive with Poly AT working in a useful way. Well done Korg and Dan for resolving it.

Like the idea of the Op Six, but the mod matrix is limited to only 12 slots?

@ Dan Phillips

I`m not sure if you`re able to or not, but if you can get in contact with the devs, could you ask them for me, in the next update to make it possible to move through the patches faster, maybe hit Shift and scroll a page at a time (5 patches) because going from 1 to somewhere in the 400`s will wear out the encoder eventually, so doing page at a time, or even direct entry via the SEQ buttons would be great!

[edit: I responded on my phone, mistakenly thinking that this question was about wavestate or modwave. I’ll pass your comment on to the opsix developers.]

That's cool, why can't the VALUE knob also be used with ENTER to jump 5 too as well or does it?

The opsix was developed by a different group than my own. That shortcut works on wavestate and modwave, but I haven't found a similar one for opsix. It's quite possible that there is one that I don't know about, though.

Thank You!

Sorry. Just wondered here what do the parameters for wave folder do. Osc mix seems to be the gain of the oscillator signal summed to the signal coming from the modulator before they hit the wave folding.

That is correct. It's explained in the manual IIRC.

Well, so and so: "OSC MIX (OSC Mix Level)
Sets the oscillator level inputted into the Wave Folder."

True. I was confused by the fact that the modulator signal level is still set by the modulator level fader. I expected the mix to somehow mix between carrier and modulator signal strengths, while it is just osc volume.

What on the Opsix are missing is an offset and invert Function for the operator Envelopes , the Problem with these ADSR Envelopes are they start ever at 0 , it is not possible to start at 50 or -50, no time and Level Segments So that makes the Sounddesign for many interesting Sounds hard or impossible . The Trend in the last years goes to Multistage Envelopes with Loop. For an FM Synth is ADSR really backwards, i dont really understand they strange desicions they have made at Korg. Also not enough Pitch Envelopes for the Operators. Operator Envelopes cannot use as a Modsource for other Moddestinations. They put 120 Voices into the Opsix SE Version but no Multimode, how is that to understand? The last big Update is over 2 Years back...nothing new comes here.

Just bought one of the last OG Opsixes.
Is there a firmware changelog or list somewhere other than inside the update software? And is the manual up-to-date? There's only one download link on the support page (opsix_OM_E6.pdf).

what is the best modern HW FM synth that does not have this envelope shortcoming?