HydrogenAudio

Hosted Forums => foobar2000 => Support - (fb2k) => Topic started by: papavlos on 2022-10-01 19:21:59

Title: stubborn "Output trace" value
Post by: papavlos on 2022-10-01 19:21:59
Please help!

I am running fb2k 1.6.12 on two computers, one is Win64, second is Win32. Both are driving external DACs of different manufacturers, each of them with dedicated ASIO driver. All based on Thesycon USB Audio 2.0 Class Driver for Windows. The following problem occurs on both machines:

I would like to stop my ASIO drivers creating ASIOhost*.trc files in my temp dir. They are blowing unexpectedly leading my system to crash.
So I am setting 0 (zero) to Preferences > Advanced > Debugging > Output trace.
"Apply" and "Save". Now the new trace file is of length 0 (zero). Yes, this is what I wanted. Even after restarting foobar.
But, for unknown reasons in unpredictable circumstances foobar resets the value to 3 and the trace file starts blowing again.

Is it a bug, or is it on purpose?

If on purpose - how to get rid of ASIOhost*.trc files? Or, how to set the value to 0 (zero) permanently?

Title: Re: stubborn "Output trace" value
Post by: papavlos on 2022-10-01 23:28:43
A reply to myself:
After some investigation I have figured out that the "Output trace" parameter comes with the "foo_out_asio+dsd" component from SorceForge project. After uninstalling it and installing the stock component "foo_out_asio" by Peter - this parameter has disappeared, so "ASIOhost*.trc" files have also vanished.

I have already opened discussion on SourceForge so this case here becomes obsolete.
Title: Re: stubborn "Output trace" value
Post by: papavlos on 2022-10-03 22:29:18
For those who were observing my post: with the 0.3.1 version of the foo_out_asio+dsd (https://sourceforge.net/projects/sacddecoder/files/) component from SourceForge the problem was solved. No more trace log files.