When I change a track in BubbleUPnP, the current track stops almost immediately. The lag is starting the next track. How would we find out how much of the lag time is the server fetching and preparing to serve and how much of the lag time is BubbleUPnP preparing to play?
So it happens to you, too. Try this experiment:
- store some music files on the same HDD as JRiver
- download JRemote2 trial (this is the remote control app for JRiver, made by JRiver themselves)
- compare the lag in track change with JRemote2 vs. BubbleUPNP. In my system, the lag is substantially less and JRemote2 is almost immediate.
JRemote2 communicates with JRiver by sending it commands through the LAN. BubbleUPNP works by sending it commands through DLNA. So for me it was clear that it was either JRiver's implementation of DLNA, or BubbleUPNP.
So I downloaded mConnect, which is another app that talks to JRiver via DLNA. I get the same lag as BubbleUPNP.
Conclusion: the culprit is JRiver's implementation of DLNA, or maybe DLNA itself.