I have tried to search if anyone else has posted this bug but I could’t find it.
One of the wonderful and from a musical creation perspective most basic and obviously essential functions is for the user to be able to edit any chord in anyway he she or it pleases so that it fits into the song.
Control click on a chord opens the Create Page where you can then choose which notes are in and out of the selected chord. That is great but when re-opening Scaler 3, the modified chord notes are not returned to Section C Main Track until the binding is refreshed from Main Track to Current Scale and back again.
Has anyone else notice this “refresh” bug when editing individual chords and then playing back the next session?
Hi @beport Chord Editing works fine for me. It immediately stores it. Could you please provide exact steps for us to try and reproduce what you are doing. Also could you please ensure you are using the latest version - 3.2.
Thanks, Davide. Yes 3.2 and no, I am not able to reproduce this glitch on a regular basis. I have, however, started saving patches on a more regular basis. This is essential to avoid losing settings and progressions in Scaler. I have a feeling that the bug is linked to audio interface switches in Logic. Switching speaker/headphone outputs caused Scaler plugins to completely re-initialise. Unfortunately, I don’t think I was hallucinating either.
Searching Lumo returned the following: When you switch the I/O device, Logic tears down the current Audio‑Unit graph and rebuilds it with the new driver. During that rebuild every AU plug‑in is re‑instantiated, which means any plug‑in that keeps its state only in RAM will lose the settings it had for the current session. Scaler 3 stores its last‑used parameters in memory (it writes a preset only when you explicitly save one), so when Logic reloads the plug‑in after an interface change it falls back to its default state and the chords / scale settings you were working with disappear.
Evidence – Users have reported that “Logic resets all plug‑ins back to default” whenever they change the audio output device, and that the problem is reproduced with Scaler 3 as well.
Hi @beport That’s not right. We’d all be going crazy if plug-ins were initialised on audio engine switches. I change audio devices in logic all the time and Scaler 3 (and all other plugins) retains its state fine. Can you try switching your Audio Buffer size and Apply to see whether that reinitialises state? Process of elimination.
