Duration of recordings wrong, says 12 hours!

[dcxmurphy 2]

Hiya.

 

I've noticed a few times that an odd recording will give a really weird duration (like 12-24 hours long) after recording when I go to watcj it. It will play what it has recorded but after that it just freezes. How can I prevent this?

[Luke 37474]

Hi, yes we've noticed this once in a while with certain recordings. We are looking into it, thanks.

[dcxmurphy 2]

Are you guys making any progress with this issue? This is happening quite frequently. Sometimes the recordings are corrupted or something and I'm not able to play past a certain point, even after converting to mp4.

[Luke 37474]

We are looking into this, thanks.

[xanthos84 1]

any progress here?

experiencing the same issue!

instead of 50min duration is 1d20h+

[Luke 37474]

any progress here?

experiencing the same issue!

instead of 50min duration is 1d20h+

 

Hi @@xanthos84, this should be improved with the 4.2 release. Let's look at an example. Please attach the information requested in how to report a problem. thanks !

[xanthos84 1]

Hi @@xanthos84, this should be improved with the 4.2 release. Let's look at an example. Please attach the information requested in how to report a problem. thanks !

 

Logfile of the problematic recording:

2019-07-29 20:12:00.002 Info App: Recording timer fired for Achtung Abzocke - Urlaubsbetrügern auf der Spur.
2019-07-29 20:12:00.003 Info App: Getting media sources for recording from channel 610503 610503
2019-07-29 20:12:00.004 Info App: Opening live stream for recording from channel 610503 610503
2019-07-29 20:12:00.004 Info App: Opening channel stream from Emby, external channel Id: m3u_098cf0a41285b2d4389b0c519d7f22070dd19f7d57ab6a7fc93669780db8386e
2019-07-29 20:12:00.004 Info App: Streaming Channel m3u_098cf0a41285b2d4389b0c519d7f22070dd19f7d57ab6a7fc93669780db8386e
2019-07-29 20:12:00.005 Info App: Opening SharedHttpStream Live stream from http://tvprovider.mine:80/live/my/link/17167.ts
2019-07-29 20:12:00.005 Info HttpClient: GET http://tvprovider.mine:80/live/my/link/17167.ts
2019-07-29 20:12:00.499 Info HttpClient: Http response 200 from http://tvprovider.mine:80/live/my/link/17167.ts after 494ms. HeadersServer=nginx, Date=Mon, 29 Jul 2019 18:13:01 GMT, Connection=close, Access-Control-Allow-Origin=*
2019-07-29 20:12:00.500 Info App: Beginning SharedHttpStream stream to /var/lib/emby/transcoding-temp/71b1617102ec49bca0ce6ead6c9e097a.ts
2019-07-29 20:12:00.500 Info App: Live stream opened after 494.8735ms
2019-07-29 20:12:00.500 Info App: Returning mediasource streamId 42abe5a7be3ae5af367eadb695e14565, mediaSource.Id 42abe5a7be3ae5af367eadb695e14565, mediaSource.LiveStreamId null
2019-07-29 20:12:00.503 Info MediaSourceManager: Live tv media info probe took 0.0027286 seconds
2019-07-29 20:12:00.503 Info MediaSourceManager: Live stream opened: {"Protocol":"Http","Id":"42abe5a7be3ae5af367eadb695e14565","Path":"http://127.0.0.1:8096/LiveTv/LiveStreamFiles/71b1617102ec49bca0ce6ead6c9e097a/stream.ts","Type":"Default","Container":"mpegts","IsRemote":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":false,"IsInfiniteStream":true,"RequiresOpening":true,"RequiresClosing":true,"LiveStreamId":"06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_42abe5a7be3ae5af367eadb695e14565","RequiresLooping":false,"SupportsProbing":false,"MediaStreams":[{"Codec":"h264","TimeBase":"1/90000","CodecTimeBase":"1/50","VideoRange":"SDR","DisplayTitle":"720p H264","NalLengthSize":"0","IsInterlaced":false,"BitRate":8000000,"BitDepth":8,"RefFrames":1,"IsDefault":false,"IsForced":false,"Height":720,"Width":1280,"AverageFrameRate":25,"RealFrameRate":25,"Profile":"High","Type":"Video","AspectRatio":"16:9","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"PixelFormat":"yuv420p","Level":31,"IsAnamorphic":false},{"Codec":"aac","TimeBase":"1/90000","CodecTimeBase":"1/44100","DisplayTitle":"AAC stereo","IsInterlaced":false,"ChannelLayout":"stereo","BitRate":125409,"Channels":2,"SampleRate":44100,"IsDefault":false,"IsForced":false,"Profile":"LC","Type":"Audio","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Level":0}],"Formats":[],"Bitrate":8125409,"RequiredHttpHeaders":{"User-Agent":"VLC/3.0.1"},"ReadAtNativeFramerate":false}
2019-07-29 20:12:00.503 Info App: Will record to /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts for 105.991604271667 minutes.
2019-07-29 20:12:00.520 Info App: Triggering refresh on /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts
2019-07-29 20:12:00.521 Info App: Refreshing recording parent /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur
2019-07-29 20:12:00.521 Info App: Copying recording stream to file /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts
1:01:06.462 Info TaskManager: Convert media Completed after 0 minute(s) and 0 seconds
2019-07-29 21:01:06.462 Info TaskManager: Executing Cloud & Folder Sync
2019-07-29 21:01:06.464 Info TaskManager: ExecuteQueuedTasks
2019-07-29 21:01:06.532 Info TaskManager: Cloud & Folder Sync Completed after 0 minute(s) and 0 seconds
2019-07-29 21:01:06.532 Info TaskManager: ExecuteQueuedTasks
2019-07-29 21:01:06.560 Info TaskManager: IntervalTrigger fired for task: Cloud & Folder Sync
2019-07-29 21:01:06.560 Info TaskManager: Queueing task ServerSyncScheduledTask
2019-07-29 21:01:06.560 Info TaskManager: Executing Cloud & Folder Sync
2019-07-29 21:01:06.561 Info TaskManager: Cloud & Folder Sync Completed after 0 minute(s) and 0 seconds
2019-07-29 21:01:06.561 Info TaskManager: ExecuteQueuedTasks
2019-07-29 21:58:00.070 Info App: Recording stopped: /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts
2019-07-29 21:58:00.070 Info MediaSourceManager: Live stream 42abe5a7be3ae5af367eadb695e14565 consumer count is now 0
2019-07-29 21:58:00.070 Info MediaSourceManager: Closing live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_42abe5a7be3ae5af367eadb695e14565
2019-07-29 21:58:00.070 Info App: Closing SharedHttpStream
2019-07-29 21:58:00.070 Info MediaSourceManager: Live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_42abe5a7be3ae5af367eadb695e14565 closed successfully
2019-07-29 21:58:00.070 Info App: Triggering refresh on /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts
2019-07-29 21:58:00.071 Info App: SharedHttpStream is done streaming.
2019-07-29 21:58:00.071 Info App: Deleting temp files /var/lib/emby/transcoding-temp/71b1617102ec49bca0ce6ead6c9e097a.ts
2019-07-29 21:58:00.072 Info App: Refreshing recording parent /video/Achtung Abzocke - Urlaubsbetrügern auf der Spur
2019-07-29 21:58:00.183 Debug MediaEncoder: Ffprobe -i file:"/video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-07-29 21:58:00.183 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /opt/emby-server/bin/ffprobe -i file:"/video/Achtung Abzocke - Urlaubsbetrügern auf der Spur/Achtung Abzocke - Urlaubsbetrügern auf der Spur 2019_07_29_20_15_00.ts" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-07-29 21:58:00.228 Info MediaEncoder: ProcessRun 'ffprobe' Started.
2019-07-29 21:58:00.285 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 0

[xanthos84 1]

Hi @@xanthos84, this should be improved with the 4.2 release. Let's look at an example. Please attach the information requested in how to report a problem. thanks !

 

updated today to 4.2 - will look at the new recordings if it happens again.

[Luke 37474]

Let us know how you get on. Thanks.

[xanthos84 1]

Let us know how you get on. Thanks.

sadly it happened again.

2019-07-30 18:47:00.000 Info LiveTV: Recording timer fired for Reportage.
2019-07-30 18:47:00.001 Info LiveTV: Getting media sources for recording from channel 610485 610485
2019-07-30 18:47:00.002 Info LiveTV: Opening live stream for recording from channel 610485 610485
2019-07-30 18:47:00.002 Info LiveTvManager: Opening channel stream from Emby, external channel Id: m3u_098cf0a41285b2d4389b0c519d7f220714028b13b1f5fdfc8926127bd304fef5
2019-07-30 18:47:00.002 Info LiveTV: Streaming Channel m3u_098cf0a41285b2d4389b0c519d7f220714028b13b1f5fdfc8926127bd304fef5
2019-07-30 18:47:00.003 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://my.tv/live/x/y/19658.ts
2019-07-30 18:47:00.003 Info HttpClient: GET http://my.tv/live/x/y/19658.ts
2019-07-30 18:47:00.558 Info HttpClient: Http response 200 from http://my.tv/live/x/y/19658.ts after 555ms. HeadersServer=nginx, Date=Tue, 30 Jul 2019 16:48:01 GMT, Connection=close, Access-Control-Allow-Origin=*
2019-07-30 18:47:00.558 Info SharedHttpPipelineSource: Beginning SharedHttpPipelineSource stream to /var/lib/emby/transcoding-temp/32128b6c7abc4e2bb9fd89fe39496639.ts
2019-07-30 18:47:00.559 Info M3UTunerHost: Live stream opened after 555.6926ms
2019-07-30 18:47:00.559 Info LiveTV: Returning mediasource streamId d566dad5482b689b2420e528e2a43d99, mediaSource.Id d566dad5482b689b2420e528e2a43d99, mediaSource.LiveStreamId null
2019-07-30 18:47:00.561 Info MediaSourceManager: Live tv media info probe took 0.0024161 seconds
2019-07-30 18:47:00.561 Info MediaSourceManager: Live stream opened: {"Protocol":"Http","Id":"d566dad5482b689b2420e528e2a43d99","Path":"http://127.0.0.1:8096/LiveTv/LiveStreamFiles/32128b6c7abc4e2bb9fd89fe39496639/stream.ts","Type":"Default","Container":"mpegts","IsRemote":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":false,"IsInfiniteStream":true,"RequiresOpening":true,"RequiresClosing":true,"LiveStreamId":"06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_d566dad5482b689b2420e528e2a43d99","RequiresLooping":false,"SupportsProbing":false,"MediaStreams":[{"Codec":"h264","TimeBase":"1/90000","CodecTimeBase":"1/50","VideoRange":"SDR","DisplayTitle":"720p H264","NalLengthSize":"0","IsInterlaced":false,"BitRate":8000000,"BitDepth":8,"RefFrames":1,"IsDefault":false,"IsForced":false,"Height":720,"Width":1280,"AverageFrameRate":25,"RealFrameRate":25,"Profile":"High","Type":"Video","AspectRatio":"16:9","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Protocol":"File","PixelFormat":"yuv420p","Level":31,"IsAnamorphic":false},{"Codec":"mp2","TimeBase":"1/90000","CodecTimeBase":"1/48000","DisplayTitle":"MP2 stereo","IsInterlaced":false,"ChannelLayout":"stereo","BitRate":192000,"Channels":2,"SampleRate":48000,"IsDefault":false,"IsForced":false,"Type":"Audio","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"Protocol":"File","Level":0}],"Formats":[],"Bitrate":8192000,"RequiredHttpHeaders":{"User-Agent":"VLC/3.0.1"},"ReadAtNativeFramerate":false}
2019-07-30 18:47:00.562 Info LiveTV: Will record to /video/Reportage/Reportage 2019_07_30_18_50_00.ts for 35.99062942 minutes.
2019-07-30 18:47:00.579 Info LiveTV: Triggering refresh on /video/Reportage/Reportage 2019_07_30_18_50_00.ts
2019-07-30 18:47:00.580 Info LiveTV: Refreshing recording parent /video
2019-07-30 18:47:00.580 Info LiveTV: Copying recording stream to file /video/Reportage/Reportage 2019_07_30_18_50_00.ts
2019-07-30 18:47:00.919 Info HttpClient: GET https://www.thetvdb.com/api/GetSeries.php?seriesname=Reportage&language=de
2019-07-30 18:47:01.778 Info HttpClient: GET https://www.thetvdb.com/api/B89CE93890E9419B/series/272599/all/de.zip
2019-07-30 18:47:03.729 Info HttpClient: GET https://api.themoviedb.org/3/find/tt0457219?api_key=f6bd687ffa63cd282b6ff2c6877f2669&external_source=imdb_id
2019-07-30 18:47:04.277 Info HttpClient: GET https://api.themoviedb.org/3/find/272599?api_key=f6bd687ffa63cd282b6ff2c6877f2669&external_source=tvdb_id
2019-07-30 18:47:04.423 Info App: MovieDbProvider: Finding id for item: Reportage
2019-07-30 18:47:04.580 Info HttpClient: GET https://api.themoviedb.org/3/search/tv?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Reportage&language=de
2019-07-30 18:47:04.884 Info HttpClient: GET https://api.themoviedb.org/3/tv/25027?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,keywords,external_ids,videos,content_ratings&language=de&include_image_language=de,null,en
2019-07-30 18:47:05.138 Info App: MovieDbSeriesProvider couldn't find meta for language de. Trying English...
2019-07-30 18:47:05.189 Info HttpClient: GET https://api.themoviedb.org/3/tv/25027?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=credits,images,keywords,external_ids,videos,content_ratings&language=en&include_image_language=de,null,en
2019-07-30 18:47:05.540 Info HttpClient: GET https://webservice.fanart.tv/v3/tv/272599?api_key=5c6b04c68e904cfed1e6cbc9a9e683d4
2019-07-30 18:47:05.722 Info App: Creating Season Staffel unbekannt entry for Reportage
2019-07-30 19:17:01.178 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://my.tv/live/x/y/19658.ts
2019-07-30 19:17:01.178 Info HttpClient: GET http://my.tv/live/x/y/19658.ts
2019-07-30 19:17:01.455 Info HttpClient: Http response 200 from http://my.tv/live/x/y/19658.ts after 277ms. HeadersServer=nginx, Date=Tue, 30 Jul 2019 17:18:02 GMT, Connection=close, Access-Control-Allow-Origin=*
2019-07-30 19:23:00.097 Info LiveTV: Recording stopped: /video/Reportage/Reportage 2019_07_30_18_50_00.ts
2019-07-30 19:23:00.097 Info MediaSourceManager: Live stream d566dad5482b689b2420e528e2a43d99 consumer count is now 0
2019-07-30 19:23:00.097 Info MediaSourceManager: Closing live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_d566dad5482b689b2420e528e2a43d99
2019-07-30 19:23:00.097 Info SharedHttpPipelineSource: Closing SharedHttpPipelineSource
2019-07-30 19:23:00.097 Info MediaSourceManager: Live stream 06044cf0e6f93cdae5f285c9ecfaaeb4_01413a525b3a9622ce6fdf19f7dde354_d566dad5482b689b2420e528e2a43d99 closed successfully
2019-07-30 19:23:00.097 Info LiveTV: Triggering refresh on /video/Reportage/Reportage 2019_07_30_18_50_00.ts
2019-07-30 19:23:00.103 Info SharedHttpPipelineSource: SharedHttpPipelineSource is done streaming.
2019-07-30 19:23:00.103 Info SharedHttpPipelineSource: Deleting temp files /var/lib/emby/transcoding-temp/32128b6c7abc4e2bb9fd89fe39496639.ts
2019-07-30 19:23:00.308 Info LiveTV: Refreshing recording parent /video/Reportage
2019-07-30 19:23:00.327 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://my.tv/live/x/y/16496.ts
2019-07-30 19:23:00.327 Info HttpClient: GET http://my.tv/live/x/y/16496.ts
2019-07-30 19:23:00.507 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /opt/emby-server/bin/ffprobe -i file:"/video/Reportage/Reportage 2019_07_30_18_50_00.ts" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-07-30 19:23:00.603 Info MediaEncoder: ProcessRun 'ffprobe' Started.

