Jump to content

Recodings ending after 3 hours


Recommended Posts

Posted (edited)

I've been trying recording NFL games early in morning (UK,) m3u stream scheduled Live TV,

Cuts out at 3 hours of recording every time.

using xTeVe (default FFmpeg Options: -hide_banner -loglevel error -i [URL] -c copy -f mpegts pipe:1) no Buffer

problem at 2023-10-17 04:01:45 ..... any help appreciated.

embyserver (rec error).txt

Edited by daffyonlsd
Posted

The log says it ended normally. It seams likely?? as many sporting/live tv event run longer than the allotted time slot you should add some extra padding to these recordings.

As here:

image.png.0735be3cbd8d77f26e03fcb934f5e051.png

or I could be completely wrong!

Posted

Yep, I understand. But that just cant be my case.

I actually have mine set to 120... as nfl often overruns.

Posted
20 hours ago, TMCsw said:

The log says it ended normally. It seams likely?? as many sporting/live tv event run longer than the allotted time slot you should add some extra padding to these recordings.

As here:

image.png.0735be3cbd8d77f26e03fcb934f5e051.png

or I could be completely wrong!

This isn't it. It's not related to guide data or recording setup.

The source stream is just ending: 

Quote

2023-10-17 04:00:02.974 Info SharedHttpPipelineSource: Remote server closed stream

The server is currently treating this as success given the absence of an error. We can probably look at restarting the recording. You'd end up with multiple ts files but at least you'd have it all.

Posted (edited)
Quote

We can probably look at restarting the recording

is this to be implemented in future version?

cheers

Edited by daffyonlsd
  • 1 month later...
Posted

No, I've figured out a workaround. 

Xteve as a buffer, seems to do the trick.

cheer though

  • 2 months later...
Posted (edited)

I experienced exactly this issue twice today for a spoting event that was 4 hours long, both times exactly 3hours in, the recording stopped.

edit : looked in the logs, found the reason.

Edited by RobDenny
  • 1 month later...
Posted
On 28/11/2023 at 22:46, daffyonlsd said:

No, I've figured out a workaround. 

Xteve as a buffer, seems to do the trick.

cheer though

Can you explain in more detail?

Posted
On 18/10/2023 at 20:22, Luke said:

This isn't it. It's not related to guide data or recording setup.

The source stream is just ending: 

The server is currently treating this as success given the absence of an error. We can probably look at restarting the recording. You'd end up with multiple ts files but at least you'd have it all.

Restart recording would be great, even if some seconds or minutes is missing on sport events! It there any feature requested for this?

Posted
On 3/26/2024 at 2:59 PM, Nonnos said:

Restart recording would be great, even if some seconds or minutes is missing on sport events! It there any feature requested for this?

HI there, let's look at a specific example:

Thanks !

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...