Ableton Forum

There has been lots of threads on this issue, and i had that problem when i bought 7 too.

Hi

Yeah, I tried djgroovy's suggestion and things seem to be much better. I haven't been able to test fully - I have to work - but it felt better.


Thanks for the fix.


Cheers
Ni

djgroovy wrote:You guys can probably solve that by doing this:

- Go to preferences, midi tab.
- On the midi port for your controller, press the little arrow before the name, so that more parameters expand into view.
- Change the port type from Direct to MME.

I'm getting some "swing" when recording my hardware synth. changing to MME made it tighter but the notes still move back and forth off the grid ever so slightly. not as noticable as before though.

unfortunately this is all new to me. i have a few years using softsynths as my experience. hardware is new so dunno if its my equipment or if its live 7 ? or some setting? or maybe hardware midi is supposed to slide around like that

Hi People

BIG thanks!!!
I did not know about these settings.
Now I have found them.
While, that all is normal.

Thanks DJ for the tips, but Mac uses coreaudio, so we don't have that option to change the driver. Any other mac users out there feelin' me> Thx B

djgroovy wrote:Yes, i bet most if not all of them will be solved... if they only care to read the replies!

im readin the replies but nothing in here is answering my question lol i have ableton 6 can anyone help me? i need help with recording automation send me a message if you know about this & ill tell you my problem thanks

mutual greenhit wrote:

djgroovy wrote:Yes, i bet most if not all of them will be solved... if they only care to read the replies!

im readin the replies but nothing in here is answering my question lol i have ableton 6 can anyone help me? i need help with recording automation send me a message if you know about this & ill tell you my problem thanks

Then you're in the wrong thread.
Lots of topics about recording automation, but basically recording automation in session view is a no-no.

I have also experienced the latency growth. And I can assure you it is dependent on the MIDI interface in use. I have a Dakota, where the growth never occurs, and I have three different Maudio products, all of which show the latency growth. This is all in windows, I can say nothing about OSX.

This is not dependent on the plugin.

Here is what is happening: I believe ableton added a feature to obey the Midi time stamp events that come from the interfaces. Some interfaces fail to implement this and always pass a zero value. These interfaces will appear to show now latency growth... But all midi events will be responded at the very beginning of the next audio buffer, hence the latency is always between one full buffer and two full buffers.

Midi timestamping aims to produce a latency value that is consistently the same amount.

Some other interfaces attempt to implement the timestamps but the timing reference that they use to calculate the values cannot possibly be synchronized to the quartz clock on the audio hardware. It just can't be, there are no wires going from one clock to the other. Who knows what they use as a time reference. So the software implementation of midi timestamping needs to account for this, somehow accounting for whatever time reference is used and deriving a relationship to the audio clock; or otherwise, ableton should discontinue the use of midi timestamping (or otherwise make it selectable by a configuration file)

-Aurelio

I should add, that in my case, the M-audio interfaces I own (Axiom-25, Uno and Trigger finger) are all subject to the midi latency growth.

And that my Dakota is also an audio interface, perhaps this being the reason why it works well (it's midi timestamps may be phase locked to the audio hardware clock) or maybe they (frontier) don't implement midi timestamps.

I am now trying to use the "Port Type" setting to see if the growth problem is solved for me.... so far (about an hour) there's been no growth...

Many Thanks to the member who contributed this workaround.

-arr

It's not really a workaround, it's the solution of the problem.
Setting the port type to MME is the way Live has always behaved until 7.

In this version they added Direct type and made that default, and that is buggy as hell. May i add that in the latest beta and in the next update they've gone back to MME. So you should be fine now.

Hi. I am on a Mac so the answer does not apply for me..It is something that appears to be not even an issue with Ableton..I have seen NO responses from Ableton on this..Yet there appear to be many affected...I hope there is a solution,, the MME thing is not a solution for me..I sure wish it were...But it is not...Nor is it an issue that resides with using M-audio gear..I use the same Axiom 61 with Logic Pro-8 and never have this issue..I am more and more of the opinion that it is a bug in Live...

Believe Me I sure would love for it to be user error on my part..I would be the most delighted idiot on the planet..However,,,I have attempted all I know to no avail...

Here's hoping Ableton will release a comprehensive explanation for this so people can actually use the product...JON

I'm on the MME selections and I still get the problem.

Computers can increasingly drift in audio and MIDI in relation to time turned on. Not just an issue with Live, Cubase, ACID, Sonar all the same. Partially down to o/s background tasks, powersaving or components running hot.

It pays to turn off your computer or at least close down the program and reopen it if you are going to be leaving it running for a while. Resetting asio drivers can sometimes help too.

leedsquietman wrote:Computers can increasingly drift in audio and MIDI in relation to time turned on. Not just an issue with Live, Cubase, ACID, Sonar all the same. Partially down to o/s background tasks, powersaving or components running hot.

It pays to turn off your computer or at least close down the program and reopen it if you are going to be leaving it running for a while. Resetting asio drivers can sometimes help too.

That's not the issue here, because it never happened in Live 5, but it does happen in Live 7.

Thought I'd just say that setting my Triton and Trigger Finger MIDI inputs to MME solved this issue for me. My symptoms were basically that I load up Live - no noticable MIDI latency. Start loading different sets/lessons, the latency would just get gradually bigger and bigger. Closing and reopening Live would always fix the issue, until I opened more sets/VSTs once again, etc.

Live 7.0.2 (same issue with 7.0.1), XP, Focusrite Saffire. Cheers all.