Amp match - Tips for generating of a good amp match

  • This thread is for questions and tips on matching amps the best way.
    Tip: Here you can find a thread with ressources for downloading tones to match them.

    It is also welcome, to list good suggestions out of the help-files, as the infos seem to be fragmented there.

  • When I've done amp matching in the past I've always played the same thing through the amp being matched, and bias. Is it necessary to do it this way or will it work just fine strumming a few chords even if it's different to what's in the recordings used for the match?

  • @liam Unfortunately this is noting I can answer, but I am pretty sure it will lead to better matches, if you play something in the same ballpark, frequency-wise. So try to keep the riff as close as possible or maybe use the same strings and frets.

  • @sascha-ballweg I'm curious if anyone has used a wave audio file that's less than 20 seconds (bias needs a minimum of 20 seconds I think?) Maybe I'll have to create a file that contains the same sample played twice to get the length...sounds doable.

  • @anthony-newcomb Exact! Just loop it twice

  • @sascha-ballweg said in Amp match - Tips for generating of a good amp match:

    @anthony-newcomb Exact! Just loop it twice

    Yeah I was in the middle of experimenting when I typed that last comment so I was kinda thinking out loud (hence me answering myself lol). I've found some good material on SoundCloud but the wave files are less than 20 seconds on average. I'm using logic to quickly make the extended versions now and will start the amp match process tomorrow. I've never used the amp match feature in Bias v1, but with v2 the audio clip matching process seems pretty straight forward

  • @anthony-newcomb I never used it myself before but now I have already matched one chanel of my prefered tube-amp, the Ampete Two (which is at 1800 USD, just the head). I will post a tone-comparison and my amp-match in the next days. Seems to be real fun to play with the amp match feature :)

  • You typically want to try to replicate all manner of tonal capture from the guitar. So you'll want to play high notes, low notes, full chords, power chords, octaves, palm mutes, etc.

    Separately, don't be afraid to try things that might not be possible. For example, I recorded a Dual Dark with two mics (one on cone and one angled). I blended the two mics together and bounced to a wav file. I used the bounced wav as my Amp Match source, and the application did it's best to match that tone as if it was a single amp source and really did a great job of mimicking the tone.

    If you have two heads/cabs, try bouncing them together and let Amp Match try to find some close way of matching those tones. It doesn't hurt to try, even if it doesn't seem like it'll be possible with a single channel amp.

  • @danbieranowski Yeah that makes total sense to me. An amp tone file that originally used dual mics should not be an issue when using the file for audio file amp matching. The end result of using two mics for an audio file is just "one tone" as long as the mics are blended to both right and left channels in the rendered source file...or even better, mono. Unless the different mics share separate channels in the audio file's stereo field, Bias should see/read the sum (mix) as if they were one, not the individual mics. Probably stating the obvious here...

    I see effects and natural room reverberations being an issue, not combined mic tones.

  • I prefer to convert the source-Audio file to mono, independently of what Bias Amp renders in the match process.

    The reason for that is, that I like to hear the source as plain as possible, when it comes to fine-tuning the matched preset by some tweaks.