It has arrived! It was delivered very unceremoniously. I didn’t even know it was sitting outside until I happened to take the trash out after work.
First impressions are good. I really like the all-in-one loadbox concept. I’m lazy enough that having to queue up an IR to use my LB-2 is enough of a hassle that it doesn’t get used too, too often. Having the IR loader, headphone amplifier, and even some effects in a single package is really nice. I loaded up a single IR from @MirrorProfiles and was immediately pleased with how everything sounded through my HD6XX headphones.
I still have yet to really put it through its paces, but I’m happy to have this as part of my rig.
@st.Rock I'm looking at the Tone Matcher feature in the React:IR and I'd like to understand more about the "Block Size" feature.
If I make an IR using the "Tone Matcher", which "Block Size" will give me the better quality result?
The "IR Making Manual" from the React:IR 1, briefly mentioned setting the block size to 8192-16384 values but I'm not well enough educated to understand what's behind it and how the output quality is influenced by these settings:
Ohh.... it will be a little bit complicated...
Better to use Auto...
If you want to just a make an IR, with internal test file signal then use Auto or 65536.
Block size must be more than Sample Rate. For example 44100 or 48000 first close value is 65536.
For 96k it will be 131072 and so on.
You can set lower Block Size for more smooth results. It's something like decrease IR length.
This is advanced settings for matching different files with differents Sample Rates.
For usual using Auto will be a right choise.
Also Block Size can be used only for Preview Graph in smooth view.
For example - when you comparing a frequency responce of two IR's you can want to see less details.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.