Likely a sign the underlying model runs at 24kHz
1 Like
Exactly.
I definitely believe Robin will fix this issue immediately.
Here? At SL?
No response means two things:
- we are working on it
or - the functionality is by design
And this is where having overly minimal owners manual instructions rears its ugly head. If the documentation fully explained the designs, there would be fewer questions and confusion about the intended design and whether user experiences functionality validate or question said designs.
I’m more inclined towards the extra 2GB in the v12 installer containing some half-baked or poorly integrated de-mixing models from external sources. Any problems with those models land at the feet of the developer who integrates them into the application.
1 Like
Hi, sorry I cannot read and respond as frequently as I used to here but I eventually read all comments.
Regarding the 12kHz cut, this has been improved in the upcoming patch 2, which goes up to 16kHz and above depending on the type of recording.
6 Likes
@Robin_Lobel Thank you very much!
Thanks Robin!
I’m currently trialling SL12 12.0.10 build423
I’m just now testing SL12 against my SL11 workflow.
I can confirm on Win10 22H2 with CPU processing that SL12 Unmix Noisy Speech moves all freqs above 12900Hz to the noise layer in my (single) test of unmixing a lavalier mic location recording.
SL11 sends all freqs above 21900Hz to the noise layer.
1 Like
hmmmm, in further discussions with others about this LPF behaviour in SL12, I’ve realized we can be yielding a somewhat unbalanced unmix if speech components remain in the unmixed (wanted) noise. From the Film & Broadcast perspective, post prod can easily be outputting ambience which is often left in the mix to retain “air” / “ambience” along with reducing the perception of artefacts.