Blending my two loves; Bass and Computer Science!
So I am building a program that already generates "monoscale" fret distances from the nut/zero fret... That's easy and already exists. I am looking to write one that will offer the user the ability to set *two* different scale lengths and then I will eventually build in an ability to export to PDF an actual diagram of the fretboard layout (mono or multiscale).
This is fun to write, but I have a question for the luthiers out there...
Since the fanned frets have to extend to the edges of the board, but must intersect with the strings at their established scale point (i.e. fret "X" at the edge of the board won't be the same distance from the nut as it is under any given string) I am trying to figure out the best practice for rendering the board accurately.
Can I take the nut width and require the user to input a "gutter" value; being a constant distance from the board edge to the High/Low strings and then calculate the fret scaling with the "gutters" being the continuation of the frets past their scale points?
If I can approach it like that, it would make this a bit less complicated as it wouldn't need to worry about # of strings and actual spacing. It would just assume that on both sides of the fret board, the distance from edge to highest/lowest string is constant.
Or would it be more proper to get full dimensions of # of strings and nut/bridge spacings, nut and heel width and stuff so that each fret can be precisely "mathed" out?
I'm not sure I'm even using the correct terminology here so sorry if this is confusing. Just trying to figure out if there is already an understood set of data points people use to calculate this stuff so that if I ever decide to share, or heaven forbid sell(!) this app it would be something usable by those in the know...
Thanks!
So I am building a program that already generates "monoscale" fret distances from the nut/zero fret... That's easy and already exists. I am looking to write one that will offer the user the ability to set *two* different scale lengths and then I will eventually build in an ability to export to PDF an actual diagram of the fretboard layout (mono or multiscale).
This is fun to write, but I have a question for the luthiers out there...
Since the fanned frets have to extend to the edges of the board, but must intersect with the strings at their established scale point (i.e. fret "X" at the edge of the board won't be the same distance from the nut as it is under any given string) I am trying to figure out the best practice for rendering the board accurately.
Can I take the nut width and require the user to input a "gutter" value; being a constant distance from the board edge to the High/Low strings and then calculate the fret scaling with the "gutters" being the continuation of the frets past their scale points?
If I can approach it like that, it would make this a bit less complicated as it wouldn't need to worry about # of strings and actual spacing. It would just assume that on both sides of the fret board, the distance from edge to highest/lowest string is constant.
Or would it be more proper to get full dimensions of # of strings and nut/bridge spacings, nut and heel width and stuff so that each fret can be precisely "mathed" out?
I'm not sure I'm even using the correct terminology here so sorry if this is confusing. Just trying to figure out if there is already an understood set of data points people use to calculate this stuff so that if I ever decide to share, or heaven forbid sell(!) this app it would be something usable by those in the know...
Thanks!