Ableton Forum

Anyway, fact is that Ableton have introduced latency of external midi by design.
Maybe the manual doesn't explain the complete reasoning behind this.
But I won't doubt the capacity of Ableton in overall system design.

broc wrote:Anyway, fact is that Ableton have introduced latency of external midi by design.
Maybe the manual doesn't explain the complete reasoning behind this.
But I won't doubt the capacity of Ableton in overall system design.

maybe not the capacity..but the ability
when design optimisations are not on the agenda there wont be any

and up

In my view this thread has already achieved something,
namely acknowledgement from Ableton that

1. Midi clock tempo recognition can and should be improved

2. MTC output should be implemented

Now we could discuss remaining sync issues, if any.

broc wrote:In my view this thread has already achieved something,
namely acknowledgement from Ableton that

1. Midi clock tempo recognition can and should be improved

2. MTC output should be implemented

Now we could discuss remaining sync issues, if any.

that was the two main points.. except the in general shoddy midi handling that allows clock glitches on high loads on the midi bus.. like the miri remote feedback szenario.
because that opsoses the midi standard and also should be easy to give the clock prioroty it could be seen as a bug..

Is a bug only lines of code that hang and crash.. so wrong programing syntax or structure, or is a bug aswell the wrong aproach to solve a problem what ultimatly leads to faulty or glitchy operation?

Another problem on the recieving side of timecode.. live dont starts propely on external timecode when beeing in session mode.. it cant start in the middle of clips... only at the start of clips..

This seem to be a not so easy to solve problem as the others.. or has anybody some ideas?


However..

There is one other point regarding the clock syncing that can be improoved.. we have song and pattern mode as clock out options..

while song is with song position pointer you can start in the middle of an arrangement ther is no possebility to do that in pattern mode..

it would be nice if ableton life would work like kenton interfaces or opcode studio vision there.. and genertates a new start command at the correct position ( or acording to global quant) at the next apropiate one.

that would be helpful and state of the art ..at least matching with was state of he art mid of the 1990´s

As said before.. its rather painfull when our main workplatform falls behind the standards of the 90´s in so many regards

drunk typing

broc wrote: 2. MTC output should be implemented

and MTC input (slave mode)!

-Luddy

luddy wrote:

broc wrote: 2. MTC output should be implemented

and MTC input (slave mode)!

-Luddy

look at the preferences under MIDI input sync...

poll is done? or more interested in a fix of the ableton shame?

"I will fix the sync!!!"

create force to get the sync fixed..

please vote in the poll.. to sync or not to sync is the question here

on the weekend i talked with 2 live acts that was playing with 2 laptops, each apple, each on ableton live...
they had to run in free sync because they wasnt able to sync to computers with ableton live with each other..
and asked me if i know any tricks..

i answered.. yeah..the trick is to complain at ableton that they maybe finally after 9 years that problem gets critizised fix the thing or include at least an ableton internal variant to get this done.

Enough!, no one give a shit anymore.

Quit bumping your own crap thread and let it die...

Digital_Damage wrote:Enough!, no one give a shit anymore.

Quit bumping your own crap thread and let it die...

That's why 127 people have voted, with almost 80% in agreement that Live's midi sync needs fixing.

Digital_Damage wrote:Enough!, no one give a shit anymore.

Quit bumping your own crap thread and let it die...

as long each up gives 10 more votes its deffenetly not over. as long collegs of me suffer each weekend during theire live shows its not over. as long they dont even try to fix it its not over.

Problem is that ablton sold theire shitty performance as a must be to theire customers.. this thread is actually ment to inform you that this is not the case.

a midi clock output that follows the midi standard and cant be interupted by remote feedback is no esoteric wish.. thats clearly a faulty implemantation..

and a midiclock input that jitters so muc around in computers with a stable internal clock distribution is clearly a faulty implementation aswell..

and that live is now able to folew time code records but not an other ableton instance is so strange that its actually rather funny than scandalous.

sorry .. this is not over.. actually i would wish that there would be more threads like this.