[softworkz 3420]

@@xanthos84 - Could you please post the full log file?

[xanthos84 1]

@@xanthos84 - Could you please post the full log file?

i can send you in private message.

[softworkz 3420]

@@xanthos84 - Thanks for sending the log file via PM.

 

Which was the recording where the problem occurred?

[softworkz 3420]

I'm asking because I could see a number of connection errors (140) while trying to access the IPTV streams. 

 

Does that happen frequently or just occasionally? 

 

Could you enable debug logging? the additional information might be helpful.

[xanthos84 1]

@@xanthos84 - Thanks for sending the log file via PM.

 

Which was the recording where the problem occurred?

 

the one I posted above! its also included in the big log file...

[xanthos84 1]

I'm asking because I could see a number of connection errors (140) while trying to access the IPTV streams. 

 

Does that happen frequently or just occasionally? 

 

Could you enable debug logging? the additional information might be helpful.

 

from time to time its happening, yeah.

 

i will enable it and look for another bad recording, but will take some time.

[Happy2Play 8505]

from time to time its happening, yeah.

 

i will enable it and look for another bad recording, but will take some time.

 

Note you have to restart your server when enabling and disabling debug logging.

[xanthos84 1]

Note you have to restart your server when enabling and disabling debug logging.

thanks for  the hint!

 

