(This is probably my #1 desire for a Bandhelper enhancement, so pardon my long rambling)
Background: we play with backing tracks, BH song automation, and attached MIDI files (lighting), with second song selection triggering song starts. First song selection occurs automatically at the end of the previous song, and is still important since it sets up initial equipment configurations using the default MIDI preset for the next song.
Currently we tap the next song on the setlist on our iPad (which is the 'second song selection') to start each song. Works great! But...
What we'd like to accomplish: After generating a setlist, tag a number of songs in the setlist so they will just play back to back after a previous song is done, with no manual intervention. (In my old pre-BH full band, we did this all the time, deciding collectively ahead of time which songs do well with a minimal pause between.)
More technically, what we'd want is some way to take a given setlist and associate an attribute to any song in the setlist that effectively means 'initiate second song selection for this song immediately after first song selection'. It would be an attribute of the setlist for a given song position, not something persistently associated with a song. (Understood that this might be complex to develop, with perhaps no current 'setlist position' data element to hang this attribute on.)
We're not after literal time-synced song end and start (like a DJ might do); just a very rapid segue from one song to the next (like the drummer knows ahead of time he's to immediately click us in to that next song).
For us there's always a bit of dead time at the end of a song, and an audible count-off (in the backing track) at the start of the next song, so the absense of a pause shouldn't cause an issue with managing changing MIDI presets. (But some kind of user-set pause duration parameter might be useful in case there are equipment issues with zero delay between first and second song selection.)
Adding an explicit pause between every song (except those that run together) seems like so much clutter to the setlist, and reduces visibility of what's next while playing.
I've tried the 'combining two songs into one' approach but it was a lot of work and a nightmare to maintain (e.g. multiple DAW source files at different tempos, reconciling multiple lighting MIDI files, etc.), and moreover is not flexible if you want to change what runs together from gig to gig.
Thanks for the consideration!