Wasn't able to run "rake". Doing "mkdir node_modules" was the fix because I had a "~/node_modules"

http://stackoverflow.com/questions/6514621/npm-install-locally

Might want to make a note in the README.

Thanks!

This might exist already, but is there a way to show stave numbers? Sort of like this:

It would be great if you could include first time, second time repetitions into vextab.
Like:

Current messaging is too "techy".

One option is to display the code, and highlight the buggy section.

How do you create ties at the last note of the stave, to the note on a new line stave? I can create one on the new line tying back, but not from the last note tying to the new line.

Is there any way to hide accidentals when they are already in the key signature? For instance, if I am in the Key of D, then all C's and F's should be played sharp. So if I set the key signature to the Key of D, and then type:

notes :q C#-E-F#/4

The sharps on the C and the F shouldn't actually appear in the tabliture automatically. Maybe there should be a setting for accidentals. "True" would mean that it always shows accidentals, and "False" means that it only shows accidentals if they are not already in the key signature.

Have a look at this for an example:

tabstave
notes :8 8b9/3 8b10/3 9b10/3 9b11/3 10b11/3

The bends from 8 or 9 to 10 or 11 don't render properly, however the bend from 10 to 11 does.

Consider this vextab

vextab
options width=400
tabstave notation=true tablature=false
notes :qd X/5 :8 X/5 :h sX/5

The last note is not a half note but a quarter note...

OK, this is minor, but ... I'd like to be able to specify that the notation use b or # in the options section. I find it jarring to see 3/3 rendered as A# rather than Bb. I know I could write B@, but I can't see how to do it in tab. So something like

options accidentals=flats

Thanks!

Hi, it would be great to have hyphenation in lyrics between syllables – to be able to enter one word over multiple notes (e.g. mul–ti–ple). Thank you, zomp

Hi there, I've read extensively about getting text underneath a bar of music as opposed to on top, and have used several methods (e.g. ++) but none seem to be working. I'll paste the mark up here:

tabstave notation=true tablature=false time=C key=F
notes :q F/4 | :8 F-G/4 :q A/4 :8 D-E/4 :q F/4 | F-E-F-A/4 | A-A-A/4 :8 A-G/4 | :hd F/4
text :q, ++, O,|,Haupt,voll,Blut,und,|,Wun,den,voll,|,Schemrz,und,vol,ler,|,Hohn!

In the following, I'm seeing the # applied to the wrong note (if I move the sharp to C then it shows as though applying to F).

