On Krome and Logic, Drum Tracks and Arpeggios

[lutefish]

Hi, All -

I've also been struggling with Krome and a DAW (in my case, Logic 9). Eventually, I came across a post by Nik1 in the Korg M50 subforum, and also over on a Reaper-specific board, that proved _enormously_ helpful. Much of what I'm setting out below is indebted to him and this post.

1) The Krome Plug-In Editor is 32 bit. It can be used in Logic 9, but not Logic Pro X. I'm not sure what's up with the VST version. If you don't see the Krome plugin in Logic 9, you may need to start the app in 32 bit mode (select the Logic Pro app, get info, tick the box; once Logic has scanned it in 32 bit mode once, it can be restarted in 64 bit mode.)

2) Capturing MIDI data from Drum Track and Arpeggios is stupidly complicated.

3) Capturing MIDI data from Drum Track seems to work in Program mode, and in Sequencer mode, but not in Combi mode. Your mileage may vary.

3a) In an empty project, create a multiltimbral software instrument with 16 tracks.

3b) In Global P1 leave local control on (which is counterintuitive), and make sure that "Drum Track Prog Midi Out" is checked, which I don't believe is default.

3c) Select Midi track 10, manually set Logic's project tempo to the same as the Krome, enable the drum track, start recording. You may have to trigger it with a note, or set the drum track to "start immediately".

4) Arpeggios. I'm still struggling with this - there are some weird effects when you trigger them.

5) Everything else

5a) Turn _off_ local control in Global P1. Programs record Midi data and playback pretty straightforwardly. Sequences also work pretty straightforwardly, with one program per midi channel. Combis get a bit weird, as they tend to layer multiple programs on a single midi channel. But it can be done.

Anyway, after staring at Logic's midi monitor, baffled as to why drum track data wasn't appearing anywhere, thanks again to Nik1 for making some of this possible.

[2020digging]

2) Capturing MIDI data from Drum Track and Arpeggios is stupidly complicated.

Ditto everything else to do with the sequencer and any connection to a DAW. You'd think we were in 1985 not 2013 going on 2014. And the worst part about it is that absolutely no one from Korg is there to help!

Whoever came up with the GUI didn't do justice to what the Korg could possibly do in tandem with a DAW.

Rather than GUI I should have said Information Design. The hoops and hurdles not to mention the inconsistencies one has to go through to record midi data is mind boggling. For example if you are recording more than one song, let's say parts of a song like verse, chorus etc, every time you go to record the new song the combi changes or defaults to the a combi that you dont want.
How does this make any sense? Surely if you are in record mode with a particular combi you should be the one that should be allowed to change the combi if you want not the other way around.

[SanderXpander]

For this reason I almost never midi my hardware synths anymore. I just record audio, or use a VST.