search

lossless1024 / StreaMonitor

Adult live stream downloader for advanced people. I could have chosen a better name.
GNU General Public License v3.0
198 stars 52 forks source link

Start/Stop all and Selected Recordings #22

Closed Odogwu3000 closed 1 year ago

Odogwu3000 commented 1 year ago

Possibility to Stop/Start all/selected recordings

lossless1024 commented 1 year ago

I thought about this already and is partly done

lossless1024 commented 1 year ago

But i think only the start/stop all can be implemented nicely, because there is a chance that you have streamers with the same name on different sites. The other solution is to separate streamers with commas or something, but I don't like that approach.

DerBunteBall commented 1 year ago

Wouldn't it help to assign streamers/jobs something like a uuid? This makes it easier to have same names on different sites or VR and normal streams.

How the stuff could be handled on the command line is another thing.

lossless1024 commented 1 year ago

It wouldn't really, because I think you might not want to copy&paste id-s or find numbers yourself to start/stop/etc a streamer. This means you will use username. If there would be a collision, you have to specify site too. Or at least I think that this is a proper way. So the program actually have to search the list of streamers for the username and site. Of course this could be smarter, as everything, but currently I don't have so much time for this. However I wanted to migrate the command line to use the cmd library, but that is another story and doesn't help us here. (A history and auto-completion feature also would be great)

DerBunteBall commented 1 year ago

Hm.... yes it would have the most effect to the internal logic.

So the Controller could be generally made more userfriendly (in sense of a well defined CLI app).

That would be easy for GUI software hm.... to have it in the CLI of the Downloader would be really a problem. So it couldn't be nearly impossible to do this nicely. My only thought would be to make CLI GUI with (n)curses.

lossless1024 commented 1 year ago

Indeed, a GUI will be much more user-friendly. :)

When I started this project, the concept was that this should be ran on a server or NAS and it will be working in the background with a reasonably low system load. Also this is why it doesn't have a GUI. However I've already thought about making it with TKinter. For a nice CLI/TUI, ncurses would be perfect.

There are lots of features which could be implemented, but I don't have time for them right now. However if you or someone have time to improve it, feel free to send PRs :)

lossless1024 commented 1 year ago

Also you can check the start * and stop *

DerBunteBall commented 1 year ago

The concept you have designed it for is my usecase. So a GUI could be also a remote GUI that's the nice thing at this design. I would keep the Downlaoder as thin as possible.

I think my Python skills are saidly to bad to do patches.

lossless1024 commented 1 year ago

A remote GUI would be a good idea. Also it can be easily done with ZMQ using a JSON based protocol.

DerBunteBall commented 1 year ago

Exactly this. So the protocol would need a bit of "specification" so it would be possible to have GUIs, TUIs or WebUIs like wanted.

A bit of authentication possibilities or so and a GUI could be used for mutli host managment.

Also it can be used locally so it's not important whether the server runs local or remote.