Menu

#58 Problem with DSDTascoder

1.x.x
open
nobody
None
1
2022-10-15
2020-11-02
Anonymous
No

Good evening, it was a while that I wanted to ask this question and finally I decided: D in a nutshell to play native dsd the only way is to use the output module DSDTrascoder and in this regard I wanted to ask why if I make a compilation of different songs when you switch from one frequency to another almost always playback stops while if I use another output module this does not happen, is it just my problem or is it normal?
Thanks

Discussion

1 2 > >> (Page 1 of 2)
  • Maxim V.Anisiutkin

    It does work with only some ASIO drivers. Could I have a look on transcoder log file at level 3 for such switches?

     
  • Anonymous

    Anonymous - 2020-11-03

    Thank you so much for your reply, the dac is a Gustard A18 and the drivers are these taken in this site, version 4.86 https://download.shenzhenaudio.com/#all I don't know how to send you the log file, you can Please explain? Anyway as I said it only stops when there are frequency changes and not always, otherwise can I use another output module instead of DSDTrascoder to send to native dac dsd? I tried asio proxy with foo_dsd_asio module but not does it work, otherwise if i use dsd processor? with dsd processor send native dsd? What output module should i use with dsd processor to send native dsd?
    Thanks

     
  • Maxim V.Anisiutkin

    You can attach log file here. Go to DSD Transcoder control panel, select "Level 3" at "Trace Output", press "Save As..." and enter trace file name. The only way to get native DSD from foo_input_sacd plugin v 1.x.x is to use DSD Transcoder. DSD processor outputs in DoP as well.

     
  • Anonymous

    Anonymous - 2020-11-03

    Thank you so much for your availability, I am attaching the .trc file ..... let's say that this could also be fine as as long as I listen to an entire album without variations there are no problems but I often listen to compilations and put both pcm and dsd songs different frequencies, if you could fix this it would be great. How do I attach the file, I can't find the option ....
    Thanks

     
  • Anonymous

    Anonymous - 2020-11-03

    I am attaching another file as the one I put I saved as soon as I turned on foobar without having done any reproduction, this one that I am attaching now instead the compilation stopped when it had to switch from a dsd64 to a dsd128, in this case they are two dsd files but it also happens when you switch from a dsd to a pcm ...... In the DSDTrascoder options window there are some ticks, sample position override and Async driver calls, how should they fit?
    Thanks

     
  • Maxim V.Anisiutkin

    Unfortunately both logs logs only show that control panel was run and no other info. Could you please try make trace in this way:
    1. Set the name of trace file.
    2. Exit foobar and delete trace file. It will be created on the next run.
    3. Run foobar and try to switch between tracks.
    4. After you get an error exit foobar.
    5. Attach trace file here.

     
  • Anonymous

    Anonymous - 2020-11-04

    It will seem strange to you but this morning I started doing tests after tests and it never stopped, as soon as it happens again I will send the file, in the meantime I have obtained these two and I will send them to you in case they may be useful to you ..... cmq yesterday I could see that the DSDTrascoder output module works very well, it never ticks when it goes from one song to another (almost always happens with dsd) and the asio driver window of my dac changes writing when I play a dsd writes dsd-mode, when I switch to a pcm it writes pcm-mode, with any other output module other than DSDTrascoder always writes pcm-mode ........ now what I wanted to understand is if there are differences between sending the flow of dsd in DOP or in native, in my opinion there are no differences ......!

     
  • Anonymous

    Anonymous - 2020-11-04

    Here are the attachments

     
  • Anonymous

    Anonymous - 2020-11-04

    I'm sorry but I can't send the register attachments because they weigh 57 and 42 megs .... I don't know why they came so big

     
  • Maxim V.Anisiutkin

    At Level 3 they grow pretty fast and their length is a kind of proportional to total playback time. Can be zipped very much. Or trace can be done at Level 2. Small size, but less informative.

     
  • Anonymous

    Anonymous - 2020-11-04

    Hello and thanks again for your availability, I zipped the two files but with these there was no interruption and even tonight I listened for almost two hours where I put all mixed songs between dsd and pcm of different frequencies and it never skipped , if it were always like this it would be fantastic, anyway as soon as the defect reappears I will send you the file, for now see if you can get something from these. doing.....
    Thanks

     
  • Maxim V.Anisiutkin

    Thanks for testing. As is seen from the last traces "Async driver calls" checkbox is not ticked.

     
  • Anonymous

    Anonymous - 2020-11-05

    Yes, I keep it unchecked also because yesterday it never stopped ...... but I was wondering what that function is for ....
    Thanks

     
  • Anonymous

    Anonymous - 2020-11-05

    Anyway returning to the native DSD discourse in the manual of my dac (Gustard A18) it says to use ASIOProxy, I downloaded this version 0.9.4 https://sourceforge.net/projects/sacddecoder/files/foo_dsd_asio/ but I don't get native dsd but always dop, I don't know if I'm wrong something, the only one with which I get native dsd is DSDTrascoder https://sourceforge.net/projects/sacddecoder/files/dsd_transcoder/ and I put the latest version you released, 1.1.0
    Thanks

     
  • Anonymous

    Anonymous - 2020-11-06

    Hi, sorry for the trouble again, this evening it often stopped, I created a mixed compilation on purpose and got this information, I am sending it to you hoping that it will be useful to understand the problem.
    Thanks

     
  • Maxim V.Anisiutkin

    Thank you, traces were quite informative. I've prepared v. 1.1.0-6 and put in interim folder. Would be nice to see traces when foobar switches between tracks (even if doesn't stop with error).

     
  • Anonymous

    Anonymous - 2020-11-07

    Thank you so much, I try it and I will let you know .....

     
  • Anonymous

    Anonymous - 2020-11-08

    So, I installed the DSDTrascoder 1.1.0-6 and for the whole listening period it never stopped, I made a mixed compilation putting all dsd and pcm of different frequencies one after the other, I will do other tests but if so you solved the problem and I give you my most sincere congratulations ... Now I wanted to ask you something and sorry if maybe it is a trivial question, I could only install the DSDTrascoder component and the dac drivers or DSDTrascoder always needs the foo_input_sacd plugin to work?
    Thank you so much for your availability

     
  • Maxim V.Anisiutkin

    Thanks! Could you give me trace for 1.1.0-6, please? Need to see how switching between tracks goes now. DSDTranscoder doesn't need neither foo_input_sacd, nor foobar2000. It works with J River MC, for example.

     
  • Anonymous

    Anonymous - 2020-11-08

    Thank you so much, by tonight if I can I will send you the new log file, this thing I did not know, so since my dac accepts native dsd up to 512 and pcm up to 32/768 I can safely remove both foo_input_sacd and AsioProxy? I knew it worked too son Jriver even if Jriver tried it more than once but I prefer Foobar .....
    Thanks

     
  • Anonymous

    Anonymous - 2020-11-08

    Hi, here is the file you asked me, everything went ok, I don't know if it recorded a foobar crack but it was due to the fact that I went too fast in forwarding the tracks, as for the problem that stops when it changes frequency or from a dsd / pcm or pcm / dsd it never stopped ...... I would say that now the DSDTrascoder is fine, congratulations to you for solving this thing.
    Regards

     
  • Maxim V.Anisiutkin

    Trace looks good. If transcoder works well you don't need ASIOProxy any more.

     
    • uriele jonah haydn

      installed dsd plug in 1.2.4 and it doesn't recognize the version installed and it won't ask to upgrade but to install a new package then, upon restart..

      "Failed to load DLL: foo_input_sacd.dll
      Reason: This component is missing a required dependency, or was made for different version of foobar2000."

       
      • Anonymous

        Anonymous - 2020-11-08

        Have the same problem! foobar2000 v.1.6.2. MSVC+ 14.0, Win10 x64

         
  • Maxim V.Anisiutkin

    What foobar2000 version do you use? Plugin needs v1.4 and up and MSVC 14.0 runtime.

     
1 2 > >> (Page 1 of 2)

Anonymous
Anonymous

Add attachments
Cancel