When trying to use the Detect Audio feature it glitches like crazy, basically cutting out the audio. It is eating up the CPU, I ran the performance meter in Reaper and had to stop it after it reached 126%. I’ve never had this problem with version 2, hopefully it will get fixed because I use this feature a lot when I am working in open tunings.
4 Likes
I have the same problem! Even when I set the CPU settings to high priority on both Ableton live 12 and the normal Windows audio.adg handles more power, it STILLS bugs out and says the CPU usage of both scaler 3 plugins is above 400 percent even though looking at task manager, its still very calm and barely takes up even 14 percent of the CPU usage in general for my PC. Please there is a quick patch coming our way that optimizes the plugin with the DAWs we’ve paid for, I seriously want to learn how to use this plugin when ALL of its features can work.
Windows 11 Pro
Ableton Live 12.1
AMD Ryzen 7 3700X 8 core processor
ROG Strix B550-F gaming motherboard (Wi-Fi)
32gb Ram
1 Like
Using Scaler 3 inside Cubase 14 as an instrument on a Windows PC with plenty of power.
When using the Detect Audio with a small 4 second WAV file inserted as an audio track it causes the CPU usage meter to go to max from the moment you press the record button in Scaler 3. The wav file judders and doesn’t play and Scaler does not detect. Have tried changing the audio buffer multiple times to see if that changes anything but doesn’t solve it.
Any ideas or is this a common issue ?
Thanks
Ian
4 Likes
I am so glad you brought this up. I’m having the same exact issues with the same feature on Ableton 12 Live. I thought I was going nuts. No this seems to be a common issue with 3 for some people, someone else had the same problem earlier into the previous week.
2 Likes
Hi @Malivar14 May I just ask, are you using Scaler 3’s Instrument sidechain input or Scaler Audio? We can’t replicate this. @Tristan Can you please check on Ableton and see if you can spot this so we can report?
Hi there. I put Scaler 3 on an instrument track in Cubase. I then put a small wav file on a separate track as an audio track in Cubase. In Scaler 3 I then use the detect audio feature at the top and press the record button on Scaler and play the audio wave in Cubase. It just maxes out Cubase showing a processing overload on both the pc and I’ve just tried it on my Mac. Same issue. Music jumps. Nothing gets detected. Hope this helps. Am I doing it right ??
2 Likes
Hi folks. Just chiming in to say we have confirmed this to be an issue when activating audio detection on Windows. We are seeing smaller spikes with the VST plugin on Mac OS.
Apologies for this, we have lodged the issue and will address it in an upcoming update.
2 Likes
Ahh so that’s what happened. My newly built PC completely slowed down and I thought it was going to crash. Thanks for sharing.
Thank you. I thought I was going nuts. I would like it just better optimized so I don’t have to sacrifice much of the CPU usage when trying to combine it with other synth plugins, machine 3 etc. Seriously appreciate you guys working on it the best yall can.
When trying to use the Detect Audio feature, it glitches like crazy, basically cutting out the audio. It is eating up the CPU. I ran the performance meter in Ableton and had to stop it after it reached 154%. I’ve never had this problem with version 2. Hopefully, it will get fixed because I use this feature often when working within my production workflow. P.S.* I have the same problem as before, even with the small patch update. It made it worse. I press the record button after selecting detect audio, and it spikes up to over 200 percent of the CPU usage.
Same for me in FL Studio 24 with VST3. When the Record button is pressed, CPU goes instantly to 100% (even if no audio clip is playing).
They answered us on another thread im on if you would like to follow it and also tell them too, its with cubase i think but everyone thats had that problem is there and the devs are trying to note it and solve the issue on the next update.
Same here. Cubase 14. Windows 11. Powerhouse computer. Scaler3 Audio Detect absolutely unusable. Chokes and cant guess correctly!
I’m in Cubase 14 Pro, on Windows 11 - everything runs smoothly until I try to Detect Audio using Scaler 3. Not only does it absolutely choke on the first 2 bars, the real-time audio goes in and out as Scaler struggles, and finally, none of the 3 different audio chord loops I tried were correctly recognized (they don’t match the key in the loop’s metadata). Is this feature even ready? Has it been tested in C14 on Windows 11?
I only have one audio track, and it has the 4 bar chord loop. Definitely not overloading Cubase but Scaler 3 Audio is absolutely choking, despite a very powerful desktop workstation.
In Cubase, we thankfully have a workaround: create a chord track and drag the audio loop to it. The chords will be detected immediately without a need for real-time listening by a plugin - would just need to then input the chords manually into Scaler.
I have Windows 11, Cubase 14 Pro, 64 GB DDR4 RAM.
Audio Detection on Scaler 3.0 was impossible! It didn’t work and the system froze.
I upgraded to Scaler 3.0.1 and at first Audio Detection was buggy and wouldn’t perform. However, after deleting all Scaler 2 files from the system and restarting, Audio Dection got better. But still buggy and performs badly.
My temporary solution to the problem was to use VariAudio, available on Cubase 14 Pro, to convert my audio to MIDI. And after that I used Midi Dection in Scaler 3.0.1 to perform the task which performed much better than Audio Dectection. Hoping this will be fixed in Scaler 3.1.
1 Like
BTW we have got this and a fix is coming soon!
4 Likes
I have the same in Ableton.
Std Alone is ok, but why it didn’t have the capability to listen input ?
Detect Audio is not responding, I can’t load the video on here, so just reply to my email, and I will respond back with the video of the problem.
I have a video of the problem, how can I sed it to you?
Will it be in the 1.0.5 update or another one later on? Updated mine towards .5 and still is giving me the same issues. We appreciate all the efforts your including in the plugin, thank you.