[Bug 55090] New: Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

Bug ID: 55090
           Summary: Foobar2000 v2.0: Play button needs to be pressed twice
                    after stop for playback
           Product: Wine
           Version: 8.10
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 74647
  --> https://bugs.winehq.org/attachment.cgi?id=74647
An edited snippet of the logs

Steps to reproduce:

- Install Wine 8.10-103 (compiled it this morning)
- Install foobar2000 via the installer on their site:
https://www.foobar2000.org/
- Put a song in a playlist
- Press play (the triangle button); a tiny snippet of the song will play and
then it will stop.
- Press play again; the music plays properly this time.

You can make this happen again by pressing stop (square button); you need to
press play twice for the song to properly play.

See the attached log snippet (which is marked up with what the user is doing).
Note that it's trying to do something at address `0000000012345678`...

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

--- Comment #1 from Petrichor Park  ---
The amount played doesn't seem to depend on the size of the buffer at all.

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

--- Comment #2 from Petrichor Park  ---
This *might* be a duplicate of this?

https://bugs.winehq.org/show_bug.cgi?id=53486

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

Jinoh Kang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Jinoh Kang  ---
(In reply to Petrichor Park from comment #2)
> This *might* be a duplicate of this?
>
> https://bugs.winehq.org/show_bug.cgi?id=53486

Does foobar2k raise an exception internally after some I/O failure? If then, it
may be related. Otherwise I'm not so sure about that.

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

--- Comment #4 from Petrichor Park  ---
Created attachment 74667
  --> https://bugs.winehq.org/attachment.cgi?id=74667
Log with WINEDEBUG=+seh

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

--- Comment #5 from Petrichor Park  ---
Hello Jinoh, I was thinking about emailing you actually.

I just attached a log with WINEDEBUG=+seh; although I'm not super sure what
points in the log correspond to what I did, it does seem like there are
exceptions thrown on both successful and unsuccessful plays.

In the log, I opened fb2k, played a song (and it stopped), played it again,
stopped it, and closed fb2k.

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

--- Comment #6 from Petrichor Park  ---
Unless I'm missing something, the code in your merge request #617 hasn't been
modified since it was merged. So it doesn't look like there was a regression.

https://gitlab.winehq.org/wine/wine/-/merge_requests/617

[Bug 55090] Foobar2000 v2.0: Play button needs to be pressed twice after stop for playback

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=55090

--- Comment #7 from Jinoh Kang  ---
(In reply to Petrichor Park from comment #0)
> Note that it's trying to do something at address
> `0000000012345678`...

0x12345678 is just a dummy value returned by Wine's
AvSetMmThreadCharacteristicsW stub.

Since you didn't use the UPnP plugin and only performed local playback, this is
unlikely to be a socket I/O problem.

Have you tried enabling debug channels from audio/media-related DLLs?