Scaler 3

[TimC340]

I didn't have Scaler 2. I do have Scaler 3 and, while I find it quite interesting if I've got some (a lot of...) time to waste, it's not user-friendly at all! And I find it bizarre that a modern piece of software doesn't auto-update - or at least give you the option. Scaler 3 doesn't even tell you that an update is available.

Their forums are not a happy place - bit like Studio One just recently!

 

[TheMaartian]

Scaler 3 doesn't even tell you that an update is available.

Which reminded me to go look. And, yes, there's a v3.1.3 update available for my v3.1.2 install. Maybe the forthcoming v3.2 update will have an option for using the v2 workflow? Just aimless, wishful thinking.

 

[Vocalpoint]

Which reminded me to go look. And, yes, there's a v3.1.3 update available for my v3.1.2 install. Maybe the forthcoming v3.2 update will have an option for using the v2 workflow? Just aimless, wishful thinking.

v3.1.3 is installed here - there is no going back. In this one or any other future release.

If a v2 workflow is your thing - you will need to stay in v2.9.1 - which is also the last version of v2 as well.

VP

 

[TimC340]

Which reminded me to go look. And, yes, there's a v3.1.3 update available for my v3.1.2 install. Maybe the forthcoming v3.2 update will have an option for using the v2 workflow? Just aimless, wishful thinking.

I just thought I'd follow up on this in case I'd missed anything. There was a thread in 'Feature Requests' asking for at least update notification. This was given short shrift, and the poster was told to bookmark the 'Scaler 3 Latest Version' thread in some other part of the forum. I got the impression that the developer regarded notifying users of an update via the program itself was unacceptable in some way. The forum itself is a bit of an unnavigable mess, so maybe he is not great with organisation!

 

[Vocalpoint]

I got the impression that the developer regarded notifying users of an update via the program itself was unacceptable in some way. The forum itself is a bit of an unnavigable mess, so maybe he is not great with organisation!

I have had several offline chats with the crew over there and yes - they have been overwhelmed by a lack of attention to detail, poor testing across a variety of DAWS and a general sense of trying to do too much too fast.

They have issued at least a dozen versions of the app since this time last year - and while it is starting to take shape - the issues continue to persist.

I have been fighting several instances of Studio One 7 placing Scaler 3.1.2 AND 3.1.3 on the blacklist - which is not something I have seen in years.

Which tells me that these guys are cutting corners somewhere - at least on PC - where it is critical for Studio One use - to code your stuff according to the very latest VST3 SDK specs as stated by Steinberg.

Anytime I have seen a plugin go directly on the blacklist - is a clear sign that during the S1 plugin scan - something is not right and that usually means not up to spec.

VP

 

[TimC340]

I haven't had it blacklisted, though I've only just updated from 3.0.7 (I think) to 3.1.3. I just reloaded S1 and it seems happy enough with the new version.

 

[Vocalpoint]

I haven't had it blacklisted, though I've only just updated from 3.0.7 (I think) to 3.1.3. I just reloaded S1 and it seems happy enough with the new version.

One day back in early August I loaded 3.1.2 and all was well for about two weeks. Then suddenly one day - out of the blue - it's blacklisted.

Took me about three "plugin DB" rebuilds to get it to behave and then it happened again - so I gave up. Chatted with the crew at Scaler and they sent me a pre-release of the v3.1.3 final.

I install it but this time - instead of the actual Scaler3.vst3 getting banned - I get the ScalerAudio.vst3 getting blacklisted. Again with the rebuilds - and it is now finally "working".

But my trust is not absolute right now with this thing.

VP

 

[madFloyd]

What I'd want is to have a much more immediate way to change and test out inversions, additions etc. Currently, it's really not slick for that.

Exactly.

 

[JBMusic]

I'm glad I kept 2 on my system. It's easier to work with. I bought the tutorial video but I didn't get around to watching it yet.

JB

 

[ananmusatili]

Exactly.

I'll correct myself. It is actually much easier in 3 than 2. It's just the amount of new functionality and completely different workflow that makes it less obvious. You can directly do it in the Circle of fifths page per chord.

That being said, it does have bugs, and getting the right sound is not as straightforward, because manual edit of chord notes isn't proper. At least for me, it doesn't work fluently.