Do all HTTP streaming through Tomahawk

[theli-ua]

For consistency and better control.
Currently if resolver returns direct http link - they go as is to VLC, if resolver returns custom scheme link (tidal://) but later in geturlstream handler returns http link - it goes through Tomahawk+imem

[xhochy]

We were thinking of this since a long time but there were some issues because of which I did not want to make the switch. The most important one was that seeking with at least Spotify did not really work with our builtin imem-http layer.

[theli-ua]

Then make all http links passthrough to vlc. You shouldn't be half here and half there. You have to be at least consistent. And I know imem has seeking problems, in fact it doesn't even support seeking natively. With imem flac seeking in TIDAL doesn't work for example.

[muesli]

That's not an option because we then can't accept self-signed certificates for resolvers like subsonic/ampache/owncloud.

[theli-ua]

@muesli I said HTTP not HTTPS, as I was explaining its inconsistend atm - if resolver will set track URL to http link - it is passthroughed to vlc, but if resolver returns something like tidal://trackID and later resolves that to http - it goes through imem