Korg Forums

in /Applications/KORG/Kronos 2/Readme.rtf towards the bottom: Uninstalling the Kronos Editor 1.0.0 (Macintosh) If you choose to remove the Kronos Editor 1 from your system, you should delete the following files Folder: Applications/KORG/KRONOS Folder: /Library/Application Support/Sound Quest ...

I installed the version 2.xx editor and now both are appearing in Logic. How to I uninstall the old editor? Running Mac OS X v10.7.5.

I've been trying everything and I keep getting some pop up msg saying " a compatible korg kronos with O.S v1.6 was not detected..." my kronos x is 2.0.1 I'll recheck the midi set up... thanks for your help... I had the same problem, but upgrading the MIDI driver for the Kronos to the latest version ...

RonF wrote:Which specific "bugs" are you referring to?

Well, there's this:

http://www.korgforums.com/forum/phpBB2/ ... tor+window

and this:

http://www.korgforums.com/forum/phpBB2/ ... 301#468301

Anyone know if Korg/Sound Quest is at least planning to release an editor update with bug-fixes?

SoundQuest wrote:The program maintains separate Preferences for the stand-alone and plug-in versions so did you turn it off in the same environment that you are testing with?

Yes.

If you go back and look at the setting in Preferences, is it turned off?

Yes.

SoundQuest wrote:You can. In Preferences in the Studio tab uncheck "AutoSense on Program Execution".

Tried this, but the issue still remains. I'm running OS X 10.6.8 BTW.

All, I'm finding that when I open a project in Logic that includes the plugin editor, I get an 'AutoSense Instrument Settings' dialog. It's apparently trying to find the Kronos. It tries for for about 20 seconds, then an error pops up: 'Compatible Kronos with OSv1.6 not found...'. I can click OK in ...

Regarding the editor not opening, we can't replicate this here and I know the amoun of beta testing that Korg did and they would have reported this had it happened on any of their machines. My only practical suggestion at this time would be the following. Before adding/opening the editor switch to ...

This shouldn't happen and Sound Quest will look into it however, because of how MIDI is handled in a MIDI track vs a plug-in track, all MIDI performance data intended for the Kronos should be placed on a separate MIDI track directed to the Kronos' MIDI port. The plug-in track should just be used ...

What you are doing is "Closing" the plug-in? Effectively, yes. Instead of closing the plug, just hit the 'V" key.. all plugs will vanish and reappear when you press the "V" key again Tried this, but I think all this does is to hide the window, not close it (but without closing the actual editor ...

This suggestion may or may not help you. The Kronos editor is a 32 bit program as we know. If you are running Logic in 64 bit mode, after you have installed the Kronos plugin, you have to run Logic in 32 bit mode in order for the program to scan and validate the plugin. This will not happen in 64 ...

All, Not having any issues with Kronos and the editor talking to each other; the issue comes when trying to use the editor as a plugin with Logic. when I first choose the plugin from the I/O option in the channel strip, the editor launches with no problem. But if I close the editor window and double ...

Either Korgzilla or King Korg.

I've got my Kronos talking digitally to Logic via RME Babyface and have no trouble recording audio tracks from the Kronos. The problem starts when I try to add said track to an existing project, the hiccup being that the Kronos sample rate is fixed at 48 khz, and my existing projects are at 44.1 khz ...