"Simulated After" Curve No Longer Adjusts According to Dry/Wet Mix

Comments

4 comments

  • Avatar
    Zane

    Hi Josh,

    Thanks for reaching out!

    Sorry to hear about this! The Simulated After curve should be adjusting to the Wet/Dry setting in the newest SoundID Reference update (v.5.2.1) as well. Can you let me know if other features in the app appear to be working normally? Can you let us know what OS and its version you are currently running SoundID Reference on? Thank you in advance for the details you can provide!

    0
    Comment actions Permalink
  • Avatar
    Josh Losey

    I'm using Windows 10 21H1 64-bit. After playing around with the settings and switching back and forth between driver types several times, the problem corrected itself. Apparently, on my computer at least, when "Windows audio device insert (APO)" is selected, SoundID Reference sometimes behaves strangely. The Dry/Wet knob wasn't doing anything to the audio or visuals and the Calibration Enabled/Disabled button wasn't affecting the sound. For some reason, the program is working as expected now. I dunno. Thanks for the quick response.

    0
    Comment actions Permalink
  • Avatar
    Josh Losey

    The problem started again all on its own. It only happens when "Windows audio device insert (APO)" is selected. There's no noticeable change in the audio and certain parts of the GUI don't respond to clicks or knob adjustments. I'll just use the "Virtual Windows audio driver" for the time being, though one of the main reasons that I upgraded to SoundID Reference from Reference 4 was to get a lower latency with the new driver type. Should I just open a support ticket for this?

    0
    Comment actions Permalink
  • Avatar
    Zane

    Hey Josh,

    Thanks for your response and for providing more details! 

    It is useful that you have isolated the scenario in which the issues appear. Could you try removing previously installed APO instances to see if that improves the behavior of APO for you? For instructions on how to do this, see our support article here: APO can't be applied" error [WIN] 
    After that, add a new output with APO, try it out, and let me know if the behavior of the app has changed. 

    I have also opened a support ticket on your behalf about this issue to gather a bit more details. 

    0
    Comment actions Permalink

Please sign in to leave a comment.