> On 09/22/2016 07:30 PM, Tito Latini wrote:
>> On Thu, Sep 22, 2016 at 09:16:12AM -0500, Paul Davis wrote:
>> [...]
>>> > Ableton have now done that, albeit by circumventing the hardest parts
>>> of
>>> > the problem (a tempo map with varying meter and tempo).
>> What?
>>
>> I repeat: that's not
On Thu, Sep 22, 2016 at 4:27 PM, Tito Latini wrote:
> On Thu, Sep 22, 2016 at 12:49:42PM -0500, Paul Davis wrote:
> > The innovation is defining an API and protocol based on 3 concepts:
> >
> > tempo synchronization
>
> an integral to get the position with the new bpm
On Thu, Sep 22, 2016 at 07:58:03PM +0200, Robin Gareus wrote:
> [...]
> Also coming up with a protocol is the easier part. Documenting it,
> pushing it out to users, gaining traction in the industry etc is the
> hard part.
opus-codec is an example of authentic Art (rfc, code, etc) and not
On Thu, Sep 22, 2016 at 12:49:42PM -0500, Paul Davis wrote:
> The innovation is defining an API and protocol based on 3 concepts:
>
> tempo synchronization
an integral to get the position with the new bpm
> beat alignment
ask to live coders
> phase alignment
related to beat
On 09/22/2016 07:30 PM, Tito Latini wrote:
> On Thu, Sep 22, 2016 at 09:16:12AM -0500, Paul Davis wrote:
> [...]
>> > Ableton have now done that, albeit by circumventing the hardest parts of
>> > the problem (a tempo map with varying meter and tempo).
> What?
>
> I repeat: that's not an
On Thu, Sep 22, 2016 at 12:30 PM, Tito Latini wrote:
> On Thu, Sep 22, 2016 at 09:16:12AM -0500, Paul Davis wrote:
> [...]
> > Ableton have now done that, albeit by circumventing the hardest parts of
> > the problem (a tempo map with varying meter and tempo).
>
> What?
>
>
On Thu, Sep 22, 2016 at 09:16:12AM -0500, Paul Davis wrote:
[...]
> Ableton have now done that, albeit by circumventing the hardest parts of
> the problem (a tempo map with varying meter and tempo).
What?
I repeat: that's not an innovation.
>From Incudine web page [1]:
Features
[...]
*
On Thu, Sep 22, 2016 at 2:34 AM, Patrick Shirkey wrote:
>
> It seems that the lack of interest in adding similar functionality to JACK
> has opened up a gap in the "market".
>
there was no lack of interest, but rather an inability to come up with an
abstraction for
> On 09/21/2016 11:24 AM, Perry Nguyen wrote:
>>
>> Though after reading your post to LAD a couple times over it seems like
>> there is possibly overlooked but important incongruity between BPM and
>> "linear/real-time".. and perhaps that limits the ability of word-clock
>> time designators like