Hello, I have been using Scaler for many years. Scaler3 was released and I tried it yesterday. However, I encountered a bug.
I will now explain the bug situation.
Start Scaler3 with Ableton Live. Create 4 chords of my choice, separated by 2 bars. It is an 8 bar chord progression.
Defined as 1st to 4th.
Play it. The first chord does not sound. Daw is set to loop, and the first sound does sound when once it goes around it. The first sound does not sound when I first start playing. I think this is a bug. I would like to solve it.
I have experienced a similar situation in Studio One. I got around the issue by putting an empty bar in the DAW timeline prior to the start of the chords. I think Scaler needs some time to process the first chord. I assume this will be addressed in a future release. This appears to work in Ableton as well by putting the start marker at -1 for the clip. Not a very practical solution for Ableton since it is loop based but it does demonstrate the issue.
I’ve got the same issue in FL Studio!
When I record a progression in the MPC software and stop and start it the first chord doesn’t play but does after it loops and when i bounce the track the first chord doesn’t bounce. Anyone else have this issue?
Same issue for me as well.
I have not yet used Scaler3 for the second time since the first time I used it. Scaler3 has been significantly improved and upgraded, and I think it will not disappoint. However, I find myself spoiled during production because of this problem, so I naturally find myself using Scaler2.
I also experience this in Bitwig Studio. It’s a major bug which I hope will be fixed in the next update as Scaler 3 isn’t enjoyable to use in this state (rendered FLACs etc also contain the bug). If I’m not mistaken, it isn’t on the list of known issues. @davide, please add it.