CCLI/Midi
Shara Heiniger (Logos)
Member, Logos Employee Posts: 132
The ChordPro implementation does not read CCLI’s ChordPro sheets correctly, so I have to heavily edit them into “Proclaim’s version” of ChordPro. There are several issues, but most importantly, I think Proclaim should display anything in brackets only on the confidence monitor, but it only works with “approved” characters. For instance, CCLI’s charts use the vertical bar character [|] for bar divisions, and unless I change them all to slashes [/], Proclaim displays them on the audience screens. CCLI’s charts also use a period [.] to indicate a repeated chord, and I have to change them all to hyphens [-]. I believe standard ChordPro is supposed to designate everything in brackets as “above the line,” including a whole library of directives such as {go to chorus} or {comment: Title} or whatever, so I’m actually quite confused at Proclaim’s behavior. I would like to be able to copy/paste directly from CCLI’s ChordPro downloads. As a nice-to-have, I would like to be able to skip extra spaces, since those only make sense on a paper chart and not on a lyrics screen or confidence monitor.
The confidence monitor lags behind the main display by 1 to 2 seconds. It makes sense that Proclaim would be programmed to prioritize computing resources on the main display, but if I am triggering slides with MIDI, I would like to see my cues before the audience, or at least at the same time, definitely not seconds later. Even a selectable delay on the main audience slides would be helpful.
The confidence monitor lags behind the main display by 1 to 2 seconds. It makes sense that Proclaim would be programmed to prioritize computing resources on the main display, but if I am triggering slides with MIDI, I would like to see my cues before the audience, or at least at the same time, definitely not seconds later. Even a selectable delay on the main audience slides would be helpful.
Tagged:
8
Comments
-
Nashville numbers too. ;)0
-
Different platforms seem to do different things with the things in brackets in ChordPro format that are not, as the previous author said "approved." But almost universally, that means that unapproved content in brackets will be displayed on the same line as the chords. With Proclaim that is not so, and it is odd/hard to work around. It would be really nice if there were somewhere that Proclaim published what version of ChordPro they were supporting. (And the icing on the cake would be to support the most recent version, ChordPro 6.)0
-
Please support ChordPro 6 or their latest release version.0
