[nis] wrote:3phase wrote:
but with propper syncing in all directions you can !!
Ok 3phase, how about this: I repeat what I said before, which is that I'm about to investigate the whole sync topic and, if I find things that we can improve, I'll try to push its priority as good as I can. I will play a fair game and inform you about the status as often as I can. In return I expect you to stop hijacking other threads with all these lengthy rants about your sync issue and keep them in your own sync thread. I also offer to assist you with setting up your next show. I'm not sure if you already realized this: I am your studio neighbor. It takes me a few seconds to come over and help you with your problems. I may not be able to solve all issues you have, but we should be able to find a halfway satisfying setup for your next show. I offered this a while ago, but you ignored it. Not sure if you have overlooked it or if you simply ignored it. Anyway, I'm offering it again. Take it or leave it.
Deal?
neighbor? thats quite strange... however there is nothing you can help me with the sync issues.. no offense.. but its ableton life itself that has build a barrier for any possible workaround..even free syncing or dj sync is flawed by the unpredictable offset of the reaktion to the start command..
another problem i ve reported, but unrealised as bug..
How you can even dare to adress the dj market with oversseing such important details that a musican needs to trust the offset on the start commmand?
i elaborated how this is done in the older linn mpc´s to show a way to get imideate reaction.. but when there is no imideate reaktion its better to have a fixed offset the musican can learn..
As it is now its pure random. so you have to nudge like a monkey.. i wouldnt dj with that ...
and on a live show its not helpfull either.. needs too much time..
when i start in with my drummachines or 303 i usually dont need to nudge.. its just spot on when you know your machines ...
i was writing half a book about lifes sync issues here allready because i am dealing with that for 8 years now...
i actually doubt that you at ableton really have the complete picture otherwise it would have been on priority 1 allready. You all work just solitary with one computer.. no hardware ..and if hardware not as master. Otherwise the program would be better in this regards allready. When Mr Henke would suffer himself.
but thanks that you want to push that the issues are handled..
But please..when you push it.. try to push in ways that complete solutions are made..
There should be a musical logic behind the decissions.. no compromises like the actual half bar speed update. The external slave algo can be a bit more complikated..and for musicans that work on steady tempos its totally allwright to have 2 bar or more smoothing.. that sounds actually cool on stage when the tempo is on the rubber band..
and in earlier postings i pointed to some ways to realize fast reaktion on tempo changes while having long smoothig in the same time..
But in general ther should be 3 options.. smoothed like in reaktor as standard operation..
fast..for the few that need imideate tempo changes..
and auto..an intelligent algorythm that gets further developed over time or even can be script adjusted by user prefference...
That is what i would like to see in the clock slave department.
To fix it one and for all. Without half baked compromise.
Ther is only one propper syncing. everything less than propper is not good enough.. as i said..you are competiting with stage hardware here..thats the refference..
no other studio DAW...
I guess it needs more than a single developer to get this problem assigned with enough force and overview..
maybe i should do a petition within the berlin producer scene adressed to the owners themself..
I am pretty sure that i will have a 100% there oposite to the poll in the fanboy forum that only had 80% on 15% participation..
And maybe big names count more than forum voices?
However.. good luck.. at least the first time a word that the problem is on the agenda.. just not with any priority..as allways :-/
sync comes last.. but it should have been first.. at the end of the day any sequencer is a clock..
the reason drumachines are so good in this regard is because the clocking is the first thing the os is taking care of..everything else comes second..