Post Reply 
MQA through TIDAL in MinimServer
03-02-2017, 08:47 (This post was last modified: 03-02-2017 08:50 by Pepsican.)
Post: #5
RE: MQA through TIDAL in MinimServer
(02-02-2017 14:10)Cebolla Wrote:  
(02-02-2017 11:43)simoncn Wrote:  MinimServer (not MinimStreamer) can play from a network URL if you put the URL in a .m3u playlist. In this case, the URL is passed to the renderer and it is up to the renderer whether or not it can handle it. This is currently working for qobuz: URLs and it could work for TIDAL if they decide to expose MQA streams as (for example) tidal: URLs that are playable by your renderer. This would be transparent to MinimServer as it is just passing the URL to the renderer for playing.
The implication is that the OP would be able to obtain the URLs to stream from TIDAL in the first place. That is currently not possible from the OP's current setup, as it's all handled internally by BubbleUPnP.

I don't know the exact details, but it seems the TIDAL URLs are not so easy to grab. They are certainly not stable over a longer period from what I understand. Also, TIDAL have stated that the MQA stream can only be listened to on their PC App. So, there may be something on the client side to do some work on the MQA stream.

Based on what you are saying, it may be best to check with the Bubble developer whether it can be updated to deal with the MQA side of things. But that would also mean TIDAL release their MQA API.

Edit: found it. It seems that when MQA arrives on the client, there is an "unfolding process" that happens. That's what the client does and at the moment, neither the web browser extensions, nor any mobile versions of the app, do this. So, I guess Bubble could do it, although I have no idea how intensive the unfolding process is.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: MQA through TIDAL in MinimServer - Pepsican - 03-02-2017 08:47

Forum Jump:


User(s) browsing this thread: 1 Guest(s)