dingdong3

LVI = L, RVI = R are, quite literally, virtual channels. Let me explain the idea of how it operates based on your configuration. Create mono tracks for FLL, FLR, FRL, FRR and convolve them on each channel as you wish. Then finalize it with your output code. That’s how it works. But where did I see "the left speaker's right ear is actually R input"? I’ve mentioned it multiple times already. Please refer to APO’s wiki on convolution, or it’s already stated in what I’ve written. According to the round-robin...

I use personalized files, so I don’t know how the default HesuVi presets are structured. (The order might be the same, but I don’t know what input and output that file is actually supposed to use.) However, if it’s structured like the HesuVi.wav from Impulcifer, then the method I proposed is correct. And some of you, including yourself, keep saying, "That’s wrong." Then explain the convolution input assignment logic in APO, how the order matches or doesn’t match, and how it connects to the output....

I use personalized files, so I don’t know how the default HesuVi presets are structured. (The order might be the same, but I don’t know what input and output that file is actually supposed to use.) However, if it’s structured like the HesuVi.wav from Impulcifer, then the method I proposed is correct. And some of you, including yourself, keep saying, "That’s wrong." Then explain the convolution input assignment logic in APO, how the order matches or doesn’t match, and how it connects to the output....

not hrir.wav I'm saying Hesuvi.wav Please, Read My Word. HESUVI.WAV The Hrir.wav generated by Impulcifer and HesuVi.wav have different track orders. Please understand this...................................... I clearly stated multiple times that it was an example referring to HesuVi.wav. Please, understand this. If you insist on using Hrir.wav with HesuVi's configuration, you’ll need to assign the order as desired to match it. (Input L is odd-numbered, Input R is even-numbered.)

Oh........................... This will be the last time I repeat the same point. It’s simple. I’ve explained this multiple times from yesterday to today. When a "multi-channel IR" is convolved, the L and R inputs are assigned based on the order of the tracks. HesuVi was created to make it easier to use APO configurations, and yes, that’s correct. However, the default track order of HesuVi.wav is assigned as FLL, FLR, ... and so on. Since FLR corresponds to an even-numbered track, it is assigned...

Oh........................... This will be the last time I repeat the same point. It’s simple. I’ve explained this multiple times from yesterday to today. When a "multi-channel IR" is convolved, the L and R inputs are assigned based on the order of the tracks. HesuVi was created to make it easier to use APO configurations, and yes, that’s correct. However, the default track order of HesuVi.wav is assigned as FLL, FLR, ... and so on. Since FLR corresponds to an even-numbered track, it is assigned...

You mentioned that you’re using the SBX preset, which seems to be a default preset. If that’s the case, it may be even harder for you to notice the difference. This is because it deviates from "your" natural ITD and ILD, causing mismatches. Additionally, there are numerous variables: whether the current setup is in a dual-mono or true stereo state, whether phase cancellation is occurring, and whether the personalized HPCF for your specific headphones or IEMs is being applied correctly. I am speaking...

You mentioned that you’re using the SBX preset, which seems to be a default preset. If that’s the case, it may be even harder for you to notice the difference. This is because it deviates from your natural ITD and ILD, causing mismatches. Additionally, there are numerous variables: whether the current setup is in a dual-mono or true stereo state, whether phase cancellation is occurring, and whether the personalized HPCF for your specific headphones or IEMs is being applied correctly. I am speaking...