Using Axe-Fx III and Sonarworks Reference 4

[laxu]

For those of us who would like to give a try capturing it, what was the issue with the files? Was it just not deconvolved or what?

 

[jin1995x]

Thanks for this. I feel like I'm doing everything correctly, but it's still not working. These are the two files - sine sweep, and sine sweep bounced down in Logic through Sonarworks. It doesn't seem like Voxengo is generating a proper IR. If anyone with Voxengo can give these files a try, I'd appreciate it!

Sweep:
https://www.dropbox.com/s/xnx8kr3u4ff8yvs/Sweep-48000-24-SLR-10.0s.wav?dl=0

Sweep through Sonarworks:
https://www.dropbox.com/s/lfqahm780716pa3/Sine_Sweep_HD650_SW.wav?dl=0

For those of us who would like to give a try capturing it, what was the issue with the files? Was it just not deconvolved or what?

Something is wrong above your file when i deconvolved the above two files and tried to transfer the resulting file to my cab block my axe edit crashed and has some usb errors repeated it same results.

So i did the process myself using voxengo and sonarworks in reaper for hd650 curve., and my file is working.

I think there is some issue with your sine wave. , or its something unknown to us altogether

i Use a 3 second test tone gen by voxengo, add sonarworks correction insert on track, export the resultant file ,extract and deconvolve the two files in voxengo and copy to cab block. and it works

pming you the file.

 

[jaycal6]

Thanks @jin1995x ! That file worked, too.

 

[Fotukito]

FYI I've managed to create IRs for the Axe to match my custom SonarWorks SoundID calibrations (speakers and headphones) using the convenient 'Impulse Response Utility' that comes with Logic Pro X. It required putting my RME audio interface in 'loopback' mode during sweeep recordings, but it avoided the need to run a Windows app like voxengo.

I've loaded the IRs as L/R pairs in a Cab block just before the Output block as @DLC86 had suggested; very nice! Why: when I'm messing with presets, playing, and monitoring while recording, my Axe output goes directly to a shared analog mixer driving room monitors and headphones (and not through the computer). Therefore the IRs in Axe are useful so that these 'direct' Axe tones now sound the same as recorded Axe tones played back by the DAW through SoundID calibrations. Critical? Nah!, but good geeky fun. (I just have to remember to bypass that compensation pad when recording!)

(If someone else has a similar Mac setup and objectives, let me know and I can post my 'cookbook' on the IR capture steps involved.)

 

[toneseeker911]

FYI I've managed to create IRs for the Axe to match my custom SonarWorks SoundID calibrations (speakers and headphones) using the convenient 'Impulse Response Utility' that comes with Logic Pro X. It required putting my RME audio interface in 'loopback' mode during sweeep recordings, but it avoided the need to run a Windows app like voxengo.

I've loaded the IRs as L/R pairs in a Cab block just before the Output block as @DLC86 had suggested; very nice! Why: when I'm messing with presets, playing, and monitoring while recording, my Axe output goes directly to a shared analog mixer driving room monitors and headphones (and not through the computer). Therefore the IRs in Axe are useful so that these 'direct' Axe tones now sound the same as recorded Axe tones played back by the DAW through SoundID calibrations. Critical? Nah!, but good geeky fun. (I just have to remember to bypass that compensation pad when recording!)

(If someone else has a similar Mac setup and objectives, let me know and I can post my 'cookbook' on the IR capture steps involved.)

I’m trying to do the same thing with my calibrated HD650. I am not able to get a good capture file. Do you mind sharing the steps to do this ?

 

[Fotukito]

I’m trying to do the same thing with my calibrated HD650. I am not able to get a good capture file. Do you mind sharing the steps to do this ?

Here's what worked for me, documented as a pdf....

 

[jaycal6]

Here's what worked for me, documented as a pdf....

Tried this, but it looks like my impulse responses ended up with about .05 seconds of silence at the beginning. Not sure if that’s some kind of latency in the loopback system or what. I’m using UAD Apollo on a Mac.

 

[Fotukito]

Tried this, but it looks like my impulse responses ended up with about .05 seconds of silence at the beginning. Not sure if that’s some kind of latency in the loopback system or what. I’m using UAD Apollo on a Mac.

I think you can safely trim off that initial flat region at the start of the IR. I don't recall how much of this region was present in the waveform before I trimmed it, but in the final result I see that I retained about 39 samples before the initial spike in the IR. (Probably best to edit the L & R to equal start/end sample ranges.)

 

[toneseeker911]

Here's what worked for me, documented as a pdf....

Thank you for that. Got the IRs finally.

 

[Steven Persson]

Here's what worked for me, documented as a pdf....

Do you have to use the IR in the cab block?

Can it be put into an IR-block last in the Axe-chain? Having it in a IR block is what I do now with Auto EQ-IR:s for my headphone type because I use every channel in my cab block for my guitar sound.

 

[laxu]

Do you have to use the IR in the cab block?

Can it be put into an IR-block last in the Axe-chain? Having it in a IR block is what I do now with Auto EQ-IR:s for my headphone type because I use every channel in my cab block for my guitar sound.

Yes you can use the IR Player block instead, it's almost perfect for this purpose. I use each of the channels for a different output device (e.g studio monitors, a few sets of headphones).

I wish we could make the IR Player block a global block or set it up for scene ignore so you can set it up for your current output device easier.

 

[Fotukito]

Yes you can use the IR Player block instead... []

I hadn't noticed that the IR Player was enhanced to support two IRs as of firmware v17... nice! (IR Player was previously 'mono', which is why I'd been using a Cab.) I updated my pdf description in my post #66 above to reflect that better approach.

 

[GlennO]

I wish we could make the IR Player block a global block or set it up for scene ignore so you can set it up for your current output device easier.

I share the same wish. Global (in the way the Global EQ is global...it's not a block in the grid at all) AND apply to both the grid output and playback audio.

 

[Fotukito]

Yes you can use the IR Player block instead, it's almost perfect for this purpose. I use each of the channels for a different output device (e.g studio monitors, a few sets of headphones).

I wish we could make the IR Player block a global block or set it up for scene ignore so you can set it up for your current output device easier.

Hmmm... good point about no Scene Ignore on the IR Player. That's a good enough reason for me to stick with using the Cab for now.

If it was 'global' outside of the grid, I'd be concerned about CPU; that might tip some of my presets into the red, whereas managing it as a block in the grid allows me to avoid it for CPU-heavy presets.

 

[Sven Talbot]

Fotukito...that PDF is precisely what I was looking for. Great explanation. Worked perfectly. Thanks! I used Cubase on a Windows machine to achieve the same result, so there were a couple of misfires on my first go or two as there were a couple of Cubase parameters I had overlooked, but got there in the end! Thanks again!