Hello.
Everything is in the title.
I have a live set that runs with a stable 20% CPU monitor.
If I switch ON "EXT" the CPU meter instantly goes crazy.
W11pro
Live 12.1.5 (same with 12.1.10b3)
Rme UC / buffer 64 samples
(With 128 or higher, the CpU is still multiplicated by 4 or 5 with no drop out but I have to keep this 64 samples buffer, and, anyway, just reveiving a clock should not create problems ! Isnt it ?
I tried to receive midi clock from an Octatrack mk2/ a Teenage engineering OP xy / an ext clock simulated with maxmsp.
The issue occurs whatever the master is...
I tried to find culprits in the live set with no success.. the more I delete tracks the less the problem is but the cpu is still very higher with EXT on.
Someone has an idea ?
Thank you a lot.
The problem is so important that I just cannot receive clock without massive drop out...
massive CPU spikes and dropout if EXT midi clock IN is enabled.
Re: massive CPU spikes and dropout if EXT midi clock IN is enabled.
mini bump...
3 days I cannot work with my usual buffer size just because Live has to receive a simple midi clock..
Any clue of the culprit ? I am really disappointed.
thank you
3 days I cannot work with my usual buffer size just because Live has to receive a simple midi clock..
Any clue of the culprit ? I am really disappointed.
thank you
Re: massive CPU spikes and dropout if EXT midi clock IN is enabled.
Hello
I still have the issue, but I can reproduce it with empty live_set.
Is there someone to try the steps below and tell me if the problem occurs ?
The problem occurs here with a 64 samples buffer with an RME UC
increasing the buffer makes the problem occuring too, but with less difference between EXT on / EXT off.
-open the default live_set
-copy/paste the 4 empty tracks a lot of time until you have sevrals hundred tracks.
-the CPU here is very low since all tracks are empty
-send a master clock from any gear/program to Live
-click "EXT" ON in the upper left corner (the button is visible after enabled it in live's preferences, you have too to check "sync" in the pref for the input port you receive the clock)
-->CPU goes crazy (but Live is well sync)
-click "EXT" OFF
-->CPU is low as usual with empty tracks
Someone can reproduce ?
thank you a lot !
Julien
I still have the issue, but I can reproduce it with empty live_set.
Is there someone to try the steps below and tell me if the problem occurs ?
The problem occurs here with a 64 samples buffer with an RME UC
increasing the buffer makes the problem occuring too, but with less difference between EXT on / EXT off.
-open the default live_set
-copy/paste the 4 empty tracks a lot of time until you have sevrals hundred tracks.
-the CPU here is very low since all tracks are empty
-send a master clock from any gear/program to Live
-click "EXT" ON in the upper left corner (the button is visible after enabled it in live's preferences, you have too to check "sync" in the pref for the input port you receive the clock)
-->CPU goes crazy (but Live is well sync)
-click "EXT" OFF
-->CPU is low as usual with empty tracks
Someone can reproduce ?
thank you a lot !
Julien
Re: massive CPU spikes and dropout if EXT midi clock IN is enabled.
bump again !
This problem makes me crazy. With my simple set, impossible de sync the set with an external clock without dropout...
win11pro
Beelink SER8 AMD Ryzen™ 7 8845HS 8C/16T
ableton Live 12.1.11 / 12.2b13
RME Fireface UC
This problem makes me crazy. With my simple set, impossible de sync the set with an external clock without dropout...
win11pro
Beelink SER8 AMD Ryzen™ 7 8845HS 8C/16T
ableton Live 12.1.11 / 12.2b13
RME Fireface UC
Re: massive CPU spikes and dropout if EXT midi clock IN is enabled.
Did you open a case with Ableton support?
Mac Studio M2 Max and MacBook Pro M1
Genelec M030; Live 12.2; macOS Sequoia
UAD Apollo Twin
Ableton Push 2
Genelec M030; Live 12.2; macOS Sequoia
UAD Apollo Twin
Ableton Push 2
Re: massive CPU spikes and dropout if EXT midi clock IN is enabled.
Hello,
Of course, since months and after severals generalities, nothing has been proposed. I made them a clear step by step to reproduce the problem, I even dont know if they managed to reproduce it. They told me about errors in a m4l device of the 1st set i sent them, those errors have nothing to do with the issue, since it's reproductible here with a fresh empty default set
Do you manage de reproduce the issue following a default set and a 64 buffer size ?
Thank you to look at my problem
Have a nice day
Of course, since months and after severals generalities, nothing has been proposed. I made them a clear step by step to reproduce the problem, I even dont know if they managed to reproduce it. They told me about errors in a m4l device of the 1st set i sent them, those errors have nothing to do with the issue, since it's reproductible here with a fresh empty default set
Do you manage de reproduce the issue following a default set and a 64 buffer size ?
Thank you to look at my problem
Have a nice day
Re: massive CPU spikes and dropout if EXT midi clock IN is enabled.
Bump.again and again...
The support is useless here, answering me without reading my messages... I am really desappointed.
So sorry to bump again and again this question.
So is there someone who notice that the CPU is multiplicated by 2, 3 or 4 when live is synchronized to an external clock while the buffer is set to 64 samples ? I can reproduce with a default set with hundreds empties tracks.
Without EXT enabled : few percents.
With EXT drop outs more than 100%.
Thank you
The support is useless here, answering me without reading my messages... I am really desappointed.
So sorry to bump again and again this question.
So is there someone who notice that the CPU is multiplicated by 2, 3 or 4 when live is synchronized to an external clock while the buffer is set to 64 samples ? I can reproduce with a default set with hundreds empties tracks.
Without EXT enabled : few percents.
With EXT drop outs more than 100%.
Thank you