Sublab Presets -
Using Sublab presets is straightforward. Simply load the plugin into your digital audio workstation (DAW), browse through the preset library, and select a preset that suits your needs. You can then adjust the parameters to customize the sound to your liking.
Sublab presets are pre-configured settings that can be loaded into the plugin to instantly access a wide range of bass sounds. These presets are designed by expert sound engineers and cover a variety of genres, from electronic dance music (EDM) and hip-hop to rock and pop. Each preset is carefully crafted to provide a solid foundation for producers to build upon, with adjustable parameters such as tone, level, and dynamics. sublab presets
Sublab is a powerful plugin developed by XLN Audio, designed to help music producers and sound designers create high-quality, professional-sounding bass sounds. One of the key features that sets Sublab apart is its extensive library of presets, which can be used as a starting point for creating unique and customized bass sounds. Using Sublab presets is straightforward
I can imagine it took quite a while to figure it out.
I’m looking forward to play with the new .net 5/6 build of NDepend. I guess that also took quite some testing to make sure everything was right.
I understand the reasons to pick .net reactor. The UI is indeed very understandable. There are a few things I don’t like about it but in general it’s a good choice.
Thanks for sharing your experience.
Nice write-up and much appreciated.
Very good article. I was questioning myself a lot about the use of obfuscators and have also tried out some of the mentioned, but at the company we don’t use one in the end…
What I am asking myself is when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
At first glance I cannot dissasemble and reconstruct any code from it.
What do you think, do I still need an obfuscator for this szenario?
> when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
Do you mean that you are using .NET Ahead Of Time compilation (AOT)? as explained here:
https://blog.ndepend.com/net-native-aot-explained/
In that case the code is much less decompilable (since there is no more IL Intermediate Language code). But a motivated hacker can still decompile it and see how the code works. However Obfuscator presented here are not concerned with this scenario.
OK. After some thinking and updating my ILSpy to the latest version I found out that ILpy can diassemble and show all sources of an “publish single file” application. (DnSpy can’t by the way…)
So there IS definitifely still the need to obfuscate….
Ok, Btw we compared .NET decompilers available nowadays here: https://blog.ndepend.com/in-the-jungle-of-net-decompilers/