Korg and Raspberry PI

Soundsgood · Post by **Soundsgood** » Mon Jan 01, 2024 3:11 pm

Saw this on the raspberry pi site.

https://www.raspberrypi.com/success-sto ... thesizers/

Interesting read!

MartinHines · Post by **MartinHines** » Mon Jan 01, 2024 4:23 pm

Very interesting.

afr · Post by **afr** » Wed Jan 03, 2024 1:19 pm

Really interesting, Thx a lot

SeedyLee · Post by **SeedyLee** » Thu Jan 04, 2024 6:03 am

It's possibly worth noting that Korg have done a lot of work in the past around optimising their audio subsystem to run efficiently on Linux, which in turn has probably made it relatively simple to migrate to Linux and ARM on the Raspberry Pi. Unlike typical software instruments, that run in user space and communicate with the audio codec through drivers and a hardware abstraction layer, the Kronos and OASYS ran the sound & synthesis engine within the operating system kernel, allowing it to run with very robust timing accuracy and low latency. It's possibly also worth noting that the Kronos and OASYS appear to use the same UI toolkit as their earlier Triton line - and I suspect that there's lots of re-used code between the Triton, MOSS, original OASYS PCI, the OASYS keyboard, Kronos and Nautilus. Even some of the file handling routines appear to be the same.

When it comes to the newest generation of Raspberry PI-based products, I suspect that a lot of the audio system architecture around sample memory allocation, RTAS and device communication have been taken directly from the OASYS/Kronos/Nautilus, with new UI and panel code.

It does make me wonder if we will see a Kronos successor based on the Compute Module...

SynthfulDwarphus · Post by **SynthfulDwarphus** » Thu Apr 25, 2024 6:38 am

SeedyLee wrote:. It's possibly also worth noting that the Kronos and OASYS appear to use the same UI toolkit as their earlier Triton line - and I suspect that there's lots of re-used code between the Triton, MOSS, original OASYS PCI, the OASYS keyboard, Kronos and Nautilus. Even some of the file handling routines appear to be the same.

Very interesting! How were you able to determine the common "UI toolkit" and file handling routines amongst these Korg items? Thanks.

fomalhaut · Post by **fomalhaut** » Fri Apr 26, 2024 7:23 am

SeedyLee wrote:It does make me wonder if we will see a Kronos successor based on the Compute Module...

The real question is if there will be a Kronos successor, though the question has already been discussed here. I believe while the Nautilus holds itself against the phantom montages of the world, Korg will not be launching anything new.

But if the answer is yes, I would bet that it will be based on the Compute Module given all the R&D investment Korg has on that platform.

SeedyLee · Post by **SeedyLee** » Fri Apr 26, 2024 4:15 pm

SynthfulDwarphus wrote:
SeedyLee wrote:. It's possibly also worth noting that the Kronos and OASYS appear to use the same UI toolkit as their earlier Triton line - and I suspect that there's lots of re-used code between the Triton, MOSS, original OASYS PCI, the OASYS keyboard, Kronos and Nautilus. Even some of the file handling routines appear to be the same.
Very interesting! How were you able to determine the common "UI toolkit" and file handling routines amongst these Korg items? Thanks.

Through disassembly of the Eva binaries and associated kernel modules. The developers helpfully left symbols in the compiled binaries