Activity for papavlos
-
papavlos posted a comment on discussion Open Discussion
Thanks! It was not obvious because the sourceforge folder is named "macOS +Windows". I thought you are going to replace the "sacd" by "udsd". So there is no need to replace the "sacd" version. Thanks a lot Maxim for your great work!
-
Can you please explain what is the difference between the legacy "foo_input_sacd" and the just released new "foo_input_udsd" plugins? One thing just checked - both can not exist at the same time in the system. Starting playing a DSD file crashes fb2k. From configuration point of view they look the same. [edit] I mean both plugins are working, but only one of them can be installed at the time.
-
Can you please explain what is the difference between the legacy "foo_input_sacd" and the just released new "foo_input_udsd" plugins? One thing just checked - both can not exist at the same time in the system. Starting playing a DSD file crashes fb2k. From configuration point of view they look the same.
-
I didn't perform any completely fresh install, but the value "0" is consequently kept over multiple upgrades of foobar2000 and the asio+dsd plugin. So no more trace files, in my case. I'm still running fb2k 1.6.16 32-bit version, btw.
-
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.
-
Version 0.3.1 released. I confirm - no more trace files. Thanks! Please close the ticket.
-
Zero as the default value of "Output trace"
-
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,...
-
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...
-
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. Please let me know, should I have missed anything....
-
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.
-
@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....
1