Korg Forums

[CharlesFerraro]

I was watching a recording of a livestream rich formidoni hosted showcasing the Kronos. In it he pulled up a screen showing cpu usage and explained that if you were to insert "O verb" into every effects slot the unit would encumber some lag.

Is it possible for the M3 to experience processor intensive lag?

I remember seeing a post a long time ago where someone bragged about crashing their M3 because they were doing everything you could do with the unit. Not sure if that was a random occurrence or if you can work the M3 so hard that it will consistently crash, say if you had a huge song file or something...

Ever crash your M3 or experience lag because you were working it too hard?
_________________
paypal.me/CharlesFerraro

[Bakerman]

I've noticed the UI becomes slow to respond & draw new screens if KARMA is generating enough data.

[JuneauUnderground]

[X-Trade]

The OASYS and Kronos utilise a dynamic polyphony system where different voices of different types from different engines are able to compete for processing time and resources and have the operating system hand them out on the fly.

It all generates all of its OS, control signals, audio, and fx processing on the Atom processor.


The M3 on the other hand has separate dedicated audio and system processors - the audio beng handled by some kind of DSP whilst the OS and control data is handled by an ARM CPU. The DSP only has to handle one engine, so its resources are entirely known and so the sound engine has fixed limitations such as polyphony.

So apparently generating a lot of KARMA data will overwhelm the ARM CPU that also handles graphics, MIDI, etc. But the state of the DSP is always much more controlled.

Additional engines such as the Radias would be handled by separate DSP resources on the card.

So the Kronos/OASYS software is considerably more complex, in part because it runs in a much simpler hardware (and more widely available as a commodity) setup.
_________________
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro

[CharlesFerraro]

Thanks for the feedback guys. X-Trade, very well explained. You've always been a wealth of knowledge for me. You're definitely my go-to guy for all things Korg.
_________________
paypal.me/CharlesFerraro

[iixorbiusii]

The only time I have noticed lag is when some pretty serious Karma stuff is going on at the same time as creating an audio recording direct to the M3 or iirc to external USB devices. To avoid this, I just created audio recordings directly to an external recording device and avoided recording directly to the M3 altogether (using spdif)
_________________
CURRENT GEAR: A yellowing Casio PT-80, 4 leaking batteries and some broken headphones.
WISHLIST: A PSU and some different headphones.

[CharlesFerraro]

Does anyone know if using the M3 KARMA software will exacerbate the lag caused by doing too much with KARMA?

The software lets you use 10 KARMA modules... Not sure if the extra power is handled by the computer running the software or the M3 processor.

I think the MIDI info is only sent through the M3 and not generated by the M3 but I haven't purchased the software yet so I can't speak firsthand.
_________________
paypal.me/CharlesFerraro

[Bald Eagle]

The KARMA software generates the midi data on the computer so that part does not put a load on the M3. However, the M3 engine still has to process all the midi data being sent so that could cause the M3 to run out of polyphony or other resources.