Recording Impulse Responses for Speaker Virtualization

Oct 8, 2023 at 8:17 PM Post #1,696 of 2,034
It is clear to me that you don't understand what I say. Hearing perception - or simply: what (you think) you hear - is a construction by the brain, the actual sound is just one part of the information the brain uses for that. (Do you know for example the McGurk effect? )
Or in other words: what you hear is not fully determined by the actual sound.
Visual (and other) cues can - and in daily life often do - overrule the hrtf related cues in the actual sound. If in one setup you are looking at a pc screen 50 cm in front of you, with a wall directly behind it your brain will very likely interpret the exact same sound very differently compared to sitting in the middle of a room, seeing a tv and loudspeakers at 3 meters distance in front of you.
That doesn't mean that there couldn't be something else going on, but the above is a very real possibility and hence our question about seeting position and what you see is really relevant. And on topic in this thread.

Yes i know. and
It makes a difference even if you sit in the same seat and experiment with one on my PC and one on a laptop. the same file
It was completely different from the error I perceived. even if I look at the same screen in the same posture and compare PC and laptop alternately, 7.1 on my PC does not map correctly. I'm tired because I've already tried a lot to solve this for a month, and I'm going to take some more time...
 
Oct 8, 2023 at 10:06 PM Post #1,698 of 2,034
1.png


It's original FC ir file in hesuvi.

2.png


