Playback catching up with cacheing and playback stops

Studio
1

|Just installed new version of studio
When i select a track to play from Qobuz it caches so slowly that the playback catches up with it and stops when it has nothing there to play. I haven’t changed anything in my system (Windows 10 into RME Dac) which has been working fine for at least a year.
I have uninstalled and reinstalled Studio. Turned everything on and off,
Broadband speed 83 mb/sec.

No change. Unusable on Qobuz but local files are fine.

Help please.

Here is the log:

2024-02-08 12:19:34.642 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:19:35.250 [error]: Not logged to Audirvana account: need to sign in
2024-02-08 12:19:36.113 [info]: RemoteServer: Server started and advertised on port 51359
2024-02-08 12:19:45.103 [info]: UPnP stack initialized using default interface
2024-02-08 12:19:45.322 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:22:13.427 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:22:49.264 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:22:50.790 [info]: UPnP stack initialized using default interface
2024-02-08 12:22:50.913 [info]: RemoteServer: Server started and advertised on port 51405
2024-02-08 12:22:50.994 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:24:17.182 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 12:24:17.890 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:24:27.007 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:24:28.598 [info]: UPnP stack initialized using default interface
2024-02-08 12:24:28.722 [info]: RemoteServer: Server started and advertised on port 51442
2024-02-08 12:24:28.808 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:24:55.496 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 12:26:41.052 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:28:14.875 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 12:28:52.595 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:30:42.595 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:30:44.384 [info]: UPnP stack initialized using default interface
2024-02-08 12:30:44.455 [info]: RemoteServer: Server started and advertised on port 49755
2024-02-08 12:30:44.607 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:31:05.486 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 12:32:42.181 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:32:47.147 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:32:48.774 [info]: UPnP stack initialized using default interface
2024-02-08 12:32:48.888 [info]: RemoteServer: Server started and advertised on port 49915
2024-02-08 12:32:48.998 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:33:14.379 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:33:15.800 [debug]: PlaybackController: setActivePlayQueuelocal
2024-02-08 12:33:15.912 [info]: UPnP stack initialized using default interface
2024-02-08 12:33:16.035 [info]: RemoteServer: Server started and advertised on port 49927
2024-02-08 12:33:16.120 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:33:16.289 [debug]: ASIO: start selecting driver ASIO MADIface USB
2024-02-08 12:33:16.296 [debug]: ASIO: init for ASIO MADIface USB
2024-02-08 12:33:16.296 [debug]: ASIO: call init
2024-02-08 12:33:16.296 [debug]: ASIO: init done
2024-02-08 12:33:16.297 [debug]: ASIO: got out channels: 2
2024-02-08 12:33:16.297 [debug]: ASIO: init step 2
2024-02-08 12:33:16.297 [debug]: ASIO: init step 3
2024-02-08 12:33:16.297 [debug]: ASIO: init step 4
2024-02-08 12:33:16.298 [debug]: ASIO: init step 5
2024-02-08 12:33:16.299 [debug]: ASIO: init step 5b
2024-02-08 12:33:16.299 [debug]: ASIO: init step 5c: 2822400.000000
2024-02-08 12:33:16.299 [debug]: ASIO: init step 5c: 5644800.000000
2024-02-08 12:33:16.299 [debug]: ASIO: init step 5c: 11289600.000000
2024-02-08 12:33:16.299 [debug]: ASIO: init step 6
2024-02-08 12:33:16.299 [debug]: ASIO: init step 7
2024-02-08 12:33:16.299 [debug]: ASIO: init step 8
2024-02-08 12:33:16.300 [debug]: ASIO: init step 9
2024-02-08 12:33:16.300 [debug]: ASIO: init step 10
2024-02-08 12:33:27.977 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:33:29.422 [debug]: PlaybackController: setActivePlayQueuelocal
2024-02-08 12:33:29.532 [info]: UPnP stack initialized using default interface
2024-02-08 12:33:29.623 [info]: RemoteServer: Server started and advertised on port 49939
2024-02-08 12:33:29.746 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:33:29.928 [debug]: ASIO: start selecting driver ASIO MADIface USB
2024-02-08 12:33:29.935 [debug]: ASIO: init for ASIO MADIface USB
2024-02-08 12:33:29.935 [debug]: ASIO: call init
2024-02-08 12:33:29.935 [debug]: ASIO: init done
2024-02-08 12:33:29.936 [debug]: ASIO: got out channels: 2
2024-02-08 12:33:29.937 [debug]: ASIO: init step 2
2024-02-08 12:33:29.937 [debug]: ASIO: init step 3
2024-02-08 12:33:29.937 [debug]: ASIO: init step 4
2024-02-08 12:33:29.937 [debug]: ASIO: init step 5
2024-02-08 12:33:29.938 [debug]: ASIO: init step 5b
2024-02-08 12:33:29.938 [debug]: ASIO: init step 5c: 2822400.000000
2024-02-08 12:33:29.938 [debug]: ASIO: init step 5c: 5644800.000000
2024-02-08 12:33:29.938 [debug]: ASIO: init step 5c: 11289600.000000
2024-02-08 12:33:29.938 [debug]: ASIO: init step 6
2024-02-08 12:33:29.938 [debug]: ASIO: init step 7
2024-02-08 12:33:29.938 [debug]: ASIO: init step 8
2024-02-08 12:33:29.939 [debug]: ASIO: init step 9
2024-02-08 12:33:29.940 [debug]: ASIO: init step 10
2024-02-08 12:33:39.258 [debug]: ASIO: start step 1
2024-02-08 12:33:39.258 [debug]: ASIO: start step 2
2024-02-08 12:33:39.319 [debug]: ASIO: start step 3
2024-02-08 12:33:39.319 [debug]: ASIO: start step 4 with 2 channels
2024-02-08 12:33:39.319 [debug]: ASIO: start step 5
2024-02-08 12:33:39.321 [debug]: ASIO: start step 6
2024-02-08 12:33:39.375 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 12:42:59.998 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:44:45.737 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:44:45.737 [error]: Error reading FLAC file https://streaming-qobuz-std.akamaized.net/file?uid=2193658&eid=188590794&fmt=6&profile=raw&app_id=866251341&cid=1610792&etsp=1707399800&hmac=CmO7r91ywAZJBLnepRLr5chDzcc : FLAC__STREAM_DECODER_ABORTED
2024-02-08 12:44:45.741 [error]: Fatal error reading audio file https://streaming-qobuz-std.akamaized.net/file?uid=2193658&eid=188590794&fmt=6&profile=raw&app_id=866251341&cid=1610792&etsp=1707399800&hmac=CmO7r91ywAZJBLnepRLr5chDzcc aborting loading at frame 3307500
2024-02-08 12:45:20.124 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 12:46:41.927 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 12:46:43.685 [info]: UPnP stack initialized using default interface
2024-02-08 12:46:43.703 [info]: RemoteServer: Server started and advertised on port 57061
2024-02-08 12:46:43.905 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 12:47:57.695 [error]: Unable to enable MMCSS on ASIO render thread: 1552

