Hi Carl, Let's look first at the concept of position. The general concensus is that a fret position is designated with a number, e.g. 5th position, 7th position, etc, and the number is based on what f

#ChordPro

Yes, for more than one reason. I have added a warning if the song contains song lines and no {title} was seen. I have also added an experimental command line option --fragment to allow processing a pa

#ChordPro #resolved

Yes, this is known issue (to me, at least). I get bitten by it once in a while, when I process (from emacs) a part of a song file that doesn't include the {title}. For example: aaa bbb ccc becomes aaa

#ChordPro #resolved

Hi Carl, Were any of the tips useful for you?

#ChordPro

(Note: topic changed) Blank lines: Empty (blank) lines in the input will result in as many empty lines in the output. By default empty lines are as high as a normal lyrics line, but you can change tha

#ChordPro #resolved

To show 5 (or any number of frets), adjust vcells in the config. See https://www.chordpro.org/chordpro/chordpro-configuration-pdf#chord-diagrams

#ChordPro

When you increase the base-fret, the open strings will still be open.

#ChordPro

Increase base-fret ?

#ChordPro

@bob As long as you use the command line version you can do everything you want. It is full functional. @ALL Here's a new dmg with a number of MacOS specific changes to make ChordPro more useful: http

#mac

@Sean: Thanks for chiming in. Yes, it would definitely be helpful to get active with some actual production in the CLI and become familiar with the possibilities of the chrodpro program. You can follo

#mac

An addendum to one of my earlier postings. It is currently possible to: Start ChordPro by double-clicking a ChordPro document Preview the document, make changes Save the final result (PDF) from the pr

#mac

I'm currently using CitrusPerl that includes wxWidgets 3.0. For several reasons I cannot build the perl-Wx 'glue' layer so I cannot fix anything perl or wxWidgets oriented. Likewise, I do not use Xcod

#mac

It looks like we hit Apple's sandboxing restrictions. See e.g. https://www.emaculation.com/forum/viewtopic.php?p=63584#p63584. If I understand this correctly. it means that ChordPro can not use Open a

#mac

Try chordpro -X thechordfile.txt. If this works I think something went wrong when you created your ~/.config/chordpro/chordpro.json file. Can you verify that this file is non-empty and inspect it in a

#mac #needinfo

Now also with a MacOS version. Please try it! https://github.com/ChordPro/chordpro/releases/download/R0_977/ChordPro-installer-0-977-13-1-macos-x64.dmg

#informational

https://www.chordpro.org/dl/ChordPro-installer-0-977-13-1-macos-x64.dmg This version has new icons, and supports opening from Finder (by double-clicking a chordpro document).

#resolved #mac

You may find some in https://github.com/ChordPro/chordpro/blob/master/lib/App/Music/ChordPro/res/config/guitar-legacy.json

#resolved

ChordPro comes with a couple of config files with chord definitions for guitar and ukulele. These are JSON files so they should be easy to process. See e.g. https://github.com/ChordPro/chordpro/blob/m

#resolved

Thanks for your feedback! I got some more confirmations from other MacOS users so this may be a good candidate for 0.978. BTW, you can run the CLI from a Terminal as "/Volumes/ChordPro Installer/Chord

#resolved #mac

Please try: https://www.chordpro.org/dl/ChordPro-installer-0-977-10-2-macos-x64.dmg .

#resolved #mac