http://bugs.winehq.org/show_bug.cgi?id=25329 --- Comment #34 from Wehrwolfmann <wehrwolfmann@gmail.com> --- Your branch helps on a second game here, and without the gstreamer change. Sacred Gold (Steam appid 12320) plays eight .wmv intros, WMV3 video with WMA2 audio; one of them, introuw.wmv, is WMA Pro at 48 kHz. On stock 11.18 the ASF media type is not registered, so the graph is built through File Source (Async.) and the GStreamer splitter, and both pins connect. Once the ASF media type is registered the way your branch registers it, stock 11.18 picks the WM ASF Reader, {187463a0-5bb7-11d3-acbe-0080c75e246e}, and then renders only its first output pin: FilterGraph2_RenderEx <- called exactly once FILTER "Source" PIN Raw Video 0 dir=out CONNECTED PIN Raw Audio 1 dir=out *** NOT CONNECTED *** FILTER "0001" PIN Audio Input pin (rendered) dir=in *** NOT CONNECTED *** Same binary, same file, same prefix; the only difference is that one registry entry. With your branch, on a fresh prefix, RenderEx is called twice, both WMAudio Decoder DMO and WMVideo Decoder DMO are in the graph, Raw Video and Raw Audio both connect, and the intro plays with sound. The same holds for the WMA Pro file. I did not need the gstreamer merge request: this box has gst-plugins-ugly 1.28.7 with asfdemux. Two notes on the WIP commit "amstream: Render all source Pins", in case they save you time: - dlls/amstream/multimedia.c sets ret = S_OK unconditionally after the loop over the pins, which hides failures. On a path with nothing to render, stock 11.18 returns VFW_E_CANNOT_CONNECT (0x80040217) while the branch returns S_OK. dlls/amstream/tests/amstream.c expects VFW_E_CANNOT_CONNECT in two places, so the tests should catch it once they run; I built with tests disabled and did not run winetest myself. - MAX_STREAMS is a fixed 10 rather than growing with the number of pins. The "renders only the first output pin" behaviour is filed separately as bug 60156, with a patch and a test attached there; it may be worth linking the two. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.