Mac Studio Sequoia 15.3.2 | Logic 11.1.2 | Scaler3 Control 1.0.2.40304e4
OVERVIEW
In Performance Mode I’m able to play notes polyphonically, but when changing notes if there is any overlap then some notes won’t play and the performance stops.
Also, if MIDI is looped, even if fully quantised, the Performance won’t play properly.
EDIT: Please note, I’m using Scaler3 Control (as MIDI FX) with a synth in my instrument slot (old style!), and perhaps this is not the recommended way now. Also, the failure for the MIDI performance pattern to play happens on any looped section. So, if my MIDI is on Bar 3, and I’m looping bar 3 → bar 4 it will also fail to play)
P.S. Also, quick request … can you make it possible to copy the version number from the plugin going forward, rather than having to type it out manually?
Yes i’m having the same issue in Live with the VST. Latch Is not working and if i want to play something with a performance, everytime i change note, the playback stops.
It doesn’t happen in the standalone, so i’m using the standalone, sending midi out into Live with new midi output options.
Same problem here on Windows 11. This renders Scaler 3 unusable. Have they confirmed this to be a bug? Don’t recall this being an issue in earlier versions.
Hi @nuggetz and @RobFuture and if it still occurring for you @EricJames
Can you folks please give me some exact steps to follow as I am using a live note input with performance and latch on and switching notes no problem. I have DAW Sync off in this instance.
OK this is strange as I can’t replicate this. You can see in the attached video I have Latch and Follow working perfect with Performances in Ableton Live and Third Party VSTs. Maybe this is a Windows thing? @Tristan Can you please have a play on Windows and see if you can reproduce? Only possible thing I can think of is somehow in Windows, Scaler 3 is receiving some kind of MIDI Loop / Local On - Note On / Off twice but that is the only other extenuating circumstance I can think of.
Grazie Davide!
I think that for sure is some gift from Windows, but this is only happening with the VST (2 or 3).
Standalone works as expected.
For this reason i’m using the standalone sending midi in Live.
I’m on the 25h2 that has MIDI 2.0, i have had some issues with the registry, but now it seems that everything is ok.
I have another issue that will drive you crazy (), but i’ll do a thread tonorrow.
Hi @RobFuture. Thank you for uploading the video. We have been able to reproduce the issues you are experiencing (latch not working and motions stopping when playing legato) using Scaler 3.2 on Windows 11, but only when using certain DAW hosts including Ableton Live. Strangely these issues do not seem to occur when using Scaler 3.2 as a plugin in other hosts on Windows such as Reaper and Bitwig.
Regardless we believe this issue has been addressed by the development team and the fix will be included in an upcoming Scaler 3 update, as these issues are no longer occurring in our internal test build of Scaler 3.
@Tristan@davide thank you, i think that the new Windows midi needs a bit of attention because they are changing things day by day.
Can i ask to check this other issue i’m having?
The new Scaler 3.2 standalone reload the latest project and the latest settings when opened again.The issue that i’m having comes with the settings files: if i close Scaler with a performance enabled, when i open it again, the performance “box/check mark” starts to blink, activating and deactivating the performance. At this point Scaler is unusable and the only way to have it back is to close it from task manager and delete all the settings files. It happens only on the performance tab. Humanize/keylock/voice grouping works as expected. If you plan another beta test, i’m here to check it!
Hi @EricJames thanks for the update. Yes we are able to reproduce this and it does appear to be a different issue than the Windows specific issue described above. A very similar issue is being investigated for the next Scaler 3 update where motions are occasionally not triggered properly depending on the MIDI note placement so we will take your notes here onboard here and keep you posted. Thanks again.
Hi @RobFuture. Yes the blinking behaviour you are seeing has also been recently reported and is on the list to be addressed in a coming update. In our experience, this can be temporarily resolved by toggling the global motion on and off a few times. Would you mind trying this if you encounter it again? Hopefully will save you from having to close the program.
Got it @EricJames and thanks for taking the time to repost this. We’ve had a look and concluded what the issue may be and will get our dev team to have a look. S2 did the same things but just delayed the note rather than cut it off but then we have found each DAW behaving differently. Will investigate now we have some good info.
), but i’ll do a thread tonorrow.