Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #96164
    Profile photo of Bryan vdz
    Bryan vdz
    Participant

    It works, in that I have the information I wanted: Plug in USB, immediately verify WDM has acquired the signal.

    The need is satisfied in a roundabout way. The Qu to PC input indication is still missing from the Recording tab in Sound Control, even though the signal is present (WDM v4.86 image above). By observing WDM display an output in Volume Mixer (thanks for the tip), I’ve demonstrated that WDM is actually processing the signal in both directions. Now, if there are problems with the overall setup I can move my attention downstream to app configuration etc.

    In both images above, a SigGen tone is successfully processed through to OBS, but only v4.67 will display that input in Sound Control, when paired with recent versions of Windows. So there is still a problem with v4.86 displaying a valid Qu input, but Volume Mixer gives me the info I need.

    #96130
    Profile photo of Bryan vdz
    Bryan vdz
    Participant

    Thank you for that. If I don’t have speakers plugged in (I usually don’t) I can see that the WDM has the signal. It just shows up on the output device only (playback tab ST1) not the input.

    Attachments:
    You must be logged in to view attached files.
    #96111
    Profile photo of Bryan vdz
    Bryan vdz
    Participant

    All is well, except for Microsoft putting a booby-trap in the UI just to toy with me for being too methodical. To check signal chain I SigGen a 400Hz tone to Mix 9-10 at 0 dB, and look for it as a level in the Windows Sound Control panel. No level means fix your configuration upstream (USB routing, cable, etc), or fix Windows audio device config before moving on to starting the app that wants the audio. Now with the update, Windows REMOVED all visual indications of inbound audio level in the System and Sound Control panels (at least for USB), regardless of whether the app is running. Several decades of troubleshooting flight simulators taught me to despise a shoot-from-the-hip “try this, try that” approach to problem solving as being inefficient. But in PC land, without a code-level line-by-line understanding of what’s going on, I guess that’s just how it works.

Viewing 3 posts - 1 through 3 (of 3 total)