Playback in VexFlow + "I am stupid" question

[Chris Ward]

Greetings all.

I've been using VexFlow a lot for a project I am putting together - I work down in the guts of the JavaScript.  I have two questions 

1) I am doing a lot of working in the guts of VexFlow JavaScript on a release taken in Feb 2013.  Can I get the playback/audio stuff working via JavaScript on VexFlow?

which brings me to my other question...

2) Could you tell me in really simple language what the different flavours of "Vex" are?  I am mainly focused on the open source VexFlow because of the freedom to use in my own projects which may or may not become "commercial" down the line.  I get a bit confused with VexTab and "My VexFlow" and "Tab Div".  

I fully expect this is just me being thick.  But if the playback is only available in VexTab, which has a more restrictive license, I need to have a think about how/what I am using.

Many thanks again for the awesome work.

Best regards,

Chris

[Mohit Muthanna]

On Tue, May 7, 2013 at 4:21 PM, Chris Ward
<christopher...@gmail.com> wrote:
> Greetings all.
>
>
> I've been using VexFlow a lot for a project I am putting together - I work
> down in the guts of the JavaScript. I have two questions
>
> 1) I am doing a lot of working in the guts of VexFlow JavaScript on a
> release taken in Feb 2013. Can I get the playback/audio stuff working via
> JavaScript on VexFlow?

Playback is built on top of VexTab, but it's an independent codebase
separate from both VexFlow and VexTab. I haven't released that code
(yet). (VexTab has support functions to facilitate writing your own
playback code.)

> which brings me to my other question...
>
> 2) Could you tell me in really simple language what the different flavours
> of "Vex" are? I am mainly focused on the open source VexFlow because of the
> freedom to use in my own projects which may or may not become "commercial"
> down the line. I get a bit confused with VexTab and "My VexFlow" and "Tab
> Div".

VexFlow is the renderer. It is a raw low-level API which offers a high
degree of control, but not simple to use.

VexTab is a higher-level API based on a simple representation
language. You can use it to build music-based applications without
worrying about the myriad of little notational details (e.g. key
signatures, annotations, clefs, beaming, etc.) It is open-source and
free for non-commercial use.

My VexFlow is a content publishing service, not an API.

Hope this helps.

Mohit.

> I fully expect this is just me being thick. But if the playback is only
> available in VexTab, which has a more restrictive license, I need to have a
> think about how/what I am using.
>
> Many thanks again for the awesome work.
>
> Best regards,
> Chris
>
>

> --
> --
> You received this message because you are subscribed to the Google
> Groups "vexflow" group.
> To post to this group, send email to vex...@googlegroups.com
> To unsubscribe from this group, send email to
> vexflow+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/vexflow?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vexflow" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vexflow+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Mohit Muthanna [mohit (at) muthanna (uhuh) com]

[Chris Ward]

Hi Mohit,

Thanks for the response - this clarifies things for me.

I was thinking VexTab was primarily linked to (guitar) TAB use since a lot of the examples I've seen include TAB under the main stave notation.

I use VexFlow (rather than VexTab) and I am very comfortable rummaging around in the depths of your JavaScript code (oh the happy *days* I've spent in stavenote.js where the Canvas drawing happens)  I've invested a lot of time in looking at the JS and integrating some code at the lowest levels for my own requirements.  The issue with this of course is that if there's a big update on your side it's a non-trivial pile of work for me to re-integrate.  I have my own data format (or "model") for holding the attributes of a piece of music score and I have built the rendering API code that consumes my model and used the VexFlow JavaScript API to render the notation.   

Playback is going to be one of my requirements, I was very excited to see it appear and it was in the hope that VexFlow included playback that I re-based my work on a newer codebase in Feb' of this year.  If the payback stuff does get released, what license would that be under?  I only ask as I have to plan my work out and need a feel for where the playback stuff will be as free to use/extend/distribute as the core VexFlow stuff.  

If there are commercial implication about using playback I would prefer to know early.

It's amazing work you've done on this ... now back to stavenote.js I go ... :o)

Regards,

Chris

[Mohit Muthanna]

On Sat, May 11, 2013 at 10:18 AM, Chris Ward
<christopher...@gmail.com> wrote:
>
> Hi Mohit,
>
> Thanks for the response - this clarifies things for me.
>
> I was thinking VexTab was primarily linked to (guitar) TAB use since a lot
> of the examples I've seen include TAB under the main stave notation.

It was originally for tab, but now it has comprehensive support for
both tab and standard notation.

> I use VexFlow (rather than VexTab) and I am very comfortable rummaging
> around in the depths of your JavaScript code (oh the happy *days* I've spent
> in stavenote.js where the Canvas drawing happens) I've invested a lot of
> time in looking at the JS and integrating some code at the lowest levels for
> my own requirements. The issue with this of course is that if there's a big
> update on your side it's a non-trivial pile of work for me to re-integrate.
> I have my own data format (or "model") for holding the attributes of a piece
> of music score and I have built the rendering API code that consumes my
> model and used the VexFlow JavaScript API to render the notation.
>
> Playback is going to be one of my requirements, I was very excited to see it
> appear and it was in the hope that VexFlow included playback that I re-based
> my work on a newer codebase in Feb' of this year. If the payback stuff does
> get released, what license would that be under?

Playback will most likely released under VexTab, since VexFlow is
purely the renderer and has no playback hooks or metadata. It will
most likely be commercial, but I haven't decided yet.