Please note that we've been made aware of a scam involving someone impersonating Native Instruments.
Read our community note - here.

M+ standalone optimized Reaktor content from the community

1…1718192123

Comments

  • el-bo
    el-bo Member Posts: 154 Advisor
    edited February 21

    Found Laserbrew. Ends up in aother subfolder for some reason. Just need to work out how to get the images to show

  • Astralbeats_225
    Astralbeats_225 Member Posts: 57 Advisor

    I got it working. I was misunderstanding the instructions. When it says save the preset in Reaktor I was going through the main drop down and saving the preset without hitting the store button in the panel set menu.

  • tetsuneko
    tetsuneko Member Posts: 844 Expert

    Ahh, so you didnt actually end up saving the preset, thereby the NKS mappings were not included with the ens.. guessing this lead to M+ having all the parameter names jumbled?

    Anyways, glad you got it sorted! Just do it a couple times and it becomes a habit, getting stuff working on M+ is a breeze after that

  • Astralbeats_225
    Astralbeats_225 Member Posts: 57 Advisor

    @tetsuneko yes, when I think of saving the preset I always used the drop down menu and "save as preset" option. So when the instructions were saying save that's what I thought it meant. Lol what it really meant was store the preset. Now that I understand the process I'm gonna start building more FX ensembles from scratch. I'm currently working on a saturator and a soft clipper.

    With the saturator I'm either going to have tube, tape and a slightly more aggressive saturation that is switchable or make them all separate FX if I can't get it to work smoothly as a single ensemble

  • djadidai
    djadidai Member Posts: 537 Pro

    Would be nice with a good soft clipper!

  • tetsuneko
    tetsuneko Member Posts: 844 Expert
    edited February 27
    https://community.native-instruments.com/discussion/comment/213508#Comment_213508

    Sounds good. I recommend taking a peep at the Reaktor core library macros, there should be something for saturation/clipping you could whip up together in a relatively short time.

  • tetsuneko
    tetsuneko Member Posts: 844 Expert
    https://community.native-instruments.com/discussion/comment/213683#Comment_213683

    Nice one! I'll give this a whirl during the weekend and will report back

  • ozon
    ozon Member Posts: 1,972 Expert
    https://community.native-instruments.com/discussion/comment/214073#Comment_214073

    Thanks a lot!

    A couple of observations (from someone who's rarely using dedicated clippers):

    • Clip Amount values from 1.0 to 50.0 are an odd choice. Range should probably go from 0.0 (no clipping) to 100.0 (clipping mayhem).
    • Threshold seems behave odd, as there's a huge loudness jump from -0.1 to about -0.5 then an increase until about -12 and from there on a slow decrease in loudness until -100 which is close to -0.1 regarding loudness.
    • It's unclear what the current (fixed) compression ratio is.
    • Maybe controlling the compression ratio would be more understandable than just the knee - which AFAIK is the curvature of the transition into the compression and results in different compression ratios depending on the input level (higher level results in more compression).
    • Maybe a (considerable?) shorter attack would be nice to allow clamping down on transients
    • Maybe it would also be nice to have reduction, not only increase of Gain after clipping, as I found it was easy to make the signal super loud but it was not is to loudness match the unprocessed signal. Could also be me or the somewhat unconventional behavior of the compressor.

    Would be interesting to understand your design choices and also know what other users think.

    PS: If you feel your Ensemble is finished, please also make it available from the Reaktor User Library.

  • Astralbeats_225
    Astralbeats_225 Member Posts: 57 Advisor
    edited March 6
    https://community.native-instruments.com/discussion/comment/214732#Comment_214732

    Thanks for taking the time out to test and provide feedback!

    I'm going to take a look at it tonight. I really was trying to simplify it a bit for the E.U. so I opted for some fixed controls on the comp. This was me Taking a little inspiration from the trs soft clipper but I think you're right about making that modifiable by the End user.

    I'll make the clip amount a 0-100 scale as well. Initially I found around 60 to be where the signal became mangled lol so I backed it back down to 50.

    I'm still new to building FX but have some light experience in DSP so I'm still making mistakes 😁

    Once I've ironed out things I'll definitely post it to the UL. I just wanna make sure it's worthy first!

  • ozon
    ozon Member Posts: 1,972 Expert

    @Astralbeats_225 wrote

    I really was trying to simplify it a bit for the E.U. so I opted for some fixed controls on the comp. This was me Taking a little inspiration from the trs soft clipper but I think you're right about making that modifiable by the End user.

    I think it would be nice to have the additional controls, but maybe you could provide a couple of presets which contain what you consider the most useful settings.

    You could even put the additional controls on the second parameter page, as sort of an "expert panel". But IMO it's unnecessary if all controls (threshold, ratio, attack, release, knee) with proper labels can fit on the first page.

    BTW, does "knee" work as I described above?

    I'll make the clip amount a 0-100 scale as well. Initially I found around 60 to be where the signal became mangled lol so I backed it back down to 50.

    Ok, I understand your intention. But if only the raw values from 0-60 are considered useful for the purpose, then it should still be labelled 0 - 100% in the interface. 100% then is clearly a sonic design choice of whatever value that might be, while 50 is telling the user "there's actually more, but you're missing out". Additionally, I guess the actual clip amount is depending on the input signal level. Thus, a low signal could not be clipped at 50 or 60.

    Thus it might be valuable to have the full range available, but it is up to you to decide whether this is to be considered useful or not.

    Again, thanks for sharing!

  • Astralbeats_225
    Astralbeats_225 Member Posts: 57 Advisor

    @ozon

    "BTW, does "knee" work as I described above?

    Somewhat it's acting as like a ramp to the gain reduction ratio. Mainly it is adjusting the steepness of that ramp leading into the compression ratio. So you can soften or harden the initial bite of the compression while still achieving your ratio. 10 being a long (soft)slope and 0 being short (hard) slope.

    Thanks! You're input has been super helpful I'll keep tweaking it and provide an updated version.

Back To Top

Categories