I’m really trying to understand the logic of Scaler 3, but I keep running into weird issues that take me back to Scaler 2 and this forum, and I’d really rather not do either. Why can I not edit the last two chords of this progression?
if I select any of the chords before these 2, I can change all the values as normal.
Hi @MrBlueSky. You’re saying that when you select one of the last two chords on your main track, their sidebar parameters e.g. octave, inversion etc, disappear?
This is not something I’ve encountered. There are some edge cases we’ve discovered where sidebar parameters may not appear with multiple chords selected, but these are rare cases and never occur with only one chord selected.
Could you please make sure you have updated Scaler 3 to v1.0.7? If so, would you mind sharing your Scaler 3 preset or Studio One project file here so we can take a look?
Yes exactly this. Look at the left side panel under main track, it’s completely empty when I select the Bmin and the Cmaj(no5), velocity is gone too. I have been updated to 1.0.7. Since it’s release. How would you like me to deliver the preset? I won’t be able to send it until tomorrow.
Thanks @MrBlueSky. You may be able to upload preset or project files here if you compress to a zip file first. Otherwise is there a cloud location you can upload to and link here? You can DM me this link if you’d prefer.
Scaler 3 is now crashing in standalone mode every time i try to drag select all the chords on the arranger page. DMing you preset now.
update: i’ve isolated the crashing issue to a specific vst im using.
update 2: nope its not a specific vst. just tried with felt piano internal and its crashing again.
running latest version
update 3: also crashes when I drag select the chords in cubase
Thanks @MrBlueSky yes I see the issue with the chords missing sidebar parameters. This is not something I’ve ever encountered before so we’re not sure what the cause is. There are some obscure scenarios potentially leading to chords with unusual behaviour which are being resolved in the upcoming 3.1 update. Also the ability to edit chord notes with voice grouping enabled is being removed from an upcoming update as this can lead to issues.
If you do experience this again with other chords, it would be very helpful if you could let us know any preceding steps leading to the crash i.e. where the chord was taken from and any edits that have been performed on it.
There have been similar reports from users and we believe this has been resolved in the upcoming 3.1 update. When I open your preset file in the current 1.0.7 build of Scaler 3 I do get a crash when selecting the main track chords, but this does not happen in our latest test build. So this should be resolved for you when the 3.1 update is released.
I’ve been having similar things happening with selecting multiple chords and the editing bar missing within the daw (I don’t use the standalone much). Studio one 6 on windows 11. So looking forward to the 3.1 update.
I rarely use standalone mode. I just used it for testing the sidebar issue and to grab the preset to send to Tristan. I hope 3.1 makes scaler 3 useable for me.
Thanks Tristan. It’s going to be disappointing if disabling chord editing when auto voice leading is enabled locks me out in the same way enabling voicing does in scaler 2. I was excited when this feature was announced as it was a selling point for me.
Im not a power user. I mostly use scaler 3 at its most basic level because I currently don’t find it to be very user friendly. I also keep encountering bugs and features that I always hope are bugs (no being able to change main track pad velocity and extract voicing but no apply voicing come to mind). The best help I can give you regarding the preceding steps leading to the crashes are that I used scaler 3 as intended. I say this because to the best of my knowledge, i just dragged chords to the main track and this happened. I don’t remember if I edited them. I’m going to assume I didn’t because I couldn’t.
@MrBlueSky just to clarify, auto voice leading should not be affected. Just global voice grouping (button above the keyboard) is what I was referring to as this acts as a realtime layer on top of the chords which interferes with note editing. But we are also exploring other solutions.
This is still possible either via the circle of fifths page or the arrange page midi editor. Unless I’m misunderstanding you.
Extracted voicings can currently be applied to individual chords via the voicing menu in the arrange page MIDI editor, but this is also being added to the right click menu in an upcoming update.
SO Happy to hear that about auto voice leading and right click apply voicing.
regarding section c aka main track velocity. I’m writing this from memory so I’ll have to confirm if I’m wrong later but I’ve tried to change the velocity level in scaler UI velocity in settings and it makes no change to how hard the velocity is in section C aka main track on the browse and create pages. Previewing chords in section c is so loud it distorts my monitors and I can’t seem to figure out how to fix it so I try not to press those pads. In scaler 2, all the velocity levels are the same.
Hi Tristan, after confirming things on my end, i don’t think you’re misunderstanding me but I’m still trying to understand why Scaler 3 won’t let me change the main track section c velocity universally and set my choice of velocity as the default? I can’t use the section c main track pads in the browse or the create section. the sound is so loud that it distorts my monitors and hurts my ears and i dont want to have to reach for the volume knob every time i preview a chord. i know you could tell me to set my scaler ui velocity for the a and b pads to match the c pad and turn my main volume down but then in cubase that messes with my set volume levels. you suggested that i can change the velocity in the circle of fifths section but it only seems to be for individual notes, which is time consuming and impractical. i get that its likely easy to fix if im using Scaler 3 in standalone mode but i’m not and never will. I’ve asked about this before and i didn’t understand the logic then and its still a problem now. This seems so bizarre to me. am i missing something here? i really don’t want to come on this forum and bitch and moan but i just dont get it and i want it to be user error so i can enjoy my experience with Scaler 3.
look at this.
on the circle of fifths page i have velocity selected on “show on keyboard”, velocity is set to 20
just to confirm, this is a new issue. i don’t know if its a bug, or if it is related to my problem. i would still like a solution or even a workaround to matching the velocity of Main Track (C) to Current Scale (B) and Chord Set (A) in my DAW (cubase). its unworkable as it currently is.
Following with great interest! I too have struggled with the differences heard across the various sections. I thought this was fixed with some of the recent releases but now appears to be back with the current RC3.1.0
Default Velocity appears to behave as expected in 3.1 in that It retains default velocity everywhere.
man i really hope so. thanks!
