FR09 - Export and import standard midi files (SMF)

Feature Request #09 - Export and import standard midi files (SMF)[1]

Function suggestion

  • Add ability to export/import (load/save) standard midi files (SMF) at different structural sequencer levels:
    • Track
    • Pattern
    • Song (export only: whole song, including all mute settings baked in)

What would be gained

  • Seamless interchange of sequencer data with Ableton, MPCs, whatever
    • easy external micro editing, then reimport for playback and mixdown
      • more creative and sonic control
    • possibility to create complex pattern in software and import into S2400 for that huge S2400 sound
  • With single (or few) track SMF
    • speed up process by having
      • re-use standard building blocks for kick, hihat, snare etc.
      • easy exchange of parts for variations (like HH16th → HH8t)
  • Possibility to import midis from other artists
    • remixes
    • cover versions etc.
  • In general: interchangeability with everything since invention of midi
    • hardware sequencers
    • MPCs since the MPC60
    • Atari Notator SL
    • all software sequencers and DAWs

UI suggestion

  • Easiest: under file management
  • Could also be nested like Midi → save/load → track/pattern/song (song only in save)
  • Load
    • Preview
    • Track assignment
      • Suggestion: consecutively per track in the midi file
      • Bonus (optional, advanced): possibility to assign Ch10 drum patterns to separate tracks (kick, snare etc.)

Technical aspects

  • would be great if it could include S2400-specific data (CC? NRPN? SysEx?)
  • would be great nevertheless, even if only standard stuff like note-on, note-off, velocity was included

When importing

  • SMF0 → split by channel → assign to pad/track manually
    • perhaps one channel after the other just by
      • using Bank shortcut and
      • then tap pad for dialing in and affirmation
    • other option: everything to the midi tracks
  • SMF1 → prompt user to assign each file track to S2400 track/pad
    • warn or merge if multiple tracks mapped to one pad
  • auto translate midi-notes to tuning
    • optional tuning/octave/transposition setting

When exporting

  • Depending on how far the concept shall carry
    • export for interchange only or
    • export for total backup
  • Options for selecting the specific tracks to be exported in one file
    • like checklists with ballot boxes
    • if necessary or useful: options for translating tuning to midi-notes

Comment/personal information

This (technical aspects, abstract subfunctions) is a rough sketch, because I want to limit myself to 30 minutes a day. I do have many concrete ideas how and what could be useful UX/UI wise and why — happy to elaborate if needed.


  1. numbering only for personal reference, no suggestion of priority or the like â†Šī¸Ž

1 Like