Thank you for fixing “Last-Chord Extension edge cases fixed in Main Track”. Just tried it & works like a charm now!
2 Likes
Since the 3.1 update I can’t change the motion on a track at all??
It seems the only motion that can be changed is the arpeggio.
Really hope this gets fixed soon, it worked on the previous version.
Hi Steven,
I’m new here, so I apologize if my question is redundant. How do I go about installing the new version of scaler? Do I need to uninstall the 3v 1.0.6. version before installing the new version?
No, just install 3.1; you do not need to uninstall it.
Note: It is a 1GB download, meaning you still need to download the built-in sounds. However, you can skip reinstalling them by unticking the sounds box during installation.
1 Like
Ok, after spending some time with it, other than the fact I can’t really find use for the arrange page in my workflow (no fault of Scaler 3), I’d say you guys have hit the mark! Until I find a bug or something I have no real issues! Great job Scaler team; I am back to starting my projects with Scaler first.
The only small thing I’d like to point out is I wish Chord Detection worked more like Scaler 2. As is, if you record a chord progression with a melody on top for example, Scaler 3 will settle with whatever the last note played is to establish the chord it keeps. In Scaler 2 it records and keeps each chord change the melody’s notes create. This was a big part of my workflow as sometimes I already have a good progression/melody going and I just need Scaler to point me in different direction creatively. This even affects what scales it recommends at times so, while not exactly the end of the world, I do think it is important.
I’m attaching an image to explain what I mean; For the chord progression shown it’s not that serious but once I start getting into more complex/uncommon melodies and chords that’s when this starts to factor in a bit more. I hope I am explaining this clearly.
Edit - Yeah I just tested this theory out again with something more complex; I started a chord progression with Scaler 3 in E Minor with a melody on top in key. Running it back through both Scaler 2 and 3 chord detection, 2 recognizes that it is in E Minor and recommends the right scales, 3 however thinks it’s in C Lydian because of this issue. As is, this is unfortunate and still has me going back to Scaler 2 for proper detection. Not being able to expound on my own midi/chord progressions and melodies because of this means Scaler 3 can only serve as a starting point for now; which is a bummer.
Again though, you guys are killing it; Thank you guys for the swift improvements and patience with the community!
2 Likes
Ok, very nice. Scaler is now a real tool and think that most folks will find, that like S2, it is a tool that belongs in your tool box for a long time. Great job to bring out the update for those of us who use and need your program. Thanks.
1 Like
@Steven Hey, I’m not tagging you trying to bug you, so apologies in advance, but I noticed you liked my comment and I made a couple edits to it that add to what I am referring to. I think this is something important to consider.
edit - wait I forgot E Minor and C Lydian is relative but I still think it should list E Minor first like Scaler 2 because in certain contexts it matters. They definitely function differently (like soloing for example). In the current scale window you have to scroll quite a bit (I’m talking past every C scale) to find and make the E Minor connection after the fact. To me that’s just wrong. In Scaler 2 C Lydian is number 3 on the list after detection.
1 Like
Hi @daddy_cool123, welcome to the forum! As Musicalman mentioned, there’s no need to uninstall the previous version — just download the Mac or Windows installer and double-click it to begin the installation. Once installed, we recommend rebooting your machine. You should then be good to go. Enjoy!
ok ill download the manual again thanks
I guess my concerns were worth a response!
1 Like
Hi @dshidoesit. We’re always curious to hear of scenarios where detection in Scaler 3 produces different results to Scaler 2. I’m not sure I understand what you’re saying about melodies influencing the detection. I would expect melodies to potentially throw off the detection as it is expecting chords, but the results should be the same in both S2 and S3.
If you have an example of a detection source you can share with us we’d be interested to investigate what is happening differently in Scaler 3.
1 Like
Hi @dshidoesit. Your concerns are most certainly worth a response, I just wanted to discuss with Tristan first before coming back to you. I do realise it may have seemed like I was ignoring you since I replied to others – my apologies for that. Cheers.
1 Like
This isn’t ideal I agree. Scaler 3 replaces the chord for a shared note between chords rather than adding it. We’ve got plenty of things on our list to work on but the next few months we are going to focus on three main things:
- MIDI and Audio Detection efficacy and workflow
- Creating Scenes in the Arrange Page to help with writing sections, copying, pasting editing etc
- User Track and ability to record Keys Lock and potentially Chord Triggers straight into Scaler 3
Thanks for the feedback it’s exactly the thing that motivates us.
1 Like
Thanks for the response Tristan! Here is a video link to what I am referring to:
Davide seems to have a good understanding of what I am talking about as well based on his message. Thank you also davide!
I just have to say again I love Scaler 3 and all that you guys do. Thank you.
Hi @Tim1. Thanks for your post. The selector is available for Articulations, as well as Rhythms and Performances, but not for most Expressions. We’re investigating this and have added it to the list of known issues.
Workaround for now:
Split the clip – subsequent clips will display the selector, which you can then extend as needed.
Cheers.
Thanks very much Steven, your tip to split/cut and then change motion works a treat!
I think that the Motions in the Arrange Page are such a powerful amazing feature. Do you think that in future all the motions on a track will be freely available to mix and match, rather than being greyed out?
You’re welcome, Tim! Yep, in the future we’d like to support changing the motion type after one has been selected. Each type has its own set of modifiers in the sidebar, which is the main reason the others are currently greyed out once you’ve made a selection. This thread includes a good discussion on the topic, along with a handy tip/workaround from Davide that might help in the meantime. Cheers.