Agreed, this could be very cool. Promises to be a common language for
timing, where participants can use different applications, enter and leave
at any time, make tempo changes...
On Wed, Sep 14, 2016 at 3:56 PM, Alex McLean wrote:
> Ableton link have open sourced their sync protocol:
> http
EspGrid already does this and has been used and tested for years (although
continues to develop of course)!
http://d0kt0r0.github.io/EspGrid/
-D
From: haskell-art@group.lurk.org [haskell-art@group.lurk.org] on behalf of Tom
Murphy [amin...@gmail.com]
Sen
It’s also worth noting that they haven’t really opened the protocol, they
open-sourced their implementation of it, with an option to pay for a license if
you want to use it in proprietary software. Definitely a step in the right
direction, and exciting, but I’m hoping at some point there’s actua
You can use EspGrid with commercial software right now. You run EspGrid - you
send it OSC messages.
-D
From: haskell-art@group.lurk.org [haskell-art@group.lurk.org] on behalf of
Spencer Russell [s...@media.mit.edu]
Sent: Friday, September 16, 2016 10:48
Yes, EspGrid seems really nice, and I prefer its design of a running server
that gets queried, instead of providing a C api that's embedded. The best
case would be to have Haskell libraries for both: OscGrid has its
advantages, and it would also be really nice to be able to have an open jam
with pe
This is a good point -- there's still no legal impediment, right, to making
interoperable implementations? I.e. if the spec is the implementation, and
the implementation is open-source, then effectively we can create other
implementations of the protocol, just maybe requiring more
reverse-engineeri
I think the fully legal clean-room path would be for someone to
reverse-engineer the code and write the spec, and then other people (who
haven't seen the code) to write implementations.
Or maybe Ableton just hasn’t gotten around to documenting the spec and will
eventually. But given the strongl
Is the issue that you want an implementation that is BSD licensed
instead of LGPL in order to use in proprietary software ? Because if you
just want to use it in GPL licensed software, then you have no
restrictions, you can use their implementation, change it, rewrite it,
do whatever you want,
