djaa
New Member
Posts: 5
|
Post by djaa on Jan 25, 2024 20:07:03 GMT
Would it be possible to allow either to set the file extension in a setting
Eg
.txt
.Pro
.Cho
or to allow having the extension as part of the filename
I would like to use my chordpro editing program and also to stop having to need multiple files in different locations
OSC control would be nice but I know it may be a big ask.
Regards
Damian
|
|
|
|
Post by Torsten on Jan 26, 2024 13:15:04 GMT
Hi Damian,
I'll have to think about this - there are possible issues with this, since setlists use file names without extensions to define a setlist. Of course, I could allow a broad range of extensions and match file names for setlists just ignoring the extension, but there could be conflicts if two files have the same name but different extensions - that could mess things up. Maybe I can enable alternative extensions "at your own risk". Or just allow ONE extension, but allow the user to configure which one. I'll have to chew on this a bit...
OSC control is definitely not on the roadmap - there are other, more immediate priorities. I'll put it on the backlog to revisit at some point in the future.
Not sure how this relates to "MidiReceive.txt" - can you elaborate?
Cheers,
Torsten
|
|
|
|
Post by Torsten on Jan 26, 2024 13:49:14 GMT
Out of interest: what chordpro editing program are you using?
|
|
djaa
New Member
Posts: 5
|
Post by djaa on Jan 27, 2024 16:18:07 GMT
Hi,
i'm using chordpro buddy on macbook
you have to add the filenames to the "MidiReceive.txt" for the program changes, it only recognises the .txt files
Thanks
Damian
|
|
|
|
Post by Torsten on Jan 27, 2024 17:58:11 GMT
you have to add the filenames to the "MidiReceive.txt" for the program changes, it only recognises the .txt files Damian OK, I see what you refer to. BTW: it's not only the MidiReceive.txt that relies on files having the ".txt" extension, it's also setlists and the overall identification of song files that is currently expecting files to be ".txt". So there'll be a bit of careful work necessary to do what you want... |
|
|
|
Post by Torsten on Feb 2, 2024 15:35:04 GMT
Hey Damian,
quick update on this: I've gone through the LP 2 sources - actually LP 2 is more capable than I gave it credit for 😎 - I need to pat myself on the back retroactively...
LivePrompter 2 should deal correctly with files ending in .txt, .pro, .cho, and .chopro (independent of upper / lower case).
I've checked setlists and MIDI assignments in a test directory full of files with a wild mix of extensions - and it seems to work nicely.
The only thing you shouldn't do is have two instances of the same song with different extensions - MySong.txt and MySong.chopro. This may yield different results than you'd expect - LivePrompter will simply pick the first song it finds ignoring extension when populating setlists and MIDI assignments. So just don't do that...
Why don't you give it a try with your chordpro files?
Cheers,
Torsten
|
|
