INTERACT FORUM
Networks and Remotes => Remotes => Topic started by: AndrewFG on May 10, 2015, 10:35:07 am
-
It seems that JRremote is missing the Play Doctor command menu when playing to this device. But it is present as it should be when playing to the main MC server / player..
-
That is correct. JRemote has never supported Play Doctor for local playback. It'd be sweet if it did, but it has not up until now.
You can make pre-defined Play Doctor driven Smartlists and Views, however, which is a handy way to get access to Play Doctor lists on your mobile device.
1. Make a Play Doctor list, after customizing the "Files to use" search as you'd like, and save it to your Playlists.
2. Now make a Smartlist, or Media Network View, that uses a Playlist is any [Your Play Doctor List] rule in the files to show search. Add a shuffle modifier for good measure.
3. These will open and work normally within JRemote.
More info:
http://yabb.jriver.com/interact/index.php?topic=77395.msg524805#msg524805
-
Wow! That's a mighty complicated "solution" to a rather simple request...
-
True, but I like those lists anyway. They're also nice in Theater View.
Like I said, it'd be sweet if it did work with the right-click Play command. Since it is there when playing to the server, I can only assume it isn't possible with MCWS commands (and not just an accidental omission). In other words, I think it isn't anywhere near so simple, probably because of the "learning" logic in Play Doctor, which it couldn't do by delivering a static list to the device after one "search" call.
But, honestly, even if they did add it, I'd keep my set of lists too. They're nicer than what Play Doctor often does on its own, because they're limited the way I want (by percentage). I also, however, find them to be nicer than just a pure shuffle in the same kind of ~mix list.
-
.. I can only assume it isn't possible with MCWS commands (and not just an accidental omission). In other words, I think it isn't anywhere near so simple, probably because of the "learning" logic in Play Doctor, which it couldn't do by delivering a static list to the device after one "search" call.
That was my assumption too. And that seems to imply that JRemote uses two different mechanisms for generating & managing playlists for a) "this device" and b) "for MC" / "for external renderers"; whereby in the former case it seems to build the playlist itself, and in the latter case it asks MC to build it. I guess the solution would be if JRemote presented itself as an "external renderer" and then mechanism b) could work for everything...
-
The point is that in the (b) case, MC controls the playback. JRemote just tells MC to play something to one of MCs zones, while in the (a) case MC doesn't control, just supply content.
Play Doctor is a feature of MC, it has to manage the playing now list, which is not something that works when you're just pulling a playlist and media files to play locally (which is otherwise stateless in MC).
There have been rough plans to sometime in the future allow JRemote and/or Gizmo to be a "zone" that MC can control, but that will not happen soon.
-
A possible solution could be for JRemote to tell MC to create playlists for a kind of "dummy" renderer/zone. And then it could pull the tracks from that playlist...