Limit Concurrent Streams per File

I work IT for a private school and we are discussing the viability of using PLEX for in-house streaming of physical media ripped and made available to teachers to stream into classrooms in lieu of DVD players and physical media (which is often scratched after a few years).

We obviously want to keep things above board, and the biggest issue we need to resolve is limiting the number of concurrent streams per file in relation to the number of physical copies owned to remain in compliance with copyright.

We have discussed options like Tautulli but from what we have researched nothing has a killstream function if a concurrent stream threshold is reached.

I’m interested if anyone has suggestions for automating this process.

I think this option could further legitimize PLEX and open up a whole new niche with more and more schools entering the digital age.

We will be piloting this for our film teachers as we don’t need to worry about concurrent streams of the same file.

Montclair Kimberley Academy in New Jersey has been using Plex for several years at their three campuses. However, they do not have an easy solution in regards to copyright enforcement. They use Tautulli to simply monitor streams.

For those on r/PleX, I posted this about a year ago with no true solution, so you’re not crazy if you think you’ve seen this posted before.

There have been a few similar feature requests and discussions.

I’m not aware of a “packaged” solution either.

Can you link to the post? I probably responded then :slight_smile:

Tautulli would just be the tool to trigger the script to accomplish your goal. This script, with the example arguments, would limit concurrent streams by users not by file but it provides an example that what you’re asking can be done.

So how are you setting up the users per teacher/classroom/campus? How are you sharing, how many files will be available? How you setup your users and your libraries may make what you’re trying to do easier. Or a better way to look at it would be more complexity with users, libraries, and files then less complexity of the script or standard user, library, and file structure and more complexity in the script.

1 Like

I’m more than willing to help but I would need some additional information. PM me here or here are couple other ways to get in contact with me.

You could build out a listing of ratingKeys with allowed amounts and have that in the script or in a separate config type file. Or add labels to each item with the allowed amount. The script would pull in all streams and check against the ratingKeys allowance or labels allowance. Once the threshold is met the offending stream could be killed with a message stating the allowed amount, who else is watching, how far their progress is, who will finish first, an ETA of when the next stream can start, notify any or all users via email, slack, discord, etc, etc. Lots of possiblities.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.