I’d like to report a two part issue related to how octaves behave in Scaler 3 :
The midi of the tracks added in the arranger’s page don’t follow the midi of the main track (some chords are played one octave lower than expected) ;
When activated the voice grouping midi don’t follow the midi of the main track (conversely the same chords are played one octave higher than expected).
See the videos below
It occurs :
in all keys except in C.
both on Windows 10 or 11 ;
on both my computers ;
even after doing a clean install ;
both in Scaler 3 1.0.7 and 3.1.
When considering the scales involved the issue is more severe the more we go from the C# scale (one chord is affected) to the B scale (6 chords are affected – all except the first degree’s chord).
When looking at the octave settings in the Circle of 5’s page all chords affected display by default a « 1 » instead of a « 0 ».
Thank you for taking the time.
PS : I think I understand why the settings display 1 instead of 0 in the Co5’s page on some chords. If needed I can share my thoughts but I don’t want to confuse you any further.
PS 2 : I massively edited the original post for it was really cumbersome and far too long. I hope it’s more to the point now.
Hi @Smeb thank you for the information. There is a lot to take onboard here. We have noticed in some cases the chord follow track can play chords at different octaves compared to the main track. This is something we are looking into. Is that what you are experiencing?
Hi @Tristan Thank you for replying back.
Yes it is what I’m experiencing BUT it happens also :
with “all”* the “articulation” tracks (ie. bass follow track, arpeggio tracks, passages, strumming etc.) ;
with all the “expression” tracks I tried ;
with all the voice groupings (when activated), except for the Cx-By grouping when the chords are D&D from the B section set on octave x (for exemple : C2-B3 and D&D from section B set on octave 2).
When I mean “all”, I didn’t pretend I tried every passages, arpeggios, etc. I picked them randomly and all the ones I tried are affected by the issue.
Hi @Smeb, yes the 3.1.1 update included some very important fixes, but did not address other known issues such as this one. This issue has been lodged and will hopefully be addressed the next Scaler 3 update.
