https://bugs.winehq.org/show_bug.cgi?id=43652
Bug ID: 43652 Summary: Engine Prime: no playback of tracks Product: Wine Version: 2.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: smidge@xsco.net Distribution: ---
Created attachment 59079 --> https://bugs.winehq.org/attachment.cgi?id=59079 Log file demonstrating no playback and no audio devices
Engine Prime is a music preparation application targeted at DJs who use Denon's latest hardware. It can be downloaded at http://www.denondj.com/engineprime
Engine Prime 1.0.0 starts up successfully if d3dcompiler_46.dll and d3dcompiler_47.dll are disabled. If a track is added to the collection, and then played, there is no playback. No errors are recorded.
Steps to reproduce:
* Clean wine prefix. * Install Engine Prime 1.0.0 (link above) * Copy an MP3 file of your choice to somewhere under drive_c. * Copy another MP3 file of your choice to somewhere else on your filesystem accessible via a drive mapped in Wine, e.g. the Z: drive * Start Engine Prime as follows: env WINEDLLOVERRIDES="d3dcompiler_46.dll=d;d3dcompiler_47.dll=d" wine ~/.wine/drive_c/Program\ Files\ (x86)/Engine\ Prime/EnginePrime.exe * Navigate to the filesystem browser * Choose an example track (at the time of writing, the file must be under C: drive - see bug #43651) * Right-click, choose Add To Collection * Double-click the file to load it into the deck * Allow track analysis to complete if it is still going * Press play
Expected outcome: the track plays Actual outcome: the application does not play the track, nor give any indication that it is playing or trying to play the track
Additional observations: * Navigate to the Preferences screen (the cog icon in the top right) * Observe that the "Default Device" for audio output is selected, but no info about bit depth or sample rate are shown. * Testing sound through winecfg demonstrates that sound does work in other wine applications
A terminal log capture is attached. The only line which suggests anything suspicious is the following, which is printed 20 times in a row when the application first starts up:
fixme:mmdevapi:MMDevice_Activate IID_IDeviceTopology unsupported
mmdevapi is one of the DLLs for the Core Audio API: https://msdn.microsoft.com/en-us/library/windows/desktop/dd316602(v=vs.85).a...
https://bugs.winehq.org/show_bug.cgi?id=43652
Adam Szmigin smidge@xsco.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |mmdevapi
https://bugs.winehq.org/show_bug.cgi?id=43652
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |43599
https://bugs.winehq.org/show_bug.cgi?id=43652
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download CC| |dark.shadow4@web.de
https://bugs.winehq.org/show_bug.cgi?id=43652
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.denondj.com/engi | |neprime Depends on| |43651
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Filling in a few fields.
https://bugs.winehq.org/show_bug.cgi?id=43652
--- Comment #2 from Adam Szmigin smidge@xsco.net --- The FIXME message is from dlls/mmdevapi/devenum.c, in the MMDevice_Activate function:
.. else if (IsEqualIID(riid, &IID_IDeviceTopology)) { FIXME("IID_IDeviceTopology unsupported\n"); } ..
Here is the DeviceTopology API docs: https://msdn.microsoft.com/en-us/library/windows/desktop/dd370809(v=vs.85).a...
https://bugs.winehq.org/show_bug.cgi?id=43652
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- It could be related, but it could also be a red herring. I don't know enough about it to be sure.
https://bugs.winehq.org/show_bug.cgi?id=43652
--- Comment #4 from Adam Szmigin smidge@xsco.net --- I'm trying to debug this issue using winedbg, but having issues even attaching.
$ winedbg EnginePrime.exe (this runs the app as usual, but does not ever give me the debug prompt to add breakpoints or step over, etc.)
Pressing Ctrl+C prints a message but never gives me the debug prompt either. The application itself is still usable: ^CCtrl-C: stopping debuggee
If I try to run the app and then attach, the debugger hangs:
(in one terminal) $ wine EnginePrime.exe
(other terminal) $ winedbg Wine-dbg>info process pid threads executable (all id:s are in hex) 00000030 58 'EnginePrime.exe' 0000004f 2 _ 'OfflineAnalyzer.exe' 0000004d 2 _ 'OfflineAnalyzer.exe' 0000004b 2 _ 'OfflineAnalyzer.exe' 00000049 2 _ 'OfflineAnalyzer.exe' 00000047 2 _ 'OfflineAnalyzer.exe' 00000045 2 _ 'OfflineAnalyzer.exe' 00000043 2 _ 'OfflineAnalyzer.exe' Wine-dbg>attach 0x30 (winedbg just hangs here)
The above commands seem to be as recommended in the Wine Developer's guide.
Any advice?
https://bugs.winehq.org/show_bug.cgi?id=43652 Bug 43652 depends on bug 43599, which changed state.
Bug 43599 Summary: Engine Prime 1.0.0 crashes due to HLSL compilation failure https://bugs.winehq.org/show_bug.cgi?id=43599
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
-
wine-bugs＠winehq.org -
WineHQ Bugzilla