Replies: 1 comment 7 replies
-
|
Hello! This is a question for @Tolriq indeed. When the waveform feature was added, it showed that the same song was downloaded multiple times (one time from the player and one time from symfonium itself to analyze and generate the waveform, possibly in parallel with the player). This also makes ffmpeg to be spawned several times in parallel if transcoding is active. For the last point, @srett was working on a solution. That being said, extracting waveforms is not free, and this is something LMS will eventually do itself in the future to restore its similarity based engine. I guess we could somewhat extend the OS API to provide the computed waveform... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @epoupon
I was curious how Symfonium was able to present the track waveform (Plex generates it on the back end for PlexAmp), so I looked in the logs and sure enough it appears to be downloading each track:
The first call is from Symfonium and the second from my player (UPnP streamer).
Setting the progress bar to basic (as I really don't want to download each track to the phone just so it can display the waveform) I was expecting to see just the stream.view from the UPnP streamer, but instead all I see is:
I have no idea why getSong.view is only called when not displaying the waveform (unless it's hoping to get it), but that's something I can ask Tolriq, but is there a reason I'm not seeing the stream.view from the UPnP endpoint?
Symfonium isn't proxying the track as the CurrentURI of the UPnP streamer is stream.view from LMS (and I don't see a stream.view from Symfonium).
I tried with logging set to Debug, and whilst I could see stream.view being fulfilled there was no mention of the initial call or where the data was being sent.
Beta Was this translation helpful? Give feedback.
All reactions