Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
chordcalc - a stringed instrument chord calculator
-
First you should get shellista from github. I did that with goodreader, going to text edit mode and copying the whole thing into the clipboard, switching back to pythonista and pasting it into a new script, then renaming it shellista (its handy to put it in the action menu.) Then, envoke shellista.py and use the commands
mkdir chordcalc cd chordcalc git clone http://github.com/polymerchm/chordcalc.gitHave fun
-
The git command is unknown. What do I do wrong?
-
You probably want to install from the dev-modular branch.
Another alternative is githubget, useful if you only want to clone, and not commit, etc. -
Poly, I submitted a pull request to use numpy in makeWaves, which speeds things up by a factor of many. Also, there was a missing logic case when the waves folder did not exist, I think you wanted to mkdir(otherwise the script fails when trying to create the files)
-
Major update to chordcalc. Now you can see and hear scales for any fretboard and root.
-
FInal update to chordcalc. Its got all the bells and whistles I plan to add. Onto my next magnum opus, a tool for designing guitar soundhole rosettes. Jon Sevy did one in Java. Onto pythonista!!!
-
I was studying the code a few months ago to see whether capo and especially partial capo could be added. Maybe it is already there as a special tuning, but it is not obvious. I tune my guitar with the B changed to C and then apply a partial capo across three strings. It has been a pain figuring out the useful fingerings.
-
I'll think about it. Might be best implemented as a modified tuning and assume that the nut is the capo. Would not work if you are going to "play behind the capo". Then again, there are folk like Willy Porter and Trace Bundy who play with multiple capo's. Sounds like a best implemented as a set of filters.
-
Just to let you know: there is an error line 777.
-
can you be more specific as to the error? I don't get one. What was the chord/instrument/scale/root etc that triggered it. Its a benign function that returns the length of an array which is defined at load time.
-
jmv38:
The onPrevNext function (the action for them) was not checking for presence of available chords. Its now fixed. Thanks.
-
The partial and multiple capo facility does not look simple from what I can tell. This code is pretty amazing but difficult to figure out. I was hoping that the original author would have thought about it since it would seem to be like modeling the fifth string of a banjo but provided for each individual string. In the physical world it is most like being able to move the nut to any spot on the fretboard on a per/string basis. The tuning remains the same, but open strings ring out at where the individual capos are placed. I am trying to understand your idea about it being like a filter.
-
Filter won't work. I am making an effort to add capos. Thought about the banjo as well and will incorporate it. I have to change the basic chord validating code to start its search at the "new" nut. Will add in banjo piece as well. atience please. Fiirst pain was add in a popup to read the fret number while in an action. Onwards!!!
-
I noticed that you have created a new dev-capo branch. Happy to test this whenever you want to put out a new version.
-
Will upload it when I get first working version. Got the capoes to draw, the logic to use\ them in the calculations, banjo style neck, etc. Give me a week. I have a day job, am studying mandolin and building guitars. (whew). Thanks for the push. Needed to do this, but just for me, not so much.
-
So...... shellista has sent 4 days of work into sock hyperspace. Created a temp file. moved everything in there. Messed around with git. moved everything back. Now gonzo. At least it did not remove my brain. Will get it back over the next week or so. Sorry. It was completely done and working.
-
Noooooo. I know the code will probably be better the second time around, but this sucks :-(
I would suggest doing the zip file archive thing next time before attempting the upload. http://omz-forums.appspot.com/pythonista/post/5306403304505344 The latest version even has dropbox upload support. This will come in handy when moving to a new device.
-
Did you do any commits in git, but then just accidentally clobbered it?
If so, everything is there still, hidden in the object store.
It would be possible to walk through all commits.
(Hmm... Thinking we need a git stash command for just this situation) -
@JonB - I just checked github and the last commits are from 9 day ago. This was to be his first attempt to commit to a different branch from the main branch. I was thinking that your new git repo manager app could be the solution to his original problem. He basically had already cloned his main branch into a dev_capo branch and had just completed changes to the code in the dev branch and wanted to commit those. This apparently did not go well from Shellista.
-
What I mean is, sometimes if you do a commit, but the accidentally copy other files and do another commit, it might seem as if your files were lost. Though in this case, I suspect what may have happened is he may have changed branches (checkout) after moving the files in... in shellista git this immediately does a checkout and overwrites what is there. I probably should add a check for uncommitted changes and issue a warning for operations that can clobber files.
By the way, a lot of the new development is happening within stash, (dev branch) instead of shellista. I do plan on porting a few improvements from gitview over to the stash git command, but probably won't keep shellista up to date.