sent the new log file to dev!

[softworkz 3420]

Thanks for the new log.

 

I've found out that you're encountering the same problem as the user here:

 

https://emby.media/community/index.php?/topic/74974-serious-recording-issues/?p=770736

 

 

In your case it's just the symptoms that are a little different (due to different IPTV provider probably).

[softworkz 3420]

To illustrate this, look at the following filtered view of your log:

 

At 10:57, stream 14054 is opened

 

There's no problem, not error with receiving that stream....until...

 

11:07 h: Stream 19658 is opened additionally

 

At the same time (11:07:01) - the first stream is ended by the provider (CopyToAsync completed)

 

Then the first stream is being retried and that is kicking out the second stream.

 

From now on, both streams are fighting against each other::

 

[xanthos84 1]

thank you for your help trying to solve this issue.

but i am not sure yet, why its happening - you mean, the first stream gets kicked and emby is trying to restart it all the time - and additionally trying to start a second stream?

 

For me, this sounds like an emby issue? 

 

Emby should be able to handle some kind of "streaming issues" - it could happen anytime that the stream cuts off for a second, it should resume it as fast as possible in my view?

[softworkz 3420]

thank you for your help trying to solve this issue.

but i am not sure yet, why its happening - you mean, the first stream gets kicked and emby is trying to restart it all the time - and additionally trying to start a second stream?