And Red is Mono FC file Convolution loopback. - (It's same with Original FC file.)
Green is Normal Hesuvi file loopback (Mute FL,FR without FC, In apo Copy: L=FC R=FC)

3.png


Also, In APO, Channel C, Mono convolution FC file...

I hope this loopback makes sense of what I'm going through. On PCs that don't play properly, FC can't output properly.
 
Last edited:
Oct 10, 2023 at 2:17 AM Post #1,700 of 2,034
I use Dolby atmos for headphone in the playback option in the lg tv which is used as the listening device for vb cable …
Not sure if the big change is because my tv can decode Dolby but it has made a massive difference.
Pretty much every modern tv can decode Dolby Atmos. The output of “Dolby Atmos for Headphones” would be a stereo binaural stream (not 7.1). It’s not clear exactly what you’re doing but from what you’ve stated you appear to be creating a stereo binaural mix, automatically up mixing it to 7.1 and then applying another “binauralisation” process (an additional HRTF).

If that’s the case, the result would be unpredictable and I’m not surprised you’re sometimes perceiving the centre channel in the rear.

G
 
Oct 10, 2023 at 2:32 AM Post #1,701 of 2,034
Pretty much every modern tv can decode Dolby Atmos. The output of “Dolby Atmos for Headphones” would be a stereo binaural stream (not 7.1). It’s not clear exactly what you’re doing but from what you’ve stated you appear to be creating a stereo binaural mix, automatically up mixing it to 7.1 and then applying another “binauralisation” process (an additional HRTF).

If that’s the case, the result would be unpredictable and I’m not surprised you’re sometimes perceiving the centre channel in the rear.

G
It’s the other user that’s getting the centre channel in the rear.

Yes the Dolby for headphones is only using stereo then doing its thing to give binaural sound. It might be different because I’m using the Dolby headphones on the “listened to” device.

I know two binauralisation will sound messed up. But I would request you guys give it a try at least because as good as surround sounds. This gives clear object placement and sounds like you’re actually there.
 
Oct 13, 2023 at 11:55 PM Post #1,703 of 2,034
I've already tested on different PCs, different devices with the same file... I thought this was impossible, so I initially suspected problems such as my own setup or a lack of proper installation.

1.png
On a device where this works properly, it sounds like that in the right position I marked. It's not what I feel, it's what I hear it........ =(

2.png

And if my current PC or the PC I tested doesn't work the same as my computer, the front and center are at the back as I indicated. It sounds like it's coming from behind, but it's not. It's in the back Just.

Two-channels work very accurately. So the problem is that Windows itself 7.1 doesn't work normally on some computers, including my computer.
It's not a problem with the file. Weird placement of sound in windows.
I also wrote because you replied, but as I wrote yesterday, I will no longer deviate from the topic of the thread. I'm sorry.
Can you upload your config.txt and all associated files for me to have a look? I hope to be able to solve this puzzle for you.
 
HiBy Stay updated on HiBy at their facebook, website or email (icons below). Stay updated on HiBy at their sponsor profile on Head-Fi.
 
https://www.facebook.com/hibycom https://store.hiby.com/ service@hiby.com
Oct 14, 2023 at 1:30 AM Post #1,704 of 2,034
Can you upload your config.txt and all associated files for me to have a look? I hope to be able to solve this puzzle for you.

There will be no problem with the hesuvi.txt file and the wave file itself... But I still share it. Thank you for looking into it.
The config.txt file is a copy of the current configuration and was tested in the VB cable unit column below.
 

Attachments

Oct 14, 2023 at 2:02 AM Post #1,705 of 2,034
My first idea was some out of phase channel (sometimes it’s feeling like no clear sound direction, sometimes it weirdly can feel like it’s behind), but I dismissed it, failing to imagine what situation could cause that only on some systems with the same impulses and channel settings.
 
Oct 14, 2023 at 4:44 AM Post #1,706 of 2,034
There will be no problem with the hesuvi.txt file and the wave file itself... But I still share it. Thank you for looking into it.
The config.txt file is a copy of the current configuration and was tested in the VB cable unit column below.
I don't actually use HeSuVi, but I referred to their channel mapping and your file doesn't seem to follow it.
1697272387458.png


I don't know what your actual mapping is, but I remapped it as best I could to follow the above.
https://www.dropbox.com/scl/fi/y8yc...ered.wav?rlkey=rqaf64u2z0aqyt69cjcd25p5v&dl=0

I also programmed my own implementation of convolving the wav, in case the actual HeSuVi implementation doesn't work:
https://www.dropbox.com/scl/fi/9muaoul9wbfbq8ibhexn9/config.txt?rlkey=71u74oj9z243y59gs1wvdv8jx&dl=0

I think the most likely problem is that your different computers have different virtual devices with different numbers of channels, as the behaviour of eqAPO changes depending on that, in particular the ordering of channels being processed changes.
 
Last edited:
HiBy Stay updated on HiBy at their facebook, website or email (icons below). Stay updated on HiBy at their sponsor profile on Head-Fi.
 
https://www.facebook.com/hibycom https://store.hiby.com/ service@hiby.com
Oct 14, 2023 at 4:58 AM Post #1,707 of 2,034
I don't actually use HeSuVi, but I referred to their channel mapping and your file doesn't seem to follow it.
1697272387458.png

I don't know what your actual mapping is, but I remapped it as best I could to follow the above.
https://www.dropbox.com/scl/fi/y8yc...ered.wav?rlkey=rqaf64u2z0aqyt69cjcd25p5v&dl=0

I also programmed my own implementation of convolving the wav, in case the actual HeSuVi implementation doesn't work:
https://www.dropbox.com/scl/fi/9muaoul9wbfbq8ibhexn9/config.txt?rlkey=71u74oj9z243y59gs1wvdv8jx&dl=0

I think the most likely problem is that your different computers have different virtual devices with different numbers of channels, as the behaviour of eqAPO changes depending on that, in particular the ordering of channels being processed changes.
Thank you. When I heard your file using heseuvi, all the channel mapping was to the left, and your text file is the same as the previous 7.1 file I used. The center can be heard from behind my back in the same way.
Maybe it's the issue of VBcable.

as.png


I was told by the administrator in the VB forum that a new version of the VB cable could solve this problem.
But he was talking about 2 channels and 8 channel outputs, and this is about channel mapping, so it's a bit different, but I'll still have to wait for a new driver.

My first idea was some out of phase channel (sometimes it’s feeling like no clear sound direction, sometimes it weirdly can feel like it’s behind), but I dismissed it, failing to imagine what situation could cause that only on some systems with the same impulses and channel settings.

I also expected the polarity to be inverted, and I tried to reverse phase some channels. But it was a completely different issue.
And most importantly, I understand the acoustic part of cognition, but I think anyone would feel that the voices of actors behind their backs are not normal.
Even I know the location of the original sound of my files working correctly on a bunch of PCs I tested, so 7 channels on my current PC aren't working properly.
Thank you for your advice though.
 
Oct 14, 2023 at 5:32 AM Post #1,708 of 2,034
Thank you. When I heard your file using heseuvi, all the channel mapping was to the left, and your text file is the same as the previous 7.1 file I used. The center can be heard from behind my back in the same way.
Maybe it's the issue of VBcable.

as.png

I was told by the administrator in the VB forum that a new version of the VB cable could solve this problem.
But he was talking about 2 channels and 8 channel outputs, and this is about channel mapping, so it's a bit different, but I'll still have to wait for a new driver.



I also expected the polarity to be inverted, and I tried to reverse phase some channels. But it was a completely different issue.
And most importantly, I understand the acoustic part of cognition, but I think anyone would feel that the voices of actors behind their backs are not normal.
Even I know the location of the original sound of my files working correctly on a bunch of PCs I tested, so 7 channels on my current PC aren't working properly.
Thank you for your advice though.
You need Virtual Audio Cable instead https://vac.muzychenko.net/en/
 
HiBy Stay updated on HiBy at their facebook, website or email (icons below). Stay updated on HiBy at their sponsor profile on Head-Fi.
 
https://www.facebook.com/hibycom https://store.hiby.com/ service@hiby.com
Oct 14, 2023 at 5:40 AM Post #1,709 of 2,034
Your config file is strange:
'#' means it is not active. So EQ-APO is doing nothing.

Device: hd800s TOPPING USB DAC {ef1cefd1-6c7d-4a35-b5c6-9f02ec1980c7}
# Include: HeSuVi\hesuvi2 reverb.txt
# Include: F:\Mybrir\0918 800s\HP800.txt
Device: ksc75 TOPPING USB DAC {81d9711e-d8bf-42a6-8d93-96bf68753e0d}
# Include: HeSuVi\hesuvi.txt
# Include: HeSuVi\hesuvi2 reverb.txt
# Include: HeSuVi\hesuviKSC.txt
# Include: F:\Mybrir\0918 800s\HPKsc - 복사본 - 복사본 - 복사본.txt
# Copy: L=L+-0.15*R R=-0.15*L+R
Device: CABLE Input VB-Audio Virtual Cable {17223e4d-87f6-4f95-9d4e-8f2b62e4d96f}
# Preamp: -13 dB
# Include: HeSuVi\hesuvi.txt
# Include: HeSuVi\hesuvi2 reverb.txt

I don't actually use HeSuVi, but I referred to their channel mapping and your file doesn't seem to follow it.
His file is correct.

You need Virtual Audio Cable instead https://vac.muzychenko.net/en/
No, VB cable is working. There is no need for 8ch output as EQ-APO works on the input channels.

@XingYu
Have you tried the benchmark option to test if everything inside EQ-APO works correct?
You can do it in the command window when you go to the EQ-APO folder and then use the command:
Benchmark -i "....\folder\yourwave.wav" -o " ..\folder\yourwave_output.wav"
 
Last edited:
Oct 14, 2023 at 7:22 AM Post #1,710 of 2,034
Your config file is strange:
'#' means it is not active. So EQ-APO is doing nothing.

Device: hd800s TOPPING USB DAC {ef1cefd1-6c7d-4a35-b5c6-9f02ec1980c7}
# Include: HeSuVi\hesuvi2 reverb.txt
# Include: F:\Mybrir\0918 800s\HP800.txt
Device: ksc75 TOPPING USB DAC {81d9711e-d8bf-42a6-8d93-96bf68753e0d}
# Include: HeSuVi\hesuvi.txt
# Include: HeSuVi\hesuvi2 reverb.txt
# Include: HeSuVi\hesuviKSC.txt
# Include: F:\Mybrir\0918 800s\HPKsc - 복사본 - 복사본 - 복사본.txt
# Copy: L=L+-0.15*R R=-0.15*L+R
Device: CABLE Input VB-Audio Virtual Cable {17223e4d-87f6-4f95-9d4e-8f2b62e4d96f}
# Preamp: -13 dB
# Include: HeSuVi\hesuvi.txt
# Include: HeSuVi\hesuvi2 reverb.txt


His file is correct.


No, VB cable is working. There is no need for 8ch output as EQ-APO works on the input channels.

@XingYu
Have you tried the benchmark option to test if everything inside EQ-APO works correct?
You can do it in the command window when you go to the EQ-APO folder and then use the command:
Benchmark -i "....\folder\yourwave.wav" -o " ..\folder\yourwave_output.wav"
He says that VB-cable can't accept multichannel except via KS which should bypass eqAPO. What is the actual channel mapping of a hesuvi file?
 
Last edited:
HiBy Stay updated on HiBy at their facebook, website or email (icons below). Stay updated on HiBy at their sponsor profile on Head-Fi.
 
https://www.facebook.com/hibycom https://store.hiby.com/ service@hiby.com

Users who are viewing this thread

Back
Top