My Eyes!!

[lotty1]

Has anyone a rurally tried the out for a monitor? Or looked at the specs of the display to look for larger plug and at options? Just curious.

What good would the monitor be? Unless of course you could touch the monitor and manipulate the Kronos....

Even with a monitor you still have to look back at the Kronos and touch the actual Kronos screen in order to change what you see on the external monitor.

There is a motherboard in the kronos and it has a usb connection I think so use a mouse

[Bertotti]

There are other remote touch screens out there. Just curious of any looked at the touch screen in Kronos and crossd it to compatible units. Never know might find a bigger one a d with a long cable mount it up higher so you can see and manipulate it. Just a thought, not anything I intend on trying but it seems there are so many people hear who like to experiment I figured someone would have surely tried this already.

[Bald Eagle]

Some time ago I think someone named Heider tried connecting an external screen as well as other interesting things. I don't remember if he had much luck with the screen but everything he did involved disassembling the machine as well as reverse engineering some of the code (which got him in a bit of trouble by the way).

http://www.korgforums.com/forum/phpBB2/ ... hp?t=72192

[Davidb]

Has anyone a rurally tried the out for a monitor? Or looked at the specs of the display to look for larger plug and at options? Just curious.

What good would the monitor be? Unless of course you could touch the monitor and manipulate the Kronos....

Even with a monitor you still have to look back at the Kronos and touch the actual Kronos screen in order to change what you see on the external monitor.

There is a motherboard in the kronos and it has a usb connection I think so use a mouse

Nope, Lotty1.

The OS implemented in Kronos does not support the use of the hardware monitor out, nor a mouse functionality.

[Ojustaboo]

But being Linux based, it should be very easy for them to include this if they wanted in future updates,

They could even make money out of it like they do if you get them to upgrade your ram.

Send them the Kronos, they install the monitor port into the back of the Kronos, they charge you for the upgrade.

[padking]

It would be nice to add a monitor, but a lot can be done
with the software, I had a krome for 2 weeks at
home and I'm having problems now to navigate on
my Kronos.

It's so easy on the Krome big fonts airy windows.....
sure there is more informations on the Kronos
but why do we have to see it all on the same page????
user like me do not use all the deep functions of the
Kronos,why not have a ''user mode'' with program and
combi modes with more airy pages and a ''edit mode''
with much more informations for those who use it.
I don't need all that on stage or in the studio, I need to
see what the hell I am doing and do it fast.

Yeah I know it's a workstation....................

Do yourself a favor and take a look at the tutorials
videos of the Krome you will see what I mean.
http://www.korg.com/Krome

Padking

[tonycroftkbd]

One of the few things Roland has got right recently IMHO is providing iPad apps to programme the Jupiters and Integra-7. Maybe Korg could provide a free iPad app for the Kronos.

[Saxifraga]

One of the few things Roland has got right recently IMHO is providing iPad apps to programme the Jupiters and Integra-7. Maybe Korg could provide a free iPad app for the Kronos.

Korg prefers the old ways:

For exapmle: Korgs 76 character path length restriction.
(All pages in parameter guide)

Trinity 1995
p.161 File/path not found
Situation: The specified file or directory does not exist. Or, you attempted to open a DOS direc- tory that exceeds the hierarchy limit (64 characters or less for the full pathname).
p. 163

Triton 1999
p. 232 Unable to save file
p. 230 File/path not found

KARMA
p.258 - Unable to create directory
Meaning: You attempted to create a directory that would exceed the maximum pathname length (76 charac- ters for the full pathname).
Unable to save file
Meaning: When executing the Disk mode utility menu com- mand “Copy,” the copy destination path length exceeded 76 characters.
Meaning: When saving a file in Disk mode, the save destina- tion path exceeded 76 characters.

OASYS 2005
same

M3 2007
same

M50 2008
same

KRONOS 2011
same

KROME 2012
same p.131 Krome Operations Guide

So much for improvements. Korg leads the pack they think and don´t need to get up to modern times programming standards.
So they have still fixed font sizes and a rigid inflexible UI from 1995.
But it´s no problem: It´s allready known. Danatkorg will give you the page number. Of course he will. It´s the same feature since 1995

But telling the truth just gets you banned here (in my case temporarily) because they think you show no respect and are accusing Korg employees here if you show them their mistakes or lack of progress.
http://www.korgforums.com/forum/phpBB2/ ... hp?t=79149

No idependent discussions possible here. It´s always seen as not constructive. Same worldview as during the cold war here in Germany. We want to have a nice party here! If you don´t like it here: Go east!(= buy Yamaha, Roland etc.) Sounds a bit like Sharp to me.

If users always stumble over the same problems from 1995 till today, you should think there is a problem and you should reconsider things. But what worked very profitable for Microsoft also works for Korg it seems.

Once again: I respect the sound engines and their quality, but the UI and OS are outdated. And the plugin editor is near useless because it´s more or less a Kronos UI clone. When will Korg do anything about all that?

And there is still the keybed problems. Mine is working fine now, but I can now not get the whole dynamic range.
It´s either around 50..120 (5) or 30..100 (4) or 40..110 (9). Very disapointing if you have 8 velocity layers and get only the top 6 or bottom 6.

But who cares? I am just a troll.
Over and out.

[Davidb]

Even when theres some bitchering in the way you argument all that, (and i can understand why) no one can say Those are not true facts, Saxifraga.

