[VERIFIED BUG] If you're getting the "Oops! There's an issue"- error, read this first. [OOPS ERROR]

Hello kind user,
Since we’ve been getting this error a lot, I thought I’d pin the troubleshooting suggestions, for the moment.
Please look here for answers first before making a new thread - thanks, and good luck:

image

3 Likes

FxSound2 Pro 1.1.14.0 and FxSound2 Pro 1.1.16.0, I get the next error

“Oops! There’s an issue with your playback device settings
Before we can get started, please go through the troubleshooting steps here
Contact us you’re still having problems”

None of the tips and indications that appear on the troubleshooting web page have helped me, as indicated there, of course it indicates that the program is installed, since it can be viewed in the add or remove programs section, but not it creates the virtual audio devices of FXSOUND, which interact with the physical ones of the pc’s audio card, it is as if nothing had been installed

Therefore, I appreciate your support, with a version that I praise to solve all these errors, for now I have to wait, hopefully they solve it soon and notify me,

Thank you very much for listening to me, I am waiting for a solution

1 Like

Hi @York_Gonzalez,
There are several solutions to this problem proposed in the thread I linked above,

Have you tried those?

No one likes having to wait… :wink:

1 Like

If I did but I didn’t work :frowning:

This happens every single time you connect to the computer with FxSound using Remote Desktop from another computer. It doesn’t even respond to the X close button and forces you to kill FxSound in the task manager.

2 Likes

Hi @Milincho,

Yes, this is a known problem, there have indeed already been multiple reports of issues while using FxSound combined with Remote Desktop; this was the advice offered by FxSound’s lead programmer @bvijay on the difficulties with RDP:

It would help the troubleshooting effort if you could:

  • Try the proposed solution “Allow audio and video playback redirection,” and
  • Run the Powershell check,

And post back here with the results.
Also, the user who opened the thread, added this remark:

FYI, all quotes are copied from this thread:

2 Likes

I changed the Group Policy setting but the crash keeps happening.

Run the Powershell command and this is the result:

Availability=
ConfigManagerErrorCode=0
ConfigManagerUserConfig=FALSE
Description=NVIDIA High Definition Audio
DeviceID=HDAUDIO\FUNC_01&VEN_10DE&DEV_00A4&SUBSYS_10DE167A&REV_1001\5&329484F5&0&0001
DMABufferSize=
ErrorCleared=
ErrorDescription=
InstallDate=
LastErrorCode=
Manufacturer=NVIDIA
MPU401Address=
Name=NVIDIA High Definition Audio
PNPDeviceID=HDAUDIO\FUNC_01&VEN_10DE&DEV_00A4&SUBSYS_10DE167A&REV_1001\5&329484F5&0&0001
PowerManagementCapabilities=
PowerManagementSupported=FALSE
ProductName=NVIDIA High Definition Audio
Status=OK
StatusInfo=3

Availability=
ConfigManagerErrorCode=0
ConfigManagerUserConfig=FALSE
Description=Realtek High Definition Audio
DeviceID=HDAUDIO\FUNC_01&VEN_10EC&DEV_1220&SUBSYS_1458A0C3&REV_1001\5&1EDA78B&0&0001
DMABufferSize=
ErrorCleared=
ErrorDescription=
InstallDate=
LastErrorCode=
Manufacturer=Realtek
MPU401Address=
Name=Realtek High Definition Audio
PNPDeviceID=HDAUDIO\FUNC_01&VEN_10EC&DEV_1220&SUBSYS_1458A0C3&REV_1001\5&1EDA78B&0&0001
PowerManagementCapabilities=
PowerManagementSupported=FALSE
ProductName=Realtek High Definition Audio
Status=OK
StatusInfo=3

