Korg has released a Kross 2 firmware update which corrects some of the problems people were experiencing and has finally released the Kross 2 editor. Firmware (version 1.1.0) is for the Kross 2 only, not the original Kross. It also adds some sampling features (from the notes in the software package: just installed it myself and haven't had time to test it).
And please follow all the directions before updating the firmware: backup your files as an "all" or .pcg to save your current data!
Kross 2 editor and Firmware update
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Major problem with the Editor.
Installed on my laptop which has a HD display and the Editor Window is a fixed size of about 800x600.
Text is so small I cannot read it.
If I change the resolution of the display to increase the size of the Window the text become illegible.
Has anyone else found this problem?
I have sent a tech query to Korg UK.
Installed on my laptop which has a HD display and the Editor Window is a fixed size of about 800x600.
Text is so small I cannot read it.
If I change the resolution of the display to increase the size of the Window the text become illegible.
Has anyone else found this problem?
I have sent a tech query to Korg UK.
Biggles
Lancashire, UK
Lancashire, UK
Exactly the same for Kross1 and Krome Editors... This is the same layout and software engine for these workstations... Korg just changes some details which differs for one model.
The layout, the IHM, and the user interaction are inherited from 90' ... as for their sound engine.
You can simply try the Zoom function in Windows: Windows Key & [+/-]
The layout, the IHM, and the user interaction are inherited from 90' ... as for their sound engine.
You can simply try the Zoom function in Windows: Windows Key & [+/-]
Does someone have feedback about new sample import/export features... how is it work with KEP, KSC or KMP files from Triton or Kronos ?
And how many time for loading a ""large"" file (64Mo or 128Mo) ? Is it better than Kross 1 (2mn for loading 8MB Binary file during boot time) ?
Sorry for the questions... this is only to know if this feature is really usable or a marketing gadget !
And how many time for loading a ""large"" file (64Mo or 128Mo) ? Is it better than Kross 1 (2mn for loading 8MB Binary file during boot time) ?
Sorry for the questions... this is only to know if this feature is really usable or a marketing gadget !
A lot of improvements !
I had problems with convert pad to program and now works ok,
you can save pads to ksc or wave file, very useful.
I 've loaded ksc files and kmp files from triton ( 64 mb ) , loading time about
2 hours in ram , and now when I 'm turning on it takes about 10 seconds.
What I miss is loading pcg. files, because its a lot of work make programs ,
you must have a lot of knowledge about oscilators , multisamples, velocity, efects....
I had problems with convert pad to program and now works ok,
you can save pads to ksc or wave file, very useful.
I 've loaded ksc files and kmp files from triton ( 64 mb ) , loading time about
2 hours in ram , and now when I 'm turning on it takes about 10 seconds.
What I miss is loading pcg. files, because its a lot of work make programs ,
you must have a lot of knowledge about oscilators , multisamples, velocity, efects....
Thank you for the news !
You mean 2h for flashing the 64MB into the flash memory, and then the Kross boots as usual.
2H for flashing 64MB... No surprise. I remembered my kross 1 takes near 10mn for flashing the 8MB available (I said 2mn in a previous post, but it was far too long, 10mn is a better value).
So 8 times more in this case + some time to process a KSC script.
2H for 64MB... welcome in the 80'. And I was young in 80', so it could be funny to find my young years again, remembering my floppies, my Atari ST.
Seriously this is acceptable if we consider that this feature is for loading new sound banks, or loading ready to use waveform collections...
You mean 2h for flashing the 64MB into the flash memory, and then the Kross boots as usual.
2H for flashing 64MB... No surprise. I remembered my kross 1 takes near 10mn for flashing the 8MB available (I said 2mn in a previous post, but it was far too long, 10mn is a better value).
So 8 times more in this case + some time to process a KSC script.
2H for 64MB... welcome in the 80'. And I was young in 80', so it could be funny to find my young years again, remembering my floppies, my Atari ST.
Seriously this is acceptable if we consider that this feature is for loading new sound banks, or loading ready to use waveform collections...