"Advanced MIDI Control" as an In-App Purchase?

I had a thought recently, why not make an in-app purchase for "Advanced MIDI Control" ?

Understandably adding features into an app takes resources. I guess there are three ways to recover the cost of adding new features: 1) sell more, 2) increase the price of the app by a few bucks, or 3) offer some of those features as an in-app purchase. It struck me today that "Advanced MIDI Control" might be one of those features that would work well as an in-app purchase.

The reason being that there are probably two types of users: 1) those that don't need MIDI, and wouldn't know what to do with it, and 2) those like me, who feel that without these features, the app is more of a rehearsal room thing than something to incorporate into a live rig. It is quite clear that there are advanced MIDI nerds that want these advanced features in Dream Foot (see 1, 2, 3, 4, 5, 6).

I think the following would really make this a standout app (I know, I have mentioned some of these elsewhere in the forum, consider this a consolidation of MIDI-related ideas).

1) Send MIDI CC/PC for each progression (and song)

There could be two tabs when you go into the progression information: 1) Name, and 2) MIDI

Also add a MIDI section for the "Song Detail" window under Tempo and Signature

2) Transmit MIDI out on different channels for each progression

This could be in the MIDI tab mentioned above

3) Select a global MIDI in channel

Add this to the Advanced MIDI global settings under MIDI input behavior

4) Receive program change messages to select the song in the setlist (#1-16)

Self explanatory, would be good to have a setting to ignore PC messages in the global Advanced MIDI Settings section (by the way 32 songs would be pretty awesome)

5) AUv3 MIDI plugin

So that Dream Foot can be incorporated into AUM and other AUv3 hosts

6) Bluetooth LE MIDI direct connection

Without having to connect to third party apps (e.g., the Blueboard App), also with the ability to set each MIDI map button to either momentary or latch, instead of having this as a global setting for all mappings

Of course, I have no idea how feasible this is to do as an in-app purchase from a programing perspective, and I don't know what your plans are for the app, and what features are upcoming. Just sharing without filter. Not trying to tell you how to make your app, its quite clear you guys know what you're doing!

I'm sure there are some MIDI features that I've missed, and some I mentioned that are not so useful to others. I just listed the top few that I feel would open up the app to a MIDI power user. I'd definitely pay the price of an overpriced coffee (or a few) for these features as an in-app purchase, and I think a lot of people that use AUM and have MIDI pedalboard would as well.

Hope it stirs up some ideas, thanks for making the app - really enjoying using it. As a singer/guitarist in a rock band, I never imagined I would be able to feasibly use my foot to incorporate live sounds that we use in the studio (aka my living room). It's a lot of fun and Dream Foot is by far the best tool that I've tried for accomplishing this. Take care.

3 comments

3 Comments

Filipe Michael (CEO)

Apr 16, 2020

•

Hey Kevin, Your feedback is great man.

Keep those ideas coming 👍🏼 We are in the process of adding a few of those into the next update that is coming up soon. As of now, we are currently implementing Bluetooth LE, and the ability to send program changes out of each progression. The other ideas are on our cue for the following updates, but we are definitely moving forward with AUV3 I know that is a game changer for ios producer. By curiosity, I am trying to see how global MIDI CHANNEL IN will make a difference, specially since you only get MIDI from the apps that you select under MIDI IN. Just want to see in what scenario you will use this.

kevin_627

Apr 25, 2020

Replying to

A few follow up thoughts:

1) If, when loading a song, the program/control change midi message from the first progression is sent out, then there is no need to be able to send song-specific midi messages. I suggested song-specific and progression-specific midi messages before, both are not needed.

2) Make sure to allow for multiple program/control messages to be sent for each progression. I recommend four, but I think the minimum is three. The reason for this is that a program change may be useless without accompanying bank changes (via two control change messages). For example, to select the "Orchestra Strings Spic & Leg 4" preset in iSymphonic, I need to send all three of the following commands below. If I could only send one midi message, I wouldn't be able to choose the patch that I need.

I recommend four because this will give a bit more flexibility. For example, I could switch to a new patch and use an additional control change message to lower the volume for a quieter part of the song.

3) For the midi in channel, I think the best way to do this would be to have in global settings a "Default MIDI in channel" and a "Default MIDI out channel" (both can be set to 1-16, or omni). Then have a second option for "Bluetooth MIDI in channel" and this can be set to 1-16, or "omni" or "default". If "default" it will refer to the "Default MIDI in channel"

4) For the midi out channel per progression, each progression could be set to 1-16 or "omni" or "default". If "default" it will refer to the "Default MIDI out channel" in global settings (see above). All progressions will be set to default by default, so users that don't care about midi will not face issues.

I'm trying to provide suggestions that will add functionality without making the app complicated. Hope those thoughts are useful!