Chords in OpenLP

whurlston

@focusp To enable the media plugin with chords build 44 with Windows, download the MediaInfo 32bit cli from https://mediaarea.net/en/MediaInfo/Download and place it in the same folder as OpenLP.exe They also have builds for Linux/MacOS but I haven't tried it with any other OS yet.

machadoug

Where can I find the interface to add Chords in the latest version for Ubuntu?

yyymdk1

Thanks for the great work! Followed this thread to install (dropped the print.html, slide.* into .../remotes/html, added the cl and c custom formatting tags) and the URL - http://localhost:4316/files/slide.htmlI'm using the 2.4.4 Windows release (I assumed the current release would work and not need a special build for chords). The chord lines are double spaced but don't see the chords (shown below).---[Verse:1]--- {cl}How {c}[G]{/c}great is our God, {c}[D/F#]{/c}sing with me,{/cl}The splendor of a king Clothed in majesty  <img width="394" height="243" title="Image: https://forums.openlp.org/uploads/editor/oo/6ryip556e6lt.jpg" alt="" src="https://forums.openlp.org/uploads/editor/oo/6ryip556e6lt.jpg">Thanks!Mike

cjba850

@yyymdk1 I had the same issue, but all you need to do is File>Import>Settings, and choose the chords_tags.conf file found in the ZIP download. For later travellers, it seems https://github.com/tomasss1024/openlp_chords is the place to find the files. I can confirm that on Win 8.1, OpenLP 2.4.4 (with the jquery.min.js replacement with the new version fix from irnjunior here) runs fine with the remote AND with the Transpose/Print mode. Hope that helps someone.

tomasss

Hello, I played a little with new OpenLP 2.5 (revision 2720). I found that there is only one possibility to have own chords and print view (localhost:4316/files/ is not possible now). I updated my repository for openlp_chords and added files for "Custom Stage Views". You can download stages directory and copy into OpenLP data directory. Then open: http://localhost:4316/stage/chords or http://localhost:4316/stage/print Tomas

yyymdk1

Thanks cjba850, that was it!I played with the build tgc put together - which worked OK for chords, but ran across a bug in the main presentation view when a word has more than one chord (e.g. [G]For[D]ever). I can post additional details if interested.

tgc

Hi! I've just created a new build of the chord branch, and I'd like to get some feedback :)

I consider the chord support to be "feature complete" now, since it is now possible to view chords on the special stageview on the main view and to print them (big thanks to Gyuris Gellért). I hope that everything works as expected, and if not please tell me so that it can be fixed.

Since I'm a programmer and not a musician I might have missed stuff that are obviously wrong or missing...

You can get a windows build here: https://ci.appveyor.com/project/TomasGroth/openlp/build/OpenLP-win-ci-b142/artifacts </div><div>Or get the code from here: https://code.launchpad.net/_tomasgroth/openlp/chords

STEPHANVS

@tgc Hi, downloaded and tested. First thing that noticed is that if a chord is like [/F] (only the bass is present), then it comes through untouched, instead of the /F wrap. There are other differences when comparing to my local code, which I will test later (mostly new features like mid-verse transpose and responsive font sizing), but first I would like to find out why transposing in my code is not compatible with 2.5...

tgc

@STEPHANVS I didn't know "/F" was a valid chord, that's why it is ignored. I assumed a chord always started with "alpha" characters, but I guess it should also accept chords that starts with "/"? There are some of the things that you included in your code that I deliberately left out, because I felt they should be made as a separate branch since they should by applied to all stage views, not just the chord view.

STEPHANVS

@tgc I don't know if it is an officially valid chord, we use it when only the bass note changes, but the chord does not, mainly to save space...

tomasss

@tgc: I played a little with your openlp version with chords. I have problem with chord in view: chord should be on the second line  (editor line: [G]Stále bližšie k Tebe [D]kráčať,) <img alt="" src="https://forums.openlp.org/uploads/editor/2a/ujgfqrm700w8.jpg" title="Image: https://forums.openlp.org/uploads/editor/2a/ujgfqrm700w8.jpg"> The second little problem is with some minor chords typed with lower character like 'Am' as 'a' - I know it's my fault. There is error occured when I'am trying to transpose chords, but I think it should be better to show warning 'Check your chords syntax'. And my last problem is only to allow transpose chords only in 'Edit All' mode and prevent some problem if you transpose chords only in one verse. big thanks

