Jump to content

Mark Dirac

  • Posts

    149
  • Joined

  • Last visited

  • Country

    United Kingdom

Retained

  • Member Title
    Newbie

Recent Profile Visitors

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

  1. What a pity that Android requires the app to select bit-perfect, rather than the user. (Because that imposes on developers the need to change their apps.) @thegios could you check please if there's a switch in Android's "Developer options", because there are currently all manner of switches to play with in there, regarding sample rates and stuff.
  2. I'm listening to the coronation of the British king Charles III on BBC iPlayer through a crappy Samsung TV to RME DAC-2 FS. What an imaginative programme! (Not an album yet.) And a spectacular, impeccable, technically superlative recording by BBC
  3. For those interested in trying to picture this, here's a screenshot of the new "share" step...
  4. Thanks for letting us know David. I can now stop wasting time on investigating what is going on (50 minutes incl. my post.) Please don't fall into the trap of pandering to every IT nerd's latest Big Idea. One of the the big attractions of Qobuz is its avoidance of gimmick. People are always saying that what they want to do is to enjoy music, not to be distracted by IT B*****ks. And this is exactly what you are doing here. The added value of being able to share a track to Meta is negligible, but the cost is that it has ruined my afternoon of music, and slows down every future attempt to share a track or album in true hires (BUPP) on Android.
  5. Facebook Instagram Stories hijacks Qobuz share menu For years I have used the wonderful feature of using "share" to "send" a track or album to BubbleUPnP. It takes a couple of taps and is a little laggy, but no complaints. Today, when I "share", an extra menu step is introduced offering me "Facebook stories" and "Instagram stories" and then "more". Nasty!! The result is that sending tracks to BUPP is now slow and needs three taps. This seems to be a Qobuz thing - it was happening on two of my (Android) phones, but not my (Android) tablet. When I updated the tablet's Qobuz app, it started happening there also. What a nasty imposition! Like standing in line, and Meta elbowing their way in front of you without even an "excuse me". Is anyone else aware of this, and@David Craffable to stop it?
  6. Oh dear. I have been looking forward to using Qobuz Connect with my Pi for years. I assumed it would essentially use UPnP. But is it really likely to use some proprietary protocol which requires new software for our players? Groan.
  7. David Craff - I suspect that you may not be aware that the annual renewal process is not as transparent as one would expect, and is not as one experiences with other reputable service providers. I noticed that it is not possible to delete a payment method / credit card. It is only possible to update it. I was not given any notice that my annual renewal was due, or that £130 was to be debited, or the date on which this would happen. Qobuz took £130 but without telling me that that had happened, nor even telling me that my subscription had been renewed for a year. No notification whatsoever. Despite being very happy to pay £130 for a further 12 months, I am surprised that Qobuz appeared to do this with stealth.
  8. Very similar. Essentially identical. I'm using a tablet, which would probably explain some layout differences. I've just tried to reproduce the phenomenon now, and cannot: When I close the Qobuz (Android) app using the Android back button, the player in the notification window persists. But when I close the Qobuz app by swiping it away in the Android "app chooser", then the player "notification" disappears. Perhaps my app has been updated and has partially solved the phenomenon. (I say "phenomenon" because fortunately for me it's not a "problem" or "issue".)
  9. Yes. For a few months, after closing the Qobuz Android app, the mini player in the persistent notifications continues. I cannot get rid of it except by restarting. I have never noticed that this is correlated to my use of Bubble UPnP, which I use a lot. I rarely use UAPP, but have it installed.
  10. Rando! Don't be so rude! Please withdraw this unnecessarily aggressive slur and apologise to me.
  11. I reckon it to be a tragedy that this thread was originally called "Qobuz issues". It is a very popular thread, and outsiders are always seeing posts about Qobuz issues. But not, for example, Tidal issues. And that is definitely not because Tidal have no issues! In practice, this is the Qubuz chit chat thread, except that there is a skew away from Qobuz compliments and Qobuz queries ( not issues) and Qobuz neutral comments, because of this unfortunate thread title. It's unfair on Qobuz.
  12. I've had minor problems today with BubbleUPnP and moOde, and (after being distracted from listening to music) had decided that it was probably a temporary Qobuz glitch.
  13. The app called BubbleUPnP (Android) works well for me and others, controlling the app called moOde running on RPi. Mconnect also works instead of BubbleUPnP. They are clunky, with cursory instructions, but eventually functional. Roon seems, to me, to be an unnecessary complication and expense.
  14. Hello Alex. There is an existing thread about this issue, here: I thought that the problem had gone away, after plaguing a few users for years (it has for me), but perhaps not. Do you get the problem even at CD bit rates, or only at hi res rates?
×
×
  • Create New...