SpectraLayers 12.0.10 Maintenance Update

Maybe…SE comes with Cubase Pro, so some of us got a ‘taste’ from that.

It’s normal with Steinberg for demo keys to come out a few releases later (somewhere in the .2 or .3 range). Sometimes it might even be possible that clicking on the link for the last version demo key might end up putting the newest one in your account instead. It’s worth a try.

Room to crit that policy, love it or hate it, it’s been that way with Steinberg stuff for years. People have complained for years, but it hasn’t changed a thing. It’s the way they roll. They have a million reasons ‘why’ (for better or worse).

They seem to try to stick to a release schedule of sorts. The ‘schedule’ is not disclosed to the public, but the staff knows what it is. The bosses lay out the assignments, set release dates, etc. The marketing and server people get ready for it. The sales and stuff are in motion months before they actually happen. That keeps the ‘money machine’ rolling, so the ‘staff’ can ‘collect their salary’. So, when those big dates hit, chances are they’re going to throw ‘something’ up there come hell or high water!

It helps keep those late sales in the ‘grace period’ for a free upgrade. There’s no promise it’ll work out that way, and it can sometimes be hard to anticipate such things, but…I’m kind of glad 12 came out at the time it did, despite the early release flaws. Why? I just got on board with SL 11 this summer in a 40% off sale. Had they waited, that first release would have missed the grace period for that last big sale they ran. I don’t know how many users this helped out, but I’m glad that I got a key for 12 inside the grace period! If it’s a month or two before it outperforms version 11 for me, oh well, at least I don’t have to pony up $90 bucks to move into 12. Right?

Old heads have learned over the years…
The first few releases often have issues. So if you’re not in a mood to mess with that wait a few months. If you do go ahead and take the upgrade keep the older version around. Run some tests with the new one before going mission critical with it.

Some wait a bit (.4 releases and higher) and watch the release notes in SDA to upgrade.

No, I don’t think upgrades get a ‘grace period’ to skip a cycle of payment. That only counts for full product licenses. Some users just prefer to get their hands on a demo key first, or simply to start with a more stable release.

Once you’ve bought into a product, it all shakes out for the same price whether you adopt early, or give it some time to simmer.

For better or worse, it is what it is. I have no problem with people advocating for a different kind of release model. Thing is, I’ve dealt with many dozens of software companies over a lifetime, and none of them are perfect. They all have their own quirks, and a ‘price’ to stay up to date.

It is what it is. We old heads have just learned to weigh out if the product and workflow is worth it to stay on board. The answer is usually yes. It is what it is, about all we can do is ‘accept it’ and get out the wallet, or freeze the system and use it as-is till we find some better road.

I don’t mind paying a bit from time to time. It usually shakes out to an average of around $50 per year per title (some exceptions of course). It’s competitive enough pricing I think, as I’ve dabbled in the upgrade and subscription models of MANY products over the years.

Bottom line, if the company has no revenue stream, then the programmers eventually have no job, and we get ‘no software/support at all’.

2 Likes

I made the following observation:

  1. Have a Layer and use “Crop”

  1. Deselect everything (left mouseclick elsewhere)

  1. “Select All”

  1. Move the whole selected stuff

There remains a residue, which I consider as another bug.

Rhetorical question: Is there any complex function in this program, that works 100% as expected?

Suggestion: Take four people to rigorously test the program for 2 weeks (10 days at 8 hours each), pay everyone 3000,-€ for the time, in total 12.000,-€. Afterwards fix all found issues (there are lots of them) and have an almost bugfree program .

We need SL and I consider this program as an absolute conceptual masterpiece. But its technical realisation is, sadly said, the opposite. The codebasis has grown over the years and it might have become some kind of a clusterf*ck. (This, I can tell from own experiance…it just happens. If methods, functions, modules, etc. are not completely independent, sooner or later one runs into programming trouble. And this is what it looks like. I might be in error with my judgement, of course, but than, how would one explain all those bugs and glitches?) Just because a program looks good, has a lot of options and stands as state of the art of operations, does not mean necessarily, that it is technically a good program. There are lots of eye- and ear-candy here, but it needs to be a reliable work horse, also.
Yes, I am tired of finding so many glitches in this program. Those glitches are like drops of ugly oel in pure, sweet and (very very) best drinking water. You get the idea.

Of course,

but “for a few people” ( including me :wink: ) this may have been the major reason to buy it.

If there is a software that has ONE function I need I´ll buy it, the 1035 other features may be of no interest.

1 Like

@Brian_Roland thanks for the vetran run down, much appreciated

I did edit my post to better say what I meant to say…I’ve only been at SB for a year after spending the past 25 years with other DAW makers

let me just clarify that I’m not complaining about any SB product other than the SDA, which I still feel is messy or needs better documentation…and I’m certainly not complaining about SL as can be seen all over this board

1 Like

Sunnyman, hi. Looking at your Window’s Task Manager readout, you are using a higher percetage of GPU than I am. (I have an 8G AMD card and I’m only able to use 3.1G of my GPU while you’re using 7.5 of 12G. Which is to say you should be getting much better/faster results than I am, and, also that you must be getting faster result than you were in SL 12.00? What’s happening here is pretty much matching what I saw in SL 11. Is this true for you, too? I also have 64G of memory but here I only use 22%. I’m wondering why SL 12.01 is using 30% of your memory? Also you’re on ethernet, I’m on wifi, but why is your ethernet connection so busy when you’re using SL?

1 Like

Ok, not long ago, I lamented about the gui. It needs lots of improvvement.

Here is the one glitch, that I find most annoying all the time using SL.

  1. Have some lyers

  2. Now click on “s”

  3. Now fast click back on “m” → NOTHING HAPPENS !!! THIS IS SO ANNOYING !!!

  4. Move the mouse outside the “m” and click again, it’s working

Please fix this! There is definetely something wrong with the event handling here!
It’s just not acceptable - period!
Maybe, it’s just one line of code with the eventhandling.

Thx!

(The tons of “!” just show how annoying this is)

I just expect the buttons to work as expected - without any delay or nonfunctioning or what not. Just make the gui work 100% flawless.

“s” → 1 left click
“m” → 2 left clicks
Any logic in this?

How often did you create event handlers?

I complained about this 10 months ago

I’m used to it now

but I use layers :stuck_out_tongue_winking_eye:

Seriously, I’m working on audio using SL…and SL does things no other software that I know of does

the way the mutes and solos are designed to function in SL is a bit different than a DAW…so it took some teething

Personally, I’ll live the the little issues of dbl-lft-clicking…or a click that doesn’t respond until the 2nd or 3rd click to enjoy the incredible functionalities SL does allow

and really, Marc @Sunnyman if you are going to lean on this one issue, then maybe add to my old thread or start a function specific one…because your mute/ solo issue is here has become quite specifically digressed

It’ definetely not meant as a digression. It’s one of the basic functions in the gui, that are used all the time.
Those kind of bugs make the program feel like an unfinished quick’n dirty toolbox of the developer and the customer, who paid for this, is a beta tester or guinea pig. And no, I am not here to use SL on a journey with the developer (as someone else said this, also in the buggy context) to discover ever new unfinshed features. The basic features must work 100%, reliable and without any odd side effects. Once the basics settle the grounding, the tower can raise.
Mathematically, the fundamentals here are found in FFT, numerics and massive datahandling. Combine all this with an ingenious concept and there is Spectral Layers. But please fix all fundamentals first. Otherwise, it will turn into some shack, which is not much fun to use in the long run.
And yes, I am picky and not a fan of some sour milk or something with any odd tastes.

Hi!
You might have already done this, but you can try keyboard the shortcut.
Ctrl+Alt→Solo
Ctrl+Alt→Mute

1 Like

Not very often, but the handling of a buttom seems rather standard procedure. Maybe it is meant to find a compromise of both worlds, Mac and Windows? If so, …no good.

So you are developing code in C/C++ or Rust or similar languages?

C# and nothing fancy. C++… 30 years ago as a student.

C# was released 2002

True.

Ok, to bring this to an end… a one line event handler does not exist. Including all the side effects that need to be watched this is more than just typing some fancy event code line.

Why handle “m” and “s” with obviously two different events?
Just use a them like an on/off switch .
Don’t overcomplicate things.
Just stay rigorously easy peasy.

I tried the SL11 demo and GPU support was great, and as you pointed out, not “experimental”. I expected SL12 to also include GPU support, which I think is a fair expectation, given that zero GPU support in a newer version would be a step back.

Steinberg knew what they were doing.

I’m a happy Steinberg customer and have not tried to refund the product or contact Steinberg via official support channels as I know the risks of purchasing newly released software. But it is entirely fair for others to criticise this major release version 12, and I do not understand how you can so strongly defend Steinberg while also admitting GPU support has been available for years. This is only more reason for Steinberg to have announced before or on release of the product that GPU support is either broken or removed.

If they switched AI models and GPU support is not ready yet but the outcome is better, then great, there is nothing wrong with that. But it should have been stated, and I think this is where people are feeling a little let down in terms of communication and expectations.

2 Likes

It does, the issue is you say it doesn’t work on your hardware. I believe this has been acknowledged but if you have any doubt that this will be addressed, then you should log your issue with Steinberg support, if you haven’t already done so.

The fact that it worked on SL11 might be very useful for the developers to know. The best way to let them know is to log the issue via Steinberg support.

There’s this in the release notes:
image