Hello, I have been using Scaler for many years. Scaler3 was released and I tried it . 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.
But、Click the play button twice quickly to hear the first chord.
I think this is a bug. I would like to solve it.
For this reason, I often use Scaler 2.
The other day,I tried clean reinstall.
following steps:
Mac – Clean Install:
Delete the standalone state file in this folder: /Users/[NAME]/Library/Application Support/Scaler 3.settings
Delete the personalised files in this folder: /Users/[NAME]/Library/Scaler Music/Scaler 3
Delete the shared user files in this folder: /Users/Shared/Scaler Music/Scaler 3
Reinstall using latest installer
But,the problem did not improve.
However, when I changed one setting, the first sound started to play even before looping.
I changed the settings by clicking the three lines in the upper right corner of the Scaler 3 screen, and the Sync To Daw item was set to On by defaults, but when I changed it to Off, the problem improved. I think the Sync To Daw setting is related to the connection with the Daw, but will changing this setting have no effect on other processes?
I would like to know if anyone knows what it is.
see you.
Hello davide from Plugin Boutique.
I installed latest Scaler 3 1.0.6. I tried to solve the current problem right away. However, it did not improve the problem. The only thing I did was, as I wrote before, click the three lines in the upper right corner of Scaler 3 and change the “Sync To Daw” setting from On to Off.
This did improve the problem for now, but will it affect other processes?
And what kind of setting is this “Sync To Daw” setting?
However, as a result, the support team mentioned that this Sync To Daw setting is precisely about integration with the Daw, so it hasn’t been resolved.
Hi @hiro sorry to say we’re still unable to reproduce your issue using Scaler 3 v1.0.6 in Ableton Live 12 on Mac OS. Perhaps you could upload your Ableton Live Set file here and we can try to see if there is something we are missing.
I have looked into Ableton Live.
My current version is 11, specifically Live 11 Standard Version 11.3.42.
This means I haven’t upgraded.
Perhaps this might be affecting things.
It might be the timing of the first midi note in the measure. I have noticed that in Logic, I have to extend the region a bit before the measure to get the first measure to play since moving to 1.0.6.
I prefer to use the Chord Set arrangement function (section A) and use midi notes to trigger those chords. However, when using the loop cycle function in Logic, the first midi note doesn’t get triggered. I’ve messed around with all the preferences, and have the current update, but this problem still persists.
As I mentioned before, my current version is 11, specifically Live 11 standard version 11.3.42.
I’ve currently asked the same question to Scaler Music support.
The support response seems to indicate that many Live 11 users are having this issue.
don’t you just love it when support people are like, “well, our car doesn’t have a flat tire, only your car. so since our car doesn’t have flat tire, we won’t address this.”
Reaper Win user here, so I don’t know your DAWs, but this looks like a little bit as a muted chord.
Just a question - is it a bit darker than other chords? Try to Shift + left click on it to togglemute/unmute. Does anything change?
Because this problem does not exist in Reaper so it is not generalized.
I just want to be sure that someone did not press Shift + left mouse click while on that first chord. A screen shot might help, though.
Apologies for any miscommunication here. This is not an issue that has been reported by any Ableton Live 11 or 12 users as far as I am aware. Excluding yourself of course.
As mentioned earlier, if you are able to upload an Ableton Live Set Set/Project file here which exhibits this error, we can see if we can reproduce your issue, as there may be other settings either in Ableton Live or Scaler 3 that we are not taking into account.