2

also, in addition to the previous info -Qobuz works ok in its own desktop app

3

Hi @JamesB,

do you have the same behavior when you select WASAPI instead of ASIO?

4

The RME DAC doesn’t do wasapi, but the behaviour is just the same if I use the internal speakers on the laptop instead of the DAC.
(Thanks for the quick response )

5

Have you tried to disconnect and reconnect your Qobuz account?

6

Yes, unconnected and reconnected Qobuz when I reinstalled Audirvana

7

Bizarre. I haven’t touched the system all afternoon and now it works properly again.
Takes about 10 seconds to cache a 6 minute track.:
But the log still showing errors

2024-02-08 16:32:16.823 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-08 16:32:19.091 [info]: UPnP stack initialized using default interface
2024-02-08 16:32:19.112 [info]: RemoteServer: Server started and advertised on port 49741
2024-02-08 16:32:19.314 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-08 16:32:47.614 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 16:33:29.627 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 16:33:43.761 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 16:34:02.438 [error]: FLAC decoder: error reading HTTP stream
2024-02-08 16:34:04.075 [error]: Unable to enable MMCSS on ASIO render thread: 1552
2024-02-08 16:34:50.849 [warning]: Chromecast device added: error getting device capabilities: 0 for device: 4KTV-JUP adding it anyway
(I think this last item is my wife turning on the TV in the other room)

