Jump to content

Mark Dirac

Members
  • Content Count

    75
  • Joined

  • Last visited

About Mark Dirac

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks David. That's very helpful to know. Don't be so quick with your sarcasm Chris @The Computer Audiophile. That's well over 3 hours of my life lost. I have been a loyal and constructive supporter of Qobuz for years, including paying them $1,000 during the years when their fees were high and their financial stability low. This Chromecast problem has been extant for years. I have spent hours doing my own fault-finding, researching the problem on the web, testing if the problem is with Qobuz, Google, Windows or my PC, and having several lengthy phone conversations with Google. At all times I have taken great pains (and time Chris) to ensure that my written reports are clear, unambiguous and comprehensive, in order to assist Google and Qobuz in working towards a solution. So, here's a suggestion: There are long-standing bugs in the Qobuz ecosystem. Would it be so difficult to provide a good-old simple bug list of the most common outstanding problems, to save customers needing to spend so much time researching the issues they encounter? The list doesn't need to include petty bugs, or rare bugs, or short-term easily-fixed bugs. But a list of a dozen or so of the problems which Qobuz's customers are encountering time and time again would be a appreciative response to customers filing support requests and getting nowhere.
  2. Well, that was a complete waste of time on my part then - taking a screenshot & posting it here and three conversations with support, which I wrongly imagined were helpful.
  3. This problem also occurs for me from Windows 10. I also get a bewildering message: "The current session on chromecast is not synchronizable with the player, do you still want to start listening?" (see attached screenshot) Easily-repeatedly, and for years. It's a strange problem: As you say, Qobuz support seem to be completely unable to understand the problem. I reckon the few people I spoke with have no idea at all what a Chromecast is. When I reported it here before, there was no interest. No one else seemed to have noticed the problem. But someone was interested in telling me that I shouldn't use Windows. So, years later, it is disappointing that such a potentially attractive way of connecting from a PC (or Mac) to a DAC - and at 96k/24bit - is such a massive distraction from getting on and just listening to some music. I would be grateful if at least @David Craffcould explain the error message please, and perhaps why is doesn't work and if there's any workaround. Or, in what limited circumstances it does work?
  4. Good question. Long ago, one of the qobuz boys said "yes", and to report them here. But that's just too inefficient a process - there are far too many to be processed via this forum. I reported a couple to the support desk, but was treated like a child and so have given up. If qobuz set up some reporting mechanism for enthusiasts such as us, I could imagine we could provide a worthwhile crowd service to Qobuz.
  5. Has anyone found / proved that we can use a USB flash drive or SD card for the cache and imports? I don't see the need to use my SSD, and would like the max allowable 100GB cache space. Since speed and reliability are not important for cache and importing, does it work to use cheap external storage? (I don't want to check it out myself 'cos I will lose my current cache and I guess I will need to attach a fixed drive letter to a USB drive.)
  6. Intriguing. My Qobuz application (Windows 10) doesn't do this. Are you on Apple? Does something need to be enabled?
  7. Thanks for that suggestion. How ridiculous that one would need to "remember this one" when wanting to listen to some music. Qobuz (and Tidal) are really fantastic, but there is a severe cost. Every time I settle down to listen to some music, I half-expect to have to spend some of my time in IT fault-finding. Windows quirks, or sound settings quirks, or flaky applications, or internet issues (which in turns breaks down to ISP, copper line provider, router, wifi, and now DNS provider!). The last time this happened, it took me 15 minutes to identify that I just needed to turn my DAC off and on again, a "fix" which has never ever happened before on that one component in the long, convoluted and flaky chain. Not surprising that normal people prefer to listen "on Alexa".
  8. I am still having some distractions following the new release(s) last week - I hear occasional short, not-loud clicks on some tracks. Perhaps 20 or 30 per track. Worse on hi-res tracks. Never happened before (this new release) in one year with Qobuz on 3 PCs and two DACs. Any ideas please? Windows 10 application, WASAPI Exclusive Mode, 70Mbps broadband, recent good-quality i5-8xxxU laptop, SSD, Pro-Ject S2 Digital DAC via USB. (I also experienced some of the other problems reported here - freezing, "not responding" - but those have since evaporated.)
  9. Oops. I carelessly posted a feature request in the "Qobuz issues" thread:
  10. There is a more general usability disappointment in the Windows application, in that it is always (usually?) the case that if you navigate away from a page to investigate something, when you return your context/place is lost. For example, when scrolling through a long playlist, the same happens as reported by Mr. Polyglot above with searching - if you check out an entry in your playlist, and then return, you are returned to the top of the playlist listing, and have to navigate back down again to where you started.
  11. I enjoyed listening to MQA from Tidal without difficulty for months - until I switched to Qobuz. I didn't switch to Qobuz because of bugs affecting MQA playback, but because I became jaded with trying to penetrate the obfuscation surrounding MQA. MQA for me is an extra level of complexity in an already-complex process of reproducing digitally-streamed music well. And MQA the organisation are too duplicitous in their explanations of what's going on. They have made an abstruse technology even more awkward to embrace. So, whilst my comment doesn't assist Jumpwire's with his MQA hassle, I am answering his original question "Is no one using MQA decoding with this DAC?".
  12. Yes. Very easy, cheap and effective: https://www.aliexpress.com/item/4-8V-6V-Battery-Box-With-Switch-4-AA-Batteries-Stack-USB-Battery-Storage-Clip-Holder/32820217325.html This is a simple battery box for four 1.2V NiMH cells, with a USB connector. £2 from AliExpress. The fully-charged voltage is 5.45V, and falls immediately to 5.3V when connected (and under load), which I believe is only slightly above USB voltage specs. Anyway, the S2D doesn't complain or get warm at 5.3V. The box supplies power for about 2 hours using 2900mAh NiMH cells. The S2D misbehaves when the voltage falls to about 4.5V This is such a cheap solution that I have two. When one runs out, I plug in the other and recharge. Simple, if inconvenient. No switching. No regulators. No mains noise. No common-mode noise.
×
×
  • Create New...