Clients are a bit quirky, because many are developed by third parties and so bring their own ideas (and bugs) into the mix, but that’s not different from Plex. The product itself is quite robust, though, and the chief architect/developer is responsive to questions and suggestions. I got further using swagger to pound the API than I did when I was relying on the docs. I would not say it was easy, but that’s mostly because the documentation is out of date and has lots of errors–code was a no-brainer, once you figured out how something worked, but figuring it out when the docs say one thing and the API wants another had some frustrating moments. Adds the ability to bookmark media (mark current position) and later resume from a named bookmark. Bug reports can instead be submitted to the issues section of the Github repo if you like that approach. Please submit questions or bug reports here in this thread. The CHANGELOG file in each branch will tell you what has evolved. As is typical for my work, the “master” branch represents the latest full release the “stable” branch contains updates from development that have had minimal testing and are deemed “stable” and the “develop” branch is the latest code with work in progress checkpoints (the bleeding edge). ![]() This project lives in a Github repository, here: ĭocumentation is in the README file in the above Github repository. This plugin was developed at the request of PrincessCleavage and cw-kid, so if you’re an Emby user, be sure to thank them for stepping up to get it launched! I’d also like to thank Luke, the lead Emby developer/architect, for his support. It allows you to control Emby sessions (clients playing media), and respond to basic session events. Emby Interface is a control and response interface for the Emby media server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |