3 ms·

Hello HN, I'm a self taught programmer who would like to share my fretboard visualization tool to any musicians/developers out there. It takes a root note and

Hello HN, I'm a self taught programmer who would like to share my fretboard visualization tool to any musicians/developers out there. It takes a root note and a scale/chord type as input and outputs a visual representation of your instrument's fretboard on your terminal along with the positions of corresponding notes. The tool supports several scales, modes, chords, instruments and tunings. Try running it with --help to get you started. The fretboard.py application is actually part of the larger kord music framework I wrote. It's a PyPI package that allows to do music theory stuff... feel free to read the kord documentation if you want to know more. If you are only interested in the fretboard tool, just scroll to the end of the README. :) As the kord project grew in complexity I found myself lacking the time to complete it and ATM it's still a bit rough around the edges. The fretboard.py app is a tool that I regularly use and find extremely useful and I thought it would be cool to share it with the world. I am creating this thread in the hope of: * letting other players make use of the fretboard tool * gathering feedback from programmers on my coding * gathering feedback from musicians on the music theory behind it * allowing collaboration if anyone is interested Thanks for checking it out!

tda 6y ago
Nice idea. I would love to know how the fretboard visualizer works and looks like, but am too lazy to install and run the tool. Could you add an animated gif or at least some screenshots?
- emmanueloga_ 6y ago
  Think this must be the fretboard: https://raw.githubusercontent.com/synestematic/bestia/master/resources/k.png https://raw.githubusercontent.com/synestematic/bestia/master...
  - fwip 6y ago
    This image (or a text version of it) is absolutely worth including in the README! Edit: I see that it got added to the README 2 minutes ago, nice. :)
- synestematic 6y ago
  hi, I embedded some pics to the README. take a look!
indymike 6y ago
Neat! From the PyPi listing here's the github repo. https://github.com/synestematic/kord https://github.com/synestematic/kord.
emmanueloga_ 6y ago
Looks cool! You asked for feedback, from a quick look: * I suspect you may have created the IO lib, bestia, to learn and because is fun, but if you use existing libs like Prompt-Toolkit [1] you can focus more time in the actual app vs infrastructure. Also libs like PT can do a lot of heavy lifting and boring stuff for you like enabling cross platform support (Windows!). * I saw you used .json for tuning configuration, I guess it is ok but perhaps you could just have the tuning be plain python files? Not sure you gain too much by using JSON here. * Speaking of json... could be interesting to make the _output_ of the app machine readable. So instead of focusing on pretty ANSI output, how would the app look if it generated the fretboards as pure data? One could then write a program to create ANSI or HTML or SVG and whatnot from the same data. * There are a ton of music theory libraries out there, perhaps you could get some ideas from those. music21 seems to be interesting in this area (although quite heavy / big) [2]. 1: https://python-prompt-toolkit.readthedocs.io/ https://python-prompt-toolkit.readthedocs.io/ 2: http://web.mit.edu/music21/ http://web.mit.edu/music21/
- honkycat 6y ago
  I agree they should focus on building products not boilerplate but i would argue "outputting pure data, i.e writing your own data format, is just as much boilerplate. JSON is fine IMO
- synestematic 6y ago
  Thanks for your input. The bestia library I created waaaay before I even started working on kord so at this point I just go with it since I know the API in and out. I'm sure there are other libraries out there doing the same thing better but hey, this one is mine. :) As for the .json files I thought they would be a good way for non-developer end users to deal with their self created tunings without having to mess with the code itself. Thanks for the links to the projects, I will try to take a look at them.
djaychela 6y ago
Hi. I've just had a quick look, and I've already found the fretboard.py app useful. I have a 9-string guitar (low C#, F#, B below the usual strings) which I've never really made much use of, and adding a new tuning to the .json file was easy enough, and straight away I can use it to map things out on the fretboard. When I get some time, I want to look into using this to produce PDF output for worksheets as it'll be a lot quicker than my current workflow for producing scale diagrams for pupils. Thanks!
- colejohnson66 6y ago
  Slightly off topic, but what’s the purpose of anything more than an 8 string? Because at 8 strings, you’re already hitting 2 semitones above the standard bass’ tuning (E standard). At that point, if you want to go lower, why not just use a distorted bass guitar? Maybe I just don’t like the muddiness of the guitar distortion sound of the extremely low notes (bass distortion has a different sound)?
  - tiniuclx 6y ago
    The low notes on guitar simply sound quite different from the low notes on bass, mostly because of the choice of string gauge, scale length, pickup design and amplifiers. Some genres such as progressive metal & djent find those sounds very useful! For what it's worth, I agree with you, I find the bass frequencies on even standard-range guitars to not be all that useful. In my own music productions, that part of the spectrum belongs almost entirely to the kick drum & bass guitar. However, once you cut out the low-end mud, the rest of the guitar sounds very good!
  - leetcrew 6y ago
    there are a few reasons. like tiniuclx said, it just sounds different. a downtuned guitar-scale string is going to have a very different tone than a low bass-scale string. like you say, low notes can sound very muddy when distorted. interestingly enough, people usually EQ out most of the low-end frequencies when they play in lower tunings. seems counterintuitive, but it makes for a very interesting sound to my ear. anyways, the main reason to have extra strings is to have a greater range. if you just want to play very low notes, you can downtune a regular six-string guitar pretty far, you could just get a bass, or you could get a baritone guitar for something in between. here's an example of a riff that uses almost the entire range of an eight-string guitar: https://youtu.be/v9RIJ4XlUPU?t=66 https://youtu.be/v9RIJ4XlUPU?t=66
Timpy 6y ago
Very cool project. I particularly like fretboard.py, I'm a sucker for charming command line tools like this. For what it's worth, I have a bachelor's in classical guitar and I taught guitar for 6 years. It would be cool if you could get a single form of a scale instead of an entire fretboard of scale notes, and maybe even limit it to some number of octaves. It would be useful to generate scale charts for students one piece at a time.
- synestematic 6y ago
  that is a neat idea, I'm a bit concerned about the command line options becoming too contrived in order to handle such a high degree of precision. I will defintly keep it in mind though
- synestematic 6y ago
  Hi, just letting you know I've added a -d option that might be great for teachers as it displays degree numbers instead of actual notes
  - Timpy 6y ago
    I just checked it out, very cool! Thanks for taking my idea into consideration.
dceddia 6y ago
Awesome project! In terms of getting people excited about it, embedding a screenshot or two in the README would go a long way, I think. Congrats on shipping!
- synestematic 6y ago
  thanks for the advice, I've added a couple

tda 6y ago

Nice idea. I would love to know how the fretboard visualizer works and looks like, but am too lazy to install and run the tool. Could you add an animated gif or at least some screenshots?

emmanueloga_ 6y ago
Think this must be the fretboard: https://raw.githubusercontent.com/synestematic/bestia/master/resources/k.png https://raw.githubusercontent.com/synestematic/bestia/master...
- fwip 6y ago
  This image (or a text version of it) is absolutely worth including in the README! Edit: I see that it got added to the README 2 minutes ago, nice. :)
synestematic 6y ago
hi, I embedded some pics to the README. take a look!

indymike 6y ago

Neat! From the PyPi listing here's the github repo. https://github.com/synestematic/kord https://github.com/synestematic/kord.

emmanueloga_ 6y ago

Looks cool! You asked for feedback, from a quick look: * I suspect you may have created the IO lib, bestia, to learn and because is fun, but if you use existing libs like Prompt-Toolkit [1] you can focus more time in the actual app vs infrastructure. Also libs like PT can do a lot of heavy lifting and boring stuff for you like enabling cross platform support (Windows!). * I saw you used .json for tuning configuration, I guess it is ok but perhaps you could just have the tuning be plain python files? Not sure you gain too much by using JSON here. * Speaking of json... could be interesting to make the _output_ of the app machine readable. So instead of focusing on pretty ANSI output, how would the app look if it generated the fretboards as pure data? One could then write a program to create ANSI or HTML or SVG and whatnot from the same data. * There are a ton of music theory libraries out there, perhaps you could get some ideas from those. music21 seems to be interesting in this area (although quite heavy / big) [2]. 1: https://python-prompt-toolkit.readthedocs.io/ https://python-prompt-toolkit.readthedocs.io/ 2: http://web.mit.edu/music21/ http://web.mit.edu/music21/

