Kronos Editor 2.0 - Feedbacks

[Corgy]

...I can wait another 6 months. I can pay 100 EUR for a real useful editor...

Me too

[ed_f]

ed_f did you try to update the korg usb device drvier ? It seems it is mandatory !

Cheers

Yes - I am one of those people that actually reads all the directions and then follows them. But, thanks for the suggestion!

[ed_f]

If the plug-in is still failing to validate, can you get us a full copy of what is being reported. The information that we are seeing here doesn't actually show anything but "FAIL" which obviously isn't helpful.

I will give it some more work and if I don't get anywhere I will do just that. I understand "FAIL" doesn't help you , but I was posting to a forum my feedback on installing, not contacting customer support. Or should we consider this our customer support solution for this product?

[Shakil]

For me it seems that all the modulation functions are distribution around all the tabs and you have to know where to search if you want quickly to change the one or the other modulation.

That's because, unlike other synths, KRONOS modulation source/destinations are TOO many combinations. There is no single modulation matrix page, like on some synths, like 4 sources into 4 desitnations. On KRONOS almost everything can be modulation by almost anything.

I think the Editor is doing a great job in keeping all these parameters organized. Don't compare it to the single page editors of software VSTis. There are just too many parameters.

I do not agree with "too many". It's just a question of organizing all of them in a better way. There is so much more space on a Mac or PC display for the external editor. The external editor is not required to copy the on-board GUI one by one. There is so much more freedom and less limitation. Just use it.

Well, as I said before, the issue is KRONOS architecture. Remember the VSTi editor is for an external hardware synth, not a software synth. So the editor has to work with hardware. It needs to load the screen on KRONO that will accept those parameters in realtime. This is why the edtior screens have to match with the onboard KRONOS screen.

Almost all VSTi editors are smallish and don't scale. They have to keep it small in order to fit on most screens. If someone using a small resolution (most laptops are not even full HD resolution).

[neomad]

Well, as I said before, the issue is KRONOS architecture. Remember the VSTi editor is for an external hardware synth, not a software synth. So the editor has to work with hardware. It needs to load the screen on KRONO that will accept those parameters in realtime. This is why the edtior screens have to match with the onboard KRONOS screen.

Almost all VSTi editors are smallish and don't scale. They have to keep it small in order to fit on most screens. If someone using a small resolution (most laptops are not even full HD resolution).

Nope. You seems to be a friend or big soundquest/korg fun.

It is evident: that is not correct if you write your software in 64 bits and you do not use a translator from 32 bits. BTW There is no link between 32bits and screen size.

[Shakil]

Well, as I said before, the issue is KRONOS architecture. Remember the VSTi editor is for an external hardware synth, not a software synth. So the editor has to work with hardware. It needs to load the screen on KRONO that will accept those parameters in realtime. This is why the edtior screens have to match with the onboard KRONOS screen.

Almost all VSTi editors are smallish and don't scale. They have to keep it small in order to fit on most screens. If someone using a small resolution (most laptops are not even full HD resolution).

Nope. You seems to be a friend or big soundquest/korg fun.

It is evident: that is not correct if you write your software in 64 bits and you do not use a translator from 32 bits. BTW There is no link between 32bits and screen size.

What is not correct? Can you specify?

If I am a 'friend' of KORG, then I wouldn't be bashing KRONOS architecture for being the cause of Editor's limitations.

[SoundQuest]

If the plug-in is still failing to validate, can you get us a full copy of what is being reported. The information that we are seeing here doesn't actually show anything but "FAIL" which obviously isn't helpful.

I will give it some more work and if I don't get anywhere I will do just that. I understand "FAIL" doesn't help you , but I was posting to a forum my feedback on installing, not contacting customer support. Or should we consider this our customer support solution for this product?

No, its not an official support solution but I was trying to be helpful. i am spending my own time here.

[midiman]

Thanks for actually reading my OS version and your post. I agree it does not seem to be the Apple problem - may not be soundquest problem either. I do know nothing changed on my system since V1 and V2 except this one didn't work.

