Hey man, I may have had the same experience tonight with the immediately “bricks Reaper and crashes.” This is the steps I went through to get it working:
First, I tried opening it in Bitwig – and it didn’t work there, either. That means it wasn’t a Reaper problem for me.
The version that didn’t work for me was from Plugin Boutique. So I uninstalled it and rebooted. Then I redeemed my license for Scaler 3 from Scalermusic.com.
Then I installed same as I did before, but this time I DIDN’T scan VST plugins.
When it finished installing, it ran fine in Reaper, as expected.
So what’s different? I switched from the Plugin Boutique version to the ScalerMusic version (different enough that they have a different label in the uninstall)… And I didn’t scan VST plugins this time.
I don’t know which of those two changes made the difference, but it’s working great for me now. So maybe try uninstalling and reinstalling, this time without VST and see if that works. And if that doesn’t work, try switching from the PiB version to ScalerMusic version and see if that does it.
If you use different versions, be sure to use the add/remove programs and reboot between installations. Good luck, this new version is cool.
I wasn’t sure where to post this, so here you go.
DAW: Bitwig 5.3.2
Frequently, while the track is playing and I’m experimenting with the Scaler 3 mixer—adjusting arpeggios or adding new chords to the arrangement—the program crashes, causing me to lose any progress I’ve made. This has happened numerous times now.
I’ve been using custom VSTs each time this has happened.
Detect audio try’s to cook your CPU at any buffer rate with Studio One detecting chords from audio. The cpu meter max’s out when trying to detect audio in the FX version, your fans ramp up and so does your cpu temps. The DAW locks up as does the play head, you have to force quit or remove the plugin to stop your CPU and fans hitting max settings. It can bairly handle 1024 samples on my RME, forget anything under that it will simply lock up and send your cpu and fans into over drive. Dangerous to say the least.
Close friend says it’s crashing both Ableton and Cubase just opening Scaler 3.
The standalone is cutting GUI’s off. Also why Windows audio, why not detect and link to my RME interface.
Why no automation parameter sync or options from inserts or Instruments out to the DAW? It’s set and forget or nothing unless you stick to the old V2 system or use midi out if your DAW has it.
That’s about all I noticed so far going through it over the phone with a friend using Ableton Cubase Reason and Studio One.
It’s usless to me at this stage I will stick to V2 till it’s updated.
I’ve been trying to get it to crash whilst using the Arrange window in Scaler 3.
So far if I am using Scaler 3 stock sounds and playing with arpeggios and adding chords, the program works as intended. (I am only using 3 tracks in Scaler 3)
Once I introduce outside VSTs into Scaler 3 it seems to cause issues.
The crashes only happen when the DAW Play is running and I am making on-the-fly changes in the Arrange window of Scaler 3. (adding chords, changing arpeggio performance etc.)
Once Scaler 3 has crashed the audio of the DAW is completely effected. There is a minor layer of distortion over everything, almost as if the ASIO buffer settings have been made too low, but not quite the same sound. There is some definite sound degradation caused by the Scaler 3 crash.
Closing the DAW and starting from scratch fixes the sound issues so far.
Running Reaper and crashed out after trying to adjust midi in Scaler 3.
I was really looking forward to this new upgrade.
However, experiencing issues 15 minutes into starting a track is a real bummer.
That being said, I’ve been using Scaler 2 for years and I have faith these bugs will be sorted.
Here’s an interesting little bug, but also quite annoying.
When I load a third-party VST into Scaler 3, the mouse wheel functionality for scrolling through preset menus of that particular VST doesn’t work at all. I have to resort to left clicking and dragging the vertical scroll bar in the VST I am using.
Not a deal breaker by any means, but very annoying nonetheless.
I’ve tried this with a couple of different plugins such as Arturia Pigments, VPS Avenger and even presets in a VST Compressor.
Scrolling through their preset menus when they’re added to Scaler 3 simply doesn’t work.