Forum Post

Sam H (Self Employed) asked a question.

July 20, 2023 at 9:33 AM
DAR 5.1 Crashing on Startup - Windows 11
DAR crashing on startup still appears to be an issue on the recent 5.1 update on Windows 11. DAR is the only audio application that crashes immediatly upone connecting. ProTools, Davinci Resolve, Ableton, Bitwig, Plogue Bidul, SpectraLayers all connect and are stable? Unfortuantly the log does really give much infromation on the Audio Interface or why it crashed?

Log:
2023-07-19 21:52:12 INFO Renderer App UI - Listening for remote ui on port 4010
2023-07-19 21:52:12 INFO connection_server - listing on port 4010
2023-07-19 21:52:12 INFO Renderer App - Database: C:\ProgramData\Dolby\Dolby Atmos Renderer\persistence.db
2023-07-19 21:52:12 INFO Renderer App - DB backup folder: C:\ProgramData\Dolby\Dolby Atmos Renderer\Backups
2023-07-19 21:52:12 INFO DynMetadataTimeProfiler [FS-701] - Time constants: usedDeltaTimeMs = -35, minDeltaTimeMs = 10, maxDeltaTimeMs = 110, expirationTimeMs = 500
2023-07-19 21:52:12 INFO DynMetadataTimeProfiler [FS-701] - Dynamic metadata stats profiling disabled. Enable it by creating the file C:\ProgramData\Dolby\Dolby Atmos Renderer\logs\Histogram.html
2023-07-19 21:52:12 INFO DynMetadataPeriodicityDetector [FS-702] - Time constants: blankFramesAllowedDuringPlayback = 3, blankFramesAllowedWhileStartingPlayback = 40, blankFramesAllowedWhileStopping = 40
2023-07-19 21:52:12 INFO LocalNetworkClientView - connected to localhost
2023-07-19 21:52:12 INFO connection_server - accepted client socket 1992
2023-07-19 21:52:12 INFO Comms3Server - Comms v3.2.0--dev-devel_builder
2023-07-19 21:52:12 INFO connection_server - listing on port 4826
2023-07-19 21:52:13 INFO Comms3ServerPublisher - Commslib server service published
2023-07-19 21:52:13 INFO BinauralRenderer - Empty PHRTF configuration
2023-07-19 21:52:14 INFO BinauralRenderer - Empty PHRTF configuration
2023-07-19 21:52:14 INFO RendererExecutive - Maximum latencies computed to be: 48k: 1056 samples || 96k: 2112 samples
2023-07-19 21:52:14 INFO RendererExecutive - Time profiler disabled. Enable it by creating the file C:\ProgramData\Dolby\Dolby Atmos Renderer\logs\profiling.txt
2023-07-19 21:52:14 INFO comms_client - Using Comms client v3.2.0--dev-devel_builder
2023-07-19 21:52:14 INFO Renderer App UI - Starting renderer version 5.1.0_793-98966d0d
2023-07-19 21:52:14 INFO RendererExecutive - Received 8 initialization request(s)
2023-07-19 21:52:14 INFO connection_server - accepted client socket 2244
2023-07-19 21:52:14 INFO comms_server - Assigning client id 1 to socket 2244. Client address is: 127.0.0.1
2023-07-19 21:52:14 INFO comms_server - info for client id 1: Comms3ClientForComms2
2023-07-19 21:52:14 INFO CommsBridge - Client ID 1 connected from 127.0.0.1:50950. Type: Comms3ClientForComms2
2023-07-19 21:52:14 INFO comms_server - Acquire write access failed for client 1 item id 4: WARN_RELEASE_UNNECESSARY
2023-07-19 21:52:14 INFO RendererExecutive - -------------------------------------------------initializing--------------------------------------
2023-07-19 21:52:14 INFO RendererExecutive - Received 2 initialization request(s)
2023-07-19 21:52:15 INFO RendererExecutive - Started audio driver with 512 frame size at 48000Hz
2023-07-19 21:52:15 INFO Scheduler::MultiThreadedScheduler - Running multithreaded scheduler with #3 threads
2023-07-19 21:52:16 INFO TorchLightZoneConfigurations - computing asynchronously from roomconfig file
2023-07-19 21:52:19 INFO TorchLightZoneConfigurations - Computed and ready to use
2023-07-19 21:52:19 INFO BinauralRenderer - Empty PHRTF configuration
2023-07-19 21:52:20 INFO BinauralRenderer - Empty PHRTF configuration
2023-07-19 21:52:20 INFO RendererExecutive - Total latency in samples: 1056
2023-07-19 21:52:20 INFO AudioEngine - Time constants: framesWithEventsAllowedWhileStopped = 40
2023-07-19 21:52:20 INFO RendererExecutive - ---------------------------------------------------- DONE -----------------------------------------
2023-07-19 21:52:20 INFO RendererExecutive - uninitializing


