Forum Post

User16782911122511517385 (Revolution Music) asked a question.

March 27, 2023 at 1:55 PM
Dolby Atmos Renderer V5 (Windows 11) crashes on startup
Hello. I installed Dolby Atmos Renderer V5, activated the trial license. After trying to launch, Dolby Atmos Renderer crashes on startup. Windows 11 Pro 21H2 system. What am I doing wrong?
  • 39 answers

  • AdamP (Dolby Labs)

    Hi,

    Thanks for your post. We are aware of this issue and are investigating this as a priority. Please keep an eye on this site. Thanks for your patience while we work on a resolution.

    Best,
    Adam

  • Sam H (Self Employed)

    Pretty sure this is related to how the renderer seems to be temporarily hijacking audio connections when it starts up, even though you've never set it to use them. e.g. it seems to scroll through all audio devices when starting up even though those devices might be in use or exclusive for other applications / virtual devices you're using elsewhere on the computer/network/hardware.

      • Sam H (Self Employed)

        You could try disabling all audio devices in Windows > Device Manager apart from the device you're wanting DAR to connect to so then it can't hijack and crash. There's some config files in C:\ProgramData\Dolby\Dolby Atmos Renderer and the logs are there too which might help to look at.

      • User16403395656777330015 (Laureano)

        Hi thank you for the answer. I tried this before. But with no sucess. I think Dolby is working on a solution. But i was curios if you find a solution with your configuration?

      • Sam H (Self Employed)

        No problem. I've had it crash a couple of times and eventually doing that got it back to the point I could then set the audio device to use.. There's a definite issue though because it just seems to want to connect to things you've never told it too. Davinci Resolve & ProTools often do this too on Windows. The one thing they all have in common is they are not good with High DPI scaling and us Qt graphics. Whenever I see Qt I just know the software is gonna have issues on Windows unfortunately.

  • User16403395656777330015 (Laureano)

    Hello, i solved my problem by deleting one Asio entrys of a virtual Soundcard in the registry. Since them it works perfectly.
    1. Start>Run>regedit
    2. Search for HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\
    3. Delete the culprits
    4. Done

    Regards
    Laureano
    Expand Post

    • Sam H (Self Employed)

      Make sense. It seems to have a hard time with virtual ASIO for some reason.
10 of 39

Don't see what you're looking for?

You must be logged in to submit new topics