Creating IR's from mTurboReverb for use in mConvolution

[Annabanna]

I listed this as one of many questions in another thread, but it's buried beneath a daunting wall of text, and this is the one I need to work out today, so here it is in isolation for easier reading along with a few more specifics:

GOAL:
Alleviate CPU usage by burning IR's from mTurboReverb and using them in mConvolution for the following algorithm with complexity values high enough they would cripple my system otherwise:

rp [ #fa ; #fl ; #fa ; #fh ]



QUESTIONS:
1) If there is only a single LR engine running this algorithm with the modulation panel disabled, am I correct in assuming there is no modulation going on anywhere, so an IR should be able to fully capture this, or is there some other element the IR can't capture (some issue with the "fa"'s for instance, or something about the randomization not always being the same in the feedback loops, perhaps?)

2) I thought I remembered seeing discussion in some tut of capturing your own IR's, but I can't find it now, and the "generate impulse" button seems to just generate the impulse, not capture the IR. Am I missing tools within Melda toolkit to do this, or do I need to use the Apple/Logic utility to capture the IR? Instructions I've found all seem to assume I'm capturing a mic or outboard gear, so hoping there's a streamlined way to do this ITB that doesn't require hand trimming the responses, etc so they can be used interchangeably with the originals with the same predelay values, etc.

3) Does capturing an IR also correctly capture the EQ and dynamics sections along with the high and low pass, and haigh and low dampening from the LR panel? Is there some reason why I would be better off, for instance, disabling the EQ panel and recreating those curves and filters in mConvolution?

4) Is there something I need to know about getting the stereo right? To get all the input/output width and/or related stereo goodies to port over correctly, do I need to burn a "true stereo" IR? Is that two separate IR's? In other words, are there any other specifics I need to pay attention to to make the stereo work exactly the same in mConvolution?

[Chandlerhimself]

For that particular algorithm an IR should capture it perfectly. The capture IR button should be at the bottom right of MTR. The EQ will be captured, but I don't think the dynamic will(I'm not sure). Either way it would be better to use a separate compressor after the IR loader. I'm pretty sure it will output in stereo and you shouldn't need 2 separate IRs.

[Annabanna]

Well, that certainly seems super useful.

Unfortunately, I'm stuck on 13 point something, and have already had multiple arguments with the admin who is extremely protective of his offline system about the need to update over half a dozen different plugins now as the system has been literally airgapped for over a year since he had some problems with another user.

Since I can't choose the timeline in which that gets fixed, am I correct that v13 is missing this button? If so, what is my simplest workflow for capturing the IR's on a mac without having to manually trim them or anything like that?

[Q9000]

IR(Impluse response) is just that - a response (echo) of an impulse. The origin of the IR doesn't matter.

1) depends on what effects are implemented how, see 3)

2) you can capture your own IR by feeding an impulse as the input to the effect and rendering the audio to a audiofile. You can create an impulse with audacity with the generation tools there.

3) IR captures a EQ(if the EQ doesn't use any nonlinear effects), nonlinear effects like compression(dynamics) are not captured.

4) if you need stereo just render it as a stereo audio file

[Annabanna]

All good info. Thx.

I had the chance yesterday to work on a different system. I don't recall the version number off the top of my head, but it was 14. something and I'm told it was updated recently. I tried doing the IR capture from within MTR, but am not seeing the button on any of my patches. Am I correct in my assessment that the button exists on the standalone plugin, but no such feature exists in the MTR MXXX module, or did I miss something?

[Held]

Am I correct in my assessment that the button exists on the standalone plugin, but no such feature exists in the MTR MXXX module, or did I miss something?

There was an IR button for exporting impulse responses added to MXXX in the V15 beta but it doesn't seem to be available in V14.