tubeAmp-Designer icon indicating copy to clipboard operation
tubeAmp-Designer copied to clipboard

Bad profiling on specific sound

Open robinrosenberger opened this issue 4 years ago • 4 comments

First: Thanks for this software, it's really great to have an open source alternative to a Kemper! I have one specific sound in BIAS AMP2 that reliably generates really bad profiles. It's not a serious problem, when I rebuild a similar sound I can't recreate the issue, but maybe its interesting to find out what the problem is in this specific setup. I'll attach a carla-preset for BIAS AMP2, as well as the test signal reply (created by Ardour freeze, worked flawlessly on other sounds) and the resulting profile. issue.zip

robinrosenberger avatar Nov 29 '20 13:11 robinrosenberger

Thank you!

This will help a lot!

olegkapitonov avatar Nov 29 '20 20:11 olegkapitonov

Very high bass level (20 Hz point), middle and treble points seem to be quite normal. And 20 Hz test response signal is very weak. This is why it fails - this BIAS profile doesn't pass 20 Hz bass sound.

I need to fix this case - if test response is too weak, profiler should not process it, and should give reasonable predefined low value for this frequency.

I added the hack and set 20Hz response value manually and get this profile

bad-profile-hacked.tapf.zip

in my opinion, not bad.

I will fix this issue, but I need some time to make sure that this fix will not break other cases.

olegkapitonov avatar Nov 29 '20 21:11 olegkapitonov

Thanks for hacking the profile, although that was not my primary concern ;) I think I added a quite aggressive low-cut on the input which might be the cause, I'll remove that and see what happens, and I will try to force the problem by adding one to an otherwise working setup. If it is the source of the problem I think an error message like "too low bass response" would be enough for a quick fix as well. Or make the default value an option, to avoid breaking the otherwise really impressive profiling?

robinrosenberger avatar Dec 01 '20 17:12 robinrosenberger

Confirmed, adding an EQ cutting the low end on a working setup results in this behaviour

robinrosenberger avatar Dec 05 '20 11:12 robinrosenberger