Hi Peter,

Experienced some very odd things at rehearsal tonight.
I have a visual 1,2,3,4 count in and numbers 2-4 are now highlighted in Green when there is no green colour defined in the editor. See screenshot below

Also whenever I tried selecting one track in particular it locked the whole iPad up several times and I had close it and restart it. I’ve sent you my logs just now.
This has only happened since updating to 17.5.1 and/or the latest version of ST3 (3.8.16)

I’m not sure if this has been an issue since the recent iOS update or all along as I’ve only just changed this but the midi@play syntax does not work on the slave iPad. The normal [midi: PC0@1] message works fine but not the @play. It didn’t work on band mates iPad 10 and I’ve just tried it at home with 2 of my iPads (iPad air 2 and 3) and it also does not work.

    Lishy It would help if you also show us the Lyrics Editor to see what you have programed in .

    You will find if you have placed a timecode in front of the 1234 if your first timecode is 00:00:00 you will get the 1 highlighted at start point without starting the song but if you place 00:00:01, this will also make the 1 green like the other numbers, the green colour is not a highlight it looks like this is the standard colour you have chosen for chord display , your highlight colour is another setting , perhaps play around with your colour selections to get it how you need it.
    But i cant tell you exactly to what it is till i see your Lyrics Editor information.
    If it is a bug just update all your software to the latest versions including the operating system, a lot of problems will dissapear and perhaps new ones might apper 😂

      That's not a bug, it is a feature 😉. The new version has support for the nashville numbering system. That means that the numbers 1-7 are also recognized as chords. If this bothers you, you can add a character to the line that is not recognized as a chord causing the line to be rendered as a plain lyrics line.

      1 2 3 4 in Nashville Numbering system would be the chords (assuming the song is in C): C D E F

        peter yes I did think afterwards that it might be that new numbering system. Might leave it as it is as I really don’t want to go through all my songs to change it all on 3 iPads.

        Is the midi@play syntax on the slave iPad a bug and is there any reason why that particular song song is freezing?

          Damir I don’t have any colour/chord settings selected as I use the brightness option and it has only done it since the update like I said but see Peters reply as it looks like it due to this new Nashville chord thing he’s added. I’m also on the latest versions like I said.

          Lishy The @play command on slave iPads does not work as the play command is not sent to the slaves. Only the status "Playing" or "Stopped" is sent and that does not trigger the play midi command. I don't consider this a bug and it has always worked that way.

            peter ok thanks. I’ll revert back to it just sending when the song is loaded. Could you see any issue with that that song that keeps freezing the iPad?

            There is nothing unusual in the logs. Can you export the song and send it to me with instructions how to reproduce the problem?

              I can reproduce the freeze/hang. It does eventually recover, but it will then freeze again. The issue is caused by the bass tabs in the lyrics. They cause the chord detector to freak out. Detecting chords usually takes a couple of milliseconds. With these bass tabs it needs multiple seconds to parse a single tab line (particularly those with a "5" in it). I guess it is a bug in Apples Regular Expression engine as the same code with the same input works fine in a Javascript Regex engine.

              This is a serious bug caused by the nashville number system change and I will have to release a bugfix or remove the nashville feature as soon as possible.

                peter thanks Peter. It’s odd though as all my other songs with tabs in seem fine and it’s just that one that freezes.

                I have found a workaround for this issue. Version 3.8.17 is in review by Apple and will hopefully be available by tomorrow.

                Version 3.8.17 is now available in the App Store.

                  peter thanks so much Peter. Just checked it and all seems to be fine again now.