For so many cases of troubleshooting - adding logging code for debugging proves so useful to help isolate where the problem is occurring or the circumstances in which the bug presents itself - such a logging system is essential and really helps. Logging facilities (where users/testers can turn on logging and then - in some user friendly manner - easily submit text file logs back to PG devs ) would benefit ALL of the apps and background daemons etc - that are part of BIAB.

For example recently I helpedOSX developers Rogue Amoeba track down a bug in one of their real-time audio apps LoopBack. As soon as I was told how to turn on logging in LoopBack and sent the logs back to Rogue Amoeba - the developers were able to fix the bug I had found - in a couple of days.

What would the logging do? well for example - in BIAB standalone - if one could turn on a logging feature where every menu, keyboard, context menu and button-command action was logged - this would provide a huge useful tool to recreating the circumstances in which a rare bug occurs and can save a lot of time.

Believe me I vouch for thisbenefit of comprehensive logging - both for internal code AND user actions ( as would any developer worth their salt ) in software I’ve written myself over the last 40 + decades !

MacOS Sequoia, M4 Pro Mac Mini , 64GB RAM 512GB SSD ,
BIAB, Cubase, Ableton, Logic Pro, SCALER 3, GigLad, AnyTune, Synthesizer V Pro,Vienna Ensemble Pro, Audiofuse, Fractal FM3, KOMPLETE 15, StreamDeck, iReal Pro
White beard, beer belly, bald patch