Hello,
I really loved working with Scaler 2 as a Starting-point for my productions.
The Features I used the most are Midi Capture and Drag to get the Midi-Data into my DAW.
There is a midi capture option when you click record however its not capturing the timing or rythim etc its simply draging the progression in. Its not capturing my performance at all
So for some reason its not acurately capturing my timing. Its just draging them in as if i was selecting the main track itself and draging them in rather than capturing my rythm and timing…are there any internal settings i may need to change or something of that nature? It seems to be some sort of quantization issue of some sort…based on what i can see of the video you posted im doing it corectly. Choosing midi capture/press record…as it blinks play your progression…stop record button snd the drag logo blinks indication chords have been captured and are ready to drag… i drag it in and the timing and duration is not even close…
It has to be a bug or somehting…how can I get this issue fixed…do i need to wait for an update or is there a waybfor a remote session etc. This is killing my creative workflow
Ok, I’m not in front of Logic right now, but it looks like MIDI capture only records the performance at 120 BPM, no matter what BPM is set in the DAW or whether sync is enabled in Scaler…
For example, if you set Logic to 40 BPM, add an arpeggiator, and try to capture the MIDI, the result will be at 120 BPM, whether Scaler’s sync to DAW is on or off.
…I didn’t have time to dig into it, so I just fixed it using Scaler 2
You can see how the single note midi on the actual Scaler track is the timing i played and the midi info under it is what i midi capture i draged in…look at the begining and end of the notes and how they dont line up
And all quantize settings are off in my daw which is studio One..my snap to grid is also disabled. No quantize on in the perfomances section of scaler 3 either…
Yeah, it did the same for me, so I used an instance of Scaler 2.
Just out of curiosity, what BPM is the track?
If it’s different from 120, try setting it to 120 BPM and see what happens.
For me, it works fine at 120 BPM, but if it’s different, it goes out of sync…
BPM 100 I mean i gues i can do it on scaler 2 and then detect midi with scaler 3 in order to continue the song buildout using the arrangemt capabilities scaler 3 offers but i really hate to add a step to the creative process while trying to get ideas out you wana work fast ya know. Thanks Pinzer
Yeah i have faith that they will. Its a really great product and company its early in the release of the product im sure they will work the bugs out soon… everything else is amazing though they nailed it other than the midi capture bug
@Wes@Pinzer Nice work and apologies there. No one spotted that in our beta testing, artists network or internal team!
MIDI Capture seems to be capturing at 120 irrespective of tempo. I am sure this is an easy fix for 3.1. Stay tuned and thank you…