Dear all,
we are happy to announce the immediate availability of SpectraLayers Pro 12 Trial .
With the trial version you can test the application for free for a period of 30 days without limitations.
Try SpectraLayers Pro now for 30 days | Steinberg
All the best,
Luis
2 Likes
wonderful!!! thanks for this
wow, only me so far sayin anything about this!!!..as soon I finish my current scene I gonna try out this trial 
bloody Steinberg installation routines drive me NUTZ!!!
Tried to cover all my bases before install and this moronic SDA has installed SL12 trial on my C drive grrrrrrrrrrrr!!! No , no NO!!! I have pointed the “Target folder” to D/filename and still ugh.
Sorry, Steinberg, you guys have this stuff all wrong. I want to control the destination of my install files. BUT, with the SDA my most common starting point is to uninstall and waste time…sorry, but the SDA is a joke. I will uninstall and install direct from the installer which DLed where I pointed it.
FWIW, the download directory for SDA is to direct where the downloaded components are stored before installation. That has nothing to do with whatever component you’re downloading - which makes sense when you consider that you may want to use the download directory for a large library, but when you install it, you want the library files themselves to follow settings in your library manager.
You can just move the SL executable to your D: drive after it’s installed, right?
2 Likes
FYI the SDA is completely optional (and I rarely use it). You can just download the installers from Downloads | Steinberg
1 Like
Robin, I typically avoid the SDA. That said, I’m running the trial at the moment, so I assumed I had to use the SDA.
Anyway, I’ve got it sorted, but I really do not appreciate the time drain with the SDA…extra messing around that always ends up in wasted time IME
That said, I have just started using CuBase and the SDA design is potentially helpful.
sure…which I did not
I prefer to point things to where I want them to be…I’m the type who never uses a search function…very, very seldom
yeah, for the extensive libraries and/or extension dependency installs, sure…get it set up right. For example my CuBase install is not perfect…and I didn’t reinstall everything and clean up those paths.
The fact is, users have to know how to use the SDA as there are no instructions…it is trial and error. I realize the SDA is pretty simple…but so easy to make a mistake if you aren’t setting it up once a week. Heck, I just set up my Cubase install a week or two ago and still got the paths wrong again today. Really, the “install” option in the SDA just should not be there. I do not find the SDA “idiot proof” at all.
nevermind all that SDA malarkey…on my 2018 build i7 8700K/ 64GB RAM and GeForce 1050Ti Kalmx SL12 unmixed a 6m20s original (prog) rock song
(3pc Lead Vox/backing vox/Bass/1xGtrs/Drums (acoustic set)) in 11 min at SL balanced setting.
The vox, bass and drums sounding pretty good…looking forward to the rest
OK, I’m very impressed, this particular band does suit unmixing really well
The Other layer was surprizingly not filled with much more than some remnants and some backing vox
I haven’t figured out how to get my tool presets or display prefs into SL12 yet tho…
It wasn’t possible so far to transfer presets from one version of SL to the next.
SL12 introduce this feature, but unfortunately it’s only forward compatible.
Meaning you can transfer presets from SL12 to another machine with SL12, or to SL13 next year - but SL10 or SL11 can’t transfer presets to each other or to SL12.
1 Like
So, @Robin_Lobel I realize I’m stating the obvious here
If a slp created in SL11 is opened in SL12 and zero processing done, does that then mean said slp can only now be opened in SL12? I assume that scenario is a recipe for slp corruption?
anyway, SL12 running nice for me so far
No, don’t worry about project compatibility, they remain compatible in all directions.
SL12 is able to read project from SL3, and SL3 can still read projects from SL12 (it will just ignore values such as envelopes or transcriptions which didn’t exist back then). And it’ll remain the same in the future.
1 Like
so far today, SL12 feels more stable than SL11 has felt on my machine
the ability to backtrack on freq selections alone is an enormous efficiency boost
I don’t normally unmix music, but I’ve done a little of that today. I tried unmix song on a live recording of fretless bass, guitar and Roland Octapad where the input is overloaded just enough to make the recording annoying. Also, bass player playing in guitar range and that didn’t unmix very well…the majority of the bass on guitar and other…
oh my, I probably best start another thread for my trial questions…
yes, I’ve been going back and forth between SL12 and SL11 same jobs and I’ve experienced no issues
As I have been saying, I’m just now testing my dialog NR workflow using SL12 against SL11.
Unmix Noisy Speech…results are interestings…sometimes “better” at separating multiple voices in SL12 and yet sending that same “other” voice to the speech layer (that’s understandable). Personally, I could see using both in tandem as in my small sample I found helpful unmixings for my purpose.
Voice remnants still rampant in SL12. What I did was compare unmixed layers with reverse polarity and the differences show. I wouldn’t say SL12 Unmix Noisy Speech was “better” than SL11 as of this writing.
OK, I been working separating two speakers into two mics; one speaker is the main contributor wearing a lav and second voice is in close proximity…on location at a farm on a windy day.
I have two groups:
a group with SL11 unmix noisy speech and another group with SL12 UNS.
I’m working in SL11 because of the “Cut to…” issue;
I’m finding the SL12 UNS much cleaner separation so far. I was working hard at manual tidy up of SL11 and found myself moving along pretty well SL12 group and just staying in that group. Went back to compare and I’m finding superior separation with SL12 UNS. It might just be the section I’m working on…I’ll test that…
a quick note; the 13K LPF of UNS is an issue here in this workflow altho the benefits do outweigh the issue for me