No. Emby starts a second stream and this causes the first stream to get kicked.

 

For me, this sounds like an emby issue? 

One could think so that it's Emby's fault, e.g because Emby tries to reconnect too quickly... and there's some room for improvement on that side without doubt.

 

But the problem is not originally caused by Emby.

(actually I've explained that above already)

 

We just need to look at how this all starts:

• Emby is consuming a stream
• Emby is establishing a second stream
• The first stream gets disconnected

So what would Emby have done wrong here?

It is a problem with your IPTV provider not allowing more streams.

 

Currently Emby is fighting itself with the two stream requests playing ping-pong. The result of that ping-pong game are those non-working recordings that you're seeing.

 

In the future we will fail recordings or live tv playback requests after a small number of retries.

 

 

Emby should be able to handle some kind of "streaming issues" - it could happen anytime that the stream cuts off for a second, it should resume it as fast as possible in my view?

The problem with TS streams via IPTV is that there doesn't exist something like "resume" for a stream. 

We can only re-open the stream but that doesn't mean that the data is continuing from where we stopped. In case of the other thread that I referenced, the server is always starting from 20s in the past.

 

A stream can fail every now and then and we'll still try to re-open the stream - but only a limited number of times and if doesn't help, the recording is marked as failed. 

We won't run into those endless retry-loops anymore which had caused those invalid recordings.

 

But effectively that means that  - if it would happen again - you would get no recording instead of a corrupted recording.

 

 

The underlying issue that you need to solve is about why your IPTV provider doesn't allow the additional stream?

[xanthos84 1]

No. Emby starts a second stream and this causes the first stream to get kicked.

 

One could think so that it's Emby's fault, e.g because Emby tries to reconnect too quickly... and there's some room for improvement on that side without doubt.

 

But the problem is not originally caused by Emby.

(actually I've explained that above already)

 

We just need to look at how this all starts:

• Emby is consuming a stream
• Emby is establishing a second stream
• The first stream gets disconnected

So what would Emby have done wrong here?

It is a problem with your IPTV provider not allowing more streams.

 

Currently Emby is fighting itself with the two stream requests playing ping-pong. The result of that ping-pong game are those non-working recordings that you're seeing.

 

In the future we will fail recordings or live tv playback requests after a small number of retries.

 

 

The problem with TS streams via IPTV is that there doesn't exist something like "resume" for a stream. 

We can only re-open the stream but that doesn't mean that the data is continuing from where we stopped. In case of the other thread that I referenced, the server is always starting from 20s in the past.

 

A stream can fail every now and then and we'll still try to re-open the stream - but only a limited number of times and if doesn't help, the recording is marked as failed. 

We won't run into those endless retry-loops anymore which had caused those invalid recordings.

 

But effectively that means that  - if it would happen again - you would get no recording instead of a corrupted recording.

 

 

The underlying issue that you need to solve is about why your IPTV provider doesn't allow the additional stream?

 

But the question is - why Emby opens a second stream?

I know that my IPTV provider does not allow a second stream - so thats why I am using Emby exclusively for recording and NOT watching LIVE!

And I keep watching exactly for not timing two programmes to record at the same time!

 

+ another thing: i entered <1> into the pvr setting of parallel streams - I guess emby is ignoring that setting?

my fault: i forgot that i reinstalled emby some month ago, and I forgot to set this to 1 - it was one 3... which is a mistake of course.

 

i changed it now to <1> ... and now I test again if I get some bad recordings again.

because in your theory, it should not happen again now, correct?

Edited August 2, 2019 by xanthos84

[softworkz 3420]

Yes, correct. If Emby would still open two streams simultaneously, then it would be clearly a bug in Emby.

 

But if Emby would open just a single stream and you would still encounter the problem, then it's most likely that your IPTV credentials have been compromised.

 

I'd need a new log after you changed that setting to check.

[xanthos84 1]

well after some more recordings I would say it is working now as expected.

emby is not trying to open two streams at once

and the recordings dont have any unrealistic long recording time anymore.

 

so - for every other person out there which is also using some kind of IPTV service - its essential to set the simultaneous stream setting to 1 in the emby settings!