Urs wrote: ↑
Sat Mar 27, 2021 1:57 am
ThomasLehmann wrote: ↑
Sat Mar 27, 2021 12:36 am
maybe a simple export function for a standard midifile is the solution for now. Every DAW can import standard midifiles. That would help a lot and its a good compromise.
I also mentioned that before:
I wrote:Which leaves us with the option to save sequences as a MIDI file. That requires us to have a platform file browser, which sounds like a trivial thing to do, but has proven to be a major development task to integrate into our framework in a universal manner (e.g. also to load wavetable files etc.).
With the Arp it makes little sense to export a midi file cause an Arp depends on notes being played and Hive has no idea what notes someone will play into the Arp. Midi from an Arp only works if you record output notes in realtime based on incoming notes.
Since Hive can integrate the Sequencer and the Arp, which is where you can get complex patterns, midi export would only work for the Sequencer part... and the Hive Sequencer is so simple. Just 16 steps, monophonic, and very few parameters. One can easily recreate any sequence in another sequencer, or pianoroll.
So I think midi export is a meaningless feature for Hive and a waste of development time. Either do realtime midi output of the arp/seq combo or don't bother. (my opinion only of course)