Issue sending MIDI CC via envelope automation

[miyaru]

viewtopic.php?f=1&t=226782&hilit=+sync

This topic was about the same!

[GdabZ]

Yeah I had this issue before and Ableton support never really managed to figure out what the problem was. They were able to reproduce it on one old machine with the difference that chaning the buffer size didn't affect the behaviour there. Changing the buffer did affect the problem for me. As far as I remember buffer of 512 or above made the problem go away for me. I could reproduce the issue on two different computers with two different interfaces (one running Scope PCI cards and one running Focusrite Sapphire), so it was really strange Ableton couldn't reproduce it or figure out what the issue was.

What did you end up doing? Did you solve the issue?

[GdabZ]

viewtopic.php?f=1&t=226782&hilit=+sync

This topic was about the same!

Yeah I even participed in it!

But you conclude saying "My culprit was the Timepiece AV midi interface I guess", and I don't own that kind of hardware... so the issue is a little more protean, unfortunately.

Maybe we'll succeed in narrowing it!

[miyaru]

PC wise, we are close to each other, though every system can be a bit different.I think the problem is caused by Ableton Live in this case. You PC is fast enough for MIDI of course. The Focusrite ain't the best MIDI interface, but up the job for this. MIDI over USB is capable too.

I will look at my system if clocking is switched on, of not I will test that with clocking......

[GdabZ]

Thanks for your help.

I had the same issue with my previous interface, a RME Babyface, so I don't think it's linked to the audio interface.

Really looks like something is going wrong with the thread in charge of communicating with midi interfaces (if it's threaded). As the issues are more prevalent when I add more automations, and when I keep Live running under other windows (like Chrome).

Simple test :
_ make a simple two tracks project like described (midi/audio) to an external synth
_ add various automations (i.e. cutoff, noise and pitch)
_ play
_ launch Chrome on top (say this forum). And then scroll.

The scrolling affects the quality of the midi transmission a lot, on my computer. (obviously this is not an issue with the scrolling, but more with the midi process or Live main process being muffled in the background).

[miyaru]

I will take your steps, and do the test. I have to install Chrome on my music pc as there are no other software installed than Live, Wavelab and some music applications.

Tonight I won't be able to test, so I do it tomorrow.

Greetz.

[miyaru]

I did found some time to do the test: no problem at all...... On both synths, one usin MIDI over USB (Korg R3) and one over the TIE 1i1o midi interface using midi cables (Korg N1).

Tested it with sync switched on and off, made no difference.....

[GdabZ]

Damn. I must have something that messes up the MIDI that you don't. I'm on a fresh install, I only have a tiny bunch of software installed.

What kind of graphics card do you have? Any special features like Gsync enabled? What's the refresh rate of your monitor?

I'm asking this out of nowhere, I doubt that the Ableton test machine that was able to reproduce the issue has a 144hz monitor with gsync enabled, but... I have to sort this out!

Thanks again for your time!

[miyaru]

I have the simplest of graphics card, with 1 Gb of Ram, I think an Nvidia 210 or 310 with passive cooling, standard 60Hz refresh. Nothing fancy, but that might do the trick.

Have you set up Win 10 the right way?

https://support.focusrite.com/hc/en-gb/ ... Windows-10

https://www.sweetwater.com/sweetcare/ar ... indows-10/

I can not understand that MIDI gives so much trouble as it is such a small data foorprint...... Somewhere the MIDI part of Windows is disrupted, or in Ableton.

[GdabZ]

I tried all that, particularly hoping for "Set processor scheduling to "Background services"" to do the trick. But it didn't.

The best solution I've found for now is to use FL Studio as a VST and send my automations through it. Kinda absurd, isn't it?

[snakedogman]

Yeah I had this issue before and Ableton support never really managed to figure out what the problem was. They were able to reproduce it on one old machine with the difference that chaning the buffer size didn't affect the behaviour there. Changing the buffer did affect the problem for me. As far as I remember buffer of 512 or above made the problem go away for me. I could reproduce the issue on two different computers with two different interfaces (one running Scope PCI cards and one running Focusrite Sapphire), so it was really strange Ableton couldn't reproduce it or figure out what the issue was.

What did you end up doing? Did you solve the issue?

I don't think so. Tbh I haven't had time to make music much since then so I haven't really opened Ableton in a while.

[miyaru]

I have a NVidia GeForce 210 card..... couldn't be simpler.....

[GdabZ]

I tested with disabling gsync, fully uninstalling graphics card driver and preventing windows to reinstall it, running Live in 1024x768 (or whatever resolution Windows runs at when no driver is installed) : same issue. There's no hardware interference with MIDI-USB as FL and Maschine work well.

Thanks for your tests!

[miyaru]

I do remember now that there is a script around the web for Live that thins out the CC stream in a different resolution so that it is easier on the MIDI side of things. Maybe this could work for you, it was a text script for the options.txt.

[GdabZ]

Sorry man, I just sold the whole Live package so I won't be able to make tests anymore. I figured out I'd rather make music instead of tests. Thanks a lot for your time and help.

#micdrop