Korg Forums

michelkeijzers wrote:

Jon Lord wrote:Screenshot function. After trying to take photos of my M3 screen I noticed how useful thios would be for tutorials, how to's etc., preferably to be able to dump the screenshots to disc on the kronos in PNG format would be super.

Interesting ... and wondering how they do it at Korg themselves. Maybe they have a special 'developer' version or added library for debugging and supporting related tasks.

I think it has been mentioned for the M3 that they used somekind of replica of the OS on an actual PC somehow, if I remember correctly.
But since kronos is running Linux in the bottom, this would hopefully be a easier function to implement than on the M3, well depends how much they have stripped away of the actual OS i guess...

Jon Lord wrote:

michelkeijzers wrote:

Jon Lord wrote:Screenshot function. After trying to take photos of my M3 screen I noticed how useful thios would be for tutorials, how to's etc., preferably to be able to dump the screenshots to disc on the kronos in PNG format would be super.

Interesting ... and wondering how they do it at Korg themselves. Maybe they have a special 'developer' version or added library for debugging and supporting related tasks.

I think it has been mentioned for the M3 that they used somekind of replica of the OS on an actual PC somehow, if I remember correctly.
But since kronos is running Linux in the bottom, this would hopefully be a easier function to implement than on the M3, well depends how much they have stripped away of the actual OS i guess...

The software effort should depend on if pixels are sent by the OS to the display driver or the driver is smart and is more or less independent of the OS.

I think the only part of Linux that was used was the Kernal and that the OS was written specifically for the Kronos - correct me if I'm wrong on this. Therefor, any Linux code written specifically for the Kernal wouldn't be hard to implement, but code written for the OS could be difficult. Not really sure which category the display falls into.

I think having the On Screen Pads on the Set List controls tab would be cool. It would make it easier to use them during a session because you don't have to switch to the Combi or Prog to access them.

q

qfingers wrote:I think having the On Screen Pads on the Set List controls tab would be cool. It would make it easier to use them during a session because you don't have to switch to the Combi or Prog to access them.

q

But that means less space for set list slots I assume?

michelkeijzers wrote:

qfingers wrote:I think having the On Screen Pads on the Set List controls tab would be cool. It would make it easier to use them during a session because you don't have to switch to the Combi or Prog to access them.

q

But that means less space for set list slots I assume?

Perhaps a different tab which you can keep open while you step throught patches with an pedal. And also this page would also contain the 512character patch info on top and the name of the current patch of course

michelkeijzers wrote:

qfingers wrote:I think having the On Screen Pads on the Set List controls tab would be cool. It would make it easier to use them during a session because you don't have to switch to the Combi or Prog to access them.

q

But that means less space for set list slots I assume?

No, maybe I wasn't clear. There is a "Control Surface" tab at the bottom of the Set List page that has a window with tabs for the control surface. I'm suggesting adding one more tab to that that is the Chord Pad window, so you don't have to fumble through the menus to get at it during live play. Currently, you would have to select an item from the Set List, then determine if it's a Program or Combi. Then select the Program or Combi buttons, select the */Vector page, and finally the Pads tab. If that was located where I described, the Pads would always be available quickly and easily.

q

Be able to raise the level of the modeled resonance in the SGX1 higher than +6.

Jon Lord wrote:

michelkeijzers wrote:

Jon Lord wrote:Screenshot function. After trying to take photos of my M3 screen I noticed how useful thios would be for tutorials, how to's etc., preferably to be able to dump the screenshots to disc on the kronos in PNG format would be super.

Interesting ... and wondering how they do it at Korg themselves. Maybe they have a special 'developer' version or added library for debugging and supporting related tasks.

I think it has been mentioned for the M3 that they used somekind of replica of the OS on an actual PC somehow, if I remember correctly.
But since kronos is running Linux in the bottom, this would hopefully be a easier function to implement than on the M3, well depends how much they have stripped away of the actual OS i guess...

It's a developer feature in development versions of the software. Not in release versions.

StephenKay wrote:

Jon Lord wrote:

michelkeijzers wrote: Interesting ... and wondering how they do it at Korg themselves. Maybe they have a special 'developer' version or added library for debugging and supporting related tasks.

I think it has been mentioned for the M3 that they used somekind of replica of the OS on an actual PC somehow, if I remember correctly.
But since kronos is running Linux in the bottom, this would hopefully be a easier function to implement than on the M3, well depends how much they have stripped away of the actual OS i guess...

It's a developer feature in development versions of the software. Not in release versions.

But it's on the actual keyboard itself and not on the computer side? Why can't we get this feature I see no harm having it.

Jon Lord wrote:

StephenKay wrote:

Jon Lord wrote:I think it has been mentioned for the M3 that they used somekind of replica of the OS on an actual PC somehow, if I remember correctly.
But since kronos is running Linux in the bottom, this would hopefully be a easier function to implement than on the M3, well depends how much they have stripped away of the actual OS i guess...

It's a developer feature in development versions of the software. Not in release versions.

But it's on the actual keyboard itself and not on the computer side? Why can't we get this feature I see no harm having it.

There are lots of proprietary things in the development version of the software (keyboard side). While I tend to agree with you on this particular one, the fact is that developer features don't need to be debugged, quality controlled, extensively tested and bullet-proofed, the way regular features do. So to add this "feature" to a release version would require additional testing (spend engineering $$$) that Korg likely doesn't feel is worth it, when you compare the list of other things waiting to be done.

StephenKay wrote:There are lots of proprietary things in the development version of the software (keyboard side). While I tend to agree with you on this particular one, the fact is that developer features don't need to be debugged, quality controlled, extensively tested and bullet-proofed, the way regular features do. So to add this "feature" to a release version would require additional testing (spend engineering $$$) that Korg likely doesn't feel is worth it, when you compare the list of other things waiting to be done.

Ok, makes sense. Tho I would not say no if anybody of you who have access to the dev software (No I'm not asking for 1.5) is able to share it with me

Jon Lord wrote:

StephenKay wrote:There are lots of proprietary things in the development version of the software (keyboard side). While I tend to agree with you on this particular one, the fact is that developer features don't need to be debugged, quality controlled, extensively tested and bullet-proofed, the way regular features do. So to add this "feature" to a release version would require additional testing (spend engineering $$$) that Korg likely doesn't feel is worth it, when you compare the list of other things waiting to be done.

Ok, makes sense. Tho I would not say no if anybody of you who have access to the dev software (No I'm not asking for 1.5) is able to share it with me

I'm 100% sure firmware code will not be shared (ok ... Kay is THE exception). But he worked at Korg.

If I would have access to the code (including needed development software), I would stop PCG Tools immediately and start writing changes to the firmware for topics Korg does not has time for.

It would be nice to be able to create 'plugin' software, but even that would cost the engineers time to make and it is not really the core business of Korg to 'support' 3th party developers for firmware.

(Kay: correct me if I'm wrong, you know far more than me about this subject).

michelkeijzers wrote:I'm 100% sure firmware code will not be shared (ok ... Kay is THE exception). But he worked at Korg.

I did not mean the source code. Just a dev version of the OS that can be installed on the machine so I can take screenshots

and start writing changes to the firmware for topics Korg does not has time for.

*like*

jahrome wrote:You guys do know that the leading Yamaha and Kurzweil keyboard workstations in the same price range also have screens that are not angled? The Fantom G, which I own, screen is angled slightly. But its not enough to make a difference. That leaves the M3......unless I am overlooking another workstation.

Well, it's not a "workstation" but my Moog Voyager has a really good angle...........(duh)