Hi-Gain tones unusable
-
@zes735 yikes that first half was indeed not a desired pleasant distortion - that is strangely familiar to the issue on the mobile platform when trying to use sample rates other than 44.1 khz (the exact sound I get at 48 and 96) but i have not had this issue on the desktop version on any sample rates.
The 2nd part of the clip sounds just fine - very curious these issues
-
@tafkad I've tried adjusting sample rates (and buffer rates) to 48k and 96k/64 respectively, but nothing helped. This definitely sounds like a massive aliasing issue to me, but for the life of me, I can't figure out why.
Another problem I've noticed is that when I tried Amp Matching a Preamp I have, the sound produces the same issue, and the actual Amp Matching is pretty awful. It could be that it's the preamp itself, but realistically, I don't think Bias Amp likes my computer very much.
My relevant computer specs are:
- 16gb RAM
- Windows 10 x64
Thanks for your input. I'm gonna go for a clean reinstall and see if it makes a difference.
-
I realize this thread is probably dead, but I'm wondering if anyone else has run into this issue or found a fix?
Support has stopped responding to me and hasn't advised if it's a known issue/if it's being looked into/etc. No update is disheartening, so I thought I'd turn here.
-
From the OP it says you are having issues with Tonecloud presets... why not just dial your own?
Sample rate conversion is only really an issue for Amp matches in my experience. A lot of times amp matches don't translate well from rig to rig, etc, anyway. I usually try to do my own or avoid them unless they sound really good when they demo. 90% of other people's presets are not going to sound good on your rig.
BTW, at one point I had issues with sample rate conversion between Bias Amp Matches I had shot myself and importing those into FX on the desktop but PG got it sorted... they actually delivered several development releases for me to test. It was a pain because I had to wipe and restore my presets over and over. It was worth it though because, yes, these conversion issues do sound terrible, and I have not seen any recurrence.
FWIW, those presets saved with the old, wrecked, version were permanently altered (because they got converted badly) you may be running into some of this on old tone cloud presets. I had some up there I had to delete because I was saving them to the cloud to transfer them to mobile and did not even realize they had been trashed in the process.
Amp matching is a really super cool feature but it is a double edged sword.
-
@zes735 Same happens to me. I tried some tones by DMO (https://www.youtube.com/watch?v=J_7WqdbABQ4) with the demo, all with amp match, and they didn't sound at all like in his videos, and all sounded the same between them, so I thought i had to import the "amp match" amplifier apart or something, so I entered here searching for how to do it. But I had downloaded one of his amp matches, the DMO Far beyond Driven, and the Bias FX2 corresponing sound still sounded like the rest; a harsh random distorsion. I thought maybe as I had the demo version I didn't had the amp model used in the amp match, but then I'd prefer the program to tell me "you lack this amp". Anyway, you can substitute with an amp and fiddle with it but not the same, of course. I imagine a solution is to create your own amp match with BIAS AMP 2 and then substituting it in the BIAS FX2 downloaded preset.
-
@smasher193 When you dial down gain down, does your low string sound like total garbage too?
-
@zappabain I'm unaware of any solution other than new audio hardware or a new computer, as I believe this is an Aliasing issue that I can't find a logical explanation for. I can't even use Bias Amp's IR Cab loader with other IR WAVs because it produces the exact same issue (high pitched distortion). I've never had an issue with any other IR impulse loader.
As far as I'm aware, all Cab IR samples I'm working with were recorded in 44.1khz, and I have to assume that though Amp Matches could be across multiple sample rates, AT LEAST one that I've tried has to be at 44.1khz. All my sessions are recorded at 44.1khz, and when I attempted changing session sample rates and using Bias Amp 2, the same problems persisted. It's aliasing without care for sample rates!
Support stopped emailing me back and I've even asked "so is this ticket just going to die or can someone help?" to no response. I'm extremely disappointed and don't think I'll be buying future Positive Grid plugins based on the lack of care/communication/support for this issue. Though it may plague a small number of users, it's a key feature as to why I bought Bias Amp 2, as my goal was to have consistent sound at the click of a button across in-studio mixes using my actual tube amps.
Very disheartening. I'm only providing this response because I know that anyone else having this issue is probably lurking forums looking for a solution, as I do often with music gear.
-
@zappabain In the oddest twist of fate, another user on this forum solved this problem for me but has received no recognition. Shout out to @Daniel-Cairney who 5 months ago in this thread posted: https://forum.positivegrid.com/topic/2478/rotten-sound-amps-and-guitar-profiler-flstudio
"General grunge and bad distortion on amps, cabs, guitar profiler. Edit plugin/processing and switch to fixed buffers. Sounds awesome just like it should"
In FL Studio, there's a setting called "Use Fixed Buffers" which essentially encourages plugin latency but is made to specifically troubleshoot plugins that aren't properly functioning. As soon as I engaged this, the Amp Matches worked for the first time ever.
I don't know if there are similar settings in other DAWs, but to me, this confirms it's a latency-related issue. I do still believe that based on the digital noise, it's also aliasing, but there's got to be something in the buffer size that can be a work around.
Best of luck, all.
-
@zes735 Yes, turn on the buggy plugins switch despite the dire warning. works great.