Page 1 of 1

Kronos editor plug-in is blacklisted by Cubase 9

Posted: Wed Dec 14, 2016 8:18 pm
by Purusha
Anyone else hit this? I guess it's because it's 32 bit.

Soooo Korg, I wonder what the chances are of moving on this one now?

Posted: Thu Dec 15, 2016 8:16 am
by Derek Cook
Yes, Cubase 9 is 64 bit only, but you can still use JBridge or similar to get your 32 bit plugins loaded.

Haven't tried this myself yet, as Santa has not delivered Cubase 9 yet ;) but on a quick check of my plug-in folder, I have half a dozen 32 bit only plugins that I still want to use, including some Steinberg ones, so looks like JBridge is on the shopping menu as well! :shock:

It does raise a question of ongoing maintenance of projects that I may wish to open 10, 20, 30 years from now. If I keep Cubase 8.5 as the transition point, how long will I be able to run that for?

Looks like it might be time to buy a large hard disk devoted to hold all projects have ever done as WAV exported tracks, so you will at least always have a rendered copy of the tracks to get back to.

Posted: Thu Dec 15, 2016 11:25 am
by jimknopf
I understand the old project issue. Rendering to wav is probably a good idea.

The time for 32-bit is definitely over, since some years already. The anyways not too smart Korg editor, which should NEVER have been written as 32-bit plugin, and even less as 32-bit plugin only, has remained one of the weakest spots of the Kronos.

Until today the Kronos is not remotely as well integrated into nowadays DAWs, as Yamaha's Motif and Montage are. It would be MUCH more important to update this, even at a price, than offer second rated new functionality like fast splits in OS 3.1 for the Kronos.

For me Cubase 9 has been a welcome occasion to put any remaining 32-bit plugins on my system in the trash can, forever. I don't even want to use JBridge. I want stable 64 bit performance, and am glad the Cubase sentinel (even if not working perfect yet) keeps unstable code (including half-baked 64bit stuff) out of my way. So far Cubase 9 has been running really stable here on two PC/Win7Pro systems.

Posted: Thu Dec 15, 2016 3:33 pm
by AdDeRoo
[quote="jimknopf" It would be MUCH more important to update this, even at a price, than offer second rated new functionality like fast splits in OS 3.1 for the Kronos.[/quote]

+1
64 bit, extend the 3-4 Gb RAM to 8 or 16Gb, extend to ~60 program banks, and include a 256Gb SSD..

Posted: Fri Dec 16, 2016 11:20 am
by Derek Cook
jimknopf wrote:I understand the old project issue. Rendering to wav is probably a good idea.

The time for 32-bit is definitely over, since some years already. The anyways not too smart Korg editor, which should NEVER have been written as 32-bit plugin, and even less as 32-bit plugin only, has remained one of the weakest spots of the Kronos.

Until today the Kronos is not remotely as well integrated into nowadays DAWs, as Yamaha's Motif and Montage are. It would be MUCH more important to update this, even at a price, than offer second rated new functionality like fast splits in OS 3.1 for the Kronos.

For me Cubase 9 has been a welcome occasion to put any remaining 32-bit plugins on my system in the trash can, forever. I don't even want to use JBridge. I want stable 64 bit performance, and am glad the Cubase sentinel (even if not working perfect yet) keeps unstable code (including half-baked 64bit stuff) out of my way. So far Cubase 9 has been running really stable here on two PC/Win7Pro systems.

Hi, Jim. On the 32 bit era point, I could agree with you if I had 64 bit equivalents for some of the plugins in my projects, which will no no longer load properly unless
1) I render the tracks in question as WAV and accept that the plugin is dead, so no more plugin edits on that track is possible
2) Keep Cubase 8.5 to load those projects, but to date my preference has been to get projects loaded into the latest version (and have always been able to do so up to now).

Steinberg do need to keep moving on, and I can see the logic for making their decisions. I accept that, and I am quite happy to use a 3rd party bridging plugin for what I need to keep alive for a little longer. :)

Posted: Wed Dec 21, 2016 12:14 am
by RlaRed
I have emailed Korg twice about a 64 bit editor plugin and both times they said they are aware of the request for one but don't have a status on it. I would suggest that we all email Korg support periodically asking this. It's really unacceptable that therr isn't a 64-bit version... It would make the Kronos SO much more useful with a DAW.

Posted: Wed Dec 21, 2016 6:20 pm
by Synthee
RlaRed wrote:I have emailed Korg twice about a 64 bit editor plugin and both times they said they are aware of the request for one but don't have a status on it. I would suggest that we all email Korg support periodically asking this. It's really unacceptable that therr isn't a 64-bit version... It would make the Kronos SO much more useful with a DAW.
I agree, and now when Cubase skip 32 bit, its even more good reason to put the pressure on Korg.
I will mail them.

Posted: Wed Dec 21, 2016 7:36 pm
by Derek Cook
I agree as well. If the DAW vendors are retiring 32 bit, it is time for Korg to get that 64 bit editor working.

Posted: Wed Dec 21, 2016 7:42 pm
by ando727
Synthee wrote:
RlaRed wrote:I have emailed Korg twice about a 64 bit editor plugin and both times they said they are aware of the request for one but don't have a status on it. I would suggest that we all email Korg support periodically asking this. It's really unacceptable that therr isn't a 64-bit version... It would make the Kronos SO much more useful with a DAW.
I agree, and now when Cubase skip 32 bit, its even more good reason to put the pressure on Korg.
I will mail them.
How do we mail them? I haven't found any way to contact Korg from my country.

Posted: Thu Dec 22, 2016 4:01 am
by RlaRed
There's a link to contact support on Korgs website. Not sure if it's available outside the USA though

Posted: Thu Dec 22, 2016 7:39 am
by kronoSphere
Hope that Soundforge recently bought by Magix will turn also to 64