8

This could be the same issue that’s been affecting me for a couple of days now. I’m trying to stream Qobuz off 3.5 but the preloading gets stuck either at the very start or later into the track. I’ve tried everything, from troubleshooting the router to reinstalling 3.5.

And now I can’t access Qobuz website. Not with my phone either. At this point I’m convinced it’s a Qobuz issue. I signed out in A prefs and can’t reconnect. The Q app doesn’t work either.

9

I spoke too soon.
After about an hour Qobuz disconnected from Audirvāna and when I try to reconnect I get Error 500.
Qobuz still seems to working in the desktop Qobuz app though
Rather frustrating

10

Looks like it might be a Qobuz issue

11

Qobuz is back online. Qobuz through AS works fine again after I logged in with Qobuz my Qobuz account.

1 Like
12

Oh dear. After yesterday’s trouble with Qobuz this morning when I opened Audirvāna all my favourite albums and tracks had vanished. Restarted. Still not there.
Uninstalled and reinstalled Audirvāna. Still not there.
This is very tedious.
Any suggestions for how to get them back?

13

Reconnected to Qobuz and all the favourites came back but I still have the same problem that after a minute or so the playback catches up with the very slow cacheing and consequently stops.
Help please!

14

So I still have the same issue as yesterday, disappoiningly making Qobuz unusable.
Here is the log to the point where it stopped playing:

2024-02-09 09:46:11.951 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-09 09:46:12.460 [error]: Not logged to Audirvana account: need to sign in
2024-02-09 09:49:53.149 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-09 09:49:54.870 [info]: RemoteServer: Server started and advertised on port 49770
2024-02-09 09:49:54.899 [info]: UPnP stack initialized using default interface
2024-02-09 09:49:55.114 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-09 10:00:03.943 [error]: FLAC decoder: error reading HTTP stream
2024-02-09 10:01:16.976 [info]: ============= Started Logging, Audirvana Studio 2.7.0 (20700) =============
2024-02-09 10:01:18.860 [info]: UPnP stack initialized using default interface
2024-02-09 10:01:18.948 [info]: RemoteServer: Server started and advertised on port 49745
2024-02-09 10:01:19.083 [info]: UPnP web server started on 192.168.0.66:49152
2024-02-09 10:02:22.257 [error]: FLAC decoder: error reading HTTP stream
2024-02-09 10:03:36.696 [error]: FLAC decoder: error reading HTTP stream

15

Hi @JamesB,

Can you send me the email you use on your Qobuz account in PM so I can ask the API team if they have some logs on what is going on?

16

It’s a mystery! Qobuz working fine again this evening, and cacheing very quickly.
I’ll see how it goes over the weekend…

17

Just found this on X/Twitter
Dear valued customers, As you may have already noticed, Qobuz has experienced major disruptions to its operations over the last few hours. We apologize for any inconvenience caused. We were the target of a malicious attack (DDos), which has now been dealt with. Service is now back to normal on all our apps and on http://qobuz.com. We expect no further incidents of this nature. Should such a situation arise again, we will do our very best to resolve the problem as swiftly as possible. We want to emphasize that this attack had no impact on the data of our users. The protection of your data remains our utmost priority. Once again, we apologize for any inconvenience and remain at your disposal should you have any further questions. We will answer them promptly. The Qobuz Team

9:46 AM · Feb 9, 2024

18

Might be the same hackers to hit hires audio site first ?? still down…

19

But why?

20

Euh!!
Maybe asking them money to get their site back?? :grinning:

The good thing to get hacked like Qobuz website, they don’t own anything, they are just a portal for music… just have to reload everything if you didn’t have it all backed up somewhere else…

maybe hiresaudio were not safed enough ?? Being down for like 2 weeks now or more??

@JamesB you never received an email telling you that… i know you own porn, we recorded you on that porn site, just click here to retrieve your account…

I receive crappy emails everyday saying like pay your little unpaid ticket for driving too fast in front of school… i don’t have a driver license, never have :grinning: