![]() Equipping You to Communicate Effectively | support CMN & share a library of 19K+ images, videos, etc Go Pro! |
![]() | ![]() |
| |||||||
| General Worship Software Discuss programs such as EasyWorship, SundayPlus, MediaShout, WorshipBuilder, SongShow and others. |
| View Poll Results: How much / how do you / display txt | |||
| one line at a time, right out of ccli | | 0 | 0% |
| one paragraph at a time, right out of ccli | | 7 | 19.44% |
| I have to edit the ccli songs to get a reasonable amount on at a time | | 18 | 50.00% |
| I type it all in by hand | | 11 | 30.56% |
| Voters: 36. You may not vote on this poll | |||
![]() |
| | Thread Tools | Search this Thread | Rate Thread | Display Modes |
| ||||
| Our Rector initially expressed a desire to tend towards getting a whole verse on at a time, where this is possible and the result is readable, after experiences in other churches he has visited who display one line at a time, where he has suddenly been presented with lyrics he considers unsound but without the time to stop himself singing them ![]() In practice I am tending to limit it to 4-6 lines nowadays. Yesterday was (all being well) our last Sunday of Easislides, the MediaShout disk arrived in Saturday's post... Richard |
| ||||
| Quote:
The software we use, SongShow Plus, you can use page breaks or x lines per screen and I rarely use x lines per screen, unless I've been through the song several times and know that x (usually 4) will give me breaks where I want them. And even them I've been burned by my own overtweaking. After settling on 4 lines per page on a particular song, I went back and put a line break on a line that I decided was too long. That threw the line count off and I didn't catch it. So, for me, the control freak , hard-coding the page breaks is the way to go.
__________________ Joel Osborn Milton SDB Church "...if we are to glorify God fully, we must engage our mind in knowing him truly and our hearts in loving him duly." - John Piper, Think |
| |||
| I'm still trying to get this really sorted out, so we have been varying between 3-8. Because large font and ease of following are our major goals I'm moving toward trying to get about 4 lines on a screen with occasional variations based on the song. I also discovered again what I already knew - preview is not always exactly what you think it is. For some reason MS showed all the lines on the screen in preview on one song, but chopped off the last one when projected. I was trying to get an entire verse of a hymn on each screen and it just didn't quite work out. Pastor Tim |
| ||||
| Quote:
__________________ John |
| ||||
| We do one verse or maximum 4-6 lines, whatever seems to fit the song and the screen best. All manual breaks, both line and page, partly from a control standpoint and partly because our software package doesn't auto-wrap. Sometimes we'll do more than four lines where two logical groups of lines work well on screen together; these are broken by some whitespace in between. (A perfect example is the song You Are Holy (Prince Of Peace) where there are two parts at the same time. It's rather bothersome, but that seems to be the best solution to that. All our text is hand-entered, for good or bad. Much of it has been through one system conversion (which worked remarkably well but wasn't 100 percent perfect because the conversion programmer (me) was lazy and didn't take into account one or two relatively rare exceptions to the rules of the source data). And for preview, we use a 9-inch throwdown monitor looking at the real output signal. It's not a look-ahead preview, but it's definitive when running through a set quickly before service to make sure it all sits right on the screen, and since we DSK this signal in the main switcher, the monitor is always hot even if the DSK isn't. |