Issue 250 of Future Music magazine has a nice article on iOS and MIDI and features a lot of quotes from me. Looks like a great issue overall. Those of us with iPads can pick it up digitally for around $5.
1.0.6 is live in the app store. Grab it now, if you haven't. As is usually the case, we may do a quick bug fix release before the next big feature update. If you spot any issues, please let us know (there's a support link at the bottom of every page). If you are a fan of GMS, we'd love it if you posted a review in the app store; we couldn't keep making updates without your support. Thanks!
1.0.6 has been submitted for approval! I’m very excited to get this into users hands since it offers a number of enhancements. Thanks to everyone who sent in their suggestions and everyone who has supported further development with their purchases. Users can expect to see the new version approved possibly by end of week or early next week (it’s hard to say).
If you haven’t seen it, I demo’d a couple features here:
I made a quick video to demo a couple of the new features going into 1.0.6...
I thought I’d share a bit of what is planned for Genome MIDI Sequencer in the coming year. This is a rough set of goals and timing is still TBD, but this should give people an idea where the app is heading.
I added a new item to the FAQ which I think bears pointing out since it’s a bit of a hair-puller:
Q: I’m trying to sync with another app but it’s playing at 2x the speed!
A: To understand why this is happening, you need to understand a bit about virtual MIDI ports. Genome creates it’s own Virtual MIDI port and will show up in other apps as ‘Genome’. Other apps will also generally create their own ports too and will show up in Genome’s list of MIDI destinations. If you have another app accept midi from the ‘Genome’ virtual port AND you choose to send MIDI to that App from within Genome, then you will be sending double MIDI messages. Either don’t accept MIDI from ‘Genome’ within the app or turn off that App’s virtual MIDI connection in Genome to fix the issue. It’s unintuitive, I know. Ideally all other apps would create their own I/O ports but Genome would not (that way you just pick within Genome which apps to send to), but there are some apps that don’t have their own virtual I/O’s (like Animoog) which is why Genome has it’s own virtual output port.
Another reason for double MIDI messages or messed up timing could be because you are using the Network session and virtual ports at the same time. If possible, use the virtual ports instead of the Network session, because it will have lower latency.
In other news – there is a new update to Genome coming soon. Just putting the finishing touches on it this weekend.
It’s been a long time coming, but the next update will offer many improvements and fixes. Here’s what you can look forward to:
We are in the home stretch now with the updates. We’ll post an update as soon as we have submitted it to the app store!
Some text here...