honkycat 6y ago
I agree they should focus on building products not boilerplate but i would argue "outputting pure data, i.e writing your own data format, is just as much boilerplate. JSON is fine IMO
synestematic 6y ago
Thanks for your input. The bestia library I created waaaay before I even started working on kord so at this point I just go with it since I know the API in and out. I'm sure there are other libraries out there doing the same thing better but hey, this one is mine. :) As for the .json files I thought they would be a good way for non-developer end users to deal with their self created tunings without having to mess with the code itself. Thanks for the links to the projects, I will try to take a look at them.

djaychela 6y ago

Hi. I've just had a quick look, and I've already found the fretboard.py app useful. I have a 9-string guitar (low C#, F#, B below the usual strings) which I've never really made much use of, and adding a new tuning to the .json file was easy enough, and straight away I can use it to map things out on the fretboard. When I get some time, I want to look into using this to produce PDF output for worksheets as it'll be a lot quicker than my current workflow for producing scale diagrams for pupils. Thanks!

colejohnson66 6y ago
Slightly off topic, but what’s the purpose of anything more than an 8 string? Because at 8 strings, you’re already hitting 2 semitones above the standard bass’ tuning (E standard). At that point, if you want to go lower, why not just use a distorted bass guitar? Maybe I just don’t like the muddiness of the guitar distortion sound of the extremely low notes (bass distortion has a different sound)?
- tiniuclx 6y ago
  The low notes on guitar simply sound quite different from the low notes on bass, mostly because of the choice of string gauge, scale length, pickup design and amplifiers. Some genres such as progressive metal & djent find those sounds very useful! For what it's worth, I agree with you, I find the bass frequencies on even standard-range guitars to not be all that useful. In my own music productions, that part of the spectrum belongs almost entirely to the kick drum & bass guitar. However, once you cut out the low-end mud, the rest of the guitar sounds very good!
- leetcrew 6y ago
  there are a few reasons. like tiniuclx said, it just sounds different. a downtuned guitar-scale string is going to have a very different tone than a low bass-scale string. like you say, low notes can sound very muddy when distorted. interestingly enough, people usually EQ out most of the low-end frequencies when they play in lower tunings. seems counterintuitive, but it makes for a very interesting sound to my ear. anyways, the main reason to have extra strings is to have a greater range. if you just want to play very low notes, you can downtune a regular six-string guitar pretty far, you could just get a bass, or you could get a baritone guitar for something in between. here's an example of a riff that uses almost the entire range of an eight-string guitar: https://youtu.be/v9RIJ4XlUPU?t=66 https://youtu.be/v9RIJ4XlUPU?t=66

Timpy 6y ago

Very cool project. I particularly like fretboard.py, I'm a sucker for charming command line tools like this. For what it's worth, I have a bachelor's in classical guitar and I taught guitar for 6 years. It would be cool if you could get a single form of a scale instead of an entire fretboard of scale notes, and maybe even limit it to some number of octaves. It would be useful to generate scale charts for students one piece at a time.

synestematic 6y ago
that is a neat idea, I'm a bit concerned about the command line options becoming too contrived in order to handle such a high degree of precision. I will defintly keep it in mind though
synestematic 6y ago
Hi, just letting you know I've added a -d option that might be great for teachers as it displays degree numbers instead of actual notes
- Timpy 6y ago
  I just checked it out, very cool! Thanks for taking my idea into consideration.

dceddia 6y ago

Awesome project! In terms of getting people excited about it, embedding a screenshot or two in the README would go a long way, I think. Congrats on shipping!

synestematic 6y ago
thanks for the advice, I've added a couple