Do not update to OS 3.1.0 It is not stable, with Karma bugs.
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
If anybody comes across a bug, he/she is obliged to document it well, and must provide the set of circumstances or events that result in the problem. If any other user can reproduce the failure, then it can be accepted as a bug and will be valuable for software developers, say in Korg.
Korg KronosX73, Kurzweil PC3K6, Roland V-Synth GT, Kawai K5000S, Waldorf Blofeld, Novation Ultranova, Behringer Neutron, Yamaha HS80M, Boss Micro BR80, Zoom H6, Sony PCM D100, Tascam DP32SD, Mackie 1202VLZ4, Zoom MS-70CDR, Rode NT1, Sony MDR 7506.
Good newsLeone wrote:Well after all the kind replies I thought there is perhaps something wrong with my Kronos so I went and did a full restore and it works much better now!!chris wrote:When you bought your Kronos I presume that you were aware of the hardware specs. So why complain then afterwards ? I don't get it.
Does OS 3.1 really makes Karma impossible to use ?
Would like to know by the way as I don't really get what the bugs are about in OS 3.1
Thanks in advance and Merry Christmas
Maybe as a guess one of the previous updates messed it up, probably when it crashed updating to 3.0.4.
It seems working fine now or at least has not crashed in one hour! At least it is usable now!!!
It really should't crash even when overloading it. If you get it to crash with a heavy combi maybe save the combi and post it here for others to try.
Thank youBobTheDog wrote:Good newsLeone wrote:Well after all the kind replies I thought there is perhaps something wrong with my Kronos so I went and did a full restore and it works much better now!!chris wrote:When you bought your Kronos I presume that you were aware of the hardware specs. So why complain then afterwards ? I don't get it.
Does OS 3.1 really makes Karma impossible to use ?
Would like to know by the way as I don't really get what the bugs are about in OS 3.1
Thanks in advance and Merry Christmas
Maybe as a guess one of the previous updates messed it up, probably when it crashed updating to 3.0.4.
It seems working fine now or at least has not crashed in one hour! At least it is usable now!!!
It really should't crash even when overloading it. If you get it to crash with a heavy combi maybe save the combi and post it here for others to try.
-
geoelectro
- Platinum Member
- Posts: 1045
- Joined: Fri Sep 14, 2012 2:12 am
- Location: Texas
- Contact:
I just played Christmas Eve with my updated original Kronos. I used the easy split feature so to play key bass. Ran my combi's, sequencer with imported audio, set list etc. flawless...
Geo
Geo
Kronos 2 61
Synthesizers.com Custom Modular
N.I. Komplete 13, Omnisphere 2, VB-3.
Yamaha P-80 Weighted Keyboard. NanoPad2
Synthesizers.com Custom Modular
N.I. Komplete 13, Omnisphere 2, VB-3.
Yamaha P-80 Weighted Keyboard. NanoPad2
Thanks for the video show of the new splits and layer feature.
As far as bugs, i am still holding off on installing v3.1.0
I have used apple iPad for 3 years and it has been one ios update after another. Started at v7.?.? And now up to v10.?.?
All those ios updates and and still bugs to deal with with. Some new updates came in and started me with improvements i did not care for while busting up my groove in areas i was very much accustomed to. The typing keyboard glitches got me fustrated and they keep happening with almost every upgrade.
Ipad and Apple products are still at the top of their class.
Same can be said about Kronos.
Kronos is at the cutting edge of open architecture work-station synths. Nasa space flight engineering has been cutting edge tech from day. And the number of people killed by crashes due to bugs in the rocket or space shuttle design has not stopped it from being cutting edge and going deeper into space. MARS.?
Now all that said, Kronos or any other device will get no-where with an OS that has a bug that crashes the system to the point of stop all and reboot.
I suspect Korg knows that better than me and is working fast on it.
I am still holding off on the new OS and still glad to have a kronos.
I bought my K2 despite all the bug issues in original kronos.
So many original kronos users around who find this new issue small peas compared to what they endured and overcame.
Like i say about my iPad~ where will i run to?
Its all cutting edge stuff and we are riding the evolution in real time for better or worse.
People put up with worse from their spouses and kids since the dawn of pudding, and no replacements. Some people do no replacement, to be more precise.
No wife or kids here and i am keeping kronos.
As far as bugs, i am still holding off on installing v3.1.0
I have used apple iPad for 3 years and it has been one ios update after another. Started at v7.?.? And now up to v10.?.?
All those ios updates and and still bugs to deal with with. Some new updates came in and started me with improvements i did not care for while busting up my groove in areas i was very much accustomed to. The typing keyboard glitches got me fustrated and they keep happening with almost every upgrade.
Ipad and Apple products are still at the top of their class.
Same can be said about Kronos.
Kronos is at the cutting edge of open architecture work-station synths. Nasa space flight engineering has been cutting edge tech from day. And the number of people killed by crashes due to bugs in the rocket or space shuttle design has not stopped it from being cutting edge and going deeper into space. MARS.?
Now all that said, Kronos or any other device will get no-where with an OS that has a bug that crashes the system to the point of stop all and reboot.
I suspect Korg knows that better than me and is working fast on it.
I am still holding off on the new OS and still glad to have a kronos.
I bought my K2 despite all the bug issues in original kronos.
So many original kronos users around who find this new issue small peas compared to what they endured and overcame.
Like i say about my iPad~ where will i run to?
Its all cutting edge stuff and we are riding the evolution in real time for better or worse.
People put up with worse from their spouses and kids since the dawn of pudding, and no replacements. Some people do no replacement, to be more precise.
No wife or kids here and i am keeping kronos.
And with the Karma crash issue, it would help if details were given such as; if it only happens while in the new layer split feature pages, or if it also happens using KARMA outside of the new split and layer pages.
Having work-around options is important to know and normally an ace up Kronos' sleeve.
Split layer function is not doing anything new. It just consolidates access to certain functions in new tab pages that makes things easier and less cluttered in program ,combi and sequencer mode.
I can just as easily not use the new feature or use it and set the results up in combi and sequencer when it comes time to involve Karma. Thats assuming the bug only exists for working Karma in while in the new feature tab pages..
Do the work around as is so often available in Kronos versatility. Do a work around and wait for the bug fix update.
Having work-around options is important to know and normally an ace up Kronos' sleeve.
Split layer function is not doing anything new. It just consolidates access to certain functions in new tab pages that makes things easier and less cluttered in program ,combi and sequencer mode.
I can just as easily not use the new feature or use it and set the results up in combi and sequencer when it comes time to involve Karma. Thats assuming the bug only exists for working Karma in while in the new feature tab pages..
Do the work around as is so often available in Kronos versatility. Do a work around and wait for the bug fix update.
-
Bald Eagle
- Platinum Member
- Posts: 2278
- Joined: Sun Jan 25, 2009 12:06 am
- Location: Long Island, NY