Good Midi Clock

electrofux · Post by **electrofux** » 13 Sep 2013 16:07

So many cool Sequencers and Arpeggiators could be built wihin Lemur if the Midi Clock would be finer and more stable.

Jaunmanuek · Post by **Jaunmanuek** » 06 Feb 2014 15:37

yes,
but which is the good midi clock in lemur at this moment ???
have you find a good one ?

thank you

jma

Softcore · Post by **Softcore** » 06 Feb 2014 16:08

+1

tighter timing (stable framerate at all and ANY costs - even if it meant LOWER limits in size of templates) is my only complaint with Lemur.

electrofux · Post by **electrofux** » 06 Feb 2014 16:37

Would open up a new world.

Post by **nick_liine** » 06 Feb 2014 18:12

Request duly noted.

Traxus · Post by **Traxus** » 06 Feb 2014 21:05

agreed, it would be nice to be able to pull a steady BPM from the midi clock

mat · Post by **mat** » 08 Feb 2014 15:42

+1 for a tight and stable Midiclock

The Lemur (even old jazzmutant Lemur) gives so many opportunities to create tools, so it is a hard miss that the Midiclock is so untight.
It was the big disapointment for me when discovering Lemur in 2008. If it had a stable Midiclock I would have never dig my nose into max/msp and stuff like Sequencomat would be Lemur only, which would be much more user friendly.

However, I doubt that this is possible.
The Lemur framerate is about 14 Milliseconds, which are to big steps for a tight clock and even worse, the framerate also depends on how much work is to calculate, which in a second step make the clock unstable during high load.
I think I meanwhile understand why JM chose that 14 Millisecond framerate, as I discoverd by experimenting in max that the Midiprotocol itself seems to have serious problems in sending continiuos Controller information with lower framerates: each time I send Midisignals with framerates less than 14ms my Mididriver crashes [sic], so it seems not to be a Lemur problem more a Midi problem. I guess if e.g. a Multiball send every 5ms the Mididriver will also crash...it is just too fast and too many data for that old protocol.
So the point should be to devide between an internal framerate for calculation and an framerate for sending Midi from Lemurobjects. And this will be no simple changes....
just my thoughts about the problem, not sure, maybe I am wrong... but I find it interesting that I discovered that same border in max like the framerate on Lemur.

But please, Liine, proove me wrong

cheers
mat

Softcore · Post by **Softcore** » 16 Feb 2014 22:31

Very informative Mat! Thanks for sharing!

Post by **Macciza** » 16 Feb 2014 22:38

I think they have been looking into a tighter midi rate ~ 1ms clock rate
Not sure where it got to and when'll if it will be released

electrofux · Post by **electrofux** » 17 Feb 2014 13:28

Macciza wrote:I think they have been looking into a tighter midi rate ~ 1ms clock rate
Not sure where it got to and when'll if it will be released

this would also make the timing better in case of Lemur being Midi Clock slave, does it?

This would be so overly great. All those nice arpeggiators, sequencers and other timing relevant templates would finallly work without any additional app needed.

Need more Lemur memory

Liine Forum

Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock

Re: Good Midi Clock