Availability=
ConfigManagerErrorCode=0
ConfigManagerUserConfig=FALSE
Description=NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
DeviceID=ROOT\UNNAMED_DEVICE\0000
DMABufferSize=
ErrorCleared=
ErrorDescription=
InstallDate=
LastErrorCode=
Manufacturer=NVIDIA
MPU401Address=
Name=NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
PNPDeviceID=ROOT\UNNAMED_DEVICE\0000
PowerManagementCapabilities=
PowerManagementSupported=FALSE
ProductName=NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
Status=OK
StatusInfo=3

Availability=
ConfigManagerErrorCode=0
ConfigManagerUserConfig=FALSE
Description=FxSound Audio Enhancer
DeviceID=ROOT\MEDIA\0000
DMABufferSize=
ErrorCleared=
ErrorDescription=
InstallDate=
LastErrorCode=
Manufacturer=FxSound
MPU401Address=
Name=FxSound Audio Enhancer
PNPDeviceID=ROOT\MEDIA\0000
PowerManagementCapabilities=
PowerManagementSupported=FALSE
ProductName=FxSound Audio Enhancer
Status=OK
StatusInfo=3

Availability=
ConfigManagerErrorCode=0
ConfigManagerUserConfig=FALSE
Description=Oculus Virtual Audio Device
DeviceID=ROOT\MEDIA\0001
DMABufferSize=
ErrorCleared=
ErrorDescription=
InstallDate=
LastErrorCode=
Manufacturer=Oculus
MPU401Address=
Name=Oculus Virtual Audio Device
PNPDeviceID=ROOT\MEDIA\0001
PowerManagementCapabilities=
PowerManagementSupported=FALSE
ProductName=Oculus Virtual Audio Device
Status=OK
StatusInfo=3

Availability=
ConfigManagerErrorCode=0
ConfigManagerUserConfig=FALSE
Description=Virtual Desktop Audio
DeviceID=ROOT\MEDIA\0002
DMABufferSize=
ErrorCleared=
ErrorDescription=
InstallDate=
LastErrorCode=
Manufacturer=Virtual Desktop
MPU401Address=
Name=Virtual Desktop Audio
PNPDeviceID=ROOT\MEDIA\0002
PowerManagementCapabilities=
PowerManagementSupported=FALSE
ProductName=Virtual Desktop Audio
Status=OK
StatusInfo=3

2 Likes

@bvijay:

User @Milincho is experiencing problems with Remote Desktop, and has followed all of your advice (which I quoted earlier):

  • “Allow audio and video playback redirection” was enabled;
  • “wmic sounddev list full” Powershell check results have been posted above;

Can you please offer further guidance and troubleshooting?
THANKS once again.

2 Likes

@doolhoofd I have prepared a setup to access the system running FxSound over RDP. I will debug the remote desktop problem that @Milincho has reported and update on the solution.

3 Likes

587 / 5,000

Resultados de traducción

Resultados de traducción

star_border

Hi @Milincho, good night, I understand the case you propose, however I believe that my case is not the same, because here the problem is that when trying to install the program, the drivers are not installed, it always generates error. On the other hand, I do use a remote -support program for support, it is the Anydesk in its 7.0.14 version, but I think it is not the failure, because I have performed all tests and indications that all the leaders and collaborators of the Me forum They have indicated but unfortunately it has not been achieved success, I also remain attentive to support with the solution

Thanks a lot

1 Like

When connecting over RDP, if the RDP connection setting for audio is set to Play on this computer,
image
then only Remote Audio is available as playback device. FxSound cannot start because FxSound Audio Enhancer device is not available in this scenario.
image

If Remote Desktop Client connection audio setting is Play on remote computer
image
Then the device is available and FxSound is running

So, if playing audio on the remote PC is the requirement, then set the client option accordingly and FxSound will run on the remote PC.
But, if audio has to be played on the local PC but FxSound has to run on the remote PC process the audio that plays locally then it is not possible.

3 Likes

Hello @bvijay;
Could you please assist user @Sozo experiencing loss of sound when using FxSound through RDP (see post quoted below)?
My knowledge of RDP is … limited? … No; in all honesty, it’s nearly non-existent.
Thanks again!

@bvijay: User @hwiese1980 is also experiencing problems with RDP;