I’m debugging something at the moment but can give you an idea shortly of additional storage used. Minimal though.
Perhaps music that is saved in my library (in my case, Tidal Favorites) gets a saved waveform if that is possible
A rough guide from my extension is roughly 150MB for approx 70,000 tracks based on 5 minute tracks
So nothing then 
This makes more sense to me than saving a waveform for every track I happen to click on but never add to my library and/or never play again.
I think this is the case,
and it’s what I saw as well, I think
@Rugby testing of tracks not in his library indicates waveforms do appear for tracks not in one’s library, albeit it’s taking some time for the waveform to appear.
Right, I saw that, but didn’t see waveforms myself in non-library tracks while distractedly dabbling earlier today.
I’ve now played several non-library tracks from Qobuz in lower resolutions (from CD to 92/24 at most) and about 3:30 in length and didn’t get any waveforms either.
I do get them for in-library tracks after about 20 seconds for CD resolutions.
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.
Same as me.
Doesn’t store or doesn’t generate? Because for me (and others) they are not generated at all (and that’s ok for me) while @Rugby said they got generated,
I think I need a Mea Culpa. I swore I tested using non-library tracks, but, in reviewing history I see that I did not.
In fact, the tracks which started not producing a waveform were the 24/192 tracks which were not in my library. I had initially attributed it to the resolution when it was not.
To verify, I added one of the test 24/192 albums into my library and the same track did indeed produce a waveform eventually.
Sorry, to have gotten that part wrong. 
Thanks for the clarification. 
