Frame Media Server Support

Other Gear & Services
1

@james - Is there a way for app devs building media servers to add support for Infuse? Is there like a standard API set that could help make infuse support faster/better?
EX heres a new server that would be great if infuse could pull from.
GitHub - Eleven-am/frames: Frames is a modern SVOD (Streaming Video on Demand) streaming service built with React and NestJS. It allows you to stream MP4 files from virtually any provider including local storage, S3, Dropbox, Google Drive, and more.

2

Would this help?

3

An approach for a new mediaserver could be to implement an existing (media server) API with public specifications (e.g. Jellyfin, Plex, etc) to get access and compatibility to existing clients like Infuse without requiring client updates..

4

Nope thats for using infuses player, its not for the ingestion into infuse.
I dont want to assume anything but from my past experience in software engineering, I would have interfaces that I map functionality into so when I add a new service you map the specific provider implementation into the generic infuse implementation.

@aeriquek yeah no, I would never want some other app to map to another applications format that is dumb. They could change their format and now youre dependent on what they support, it make more sense to map it to a “standard” format for infuse.

5

It all depends on what you want to achieve… and what your view is. APIs do not have to be just for one application.. they can facilitate an ecosystem.

Examples where both client and server side have multiple implementations these days, while there initially was just one server implementation: AWS S3, Kubernetes, Matrix chat, Docker, etc.

Adopting existing public media server API:
Pro:

  • Open spec, in case of Jellyfin you could consider participating to try to steer its direction.
  • Multiple independent clients already exist → helps to launch client base ease of adoption.
    Cons:
  • API spec not yours: you might end up implementing and maintaining more endpoints than you want.

vs

creating a new mediaserver API spec:
Pros:

  • It’s your spec so the right spec :slight_smile:

Cons:

  • You’ll have to develop your own clients, or
  • Requires existing clients to implement it a new one API (“when and why would the Infuse team consider implement yet-another-media server API?”)

So YMMV

And there is some of this to consider as well?