Depuis une mise a jour Windows 11 Pro (fin mars), je rencontre des difficultés avec Scaler 3 (v 3.2.2) sur reaper (v7.69).
Buffer Asio à 512 et Scaler 3 en VST 3
Lorsque je place des accords et que je vais dans la page arrange pour les mettre en boucle :
- Si je lance la lecture depuis Scaler, les accords sont lus correctement et la boucle se fait entièrement
- Si je lance la lecture depuis reaper, certains accords sont survolés mais les notes midi non déclenchées.
Du coup, pour contourner ce problème, je suis obligé de faire un « drag and drop » des accords pour les insérer dans la piste reaper ou Scaler3 est ouvert, chose que je n’avais pas à faire auparavant.
Certains utilisateurs rencontrent-ils le même soucis et auraient-ils trouvé une solution ?
Je n’ai pas remarqué ce problème dans mon système.
Si ce n’est pas le cas, pourriez-vous essayer avec les instruments internes de Scaler et nous faire savoir?
Auriez-vous le fichier .rpp dans lequel cela se passe? Le cas échéant, pourriez-vous me l’envoyer, de préférence avec les instruments internes pour avoir les mêmes conditions?
Comme cela risque d’intéresser d’autres usagers et l’équipe technique de Scaler, il serait préférable que vous utilisez l’anglais.
Thank you for taking the time to look into my issue.
I initially tried to reply earlier, but my English is quite limited, so I hesitated and ended up deleting my first message. I’ll try again now with the help of ChatGPT.
This synchronization issue appeared suddenly, even though I didn’t change any settings. It happens both with Scaler’s internal instruments and with my external plugins.
I’ve created a very simple project with only four chords (no effects), using the default “Felt Piano” internal instrument. I am attaching the
In the first loop (DAW sync), the fourth chord (Gmin) does not play AND I do not see its keys on the virtual keyboard (like “erased”). Instead, I see the ones of the previous chord (Fmaj).
In the first loop, Gmin cannot be heard. In the third loop, this happens to Dmin, in the 4th loop it is Fmaj… No exception. Add again, the keys I see while playhead goes over the affected chord are of the previous chord. See video.
Another oddity - no matter what chord I use to replace Gmin, the behavior is the same. But if I inverse Gmin and Fmaj, everything sounds OK, at least for the first few loops.
@Steven, @Tristan Can you chek this please? I have no clue why this happens. Reaper rpp project is in zip file that Paul added.
Thanks @Miki and welcome to the forum @GhiottiPaul. I was not able to replicate this error on macOS, but can replicate this on Windows 11 using the attached Reaper project.
I did find that changing my audio interface’s hardware buffer size e.g. from 128 samples to 256 samples resolved the issue. Or switching driver the from ASIO to WASAPI. Would you mind checking if that also resolves the issue for you?
I’m not sure why this is occurring in the first place so we may need to reach out to the devs to see if there is anything that can be addressed in the next update. I certainly haven’t noticed this occurring in other hosts, and wasn’t even able to replicate this on Reaper unless using the supplied project file.
To further clarify, I am unable to replicate this issue after attempting to create this same scenario in Scaler 3 from a new Reaper project i.e. adding Scaler 3 to a new track, selecting Synthwave 1 chord set, dragging first four chords from D minor scale (D min, E dim, F maj, G min) to the main track and looping four bars.
@GhiottiPaul would you mind clarifying if this occurs after creating a new project in Reaper? It does seem like there is something specific about this Reaper project file which is causing the issue.
This issue occurs every time I create a new project.
I contacted Scaler support about this (we had several exchanges), but they couldn’t find a solution and suggested I ask on specialized forums.
I also tried changing the buffer size (ASIO Topping DX1), but it didn’t change anything, so I went back to 512 samples.
I wonder if this could be related to a setting in Scaler 3 or Reaper that might have changed after the Windows 11 update at the end of March, as I didn’t have this problem before.
For now, if I drag and drop the chords into a Reaper track and loop it, playback works correctly. This allows me to continue working on melodies, basslines, etc., in Scaler 3.
I’m sending the same message to both of you, as you have both been kind enough to take the time to help me with this problem.
Suite à plusieurs heures de tests et de réglages sur Scaler 3 et Reaper avec l’aide d’une IA, nous pensons avoir identifié les causes possibles du problème.
Je vous transmets en pièce jointe le rapport de tests transmis par l’IA.
Hi @GhiottiPaul. Thank you very much for the detailed report. I am able to reproduce this issue in Scaler 3 consistently across macOS and Windows 11, but only when running in either Reaper or FL Studio, and only at 90bpm exactly. No other DAWs e.g. Ableton Live, Studio One etc, appear to be exhibiting this issue. Very strange but we will continue testing. We have forwarded this information to the development team to be addressed in a coming update, So thank again for your report and insight here.