tabstave notation=true tablature=false clef=bass
notes (F#/3.C/3)

This works:
tabstave notation=true key=Gm time=4/4 tablature=false
notes :8 D/5-D/5 :q ## ## ## | :8 C/5 C/5 C/5 B/4 :q C/5 D/5|

But replacing the first quaver of the 2nd bar with a rest doesn't:

tabstave notation=true key=Gm time=4/4 tablature=false
notes :8 D/5-D/5 :q ## ## ## | :8 ## C/5 C/5 B/4 :q C/5 D/5|

The whole line disappears... javascript uncaught type error undefined is not a function. But I only have the min.js code loaded which isn't much help to you...

Hi, i have some vextab text:
tabstave notation=true time=4/4 key=C
notes :8 (2/5.4/4) (2/5.T4/4)

if you try to draw it, you will see that vex flow make tie between wrong notes
it should be between 4/4-4/4, but vexflow draw it between 2/5-2/5

Is there some mistake in text of it is bug ?

The multiple-voice support is very nice for guitar, but, it would be nice of you could write multiple voices for piano. Meaning: two staffs (bass and treble cleff) where the barlines are aligned etc.

Goals:

• Keep build system consistent with VexFlow
• Get rid of Rake workflow which is problematic for many users
• Add support for source maps (which comes for free with grunt-contrib-uglify)

Just to be precise, I'm referring to a situation in which one fingers a note, bends it, strikes the note, then releases the bend. Since "p" is already taken by pulloff, I don't have a great suggestion for a letter so i'll just use "z":

         7z8z7/3

would indicate fretting the 7th fret, bending up 1/2 note, striking, then releasing the bend.

If you want to be very fancy, you could allow 7z9z8z7 to indicate a bend up 1 note, then releasing 1/2 note, then releasing one more half note. That may be overkill though.

Hi there,

I'd like to add support for parsing 'lines' as a tabstave option in the vextab artist.
e.g.

tabstave lines=5

I've added an additional key to the opts object (although, do note that these are properties of Staves rather than TabStaves).

890   addStave: (options) ->
891     opts =
892       tuning: "standard"
893       clef: "treble"
894       key: "C"
895       notation: "false"
896       tablature: "true"
897       lines: 6

I confirmed in the playground that passing options to the TabStave constructor like so does work (but would pass opts.lines in practice):

918     if opts.tablature is "true"
919       tab_stave = new Vex.Flow.TabStave(@x, @last_y, @customizations.width -20, num_lines: 5)

I'm having a bit of trouble understanding how to add the grammar for this however. Does there need to be a change to the jison grammar to accommodate this? Adding a lines option to tabstave results in:

Sucky VexTab: Invalid option 'lines' in line 1 column 9

I'll persist with trying to figure it out, but if you could point me in the right direction I'd appreciate it! 😄

It would be great to have tests that show the MIDI player functionality.

I am trying to experiment with writing drum set music, is there a way to force the stem direction? In this example I would want to force the F/5 step up.
http://imgur.com/J3Vv0E7

If you place a rest (##) on a non-treble clef, the initial position will be off.

Hi 0xfe, could you add breath mark support, please? I suppose it would be easy to implement and it would improve phrasing a lot. Best, zomp

I don't get an error from having an empty code window, but as soon as I've finished typing tabstave, I see the error message in the subject in red.

I closed all chrome processes, and then tried this in a completely new document in case the first one had been corrupted. This results in a new window with tabstave notation=true, also displaying this error message.

Thanks!

Open to a pull request changing the tabdiv to expect HTML5-reserved data-*-prefixed attributes (e.g., <div data-editor_height="..." instead of <div editor_height="") for namespacing?

i believe i have accidentally broken the vextab parser in my vexflow. i'm now unable to view or edit my article as the following javascript exception keeps being thrown when trying to load the page:

Uncaught TypeError: Object #<t> has no method 'getLineForRest' 

i'm not entirely sure what caused the problem. i was fooling around with voices. that might have something to do with it.

update

probably should have put this issue in vexflow now that i think about it.

I noticed that the very last example in the vextab tutorial - demonstrating tab with stems - should have an opening triplet: notes :8 5/5 5/4 5/3 ^3^ which doesn't show.
adding notation=true to the tabstave options renders the triplet correctly.

Experimenting, I created a simple melody in My Vexflow and uncovered a few VexTab problems. The article is:

http://my.vexflow.com/articles/287?source=enabled

1. All tied notes are playing as if there was no tie.
2. In the second measure, the first D on the 2nd string should have a natural sign. After a new barline, all accidentals from the previous measure are canceled.
3. The strokes at the bottom of the song should cover all notes in both voices. The problem is there is no way of specifying the stroke end note in the second voice.

This issue come from here: #53 (comment)

The next goal should be to support other module loader, as I explained here via a UMD: #53 (comment)

When checking out the repository, running rake and opening up the build/src/playground.html I then the error that

vextab_parser is not defined

which is caused by this line.

Hi, this is quite complicated enhancement request, but attractive: Make the staves responsive. It would be very nice to have reasonably wide staves on desktops and mobile devices at once. Thanks, zomp

Hi there,

I found that an eight note rest gets appended/prepended to surrounding eight notes instead of standing alone. See my minimal example, with the relevant code

:8 C/4 ##

that produces

Is this by design (e.g. to support multiple voices in a single stave with each its own rests)? If so, is there a way to create an output like (without the bar |)

Thanks in advance (and pretty neat project, btw!),
Dominik

It would be interesting to allow transport without being necessary to rewrite all the notes in the new key.

for instance:
Transport=+1
Transport=-4

Seems to be fret/string

furthermore if the staff get new notes, notes are changed dynamically the player doesn't recognize them.

notes (C/4.E/4.G/4) will render nothing

If you add something after it, then it'll render. e.g. notes (C/4.E/4.G/4) C/4

First of all: this project is really amazing! thanks for it 🙏

I want so ask you if you really need ruby for building the project, because you need node since you writting it in coffee.
And npm has also modules for uglifying and watching the source. These are the libs which you used in ruby, right?

I could do a pull request, if you agree that it makes sense 😉

It's bloated and unnecessary. The functionality used by VexTab is easily replaced by native Canvas calls.

There doesn't seem to be a way to place commas or special characters in lyrics. Maybe entities of some sort?

This would be sliding in from an indeterminate fret, or starting a slide at a specific fret without specifying the endpoint.

To make the parsing easier, maybe it's better not to mess with the current use of "s", and instead use "S" for a slide towards the bridge, and "D" for slide towards the nut:

S9/3 means slide into the 9th from from anywhere higher than the 9th fret
9S/3 means start at the 9th fret and slide towards the bridge
D9/3 means slide up into the 9th fret from anywhere between the bridge and 9th fret
9D/3 means start at the 9th fret and slide towards the nut

Just thinking out loud here ....

Hi there!

It seems there's a subtle bug, or maybe I'm doing something wrong. If a tie is preceded by a triplet, then the tie doesn't illustrate in the clef (just in the tabstave).

Here's an example of the vextab I'm using, with the triplet (and no ties to the B in stave 3 and 4)

    options stave-distance=30 space=10 player=true
    tabstave notation=true
             key=E
             time=3/8
      voice
        notes :8 (7/1.9/2) (7/1.9/2) (7/1.9/2) | (7/1.9/2) (7/1.9/2) (7/1.9/2) | (7/1.9/2) (7/1.9/2) (7/1.9/2) | (7/1.9/2) (7/1.9/2) (7/1.9/2) =:|
      voice
        notes :qd (0/6.9/4.9/3) | :16 ## 8/3 6/3 9/4 6/3 8/3 | 6h8p6/3 ^3^ :8 9/4 T9/4 | :qd T9/4

And here's the rendered output:

Here's one without the triplet, the tie renders correctly (but the bars don't, because the count is wrong, as expected)

    options stave-distance=30 space=10 player=true
    tabstave notation=true
             key=E
             time=3/8
      voice
        notes :8 (7/1.9/2) (7/1.9/2) (7/1.9/2) | (7/1.9/2) (7/1.9/2) (7/1.9/2) | (7/1.9/2) (7/1.9/2) (7/1.9/2) | (7/1.9/2) (7/1.9/2) (7/1.9/2) =:|
      voice
        notes :qd (0/6.9/4.9/3) | :16 ## 8/3 6/3 9/4 6/3 8/3 | 6h8p6/3 :8 9/4 T9/4 | :qd T9/4

And the rendered output:

You can reproduce this bug in playground (http://my.vexflow.com/playground.html):

tabstave notation=true tablature=false clef=treble key=C time=4/4
notes :q C/4 :q C/4 :q D/4 ^3,3^ :8 C/4 :8 E/4 :8 G/4 ^3,3^ :16 C/4 :16 F/4 :16 G/4 :16 F/4 |

also this one:
tabstave notation=true tablature=false clef=treble key=C time=4/4
notes :qd G/4 :8 B/4 :16 D/4 :16 D/4 :16 E/4 :16 F/4 :16 ## :16 ## :16 D/4 :16 F/4 |

The api should take beats into consideration when auto-beaming the notes.

This would be handy to have.

Try this vextab for instance:

tabstave notation=true tablature=false
notes :8dS B/4 :2S B/4

It generates an error:

Sucky VexTab: Parse error on line 2:
...ture=falsenotes :8dS B/4 :2S B/4
----------------------^
Expecting 'EOF', 'OPTIONS', 'TABSTAVE', 'VOICE', 'TEXT', 'NOTES', '=', '[',

While without the slash, it works:

tabstave notation=true tablature=false
notes :8d B/4 :2S B/4

Downloaded vextab-master to give it a try locally.
tabdiv-min.js is missing
I tried using tabdiv2.js instead but it gave me the error:
Uncaught TypeError: undefined is not a function
for line:
this.artist = new Vex.Flow.Artist(10, 0, this.width, {scale: this.scale});

Bug 1

notes 8b9/5 |

Does not ghost bent note.

tabstave notation=true
notes 5b6/5

Same issue. Looks like closeBeam needs to be called with a parameter.

Bug 2

notes | 4/4

Error: Cannot read property 'x' of null

tabstave notation=true tablature=false
notes | 4/4

This works... so it's tab related.

Bug 3

notes |

Does not render bar.

The following example the C/A should line up with the 2nd note but it doesnt and the offset remains throughout the rest of the tab:

tabstave notation=true tablature=false
text :qd,G/A,:h,C/A,:8, ,:w,Fmaj7
notes :qSd X/5 :8S X/5 :hS sX/5 | :w X/5

This only happens in Slash notation, not in normal note notation!

The player breaks when raphael context is present and active.
The file player.coffee only handles canvas context.

VexTab2 is a very nice update. Is there any plans to update it to enable multiple voices if possible? It currently is an excellent tool for single voice guitar, but can't be used for fingerstyle where two voices is a must.