What is the value in File->Preferences->Advanced->Debugging->Output trace? Set it to 0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-10-01
Already found this option and set it to 0. Doesn't stop producing trace logs. What's more foobar doesn't remember other values than 3 and after restarting there is 3 again.
I have also second computer with similar installation, only the DAC is from another manufacturer with dedicated ASIO driver, different from the problematic one. There are no ASIO trace log files. And the output trace level is set to the default 3.
Let me downgrade the version of the ASIO driver on the first computer. My guess is that the root cause is in the driver. Will let you know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-10-01
Please ignore my previous post (still being reviewed by the Moderator ;-)).
Setting Output trace option to 0 (zero), applying, closing the window and restarting foobar has remembered the new target value of 0. And the trace log files doesn't grow anymore during playback.
Everything has happened as above because this time I have stopped playback before opening Preferences window. Apparently I was trying previously to modify the option during playback, with no effect.
Thanks for your advice! And please close the ticket.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The two above anonymous posts are mine (I have created my sf account in the meantime).
Unfortunately the described problem remains, which is automate resetting the value of "File->Preferences->Advanced->Debugging->Output trace" to 3 after any change of source, type or resolution. It looks like SOMETHING (the asio+dsd component?) resets this value to foobar default instead of using value set previously by the user, whenever it resets or reloads the ASIO driver.
It happens on both of my computers.
Is it a bug? Of which element: foobar itself, the ASIO driver, or the asio+dsd component?
I have checked two versions of asio+dsd component: 0.2.2 and 0.1.7 - same behaviour.
I can investigate further, just please tell me what to check.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's funny. After opening Preferences > Advanced and scrolling to the bottom the displayed value of "Output trace" is 3, but after "Reset Page" it becomes 0 again. The bad side is that you have to restart foobar after each reset. This functionality is buggy, anyway...
So assuming foobar really has "0" in memory as the value of the "Output trace" parameter - this doesn't help: ASIO*.trc files appear, of the length much greater that zero Bytes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have uninstalled "foo_out_asio+dsd" component and have installed the current stock component "foo_out_asio" from foobar website, written by Peter.
Plays everything, I mean PCM and DSD, through ASIO to my DAC. And the DAC shows same type and density of stream as in the playlist. So bit-perfect, presumably.
In the temp dir - clean and quiet. No trace logs. So it must have been the asio+dsd component which was responsible for my problem.
BTW, on the other computer, there ARE also "ASIO*.trc" trace log files. I have simply forgotten the actual dir assigned to TEMP variable there. I didn't suffer from this misbehaviour because the TEMP dir was assigned to a directory in a hard drive, whereas on the first computer the TEMP dir was assigned to a directory in a RAM drive - relatively small, so easy to be overrun.
Please let me know, should I have missed anything....
Last edit: papavlos 2022-10-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-10-02
Hi, I have two laptops:
- FB 1.6.12 32bit plus asio+dsd 0.3 and it seems ok
- FB 2 beta 10 64bit plus asio+dsd 0.3 and it produces lots of traces files in temp folder.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After closer investigation I still see one advantage of "foo_out_asio+dsd" component over the stock "foo_out_asio" component, which is DSD playback: the latter transmits it with DoP (DSD over PCM) while the first component as DSD native. Of course, there is "DSD" set as the value of Type in the section Output (per device) in the Preferences > SACD option set. No conversion to PCM on-the-fly.
As I have mentioned - I have two DACs. The first displays that it is playing DSD input, the second - PCM, although receiving exactly the same material. When looking at the tab "Buffer settings" of ASIO driver settings, on both computers the "ASIO Status" section contains "ASIO active (PCM mode)". That means one thing - computer must be sending DoP to both DACs.
With the "asio+dsd" component both statuses are showing properly DSD stream and the second DAC also displays DSD as the input format.
This is the reason I'll be waiting for newer versions of the "asio_dsd" component, with the default value of "Output trace" set to 0 (zero), not 3, as it is currently.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes! No more trace log files! So asio+dsd component has returned to both of my systems.
And I can read "DSD mode" in ASIO driver buffer settings status and in DAC display. It must be DSD native again.
Many thanks, Maxim!
Now please close the ticket.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What is the value in File->Preferences->Advanced->Debugging->Output trace? Set it to 0.
Already found this option and set it to 0. Doesn't stop producing trace logs. What's more foobar doesn't remember other values than 3 and after restarting there is 3 again.
I have also second computer with similar installation, only the DAC is from another manufacturer with dedicated ASIO driver, different from the problematic one. There are no ASIO trace log files. And the output trace level is set to the default 3.
Let me downgrade the version of the ASIO driver on the first computer. My guess is that the root cause is in the driver. Will let you know.
Please ignore my previous post (still being reviewed by the Moderator ;-)).
Setting Output trace option to 0 (zero), applying, closing the window and restarting foobar has remembered the new target value of 0. And the trace log files doesn't grow anymore during playback.
Everything has happened as above because this time I have stopped playback before opening Preferences window. Apparently I was trying previously to modify the option during playback, with no effect.
Thanks for your advice! And please close the ticket.
@manisiutkin
please, re-open the ticket
The two above anonymous posts are mine (I have created my sf account in the meantime).
Unfortunately the described problem remains, which is automate resetting the value of "File->Preferences->Advanced->Debugging->Output trace" to 3 after any change of source, type or resolution. It looks like SOMETHING (the asio+dsd component?) resets this value to foobar default instead of using value set previously by the user, whenever it resets or reloads the ASIO driver.
It happens on both of my computers.
Is it a bug? Of which element: foobar itself, the ASIO driver, or the asio+dsd component?
I have checked two versions of asio+dsd component: 0.2.2 and 0.1.7 - same behaviour.
I can investigate further, just please tell me what to check.
Does "Reset page" help? Foobar itself handles this value. foo_out_asio+dsd just read it.
That's funny. After opening Preferences > Advanced and scrolling to the bottom the displayed value of "Output trace" is 3, but after "Reset Page" it becomes 0 again. The bad side is that you have to restart foobar after each reset. This functionality is buggy, anyway...
So assuming foobar really has "0" in memory as the value of the "Output trace" parameter - this doesn't help: ASIO*.trc files appear, of the length much greater that zero Bytes.
I have uninstalled "foo_out_asio+dsd" component and have installed the current stock component "foo_out_asio" from foobar website, written by Peter.
Plays everything, I mean PCM and DSD, through ASIO to my DAC. And the DAC shows same type and density of stream as in the playlist. So bit-perfect, presumably.
In the temp dir - clean and quiet. No trace logs. So it must have been the asio+dsd component which was responsible for my problem.
BTW, on the other computer, there ARE also "ASIO*.trc" trace log files. I have simply forgotten the actual dir assigned to TEMP variable there. I didn't suffer from this misbehaviour because the TEMP dir was assigned to a directory in a hard drive, whereas on the first computer the TEMP dir was assigned to a directory in a RAM drive - relatively small, so easy to be overrun.
Please let me know, should I have missed anything....
Last edit: papavlos 2022-10-01
Hi, I have two laptops:
- FB 1.6.12 32bit plus asio+dsd 0.3 and it seems ok
- FB 2 beta 10 64bit plus asio+dsd 0.3 and it produces lots of traces files in temp folder.
After closer investigation I still see one advantage of "foo_out_asio+dsd" component over the stock "foo_out_asio" component, which is DSD playback: the latter transmits it with DoP (DSD over PCM) while the first component as DSD native. Of course, there is "DSD" set as the value of Type in the section Output (per device) in the Preferences > SACD option set. No conversion to PCM on-the-fly.
As I have mentioned - I have two DACs. The first displays that it is playing DSD input, the second - PCM, although receiving exactly the same material. When looking at the tab "Buffer settings" of ASIO driver settings, on both computers the "ASIO Status" section contains "ASIO active (PCM mode)". That means one thing - computer must be sending DoP to both DACs.
With the "asio+dsd" component both statuses are showing properly DSD stream and the second DAC also displays DSD as the input format.
This is the reason I'll be waiting for newer versions of the "asio_dsd" component, with the default value of "Output trace" set to 0 (zero), not 3, as it is currently.
This is fixed in 0.3.1. My fault, sorry for the inconvenience. Thank you!
Yes! No more trace log files! So asio+dsd component has returned to both of my systems.
And I can read "DSD mode" in ASIO driver buffer settings status and in DAC display. It must be DSD native again.
Many thanks, Maxim!
Now please close the ticket.