Interestingly -while I didnt jump into the fray - I am somebody who thinks the editor is useful. Not perfect, a lot I would change. But I can see more information in some of the drop down menus, it it on my monitor (no need to for tilt screen) easier to type - lots of reasons I think it is worth happening. But this was a surprise to me - the first one installed perfectly and worked "fine" until V2 of of the OS.

You're welcome. One of the things I have seen reported on forums is issues with permissions causing validation to fail. Can you provide the full error that the validation tool displays?

[ed_f]

If the plug-in is still failing to validate, can you get us a full copy of what is being reported. The information that we are seeing here doesn't actually show anything but "FAIL" which obviously isn't helpful.

I will give it some more work and if I don't get anywhere I will do just that. I understand "FAIL" doesn't help you , but I was posting to a forum my feedback on installing, not contacting customer support. Or should we consider this our customer support solution for this product?

No, its not an official support solution but I was trying to be helpful. i am spending my own time here.

I appreciate that. I will send you more detailed information if/when I work on this again. Thanks again for the help.

[WVought]

The editor is useless to me until it comes out in a 64 bit version. I was very hopeful when they released 2.0, but my jaw sunk when I saw that it still would not function in a 64 bit environment.

Ridiculous.

Unbelievable.

Useless.

Just telling it like it is.

[Shakil]

WVought...

How would you use the editor if it was 64bit?

Are you going to use the standalone editor or the plugin editor?

What will you do with it? Can you tell us?

[neomad]

WVought...

How would you use the editor if it was 64bit?

Are you going to use the standalone editor or the plugin editor?

What will you do with it? Can you tell us?

Come on... read all the posts and stop defending things you can not !

Example: you work already into Cubase 64 bits, you have many synths (Ultranova, virus TI, Gaia) working with their own editors... what happen then ?? you CAN NOT use Korg Kronos because it's 32 bits !

So stop defending and try to learn a little before posting.

[neomad]

WVought...

How would you use the editor if it was 64bit?

Are you going to use the standalone editor or the plugin editor?

What will you do with it? Can you tell us?

Wait a minute: do you own a Kronos? (not into your signature) what are you doing here exactly ? Allright, just defending Soundquest, for free.

[Shakil]

WVought...

How would you use the editor if it was 64bit?

Are you going to use the standalone editor or the plugin editor?

What will you do with it? Can you tell us?

C'mon... read all the posts and stop defending things you can not !

Example: you work already into Cubase 64 bits, you have many synths (Ultranova, virus TI, Gaia) working with their own editors... what happen then ?? you CAN NOT use Korg Kronos because it's 32 bits !

So stop defending and try to learn a little before posting.

I am not trying to defend..... what you are missing is that the synths you listed work differently from KRONOS. With those synths, you just pick a track and start editing the program in the VSTi editor. No such thing with KRONOS, even if you have 64 bit editor. With KRONOS, you have to go into Program mode, edit the program, save it as a new program, come back to sequencer, select the new program. And worse with drumkits... you have to go to Global mode, edit the drums, save as new kit, go to program mode, select the new drum kit, then return to sequencer, select the new program........

[WVought]

WVought...

How would you use the editor if it was 64bit?

Are you going to use the standalone editor or the plugin editor?

What will you do with it? Can you tell us?

If the editor were 64 bit I would use it as a plugin in Sonar X2. This would allow me to save the state of the Kronos on a per project basis, so if I return to a project at a later date my Kronos settings would always be just as I had them previously. But I can't do this because my computer is 64 bit, and the editor is incompatible with this.

I can use the editor as a stand-alone app, but then I can't use Sonar at the same time. If I use the stand-alone editor, it takes over the Kronos USB port and won't let Sonar use it. I've tried tweaking all the settings to get this to work, to no avail. But even if I got this to work, it still wouldn't save the per project settings, since the stand-alone app is not a plugin.

I repeat:

Ridiculous.

Unbelievable.

Useless.

And I will add:

A huge waste of my time.