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.
Hi Filipe, I can't recall if Dream Foot currently receives on MIDI channel 1 or OMNI (i.e., all channels). Don't have my gear with me now to check. If Dream Foot receives on MIDI channel 1, this is not so urgent, but if it receives OMNI, it is important (for me at least).
If Dream Foot receives on MIDI channel 1, then being able to set the global MIDI IN channel would be useful for anyone that has other devices that are limited to MIDI channel 1 (e.g., older Studiologic MIDI Master keyboards, Midiplus Sound Module, and an arpeggiator app - I think arpeggionome - that previously only operated on channel 1). There would be no way to send different MIDI to Dream Foot and the other device/app. Not that this is a good reason to implement this - but all other modern hardware and apps allow you to choose the input channel.
If Dream Foot receives OMNI (all channels), then there is no way to isolate MIDI messages to Dream Foot if MIDI messages are aggregated anywhere in the chain. My chain is below (I actually don't have the keyboard, it's just for example). I send program change messages on the Selah Quartz v3, I can choose the channel to send to. If I set MIDI IN to "HX Stomp", and Dream Foot receives OMNI, then any time I change a song, Dream Foot will receive five different program changes. Whereas, my other devices will all only receive one program change message, corresponding to the channel they are receiving on. Also, Dream Foot will receive all of the note messages from the MIDI keyboard on channel 8 (messages that are intended for Korg Module).
This is probably not problematic for most people, and in the short term there are workarounds (e.g., put the song "Wonderwall" on the first patch for all of my devices, and so on for a maximum of 16 songs). But these workarounds eventually turn into limitations and constrain the MIDI flexibility that I would have otherwise. In other words, Dream Foot will always be the weak link in my chain.
As a side note, you can change the BlueBoard MIDI channel, but only using the BlueBoard app. Given that you are implementing Bluetooth LE MIDI (directly connect without the app), maybe it would make sense to allow people to choose the MIDI IN channel for each device.
Hope it helps, let me know if I'm mistaken or if I've missed anything.
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.