And there is still the keybed problems. Mine is working fine now, but I can now not get the whole dynamic range.
It´s either around 50..120 (5) or 30..100 (4) or 40..110 (9). Very disapointing if you have 8 velocity layers and get only the top 6 or bottom 6.

Again, very true.

After more than 2 years since the release of the Kronos series, there are still defective units yet for sale, and/or poorly fixed after the issue, as you described above.

And say so is telling the truth.

But who cares? I am just a troll.

If it helps, I dont think so.

IMHO, you are not.

[michelkeijzers]

Some things should be said with regard to the software engineering aspect:
- If Korg would create a full fledged and flexible UI it will take time ... writing a good user interface is not simple. This time would either cost money (if outsourced or more people devoted to it), or developers who normally do engine/synth improvements have to work on it. In the latter case, it would mean less or slower feature upgrades/new synth.

- Maybe it's personally but I like the UI ... the principle is the same since 1995 but when moving to a newer Korg you instantly can use it. Also every page works the same, so even if you are in less known features (like the sequencer for me), it's not difficult to find a feature. There are no hidden features (ok some are a bit hidden in menu items).

- About mouse connection ... it could be done, but probably it's a more commercial reason not to have it (costs time to support).

- Same for the monitor, but here is even a bigger problem: without a touch screen it would not be that useful, except maybe when a mouse also would be supported.

- A good editor would be nice, for both PC/Mac/IPad. I don't like solutions that only involve an IPad. Not that I dislike Apple, but not everybody wants/has an Apple so it would be strange to create support for a single system (hope I don't get too many disses since PCG Tools is natively for PC; sorry I'm not a commercial company).

- About the size: this always is difficult. Some people want a big font size and less widgets/screen elements on one window, other want as much as possible on one screen. Actually both groups have their good points. The best is to have two kind of interfaces: simple and advanced, or with a big and small font (thus having less/more screens). But creating multiple user interfaces/windows also cost time ... thus money.

[Ojustaboo]

I personally don't mind the UI layout as I'm used to it (that doesn't mean it couldn't be vastly improved with a big update)

For me the biggest problem is it not tilting, my head position having to look out of the very bottom of my varifocals to see the screen, does give me neck pain in a fairly short period of time.

With regards to the expense, while we shouldn't really have to in my opinion, I would be willing to pay around £50 to have a much bigger UI on my PC just to stop the pain

I agree about the research/development costs but these could also be used in their next workstation whether that's the Kronos2 or whatever

[brimoore]

I second (or third or fourth) the call for an iPad app that would serve as a touch screen "extension" for the Kronos touch screen. Not only would this be a great thing for those who can't see the Kronos screen very well, it would also solve the issue of the non-tilting display so many seemed to gripe about in the beginning.

And it would justify me having an iPad even more

[padking]

A kronos application on the iPad is a great
idea, I use my iPad with two applications
for my MOX and it work's great.

Padking

[SeedyLee]

Some things should be said with regard to the software engineering aspect:
- If Korg would create a full fledged and flexible UI it will take time ... writing a good user interface is not simple. This time would either cost money (if outsourced or more people devoted to it), or developers who normally do engine/synth improvements have to work on it. In the latter case, it would mean less or slower feature upgrades/new synth.

- Maybe it's personally but I like the UI ... the principle is the same since 1995 but when moving to a newer Korg you instantly can use it. Also every page works the same, so even if you are in less known features (like the sequencer for me), it's not difficult to find a feature. There are no hidden features (ok some are a bit hidden in menu items).

- About mouse connection ... it could be done, but probably it's a more commercial reason not to have it (costs time to support).

- Same for the monitor, but here is even a bigger problem: without a touch screen it would not be that useful, except maybe when a mouse also would be supported.

- A good editor would be nice, for both PC/Mac/IPad. I don't like solutions that only involve an IPad. Not that I dislike Apple, but not everybody wants/has an Apple so it would be strange to create support for a single system (hope I don't get too many disses since PCG Tools is natively for PC; sorry I'm not a commercial company).

- About the size: this always is difficult. Some people want a big font size and less widgets/screen elements on one window, other want as much as possible on one screen. Actually both groups have their good points. The best is to have two kind of interfaces: simple and advanced, or with a big and small font (thus having less/more screens). But creating multiple user interfaces/windows also cost time ... thus money.

Whilst I agree there are two distinct groups of users - those that want higher information density vs those that want greater accessibility = it becomes a matter of exclusion. A small font size potentially excludes users from using the unit altogether, compared to merely inconveniencing those that want greater density.

I have previously calculated some of the fonts in the PolySix engine to be around 1mm high, for example, which is ridiculous.

Touch screen accuracy compounds the issue. On my unit, after calibration you still need to touch slightly below the desired point on one half of the screen, vs slightly above the element on the other half of the screen. Two calibration points isn't sufficient to yield the required accuracy for the size of the UI elements involved.

I don't mind the overall structure of the interface, and am familiar with where everything is

[Davidb]

Touch screen accuracy compounds the issue. On my unit, after calibration you still need to touch slightly below the desired point on one half of the screen, vs slightly above the element on the other half of the screen. Two calibration points isn't sufficient to yield the required accuracy for the size of the UI elements involved.

True.
Some icons and buttons are too small to press a nd operate them in a comfortably way.

As an example, I never have to touch a paremeter more than one time in the OASYS, whereas in Kronos some operations take twice and even more pulsations to operate it right as supposed.