4 ms·
It took me a while to realize why my PC-based MIDI setup never "felt" right. It wasn't until I replaced it with an Akai MPC-60 style hardware sequencer that my
by primitiveape 4y ago
It took me a while to realize why my PC-based MIDI setup never "felt" right. It wasn't until I replaced it with an Akai MPC-60 style hardware sequencer that my MIDI compositions finally had that "thing" - idiosyncratic timing that felt good and made you bop along to the beat.
Missed the Atari age entirely.
- justinlloyd 4y agoYep, there is a reason people drop thousand dollar to $5,000 hardware sequencer PCIe cards, like the RME RayDat, RME AES, Focusrite RedNet, Marian, or Avid, in to their computers.
- hammyhavoc 4y agoVery happy RayDat user here, only wish I'd sprung for it a decade ago.
- primitiveape 4y agoThose are primarily audio interfaces. The sequencer on an MPC-60, or a PC based MOTU MTP deals with traditional MIDI (5-pin DIN).
- hammyhavoc 4y agoRME's MIDI timing is solid though.
- justinlloyd 4y agoYou're right, I was thinking one thing and typing another thing. Weird how that works some days.
- daneel_w 4y agoThe cause for your setup not being able to keep an accurate pace was likely something else. MIDI operates at only 31 kilobaud and even a lowly PC of the 90s had more than enough timing accuracy to handle that precisely and without delay. But certain software is just arguably worse than other.
- nonrandomstring 4y agoAbsolutely, the bane of PC (Mac slightly less so) sequencers of that era was kernel scheduling. With an OS like Windows you had layers of unpredictable buffer synchronisation. It wasn't until AV optimised RT kernels came of age after 2010 that PC sequencing offered satisfactory results - by which time almost all of the generative signal code is internal anyway (as plugins, VSTs etc).