[Bug 28174] New: winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Summary: winecfg: audio settings don't take effect until
                    winecfg is closed
           Product: Wine
           Version: 1.3.26
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Keywords: download, source
          Severity: normal
          Priority: P2
         Component: programs
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Start up winecfg, and test your sound. Assuming it works, pick some broken
settings (e.g., OSS instead of alsa for me). Test sound, still works. Close
winecfg, restart it. Test sound, test will fail. Enabling ALSA at this point
won't fix sound until winecfg is restarted.

Makes sound testing a bit annoying, especially if you don't know to do it :).

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Andrew Eikum  changed:

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

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Raymond  changed:

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

--- Comment #1 from Raymond  2011-08-25 03:51:23 CDT ---
AFAIK , wine's registry still keep a lot of entries (e.g. card which had been
physcially removed) , those mmdevapi openal devices  which stored by mmdevapi
in previous version

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Andrew Eikum  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Andrew Eikum  2011-09-01 12:13:22 CDT ---
I guess INVALID is the best resolution status after
dfe73cda4a6c08911deacb09d2752545ab32849f :)

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |WONTFIX

--- Comment #3 from Austin English  2011-09-01 12:33:03 CDT ---
(In reply to comment #2)
> I guess INVALID is the best resolution status after
> dfe73cda4a6c08911deacb09d2752545ab32849f :)

WONTFIX is more appropriate.

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

--- Comment #4 from Raymond  2011-09-01 19:32:00 CDT ---
The patch raise another problem

- user does not know which midi in and midi out devices are available

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #5 from Austin English  2011-09-22 13:31:30 CDT ---
Closing.

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Andrew Eikum  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |REOPENED
         Resolution|WONTFIX                     |

--- Comment #6 from Andrew Eikum  2011-10-28 14:22:13 CDT ---
Back again thanks to 00629cb0b3c7c3b25d8ccbfc56755344dc9a1e89. Like I explained
in the patch notes:

I originally did this so that the user's changes to the Audio tab
would take effect without having to relaunch winecfg. However, this
causes crashes with WinMM's internal devices thread. I think we should
be using MMDevAPI's IMMNotificationClient within WinMM to be informed
when the device default changes, but obviously this needs more tests.

So this commit fixes the crashy behavior, but goes back to requiring a
winecfg relaunch to have the settings take effect. After we implement
IMMNotificationClient, we can do this correctly.

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Andrew Eikum  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
      Fixed by SHA1|                            |4ab4bc5d095647ad1e4ca30c274
                   |                            |9f0e3c337ad9d
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #7 from Andrew Eikum  2012-12-26 14:17:11 CST ---
We have an IMMNotificationImplementation implemented, and this is fixed by
4ab4bc5d095647ad1e4ca30c2749f0e3c337ad9d. There are a couple more patches in
the series to re-route existing streams to the new default device, but that
commit is enough to fix winecfg.

[Bug 28174] winecfg: audio settings don't take effect until winecfg is closed

http://bugs.winehq.org/show_bug.cgi?id=28174

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #8 from Alexandre Julliard  2013-01-04 15:01:04 CST ---
Closing bugs fixed in 1.5.21.