I thought: Now I understand it! Now I know how Scaler 3 works! And I even achieved results. A great program. I have an idea of what’s possible. And that’s incredible! But suddenly Scaler 3 decides on its own which chords it wants to play and which not. That’s a bit frustrating… I thought it was because I imported MIDI files. But wrong: Even when I build a chord progression from scratch, some chords suddenly aren’t played. Are these the “overlapping chords”? I really hope this will be fixed with the next update… Because I would love to continue working with Scaler 3 now that I finally understand it…
What I would generally find great is if the workspace for the chords were larger. I don’t just build 4 chords but whole songs – and then it becomes quite detailed.
Hi @Heinrich-R would you be able to supply an example of Scaler 3 not playing some chords? This isn’t an issue I’m aware of. If you’re able to post a video of this occurring that would be very helpful. You may have to host the video on a cloud service e.g. Google Drive and post a link here.
Just an idea because I already answered similar questions on this forum: Do the chords that don’t play have different color, a bit darker (muted chords)? Like these which I pointed with arrows.
Thanks @Heinrich-R, my apologies, this had not occurred to me when reading your earlier post. There was indeed a bug discovered in Scaler 3 v1.0.7 creating these kinds of playback issues in certain time signatures including 6/8. I don’t believe this was an issue in 3/4 in case that is an option for your current song to temporarily improve reliability.
Regardless this has been resolved in the upcoming Scaler 3.1 update which is being released next week, June 24. Apologies for the inconvenience.
