fms
New Member
Posts: 19
|
Post by fms on Oct 4, 2023 4:54:55 GMT
I just started using SetlistBuilder, great utility! Couple of questions... 1) Is there a way to include the header when printing, or would I just need to edit the html each time a list is created? Future enhancement maybe?  2) We have three sets (soon to be four), making occasional minor changes to each set. For shorter shows, we only use 2 of the sets, but potentially different each time. I see that if I have set 1 loaded, and then load set 2 without clearing, set 1 is lost. Is there any way to append the two (or even three) together within SetlistBuilder? Currently the workaround is to use Notepad and create concatenated lists... e.g. Set1-2.txt, Set1-3.txt, Set 2-3.txt... but as each set is changed, I have to repeat the process. Alternatively, I can just print each set out separately but each takes a full sheet of paper.... it would be good if there's a way to print 2 separate sets as one page (without editing html.) 3) I use PureSync to keep several PCs in sync (laptop, practice room, desktop.) I can keep the .txt set lists consistent that way. I also noticed the .json files in my home directory, which I don't normally copy over. Will there be any effects when loading sets if they are not kept up to date, or are they generated on the fly? Thanks again for all you do! |
|
|
|
Post by Torsten on Oct 5, 2023 8:48:13 GMT
Good questions - I'm currently travelling, but will answer once I'm back 😉
|
|
|
|
Post by Torsten on Oct 9, 2023 11:44:42 GMT
OK, here we go:
1) include header in printing
what header are you referring to? If you mean the title of the setlist, that should print automatically once you have saved the setlist with a name. As long as a setlist is <unsaved setlist>, SetlistBuilder will not create a title, but for saved setlists, the file name should be printed in the HTML document.
Or are you talking about the HTML header that shows in your browser tab (and may, depending on your browser be printed in the page header or footer) - this is currently "Setlist", but I could make it also display the setlist file name.
2) Combining Set Lists
Easiest way to do this: create three separate setlists for your three sub-sets. For any new gig, then open Setlist Builder and select the first list you want to include on the left (Pulldown menu) - mark all songs and right-click "Add to list". Next select your second list and do the same. Now you have all your songs in your new setlist in the correct order. Now sprinkle in some dividers (right-click, add divider) to separate the sub-sets. All done!
I could add an "Append" button next to "load" in future, which would make this a bit quicker, but it's such a rare requirement...
3) JSON files
Let's make sure we are talking about the same directory. Your song files should be in the path referenced by your LivePrompter Source, wherever you put that data - if you sync this (songs, setlists, MIDI, pictures), this will keep your content in sync. LivePrompter expects no JSON data there, and there shouldn't really be any in that directory.
The other relevant folder: LivePrompter for Win creates a folder in your system Documents directory, called "LivePrompterData". This contains configuration data like your profiles (Profiles folder) and the current state of the cached song data (Database folder), which is recreated on every Sync (except for the "sources.json", which is managed in the "Manage Sources" dialog in LivePrompter.
If you want to replicate your Profiles folder in there to other PCs (and thus keep your config in sync), feel free to do so - LivePrompter reads that folder on startup to configure itself, so if you want to have 100% the same configurations on all your PCs, syncing the "Profiles" folder will do this (except some of the startup options that aren't profile-specific).
Regarding the "Database" folder, I'd recommend to stay away from most of the files - they get refreshed on every Sync, and if they get overwritten by PureSync, this may mess things up. You could actually sync your "sources.json" across devices (as long as these devices use the exact same target path to the files), so new sources you create will replicate across all devices, but be really careful around this - sync conflicts may have nasty side effects if you create sources on two devices in parallel. And of course, you'll have to start a sync on all devices after having a new sync'ed "sources.json" replicated. Use at your own risk!
Hope this helps!
Cheers,
Torsten
|
|
fms
New Member
Posts: 19
|
Post by fms on Oct 12, 2023 4:51:53 GMT
1) For the header, I was just thinking of the column headers (#, Name, Artist, Duration, Tempo, Energy) when using the print option. Not really needed, since the values in the columns couldn't be confused. 2) DOH - I completely missed the pull-down on the left. Problem solved! 3) OK, I figured the .json files were recreated each time. I sync my entire Documents folder, so I'll add an exception to tell PureSync to ignore LivePrompterData. Thanks again! |
|
|
|
Post by Torsten on Oct 12, 2023 9:34:32 GMT
1) For the header, I was just thinking of the column headers (#, Name, Artist, Duration, Tempo, Energy) when using the print option. Not really needed, since the values in the columns couldn't be confused. OK, now I understand the question. TBH, I removed the table header in the HTML output; it wasn't really useful once you start using set dividers with your setlists. These dividers also provide summary information, e.g. number of songs in the set, aggregate time, and average energy:  Give it a try with your multi-set setlists - far more helpfui than simple table headers... Cheers, Torsten P.S. Pro tip: Select the whole output in your browser, copy and paste to Word - it should correctly recognize the table with formatting. Now it's easy to remove columns or further format the whole thing for better print-out |
|
fms
New Member
Posts: 19
|
Post by fms on Oct 13, 2023 19:25:00 GMT
The dividers are excellent, very nice feature. HTML in word brings sure back memories... good idea. Kudos on the sets above, are they yours? I haven't played Locomotive Breath in years... great tune! |
|
|
|
Post by Torsten on Oct 13, 2023 21:09:31 GMT
Yup, this is one of our "cold start" set lists - one we are pretty much always ready to play without rehearsing. There's tons of other songs in our repertoire - it is constantly in motion, so for any given gig, we start with one of our standard lists, then decide to include other stuff and throw out some of these songs. Then we might have to do a bit of refreshing for some of the other songs. This here is just a set of bread-and-butter stuff we can pull off anytime.
Love Locomotive Breath - especially the piano intro ;-)
|
|
