Pairing the Kronos with sound modules

[pete.m]

Hi Chris,

That's really interesting about the inability of the newer Roland to deal with what the older one can. It does sound like it may well be to do with processing power, although I have no technical background in these things so I'm the wrong person to judge.

However, it reminded me of something that sometimes comes up in discussions about synths, namely the question of why it seemed to be commonplace some years ago to produce synths with a polyphony/multi-timbrality that puts to shame some of the (sometimes expensive) mono- and duo-phonic modern synths that we have now. Given how comparatively cheap processing power is today, that shouldn't be the reason. Personally, I'd rather have the polyphony and then decide for myself whether I want to use one finger or eight.

[SeedyLee]

There's a little known setting in Global that affects the way the Kronos sequencer behaves in this regard.

Under Global -> MIDI, there's an option titled "SEQ MIDI Out Setup". When set to the default of "For Master", the sequencer will send reset messages for program change and certain continuous controllers (not all!) when restarting the sequencer. This can have the unfortunate side effect of reseting certain external modules to an undesirable state.

This is probably the best tip of them all so far. Thanks for bringing it up, SeedyLee. I had completely forgotten about that setting and I think it's how I solved the sequencer reset issues I was having years ago. If anyone makes this setting change and it works out for you, don't forget to Write/Save your Global settings, otherwise it will revert to the former selection on your next power up, I think.

I can't bear working with DAWs, but probably not for the usual reasons others have [insert long-winded pointless rant here]. I really do prefer dedicated hardware sequencers over computer-based software ones. The first hardware/keyboard sequencer I ever used was on a friend's Yamaha V50 synth - quirky but functional. A short time later, I got a Korg M1, a Roland MC-300 sequencer and a Roland R5 drum machine. I spent many long years sequencing on all three with those small screens. These days I use Roland MC-50 and a Beatstep Pro in conjunction with the Korg on-board sequencer, all connected to far too much gear. Heck, I'm still using a JL Cooper MSB+ midi patchbay, although I do have a small Mio for my USB synths. I did attempt to switch over to DAWs a few times, but it didn't take. I'm comfortable with my old-school ways I guess.

I started with computer sequencers, and shifted to hardware when I got the Kronos. Software was fine when computers were simpler - but I just had too many issues with MIDI on modern computers, particularly with USB.

There were three things that served as a particular tipping point for me:

- MIDI Timestamping: Great idea that should, in theory, help with MIDI timing accuracy and jitter, except it depends greatly on the right combination of driver/hardware/DAW to work well, and doesn't help with realtime MIDI.
- Poor MIDI implementation in many modern software products. For example, Studio One still doesn't support Sysex - something that's been in the MIDI spec since the mid eighties!
- Poor MIDI hardware - I spent many hours trying to work out why my lovely DSI Tetra wouldn't work with the editor - turns out, the expensive MOTU MIDI interface I had mangled sysex...

The Kronos/Triton/Nautilus/OASYS sequencer might be old, but it's robust, complete, has good timing accuracy, and with the thoughtful shortcuts, I can absolutely fly on that thing. However, it's only really good for live playing, rather than programming, and the latter is what everyone seems to want to do nowadays.

[Mike Conway]

The Kronos/Triton/Nautilus/OASYS sequencer might be old, but it's robust, complete, has good timing accuracy, and with the thoughtful shortcuts, I can absolutely fly on that thing. However, it's only really good for live playing, rather than programming, and the latter is what everyone seems to want to do nowadays.

I prefer playing real time parts when possible. I use undo (COMPARE button) until I get it right. If I screw up, I press it and it goes right back to where I started the last recording (mid- measure, etc.)

For any parts that I can't play live, I use Step Record, sometimes KARMA (for harp glissandos, military snares, etc.), or external arpeggiators from my Deepmind and Virus synths. I use a MIDI merge, so that I can have multiple unis connected to the Kronos MIDI in. Really handy, especially on multi channel recording!

[ChrisDuncan]

I spent a lot of years sequencing with Cakewalk (back when it was midi only), because I had no keyboard chops. It was either that or go out and hire that symphony. I'm a software guy by trade, so doing something on a computer was a familiar experience.

Eventually I bought the Kronos and because serious (ish) about getting some chops, so now I prefer to record the parts live. If I manually create sequences now, I feel like I'm defeating the purpose of having an actual instrument.

Mind you, that's just my particular scenario. There's really no "this is better than that." It's just a matter of what feels comfortable to each person.

I think that's the real priority - what gets in the way the least when you're transmitting music from your soul / brain into an instrument or other such gizmo. For some it's hardware, for some it's software, and I'm pretty sure some just use the Force.