I did try dragging the M3 editor app out of the app folder and into the trash. Same for the two component plugins. I can find no uninstall procedure. (If there actually is one, I'd love to hear.) I then installed it again,. and the same thing happened. I wound up with v 1.2.3 instead of 2.2, which is the download from the Korg site.
note: I had also reset p-ram and MV-ram.
Spotlight doesn't see any other install of the M3 editor.
M3 Editor for Mac, having trouble.
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Are you sure you have the right file and have you tried re-downloading it?
By the way, I just downloaded and installed it, the 'About M3 Editor' says:
Host: M3 Editor version 1.2.3
Core: M3 Plug-In FX Version 2.2.0
Don't know what that means. That was from the 220 package on KORG.com
By the way, I just downloaded and installed it, the 'About M3 Editor' says:
Host: M3 Editor version 1.2.3
Core: M3 Plug-In FX Version 2.2.0
Don't know what that means. That was from the 220 package on KORG.com
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Thanks for the response. Yes I downloaded it again yesterday, and have tried three versions. The cd-rom that came with my M3 actually has v 2.2.0 on it,. I tried that. I tried installing it from downloaded software packages (2.2.0) four times. I keep winding up with v 1.2.3. Very perplexing, and frustrating. My only idea at this point is that you have to do a TOTAL uninstall (whatever that means in this case) before the new version will take, but I can't find any mention of uninstalling M3 editor software on the internet, nor on Korg's site, this forum, or the Karma forum.
BTW, I am using a Mac (Intel/dual quad processor) but I've never seen a problem like this before. This should be very straightforward.
BTW, I am using a Mac (Intel/dual quad processor) but I've never seen a problem like this before. This should be very straightforward.
Marc Soucy
AudioMusicVoice.com
AudioMusicVoice.com
I agree this is confusing. But it's mentioned here now.MarcOne wrote:Maybe the update is only on the core version. That's kinda sloppy on Korg's part. It could at least be mentioned somewhere.

I think the explanation is simply:
- If you go to the About in the bottom left corner of the editor (left click on the M3 logo), it will only show the version of the editor itself, i.e. 2.2.0. This applies to both the standalone application and the VST plugin. No confusion here.
- If you go to the About in the menu bar at the top of the screen (only available in the standalone app), as you know it shows the confusing:
Host: M3 Editor version 1.2.3
Core: M3 Plug-In Fx version 2.2.0
- But what this is revealing is that to make the standalone app they are using their own VST host to host the editor VST, so the 1.2.3 is the version of the host (maybe they just forgot to update the version or it really didn't change), and 2.2.0 is the version of the VST plugin (the same one you use in a DAW or other host).
Thanks, yeah, it's at least a bit reassuring that everyone is experiencing this. My connection between the Firewire expansion in my M3 and my Mac Pro was a bit glitchy too. I thought it had to be the software version. It might be caused by something else though. Is anyone experiencing freezing of the Editor software? I've had to force quit it, and when this happens, it still doesn't go away. It sits there, and I have to restart the computer. I did read somewhere that the firewire connectivity was not perfect, but had been improved.
Marc Soucy
AudioMusicVoice.com
AudioMusicVoice.com