|
Post by rickrepsher on Mar 15, 2024 11:34:23 GMT
Good day. I'm running the android version on a tablet. I regularly have put notation into my lyrics that designate "repeats." Here is an example out of a song: {d_time:2:30} >Intro:< 2:30 |: Guitar | Chunkys >3X< | And 1 measure | |: g f# 2 3 4 >4X< This has worked fine since I started using LivePrompter. The text between the '><' is highlighted, i.e. 3X or 4X or whatever But..... Yesterday I went to rehearsal, and suddenly I have an odd thing going on. Now, sometimes, I only see the X, and in a different highlight color. What could have caused this? Thanks! Rick
|
|
|
Post by rickrepsher on Mar 15, 2024 11:45:12 GMT
Ok.... so a quick look at your newest version would have me believe that this is a feature of your newest design. So.... how do I get show >3X< as 3X in highlighted text? >13X<?
Rick
|
|
|
Post by rickrepsher on Mar 15, 2024 11:53:31 GMT
Nevermind.... I did a little experimenting. So '>3X<' needs to become '>1 3X<'.
I like the idea. Scared the crap outta me last night at rehearsal though.
|
|
|
Post by Torsten on Mar 15, 2024 12:56:10 GMT
I did a little experimenting. So '>3X<' needs to become '>1 3X<'. '>13X<' is enough - see the manual"Note 3: you may experience issues if you have “>”-highlighted parts in your song with that start with a number. This number will now be interpreted as a selection of highlight color and not displayed. This is easy to fix: simply insert a “1” before this number to explicitly select highlight color 1 – now your original first character will be displayed again."
|
|
|
Post by rickrepsher on Mar 15, 2024 15:47:39 GMT
Torsten,
Thanks. Yeah..... I figured it out. Unfortunately Google must have updated the app this week. Went to rehearsal last night and..... ouch.
I see that this no longer works either : {cc3:some kinda text}
So I have a gig tonight, and I'm doing the mad rush to update. Luckily, we are working from a pre-arranged setlist, so I only have to update about 30 songs.
It was quite a scare last night though!
I do think that down the road this makes it a lot easier.
Rick
|
|
|
Post by Torsten on Mar 15, 2024 19:34:04 GMT
I see that this no longer works either : {cc3:some kinda text} Why should this no longer work? Works without any issues on all my systems. Can you check that that you have made the correct settings (Song Display --> Show Custom Comments)? And make sure that the {cc3:...} command stands alone on a line. Maybe you can share a song file where the ccX commands don't work? All my custom comment tags work without any issue - haven't made any change to these tags. Let me know more - if there's something wrong here, I want to fix it in the next build that's coming...
|
|
|
Post by Torsten on Mar 15, 2024 19:35:36 GMT
Also note: I always recommend to disable automatic updates on live-related tablets - I'd rather be in control of my live software updates...
|
|
|
Post by rickrepsher on Mar 16, 2024 22:43:28 GMT
My bad.
So long story short. I got to practice Thursday night and saw I had an issue. Messaged you here Friday morning, and saw your answer. Now I'm at work, and I realize I need to fix 30 songs over my lunch. So I load the newest Windows version, and set the colors.
I missed the Show Custom Comments section.
See what happens in a rush.
And thanks again for the quick reply!
Rick.
|
|
|
Post by Torsten on Mar 16, 2024 23:59:29 GMT
OK, that's good to hear! So I assume that custom comments are still working correctly and don't need a fix - correct? Sorry about the last-minute rush you had to go through to fix the files for the gig - for fixing the rest of your files (and for anyone else with this issue), here's a little trick: To make this change for a number of files automatically, you can use NotePad++ as an editor, then use its Edit-->Find In Files... function. This allows you to execute automatic find&replace across a number of files (e.g. your LivePrompter songs directory). You will need to use its Regular Expressions (RegEx) functionality to find all highlights starting with a number - use the search string '>(\d)'. This will find all "greater than" signs followed by a digit. As a Replace string, use '>1$1' - this will create the correct output of '>1' followed by your original digit. So it will replace '>5' with '>15'. Now you can run this automatic replace across all of your songs, and you should be done. To be sure you're not messing something up, use the "Find All" button first - this will show you where it finds the search pattern in your songs. If you're OK with modifying all these occurrences with the additional '1', use the "Replace in Files" button to actually execute the replacements in your files. Here is the replace dialog that should work: Make sure you set the search mode to "Regular expression". Give it a try - as long as you are only using '>' characters for highlights (and not inside comments or other tags), this should work nicely. Cheers, Torsten
|
|
|
Post by rickrepsher on Mar 18, 2024 16:11:08 GMT
Torsten,
Yep.... everything is working fine!
I forgot the "reasoning" behind custom comments. When I went back and re-read your docs, all good. In the past, I used them do highlights with different colors. Moving forward, I'm sticking with just the highlights. '><'
Thank you again! Rick
|
|