Capture Midi is not working!

I am wanting to use Capture MIDI to record live performances, which is what is intended to do correct? Except it is way off from the original playing. I have a loom video showcasing this: Loom Message - 11 April 2025 | Loom

I also have a ChatGPT chat trying to troubleshoot the process if you need to see here: ChatGPT - Scaler 3 Logic Pro Help

I essentially was trying to figure out how to capture live automation with Scaler 3 capture midi. And I figured it out, only if Capture MIDI was capturing MIDI on time. this product literally wastes my time instead of helping me save time making music because of the bugs.

1 Like

Hi @beatssparks welcome to the forum. Sorry hear you are having trouble with Scaler 3. There is a bug which is currently being addressed regarding the tempo of MIDI Capture, which is currently fixed to 120 bpm. This may be what is causing your frustrations.

We have this error logged in the known issues page, and do plan to have it resolved in the upcoming Scaler 3.1 update due later this month. Apologies for the inconvenience.

You can confirm if this is the bug you are experiencing by setting your tempo to 120 bpm and seeing if the MIDI Capture results look correct.

1 Like

In Studio One 7 (current update), I am getting the same error. improper import no matter what the BPI is. I tried 120, I tried faster and I tried slower. Midi Detect is broken. I made sure both my DAW and Scaler showed 120. Waiting for the update. Will notice be sent out?

1 Like

ok please keep me posted Tristan because this is very much needed. makes product unusable

Capture midi is broken regardless of 120. So far having Scaler 3 since day one it’s all been bugs and I’ve been going back to Scaler 2 and have yet to be able to do anything with Scaler 3. :frowning:
Detect Midi seems to work, but that’s one chord at a time. Went back to Scaler 2 capture.
This is with updating to the new 3.0.1

The typical speed of Techno and House… :thinking:
A mere accident?

its been 8 days. any update on an update or fix or did i just buy a broken product? scaler 2 also has bugs too and support is abysmal.

Hi @beatssparks If you look back at Tristan’s message you will see the update is planned for end of April. No need for the duplicate post and please no comments that can be seen as offensive and rude to people trying to help you personally. That won’t be tolerated here. Happy Easter.

Hi. I am using Scaler 3 within Logic Pro 11.1.2. I’ve recorded midi using the key bind function in Scaler. That works. The recording was made in time
with Logics metronome. To playback in time I’ve found that I have to quantise the recorded track. If I then copy the track (after capturing the midi) to another track in order to use another instrument, the midi notes of the copied track are late by one beat. The late notes begin after bar 4. Prior to bar 4 all notes are in time. Quantising the track to the same value as the original track doesn’t solve the problem. It is necessary to manually move the out of time notes.
I’ve been messing for hours creating music, but unable to successfully apply it to Logic Pro. It’s quite frustrating. Scaler 3 has been useful for finding chords etc, but the process of transferring the data into Logic Pro is a problem.
Perhaps this is a known issue. I did look but didn’t find anything.
Any help would be appreciated.
Thank you.

Welcome to the forum @whippet This is fixed and due in an update next week v1.0.6. There’s a list of known issues here.

Next week?? The waiting :flushed_face::flushed_face: