![]() "It would be great if you could have your customer playback the audio with ASIO. So far they have suggested using ASIO and helpfully provided the following: This image demonstrates that a 96kHz file is being downsampled (see the rate specified in the detail window for the audio file and the actual playback rate at the bottom of the Quad-Capture Control Panel):Īnd here is Foobar playing back a hi-rez file to the same sound card without problem:Īttempting to get some information from Roland for jiri on what they expect in terms of a query about sample rates. This is what I actually get (in this case the sound card is somehow locked at 44.1kHz): ![]() This is an image of the sample rates I expect to see in the drop down menu for WASAPI exclusive mode (as they appear on another PC, and as they appear if I select spdif output from the motherboard on the problematic PC): This has got me totally beat!Īppreciate any ideas that anyone might be able to share. I have uninstalled and reinstalled MMW and the sound card a number of times. So it looks like something to do with my PC or WASAPI on my PC. MM and Roland Support have been unable to duplicate the issue. And when MMW has locked the sound card, it is also locking the sample rate, so it can't be changed in the sound card control panel.įoobar doesn't have a problem with the sound card and the card switches automatically from sample rate to sample rate with Foobar with both ASIO and WASAPI whenever an audio file with a different sample rate is played. It doesn't seem to recognise that the sound card can cope with 44.1, 88.2, 96 and 192kHz, and if the active sample rate at the time is 44.1kHz, all hi-rez files are downsampled to that rate before passing to the sound card. MMW on the problematic PC will only send the file in the sample rate active in the Quad-Capture at the time. Three others in the house and MMW recognises the sample rate ranges for the sound card correctly and in exclusive mode passes through hi-rez files unmolested for the sound card to decode without any problems. This is a problem on just one of our PCs (unfortunately the main one I use!). I turned off all the other check boxes there for fades and stuff. I've not converted my Naim to 192/24 so I'm running on 96/24. I tried various things, eventually leaving it on exclusive mode. Unfortunately I didn't note what they were to start with. ![]() However I did dick around with the settings, and that seems to have remedied my problem. I do have all the bit rates/ widths there still. I looked at the MM output settings and the high res formats are still there, for me, so I don't have the problem you're reporting there. The source FLAC is clean and my NAIM hasn't changed. ![]() I found that I was getting some artefacts in the sound now and then, sort of like digital decoding problems. WASAPI has been fine until this new release. Before the WASAPI plugin I couldn't get the quality from MM, so I used a uPnP server to squirt bits the player. I use WASAPI to pipe bits to my NAIM because I don't want Windows mucking with the sound. I just upgraded and noticed some issues with my wasapi output, since 4. Unless someone has discovered another workaround, then I might have to downgrade. I suspect, therefore, that Wasapi is broken in the latest version on MM. My sound card is a Roland Quad-Capture and capable of playing all the hi-rez formats, which it did happily in v.1709. None of the hi-rez formats are present where they did used to appear in v.1709. ![]() When I checked the Wasapi config, in the drop down menu under the check box for Exclusive mode, the only choices available are: All I am getting sent to my sound card when Exclusive mode is selected, is 44.1KHz, irrespective of whether I play 44.1, 88.2, 96 or 192KHz files. However, there seems a whole other problem. I had understood that Wasapi was to have been fixed in the update - the one released over the last day or two, v4. There is a workaround so that you can still get your bit-perfect playback of music, including hi-rez files, by disabling Event mode in the Advanced Settings of the Wasapi configuration window. =1&t=76979 concerns the breaking of Wasapi playback in Exclusive mode in MM v.1709. ![]()
0 Comments
Leave a Reply. |