Menu

#19 Whats wrong with my ASIO

1.0
open
None
2022-01-29
2021-03-09
mo phillips
No

I can only hear short bursts of 'hiss' and no music at all, and why do I have 'output_wasap2_playback::on_playback_stop - stop_reason_user' within the ASIO
I am using Realtek ASIO

1 Attachments

Discussion

<< < 1 2 3 (Page 3 of 3)
  • Didier Galardon

    Didier Galardon - 2021-04-16

    I will check this.
    concerning the new Asio2, I have still some work to do on it. May be in a week or two.

     
  • mo phillips

    mo phillips - 2021-04-16

    I was wondering why I didnt notice this before, because I have played the 2 albums before. So I went to check again and noticed that The tracks played normally IF I started from track 1 and let it proceed to 2>3>etc on its own without stopping. If I stop>start then I get the issues I reported earlier
    There was a similar issue earlier (2021-3-27) which you solved. These tracks are also cuesheet

     

    Last edit: mo phillips 2021-04-16
  • Didier Galardon

    Didier Galardon - 2021-04-18

    Hard to reproduce the problem, but I have fixed something related to control flow with mono tracks in the attached patch.

     
  • mo phillips

    mo phillips - 2021-04-18

    Not all the 1ch mono albums have issues. Only the 2.
    With the new Asio2:
    Chunk alignment UNchecked > Tracks play normally
    Chunk alignment checked > Tracks play normally IF buffer is 5ms or greater, lower than 5ms > then skipping(doesn't freeze at 0ms anymore)

     
  • Didier Galardon

    Didier Galardon - 2021-04-19

    something was wrong in code related to "
    Renderer::GetChunkAlignedCache - chunk size is now aligned on endpoint buffer size : can switch to alignment optimized playback...."

     
  • mo phillips

    mo phillips - 2021-04-19

    Thanks, it's fixed

     
  • HansWurst

    HansWurst - 2022-01-25

    Hi Didier,
    similar to mo philips I get a crash with my Realtek ASIO driver.
    There are two newer different Realtek ASIO drivers around afaik : v 1.0.0.7 and v1.0.0.8. As mo philips pointed out he used an older version, I tried both versions and both crashed.

    Both crash locations are:
    Symbol: "DllUnregisterServer" (+107CEh)

    Could you have a quick look at the log please?

    Maybe it's soley the REALTEK ASIO driver to blame. FiiO driver 5.22.0 works with fantastic sound adn no errors here...

    Thank you very much, still enyoing your fantastic ASIO2 here!

     

    Last edit: HansWurst 2022-01-25
  • Didier Galardon

    Didier Galardon - 2022-01-26

    Hi

    May be it is a regression in 2.0.1 (there was many bugs in asio2 with this driver , due to its specific asio buffer format, but normally they have been all fixed with the help of Mo Philips). Can you check this ? i.e testing if you have a crash with both 2.0.0 and 2.0.1 or only with 2.0.1.
    May you also send me:
    the console output with asio2 trace level set to 1
    the generated .dmp file if any.
    * a screeshot of your advanced settings (cache size,,..) and your asio driver latency settings.
    I will take a look next Week-end.

    Thanks

     
  • HansWurst

    HansWurst - 2022-01-29

    Here we go:

    I setup two versions of foobar portable 1.6.9

    ASIO 2.0.0

    Playing just stops but can be resumed by play button. foobar does not crash hence no report. But I was able to crash foobar by switching from my Fiio ASIO to the Realtek ASIO.

    Crash location:
    Module: KERNELBASE
    Offset: 12B522h
    Symbol: "RaiseException" (+62h)

    ASIO 2.0.1

    foobar crashes now and then. First log is from switching ASIO drivers as described above.

    Crash location:
    Module: KERNELBASE
    Offset: 12B522h
    Symbol: "RaiseException" (+62h)

    Second log is from crashing while playing

    Crash location:
    Module: RTHDASIO
    Offset: 194DEh
    Symbol: "DllUnregisterServer" (+107CEh)

    That's the main error I always see here.

    Buffer settings and ASIO settings were not altered between tests of 2.0.0 and 2.0.1

    Thanks for looking into this.

     
  • Didier Galardon

    Didier Galardon - 2022-01-29

    Hi,
    I have tried to reproduce your problems (using same latency, same cache size, and forcing 24 bits asio buffers) but sorry I can't.
    I cannot test the Reatek asio driver itself : not compatible with my laptop.
    the text crash report is not very useful. Normally when foobar crashes there is a file with .dmp suffix in the "<foobar installation="">\profile\crash report" folder. this one could be useful : I can load it in VS debugger. Do you have one and may you send it ?
    also, could you send me the full output of the foobar console when playing the track that works with asio2 2.0.0 but crashes with 2.0.1 ? I would like to check in the log how the cache is initialized and the sample chunk size too. </foobar>

    and last, just to be sure, regarding crash while playing:
    Do you start foobar with asio output already set to Realtek asio driver ?
    does 2.0.1 always crashes immediately when starting playing ? whatever the codec you use ?

    Thanks

     
<< < 1 2 3 (Page 3 of 3)

Log in to post a comment.