This release reworks some internal mechanisms and addresses some issues, but it also contains a new user-requested feature: a reworked logic for user-specific parts of a song file.
Note: Configuration issues with Windows version
For the Windows users: unfortunately, some internal re-configuration will cause the loss of configuration changes you made in version 1.5.4 and revert settings back to pre-1.5.4 state. Please read this support thread on how to fix this.
Sorry for the inconvenience!
LP Connect – some re-work
I’ve spent some time on the “LP Connect” networking feature, trying to iron out some instabilities and add some checking mechanisms. It should be more robust now, I hope.
New logic for “exclusive” and “ignored” sections
So far, LivePrompter contains a couple of mechanisms to provide user-specific content from a common song file: custom comments, custom pictures, custom transpose / capo, and an “ignore” mechanism. But with these mechanisms, it was still difficult to have certain sections of a song just displayed to one or more musicians – or hidden for multiple users. This made me re-think the “ignore” mechanism (whtch currently just allows hiding a section to ONE user).
Now we have new groups of tags: First, there is {start_of_exclusive:...} and {end_of_exclusive} to denote a section that will only be shown to the users that have selected the correct numbers in their “Show Custom Comments” part of the settings. So {start_of_exclusive:12} will begin a section of the song file that will only be shown to the users that have “1” or “2” in their “Show Custom Comments” settings. {end_of_exclusive} ends any exclusive section – no need for numbers here. These tags can be abbreviated as {sox:...} and {eox}.
Similarly, we have {start_of_ignore:...} and {end_of_ignore} to denote a section that will be hidden for the users that have selected the correct numbers in their “Show Custom Comments” part of the settings. These tags can be abbreviated as {soi:...} and {eoi}.
So if – for example – I want to write two versions of a verse, one of which will be displayed for the singer, the other for the rest of the band, I could do it like this:
# content for the singer only
{start_of_exclusive:1}
This is content for the singer only
it can contain chords, comments, pictures, whatever
All of it will only be displayed for our singer (who has Show Custom Comments set to 1)
{end_of_exclusive}
# now the content for the rest of us
{start_of_ignore:1}
This is content for the rest of the band.
It will not be displayed to the singer, but to everyone else
Nifty, huh?
{end_of_ignore}For compatibility reasons, the existing {ignoreX}/{ignoreoffX} tags will still be recognized, but I find the new system far more useful, so I’d encourage you to use that going forward.
The update should find its way to the various app stores and the Download page over the next days.
Have fun!
