Conversion ignoring scheduled time

[User337 3]

Hello,

I am curious about a few things:

I setup "Convert Media" to run at 03:00 in the morning for 3 hours:

 

When I add an conversion at around 15:00 for example it is however not queued and started as soon as the time is 03:00 but directly.

Moreover I added a whole season conversion job at 03:00 which started directly like expected but didnt stop as soon as the 3 hours of time limit where hit (06:00).

Why is the converter totally ignoring the scheduled time?

[Abobader 3464]

Hello User337,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Sammy 790]

Abobader is a "bot" so to speak. Specifically you need to send the server log and ffmpeg logs; possibly the hardware detection logs too.

[Luke 42080]

In addition to the scheduled task, conversions will also generally start immediately if there is no other activity.

[Luke 42080]

Regarding the time limit, can we please look at an example?

How to Report a Problem

Thanks.

[User337 3]

26 minutes ago, Luke said:

In addition to the scheduled task, conversions will also generally start immediately if there is no other activity.

Ok this explains why it started right away, thank you.

 

26 minutes ago, Luke said:

Regarding the time limit, can we please look at an example?

How to Report a Problem

Thanks.

 

I will add a conversion job and cancel the task starting directly. Afterwards it should, if I am not mistaken, restart itself at 03:00 in the morning and run for 3 hours before stopping itself again right?

I will provide logs for this scenario later.

[Luke 42080]

That sounds correct yes.

[User337 3]

This time it worked. Maybe it didnt stop the first time cause the task was also started before 3 in the morning and somehow not linked to the time schedule?

I will monitor this further but for the moment I am fine

[Luke 42080]

the time limit is linked to that one particular trigger and doesn't apply to running the task manually (or if the server kicks it off after creating a conversion).