tgc

@tomasss: Thank you for the feedback, I'll try to fix the issue. Good idea to only allow transposing when the entire song is being edited.

STEPHANVS

I have a working .js with mid-verse transposing. I personally think it would be very useful, when a song changes key between verses, and the guitarists can change their capo, as the chords sheet predicts it with a <div> segment...

STEPHANVS

found some leaking chords, but only on the canvas, not in the verse list <img src="https://forums.openlp.org/uploads/editor/z0/6zdw4k34e3bd.png" alt="">

Godisawesome

I have just added the following verse to a song

<blockquote class="Quote">---[Verse:1]--- Halleluyah Halleluyah Halleluyah H[C]alleluya.[F] [G] Abba[C] Father Abba Father A[C]bba father, Abba[F] father ---[Verse:2]--- Lord we love You Lord we love You [C]Lord we love You Lord we l[F]ove You ---[Verse:3]--- You are worthy Holy Spiri[C]t Halleluyah </blockquote>

The chords that appear in the middle of a word are displayed ok, but it the chord is inbetween words as above then a double space rather than just 1 space appears between words, by moving the space so that it is before the chord rather than after it solves this problem, but on line 2 of the verse the end of the line has 10 spaces between the F and G chords but they don't appear to be double spaces :-

<blockquote class="Quote">---[Verse:1]--- Halleluyah Halleluyah Halleluyah H[C]alleluya.[F] [G] Abba [C]Father Abba Father A[C]bba father, Abba [F]father ---[Verse:2]--- Lord we love You Lord we love You [C]Lord we love You Lord we l[F]ove You ---[Verse:3]--- You are worthy Holy Spiri[C]t Halleluyah</blockquote>

Also as can be seen from the attached screenshot there are blank lines inserted after some lines but not others, is this a bug in the code or something in the way i have typed in the verses?

Thanks in advance,

Paul

STEPHANVS

Yes, an option to turn off server side whitespace adding (as the client side js is dealing with it already) would be awesome...

tomasss

hello @tgc, I have problem to export my lyrics with my old chords syntax ({cl}{c}[C]{/c}....{/cl}). there is some error lxml.etree.XMLSyntaxError: StartTag: invalid element name, line 2, column 193 thanks

yyymdk1

I noticed a couple of issues with the transpose - 1) Flats will not transpose (e.g. [Bb]). Sharps work fine.2) If the chord is [A] and transpose -2 gives you H<img title="Image: https://forums.openlp.org/uploads/editor/ri/i8jq9v77zhb4.gif" alt="" src="https://forums.openlp.org/uploads/editor/ri/i8jq9v77zhb4.gif"><img alt="">Also, this might be a useful feature (especially to me) is to keep the device from going to sleep in a browser (Android or iOS) on a stage/chord view. I currently setup my iPad to never sleep. Possibly other workarounds (other no-sleep apps, etc.), but it would be great if it was built in. I found this which I can play with and incorporate if others see it useful -https://github.com/richtr/NoSleep.js?utm_source=mobilewebweekly&utm_medium=email

STEPHANVS

I successfully set up my development environment, but until I know how to operate launchpad, I have a fix for my issue: in openlp\core\lib__init__.py on line 412 the (first) search regex is changed:

new_line += re.sub(r'[([(\w#b♭+*\d/)-]+)]([\u0080-\uFFFF,\w]*)' this way optional () and bass-only /C chords are also processed...

STEPHANVS

@tgc: I redownloaded your code once again, and interestingly it does process the /chords and (chords). Did you change it after the package? Nevertheless I found a more annoying bug: all songs take on the first theme in the list (not the default one), and when I edit the song, the first theme is there, even after I delete the theme field and save.

« Previous Page Next Page »