I’m working at implementing DumbTools-for-Plex by @coryo123 (forum post here) to add Search Support to my channels for clients that don’t support the Search function. The DumbTools check against a list of Client Products, if Client in list then the DumbTools are used to interface with the search function.
So, I’m looking for a list of Client Products that currently don’t support the Search function in a Channel (aka InputDirectoryObject). I already know some Client Products and they can be found here https://forums.plex.tv/discussion/190573, now I need to know which don’t support the Search function.
Currently I know this is an issue with Plex Media Player, and iOS. I think others have said the Roku and PS4 don’t support Search currently?
I know you are just asking about Search. But I figured I would give the specifics in terms of input for clients including InputDirectoryObject() (since it can be used for search and other user input), SearchDirectoryObject(), and PrefsObject().
Plex Web recognizes InputDirectoryObject(). It will only accept the first InputDirectoryObject() on a directory level and if you want to allow user input for something other than search, they still have to enter that user input in the Search Dialog box at the top of that directory level screen. And Plex Web recognizes and includes universal search services in the overall Plex search.
The Roku now recognizes InputDirectoryObject() on both the Classic and Plex Pass version, so it won’t be long before it makes its way to and is approved by the Roku Store and is available to all users. The new Plex Pass version also recognizes SearchDirectoryObject() as an input option, but does not yet recognize universal search services or include them in the overall Plex search.
Support for the InputDirectoryObject()/Universal search services will eventually be added to all Plex player apps. It is just that right now there are a lot of Plex player apps that are either new or recently completely overhaluled (which makes them the same as a new app). So they are still in their infancy. That is why apps that have been around the longest have the most features. And Plex is first and foremost a local media media management program, so adding channel features are always going to have a lower priority than addressing issues with the media player or adding features for local media management.
And for PrefsObject(), it is recognized by PlexWeb and a few older clients. The trend seems to be toward choosing not to include Preference support in the new or recently redesigned Plex players apps and instead users will manage Preferences from the PlexWeb interface.
So just like all the other features of Channels, like adding or updating from the Channel Directory or deleting any channel, are now handled only by PlexWeb, since most people will set Preferences when they first install a channel and/or do not change often, Preferences for any channel can also be managed by users from the Plex Web interface.
@shopgirl284 said:
Plex is first and foremost a local media media management program, so adding channel features are always going to have a lower priority than addressing issues with the media player or adding features for local media management.
Plex really needs to make InputDirectory support a high priority of the low priority features. So much functionality of 3rd-party channels is completely thrown away just because we can’t give a string to the server.
In the scheme of Plex, third party channels are the lowest priority. But search is usually the first feature related to channels, that the developer works on.
But there are just so many fixes and features for the local media they have to look at first. Just look at the Release Announcements. They are not lazy. They just have bigger fires to put out first.
And figuring out how to provide that user input from a channel is one of the hardest parts of the client design. There is no PMS code for them to pull from to build those keyboards for input. It is all independent and unique for each Plex player.
