In any case, MC appears to be taking the "unintentional" out of my hands and doing it automatically, which isn't so great. ![]() Might have done it with Audirvana at some point, too, but I'm not sure right now. I've unintentionally forced this odd static to happen while playing with PureMusic's settings. ![]() If MC is messing up those rates for you, like it is for me, it's probably going to create a DoP stream that's wrong and will cause the DAC to do weird things, including play static (be it solo static or overlapping with music). I'm hoping that you have one/some DSD files that aren't genuinely 384kHz for the purposes of these questions, since I don't have any - so when my copy of MC is telling me that my DSD files are 384kHz, I know it's wrong. ![]() The sample rate should be 2.8MHz for DSDx1 and 5.6MHz for DSDx2, and bitrate is probably 176kHz, 192kHz, or 384kHz (I've only seen a very few DSD files as 96kHz though obviously it's technically possible for one to exist at any of the usual bitrates). Just out of curiosity, what's the correct sample/bit-rate on your DSD files (generally speaking)? What does MC claim for both rates when it's playing any of those files? What does it claim the sample rate is in the "panes" view for the track info? Are you able to play those same files with different software e.g., Audirvana or PureMusic, being the only other two players for OS X I know of that can handle DSD? If so, what does that software claim for sample/bit-rate? Although it could logically be related to the cause of the static, it's not clear at this time whether that's the case. That said, I should probably start a new thread on the topic. I installed MC 18.0.219 and it exhibits the same dsf-misreading behavior. This is reinforced by the ability to tell MC not to downsample the 384kHz stream, at which point it tries to send a 384kHz stream to the DAC and the DAC driver returns an error message stating that 384kHz isn't a supported rate (meaning, somehow MC is sending a 384kHz datastream even though the original source file on disk is only 192kHz). It seems like this misreading of critical information could plausibly cause the DSD data stream to be incorrectly modified and then sent to the DAC. The bigger concern now, for me anyway, is that MC is quite clearly not getting the sample/bit rate numbers correct on dsf files, and it's not just a cosmetic issue since I can see it causing MC to activate DSP downsampling when it thinks a file is 384kHz (it's really only 192kHz). If they could fix the issue in the driver, that'd be fine, though. And since no other software (Audirvana, PureMusic) exhibits the static problem, I don't (currently) believe it's an issue solely attributable to the Chordette's USB driver. I can avoid the configuration where the static occurs just by not using DoP for now. (Audirvana and PureMusic read these DSD files correctly, for what it's worth.) If MC isn't reading the sample/bit-rates correctly from the files, who knows what it's actually sending to the DAC. Unfortunately, downgrading MC doesn't seem to be a very straightforward process (or at least not an obvious one) as I'll either end up with a prematurely expired trial period or have to use up another restore credit.Īnyway, this might turn out to be an issue separate from the static problem, or maybe not. The first version of MC I installed, if I recall correctly, was 19.0.76, and I'm nearly certain it didn't have this DSD identification problem (although clearly my memory isn't playing fair). I suspect that bug is at least partially responsible for the static, at least on my setup.Ĭhecked my other computer running OS X 10.8.4 and MC 19.0.88 still in trial mode, with the same DSD files, and that system/version is misreading the sample- and bit-rates, too. What's up with that bit/sample rate doubling, I wonder. I requested, and got, a trial extension which I gave to MC's dialog box, it accepted it, the program quit on its own, and upon relaunch it was still in "demo expired" mode and no option to extend the trial period was given - only cancel, purchase, or recover license.) ![]() (I wasn't able to get MC working in demo mode again, however, since it decided that my trial period had expired. Removed all traces of MC from the computer and reinstalled MC, to no avail. Needless to say, this makes things behave oddly and kicks in MC's DSP engine (bleh) since my DAC can't process DSD128/384kHz. Once I registered, also today, and changed nothing else, now MC is incorrectly identifying the bitrate and samplerate of DSD files - doubling them, in fact e.g., a file known to be DSD64/192kHz is being shown by MC as DSD128/384kHz. The demo version of MC worked perfectly for me today prior to registering it. Chordette Qute DAC, OS X 10.9, MC Mac 19.0.88.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |