That safeguard might be going down the rabbit hole to cover various edge cases, some of which you may not think about. Ultimately you’re going to block the user from doing something they want or ask them to resolve that conflict (or leave them with an SD card that is broken or has issues.
You could implement some simple conflict resolution strategy: “I’m sorry Dave, the inserted SD card duplicates midi PC numbers. Unless you eject and open the pod bay doors, I’m going to prefer the PC numbers on the SD card over the ones on the internal storage”. If you do thism you avoid the need to go down the rabbit hole.
It’s a simple preference that most users won’t care about, but will give those affected a guaranteed way of
working with this. Bonus points for letting hr user choose the precedence of SD over Internal (or vice versa), but that might be one preference too many.
I can see some benefits to this approach as well. I can have multiple versions of a song that responds to midi PC depending upon the SD card being inserted or not. Lots of possible uses for this. Of course it’s not much different than having multiple SD cards.
When the PC is preceded by a bank select CC32, like in may other equipment including the Beatbuddy, there will be no conflict between internal memory songs and SD card songs. The first could be bank 0 en the second bank 1.
I did not see any command covering song selection in the new MIDI implementation firmware. Can you at least be so kind as to inform us where in your planning did you fit implementation of this command?
Hey there, this is technically med-long-term, because it will most likely be in a release after Auto quantize is implemented, that is when we are planning to release an update with more MIDI commands. That being said, there has been a lot of interest in this command so we may reconsider that timeline.
However, because of the fluid nature of SD card usage, a system may not be so simple to implement, along with an adequate UX. Currently, we are more focused on standalone capabilities like Locking tracks and Auto Quantize, as well as a simple hands-free enhancement. Not to mention finishing up the current in progress release! We understand you and other users really want this feature, but we can only do so much at once.
On another note, I’d like to reference here that this update to the Aeros for song selection will most likely incorporate this closely related request for the BeatBuddy to open a specific song on the Aeros. Stay tuned.
it’s a shame that it’s not a priority. It was asked a long time ago. Which midi device with backups does not have this functionality? If in a live we have to manually change the sets of each devices it becomes very complicated.
Could not agree more with that. I hope to see this basic functionnality to be added in a upcoming release (soon). My intend is to use the aero in live situation along with the beatbuddy and having to bent down to manually select the song on the aero is a non sense. l am using setlist maker to select the songs on my beatbuddy and would like to do the same with the Aero.
I am afraid this improvement is pushed to the long term, forcing me to re install an Infinity looper in my live rig. Aeros stays in the studio for now.
Got to join the chorus here, I currently use the infinity looper which is so limited in its UX and would love to upgrade to the Aeros but I use Midi PC extensively for live selection of my loops. Please prioritize this as without it using the Aeros live and in the studio would drive me loopy (sorry)
I’d say just (“just”, I know) load the song if only 1 is found with that assignment, otherwise display a list of all songs with the same number and then make the user pick which one to load. If they want to resolve the conflict, they can do that themselves since now they know which songs all have the same number.
Don’t try to hold anyone’s hand too much for things like this. There is no UI that can easily solve it, and the developer will be driven nuts trying to figure out all the edge cases and responding to bug reports.
This is a numbering pattern the user needs to be responsible for managing and to correct when it doesn’t turn out perfect. Just show them what they’ve done.
Helix has a similar difficulty when it comes to IR numbers.
They started out just using an index into a table. That had so many problem cases that they’ve changed it to, I think, the best method. There are names for IR files in the list, but their position is now only an arbitrary assignment. I believe internally they use some form of hash for linking the IR to the preset, the the UI simply shows it’s current index. That means the user never sees the difficult numbers but there is an absolute identifier to make everything stable even when the IR table is altered or the preset is passed between different users.
Something similar should be possible with aeros songs. I hesitate to suggest more detail than that unless asked.
I echo much of what has been said above, although I’m slightly confused why this hasn’t been an option from the beginning with the Aeros. This would hamper any proper use in a gig environment.
Ideally I would want to select the song I am about to perform from OnSong app, and have my midi linked Beatbuddy and Aeros Loop Studio both select that song automatically.
Using OnSong to send Bluetooth program change command through Midi Maestro to the Beat Buddy and Aeros. Both should both be ready to start the same song from the same command. Not many live acts need more than 128 songs, so just need MIDI PC 0-127.
Thank you
I use Setlist maker in order to send PC commands to the beatbuddy, midicontroller and pedals etc and looking forward to do the same with the Aeros. although I agree that 128 songs is more then enough for a single act… I would believe that the aeros should provide the capability to save as many songs as you wish (bank O = 0 to 127 ; bank 1= 0 to 127; etc) so that songs can be mapped into songs app such as OnSong, setlist maker etc or midi controller for once. You certainly don’t want to remap songs for every performance.
I like your long term idea, but was thinking more of a temporary “quick fix.” Whatever songs are loaded into Aeros internal memory are given PC values 0-127.
My MIDI program changes are also controlling a keyboard patch and guitar fx pedal, so I need everything ready with one command. The fact that Aeros requires fiddling with between songs, does not allow me to sell my Boss RC-505.
