I have uploaded a video of the Neve Portico master Bus Processor in action on drums ;-)

have a listen to see what you think of the new model.

 

Fair enough. But it seems as if at least the highpass and lowpass type frequency loss is caused by the signal chain (or box tone?), not by the compression action. Is there any way to prevent this?

 

This would explain what I saw and heard!

 

Could you try with the drumbreak I provided earlier in this thread?

 

Did you test Proteus-capturing process with various rack gears to come to that conclusion?

 

https://analogxai.company.site/prod...on-Ai-Profiles-for-Proteus-ON-SALE-p576551101

HCL Velvet is now on sale! and these profiles are flying out like hot cakes ;-) Meticulously modelled tube pre amp and tube out put ( 5 stages of modelling) adds low mid girth and a beautiful saturation. See it in action on drums below ;-)

 

let me check this for you now ;-)

 

the loop your using is already very processed and compressed. with this weird reverb long reverb that overlaps the beat, what your probably hearing is residual compression on the basis that the compression never really goes back below the threshold and raises the apparent reverb level that already exist within the loop. i'd suggest to try the profile either on dry drum sand then add the reverb via the normal send return function in your DAW. I hope this helps.

you are hearing the effect of compression on the loop in that it is bring the lows up and reducing the peaks therefore making the reverb element in the loop a lot louder... not ideal

 

Yes. I tried making models of a few different pieces of gear and they all came back with many common and incorrect attributes. I was not able to get Proteus to do compression correctly.

I definitely could experiment further and would welcome other people who claim success to share their process (I used my own input file not the default guitar file). I also haven't tried all the models available but what I have tried seem to have similar issues to the ones I encountered.

 

There's loads of aliasing in Proteus, just do some sine sweeps and check it out for yourself

 

Proteus is plagued by the same profiling engine plague than NAM (using the same tech).
You NEED to run them at 44/48 kHz only.

Oversampling solve nothing : the aliasing is INSIDE the profiling engine.
Changing external sample rate do nothing to the problem.

May be applying a 24dB+/octave high cut filter at 20 kHz could help ...

It seems some random ppl reported IK solved the problem in ToneX by applying an high cut filter, BEFORE profiling engine, during profiling.
Don't know if it is true, but it seems a good way to solve the problem.