Will Kronos Ever Receive A Sequencer Update?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
- kingy10kingy
- Full Member
- Posts: 174
- Joined: Fri Aug 24, 2012 9:30 am
Will Kronos Ever Receive A Sequencer Update?
Any word on a possible sequencer update along the lines of the Krome?
maybe NAMM? lol...
Please subscribe and follow me on Youtube and Facebook for information related audio technology.
YouTube -
https://www.youtube.com/juliusdeberryjr
Facebook -
https://www.facebook.com/majesticstudiosllc
Instagram - https://www.instagram.com/majesticstudios_jld/
YouTube -
https://www.youtube.com/juliusdeberryjr
Facebook -
https://www.facebook.com/majesticstudiosllc
Instagram - https://www.instagram.com/majesticstudios_jld/
- BasariStudios
- Approved Merchant
- Posts: 6510
- Joined: Sun May 29, 2005 4:56 am
- Location: NYC, USA
- Contact:
Yes. Me and Apex are working on it now, in few days.
http://www.basaristudios.com
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
-
- Posts: 34
- Joined: Fri Aug 17, 2012 4:44 pm
-
- Platinum Member
- Posts: 9451
- Joined: Wed May 15, 2002 12:46 am
- Location: Discovery Bay (San Francisco Bay Area)
Re: Will Kronos Ever Receive A Sequencer Update?
this has never been asked before.kingy10kingy wrote:Any word on a possible sequencer update along the lines of the Krome?
The answer is No

There are lots of reasons: the M3 sequencer runs on a completely different hardware / software platform, so it can't simply be moved into the Kronos - it would be a big engineering project to make it run on the new platform (and run without causing problems for anything else in the Kronos)...and even small changes to released, complex software (like the Kronos has) take company resources: time, engineering, testing, technical writing, etc, and the money to pay for everything...there has to be a return on investment: the resources spent have to be paid for by increased sales...Korg's limited resources are probably always tied up in future products...etc., etc...I wish I was wrong about this, I'd love to have the M3 / Krome sequencer in my Kronos...sigh...ashboe wrote:I would like to understand why kong don't just transport the m3 sequencer over to the Kronos?
df
I don´t think the first part of that reasons is valid. The " company resources: time, engineering, testing, technical writing, etc, and the money to pay for everything..." may be true. If you spend your time and capital on miniMS20 and such ... you may have nothing left to make your flagship workstation actually what you tell your customers.dfahrner wrote:There are lots of reasons: the M3 sequencer runs on a completely different hardware / software platform, so it can't simply be moved into the Kronos - it would be a big engineering project to make it run on the new platform (and run without causing problems for anything else in the Kronos)...and even small changes to released, complex software (like the Kronos has) take company resources: time, engineering, testing, technical writing, etc, and the money to pay for everything...there has to be a return on investment: the resources spent have to be paid for by increased sales...Korg's limited resources are probably always tied up in future products...etc., etc...I wish I was wrong about this, I'd love to have the M3 / Krome sequencer in my Kronos...sigh...ashboe wrote:I would like to understand why kong don't just transport the m3 sequencer over to the Kronos?
df
The main point is: It´s not that difficult to merge those features because you have layers of software in an OS that unify the underlying hardware.
So only if you write assembler code (or C code) dedicated to a specific hardware you get into trouble. I think Korg has top level libraries and a HAL that can be compiled on any hardware they choose to support. (Like Microsoft and Apple do. btw. M3 seems to be linux based system too. Look on the files on your flash card.) They just deemed it not necessary for pro keyboarders. But there are still normal guys like me who drive down prices by also buying those stuff. But I will not complain anymore. I just don´t buy that stuff in the future anymore.
- kingy10kingy
- Full Member
- Posts: 174
- Joined: Fri Aug 24, 2012 9:30 am
- kingy10kingy
- Full Member
- Posts: 174
- Joined: Fri Aug 24, 2012 9:30 am
-
- Approved Merchant
- Posts: 1069
- Joined: Mon Mar 19, 2007 4:38 am
While the M3 is different hardware, I feel Saxifraga is right on this one. It's almost certain the code for Oasys/Kronos/M3 was done in a Integrated Development Environment and they all have different sets of hardware they can compile to. Yes I'm sure tweaks and testing would be needed, but for effectively one module of the project being ported it shouldn't be that bad. It really IS a matter of Korg deciding to spend the money to do it or not.dfahrner wrote:There are lots of reasons: the M3 sequencer runs on a completely different hardware / software platform, so it can't simply be moved into the Kronos - it would be a big engineering project to make it run on the new platform (and run without causing problems for anything else in the Kronos)...and even small changes to released, complex software (like the Kronos has) take company resources: time, engineering, testing, technical writing, etc, and the money to pay for everything...there has to be a return on investment: the resources spent have to be paid for by increased sales...Korg's limited resources are probably always tied up in future products...etc., etc...I wish I was wrong about this, I'd love to have the M3 / Krome sequencer in my Kronos...sigh...ashboe wrote:I would like to understand why kong don't just transport the m3 sequencer over to the Kronos?
df
Korg: KRONOS 73, M50-61, 01W/r
Yamaha: Motif XS7, FS1R
Kawai K5000S, Roland JD-990 w/Vintage Synth
Yamaha: Motif XS7, FS1R
Kawai K5000S, Roland JD-990 w/Vintage Synth
Whilst in no position to contribute on technical matters, it strikes me that this is the point - and Korg have already decided not to.NuSkoolTone wrote:It really IS a matter of Korg deciding to spend the money to do it or not.
Plugged in: Fantom 8, Jupiter-X, Jupiter 80, System-8, JD-XA, V-Synth GTv2, FA-06, SE-02, JU-06A, TR-09, VT-4, Go:Livecast, Rubix44, Shure SM7b, Push2, Ableton 11 Suite, Sibelius, KRK Rokit 5,
- kingy10kingy
- Full Member
- Posts: 174
- Joined: Fri Aug 24, 2012 9:30 am