Extend Scheduled recordings

[TheMadog24]

First, I want to say I love this, I use it to record Backup Audio for streams in case of twitch muting the vods, and having it run on my NAS Docker is fantastic.

However, it seems to only record/run for a max of 12 hours. I was wondering if this was intentional or if this could be extended with an config/variable setting?

If it could also not remove the scheduled task once the stream is complete, but instead reset and wait for a new stream, that would be great as well.
Having to not worry about restarting the recording every 12 hours, OR every time the stream drops and restarts would be great.

[CrazyWolf13]

Hi,
Wow, that's awesome to hear when someone can utilise the software :)

That's indeed a great suggestion, let me look into this in the next days.

[TheMadog24]

Hi, Wow, that's awesome to hear when someone can utilise the software :)

That's indeed a great suggestion, let me look into this in the next days.

Thank you! that would be much appreciated.

[CrazyWolf13]

so schedule_end will be user configurable and a new default set to 48 hours.
as this is something not often changed, it will be done via ENV_VAR.

can you tell me if you run via docker or community-scripts (Proxmox) or plain?

About the second thing, I'm unsure if/how well that would be possible, as if I would do that, I needed to "simulate" a new scheduled start request immediately after recording of the livestream, but there is just one problem, it would immediately switch to recording mode too, as streamer is live. There seems to be no way to "predict" how long a stream goes.

While that would be no problem in theory, the twitch api behavs weirdly after a stopped/interrupted stream, sometimes taking up to 30min/1h to actually reflect the channel going offline, so it will get kinda difficult and would require a massive rewrite, though I can fully understand your request.

Do you by any chance have possible ideas how such a thing could be implemented design wise?

[TheMadog24]

can you tell me if you run via docker or community-scripts (Proxmox) or plain?

I am running Docker on my DS415+, I am still a bit new to this, so not too technically knowledgeable about the environment, or variables.

so schedule_end will be user configurable and a new default set to 48 hours.

That sounds great, since Twitch streams cannot be longer than 48 hours anyway,

About the second thing, I'm unsure if/how well that would be possible, as if I would do that, I needed to "simulate" a new scheduled start request immediately after recording of the livestream, but there is just one problem, it would immediately switch to recording mode too, as streamer is live. There seems to be no way to "predict" how long a stream goes.

While that would be no problem in theory, the twitch api behavs weirdly after a stopped/interrupted stream, sometimes taking up to 30min/1h to actually reflect the channel going offline, so it will get kinda difficult and would require a massive rewrite, though I can fully understand your request.

I am not exactly sure what you mean, I was just hoping that if something happens like a network interruption (either on user's end or Twitch's/streamer's side) it would not end and cancel the scheduled recording, but would start recording once again when the new stream is up/started again

Maybe by just re-requesting the same schedule once complete, until the user selects to change/end it? If possible.

Do you by any chance have possible ideas how such a thing could be implemented design wise?

in terms of UI? not really, it seems fine to me already.
In terms of functionality? What I described above, if possible. Once a stream recording is scheduled, it stays scheduled indefinitely until the user chooses to manually end/stop it, if the stream ends/recording completes, it just re-started a new recording task/schedule again with the same settings as the one that just ended.

This way you could set a stream to record and not worry about it until you don't need it anymore. Examples of this would be a subbathon where it is continuously recording, but stream resets periodically, or if you are out and can't setup a new scheduled recording, or if a stream ends and restarts due to network issues on any end.

I hope I explained that clearly and I understood what you meant.
Hopefully this is also possible and not too difficult a request.

[CrazyWolf13]

Alright, good to know!

Yesnt, twitch partner can do even longer if they want.

Hmm network timeout/e.g. the breaking you mean is not controlled by me, that is the underlying tool called streamlink, which is command-line only, so there's nothing I can do about that.

Yes I get what you mean, though it's quite hard to implement, maybe I can find a way.

[CrazyWolf13]

Hmm I'm sorry but I think I have to pass on this one at least for now.

The twitch api does not even expose offline/online event, I have to rely on if there is a stream title or not.
And with the current implementation I would have to rewrite quite a lot of the db but then still it would be full of workarounds to correct timestamps and filenames etc.

When I started working on this app (it's my first real project), I never even though I'd add schedule function, so that is already a bit of workarounds.

Though this is only due to me having currently a little bit limited time, once I have more time, my plan is to rewrite this app and add you feature too!

[TheMadog24]

Hmm I'm sorry but I think I have to pass on this one at least for now.

If the new default is set to 48 hours, that may be all I need for the moment.
I can handle the rest manually and just make sure I am there for anything else, just that (if possible) is a huge win.

[CrazyWolf13]

alright, great :)

I'll get a docker image ready

[CrazyWolf13]

Image should be available via tag latest and 0.6, please check it out.

new default should be 48 hours and you can also set it even higher using an enviroment var in docker: SCHEDULE_END=100
to get 100hours.

[datlaziboi]

Image should be available via tag latest and 0.6, please check it out.

new default should be 48 hours and you can also set it even higher using an enviroment var in docker: SCHEDULE_END=100 to get 100hours.

Hi,

Would you be able to confirm where I can adjust the schedule for Proxmox LXC? I tried looking, but don't see anything stating SCHEDULE_END.

[CrazyWolf13]

@datlaziboi
I've just mande a new release, feel free to run the update command in the LXC and edit /opt/streamlink-webui.env to add the env var with the desired value, for example 50 for 50 Hours.

[datlaziboi]

@datlaziboi I've just mande a new release, feel free to run the update command in the LXC and edit /opt/streamlink-webui.env to add the env var with the desired value, for example 50 for 50 Hours.

@CrazyWolf13 Thanks! I ran the LXC update and checked "/opt/streamlink-webui.env". I didn't see "SCHEDULE_END=" setting so I just added the additional line, so it's at SCHEDULE_END=100 below the download location. currently it sits at this setting.

CLIENT_ID=****************************
CLIENT_SECRET=**************************
DOWNLOAD_PATH=/download path
SCHEDULE_END=100

[datlaziboi]

@CrazyWolf13 , I actually checked the "download_task_model.py"

Proxmox LCX (download_task_model.py)
stream_id: str = 0
schedule: bool = False
schedule_interval: int = 5
schedule_end: int = 12

I noticed it's not calling to int(SCHEDULE_END) like the docker release. would it be okay for me to change the value myself from "12" to "int(SCHEDULE_END)" ? ORRRR can i just change 12 to 100.