But sound quality is top notch, so I can live with that. With DVD-Audio I have had a couple of crashes when navigating to another track. SACD is playing perfectly with sound quality on par with a dedicated SACD player. I have had a few Foobar2000 crashes, especially with SIMD instructions enabled, even though my processor support SSE41.īut now everything is working with PCM, SACD and DVD-Audio playback. beta5 plugin (Asio only update) and disabled SIMD instructions and Visualisations, as well as did a manual setup of "end point buffer sizes" in Foobar2000 advanced preferences (according to hardware specs). The stereo perspective is "big" with voices and instuments placed in 3D across stereo perspective.įirst, I installed your official Asio2 1.1 beta2 plugin, but was having issues with playback (Foobar2000 crashes, no automatic shift in sample rate, sample rate locked, etc.).
Sound quality is better all over the frequency spectrum compared to the official Asio component, but I especially notice an improvement of sound stage, image, low end and high end clarity and details. Now with the Asio2 1.1 beta5 (see post #2 above), Foobar2000 sound quality is on par with or maybe even a little bit better than MPC-HC. Google: multichannel directshow asio renderer (version 2.0 is free) I just recently installed your plugin, because I discovered that MPC-HC had better sound quality with the Multichannel Directshow Asio Renderer than Foobar2000 with the official Asio component (same experience as M Z writes about in the post above). Thanks for this high-end WASAP2 & ASIO2 plugin for Foobar2000 :-)
Do you see the foo_out_wasap2 plugin in the foobar component config (see attached screenshot) ? If not, can you copy again wasap2.dll in the component folder of your foobar installation ? In that situation, the asio2 plugin cannot use any other endpoint buffer size configured explicitely in the advanced plugin config, but use the returned preferred size instead.Ĭoncerning your third issue: it seems strange. The asio driver returns that it supports only buffer size falling within the interval defined by min and max value, i.e. Renderer::init_asio_static_data - ASIOGetBufferSize (min:544, max:544, preferred:544, granularity:0) Concerning your 1st issue (sound corrupted while switching to a track with different sample rate): I think that the problem occurs because while initializing the asio driver, I am querying the driver for asio buffer size before setting the driver sample rate according to the track one: give a try to the attached patch: I have change the order and now set the sample rate before querying driver for buffer size.Ĭoncerning your 2nd issue: the limitation comes from your asio driver: you can see it in the log:
0 kommentar(er)
