2.73 - Waveform Display for Streaming Content

[Sebastian_Wilck]

Hi all,

in the latest release notes (version 2.73) Roon claims to have added waveform display for streaming content. I tried playing songs from Qobuz, added albums from Qobuz to my collection and re-analyzed some favorites of Qobuz that are already in my library. But still I cannot see any waveform when playing these files.

Is that working for any one of you?

[BlackJack]

On what device (display) were you looking?

[Sebastian_Wilck]

Isn’t that about the landing page player of Roon? (see the screenshot). This was my expectation.

[econaut]

Same expectation and no waveform.

[Suedkiez (Just a fellow user like you)]

@Sebastian_Wilck

Isn’t that about the landing page player of Roon? (see the screenshot). This was my expectation.

Yes it is, but @BlackJack had asked about which device you used for due diligence. Though it should work in any Roon app, provided they are up to date (but not with the display feature in a browser / Chromecast, I think)

In any case, be aware that it only works in streaming albums that are already in the Roon library, and it takes some play time until it appears.

But, here comes the thing: It’s apparently not working right now I am on Early Access and it definitely worked for me when the feature was released in Early Access, but right now I don’t get any waveforms. Very odd. For context, this is what people reported during EA:

B1686 Streaming Waveform Inconsistencies

Streaming from Qobuz, The time it takes a waveform to appear seems to be a factor of both track resolution and length. 16/44.1 2 minute song 10-15 sec. 16/44.1 4 minute song 31 sec 24/96 4 minute song 1:20 24/192 4 minute song Song ended before Waveform populated. Is there going to be a way to turn this off? I am assuming that on-demand analysis is happening as it is being downloaded to the buffer. This might cause issues for servers that are older/slower, less CPU headroo…

[Sebastian_Wilck]

@Suedkiez

I am on Early Access and it definitely worked for me when the feature was released in Early Access, but right now I don’t get any waveforms.

Thanks for the context. Let’s see if waveforms come back within the next days.

[MusicD (MusicD Projects)]

Not on EA now, wasn’t working terribly well with Qobuz during EA in my experience.

Now released, it isn’t working here.

[Suedkiez (Just a fellow user like you)]

While I can understand if somehow there is an issue in the production release, what I don’t get is why it doesn’t work for me in the same EA version that worked before EA version that I have now. Is there a cloud component?

[glc650]

@Suedkiez

In any case, be aware that it only works in streaming albums that are already in the Roon library, and it takes some play time until it appears.

So this doesn’t work for Tidal tracks that are just added to the queue?

[Mikael_Ollars]

Have you had any explanation in EA on how this feature is architected?

Does it rely on a schdeuled analysis/background maintenace or similar?

[MusicD (MusicD Projects)]

Albums/tracks had to be in the Roon library to work.

[MusicD (MusicD Projects)]

Play a Qobuz track from your Roon library and it’s analysed in real time. Hence it was taking almost a full track length to produce on EA.

[Rugby (aka Daniel or Big Dan)]

@Mikael_Ollars

Does it rely on a schdeuled analysis/background maintenace or similar?

It’s on demand during playback of the track. But, only for streaming tracks IN your library. No waveform for just any random playback.

@glc650

So this doesn’t work for Tidal tracks that are just added to the queue?

It works for streaming playback of tracks In your library. If you are just adding tracks not in your library then, no, you won’t get waveforms.

[Suedkiez (Just a fellow user like you)]

@Mikael_Ollars

Have you had any explanation in EA on how this feature is architected?

Does it rely on a schdeuled analysis/background maintenace or similar?

I don’t think so because it appears a short-ish time after you start playing a track (in the library). See the EA link I posted

[Suedkiez (Just a fellow user like you)]

@Suedkiez

While I can understand if somehow there is an issue in the production release, what I don’t get is why it doesn’t work for me in the same EA version that worked before. Is there a cloud component?

Hmmm, I realize now that the EA thread was written on B1686 when streaming waveforms were released in EA. But I never checked on the later EA build B1693 that I have now - maybe it was always broken there.

@vova something seems wrong here.

[Mikael_Ollars]

Not happening here… Maybe there’s something gone wrong cloud-wise…

Updated 15 minutes ago, both server and remote on iPad Air M2, latest iPad OS.

[MusicD (MusicD Projects)]

I stepped out of EA on B1686 I think. Whilst it was working-ish, it seemed to me things could be improved.

[MusicD (MusicD Projects)]

Not working here either.

[Suedkiez (Just a fellow user like you)]

@MusicD

Hence it was taking almost a full track length to produce on EA.

Well, 20 secs for average redbook tracks

@MusicD

it seemed to me things could be improved.

And they said they would:

@vova

Currently this change doesn’t store waveforms for non-library tracks. So the thing you are seeing is expected. But this conversation made us think whether this is a right approach. We will think about it more… we understand both pros and cons and just need to do a bit of measurements to make a right call here.

[MusicD (MusicD Projects)]

Yes, granted.

But (blow my own trumpet time) I got Qobuz and Tidal waveforms to produce in my extension within seconds, cache the waveform in the extensions DB, before the next track had started the waveform was already waiting.

I looked at the cost of storage for 100k tracks and deemed it fine to sacrifice some SSD space.

I also improved my waveform analysis to be 100% accurate at zero penalty to CPU compare to less accurate means.

That said, my extension now fails to produce waveforms for Qobuz