(assume this is as far as the log got as nothing more about the crash)
  • 9 answers

  • Fin B (Dolby Labs)

    Hi Sam,
    What are the exact steps to reproduce this? Does the Renderer crash or hang on a white screen on start up? What other ASIO drivers do you have on your machine? And what audio hardware to you have connected (anything MOTO)? Have you tried reproducing without hardware connected?
    Sorry for the many questions, hoping to get you up and running as soon as possible.
    Fin

  • Sam H (Self Employed)

    My audio interface is based around JACK Audio which is essentially a ‘Server <-> Client’ architecture of infinite channel count to supply the audio connections between ASIO application(s) like DAWs and editors and in this case, hopefully my DAW & DAR. I've tried using various audio hardware interfaces (Roland, Apogee, RME) but the issue seems to be DAR doesn't like the JACK ASIO Driver as it crashes as soon as it starts connecting through it.

    You can setup JACK from here. I fully appreciate single computer working isn't supported, so accept if this is beyond scope of any support/investigation, but this is the only 128+ channel Windows solution i'm aware of that could work all on the same computer without an available Dolby Audio Bridge.

    https://jackaudio.org/faq/jack_on_windows.html
    Expand Post

  • Fin B (Dolby Labs)

    Hi Sam, Thanks for the info.

    If we could drill down into this a bit more. Does the Renderer completely crash or hang on a white screen on start up? What other ASIO drivers do you have on your machine? What are the exact steps to reproduce this cash? What is your set up? What physical audio hardware do you come out of your setup through in order to listen to the audio? Have you tried reproducing this issue without this hardware connected?

  • Sam H (Self Employed)

    Steps to recreate is start JACK connected to the ASIO hardware audio interface. Open DAR>Settings>Select JACK ASIO as DAR's I/O>Save. It then connects to JACK ASIO for a fee seconds, then DAR just closes instantly with no error or warning.

  • Fin B (Dolby Labs)

    Hi Sam,
    Thanks for all the info. We'll investigate and get back to you.

    Fin

    • Sam H (Self Employed)

      Much appreciated Fin. It's not a big issue because in the end I decided to use Fiedler Atmos Composer VST solution, but the DAR does have a couple of features not available from Fielder. The headtracking and dd+joc export especially.

      • Sam H (Self Employed)

        If testing between DAW and DAR at 128 channels, it's quite important is to set the i/o up for JackRouter as the defaul is 4 channel i/o only. To set to128 i/o edit C:\Program Files\JACK\jack-router\win64\JackRouter.ini to be 128 i/o instead

        https://jackaudio.org/faq/jack_on_windows.html

  • Sam H (Self Employed)

    Any updates on this? As I was the one that worked out the 64 channel solution using ASIO Link Pro and Windows studios are aware JACK ASIO would provide the 129 channels synced to clock Windows needs, I was wondering if there was any progress to integrate JACK, either to the point DAR doesn't crash when connecting to ASIO or simply make DAR a JACK-aware application then ASIO doesn't even need to be used then, it'll all work at JACKRouter level instead.

Don't see what you're looking for?

You must be logged in to submit new topics