Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1161179" data-attributes="member: 82144">There are no codecs involved in the recording process, so I'm not sure whether this explanation works.&quot;The thing doing RTSP&quot; is called the streaming server. It definitely does not send a signal to the client. Rather, the client sends a duration update request every 5 seconds or so:15-11-2015 14:19:49.779 generateSDPDescription() duration 6058.841797 : a=range:npt=0-6058.84215-11-2015 14:19:54.29 generateSDPDescription() duration 6063.064941 : a=range:npt=0-6063.06515-11-2015 14:19:58.278 generateSDPDescription() duration 6067.326172 : a=range:npt=0-6067.326Using that information, the client is able to know how much of the recording is left to play etc.A loop is a single thread, so it is more likely to only max out one core. If your CPU only has one core then that would translate to 100% CPU; on the other hand if your CPU has 8 cores that would translate to 12.5% CPU (100 / 8). In other words, TV Server may well have been stuck in a loop. Without access to all the log files that I asked for (especially the TVService.log for the relevant period) I'm not able to say more than that.Sure it's suspicious, but It's hard to know if it is really relevant without access to the other log files (particularly TsWriter).Note SMB may be used if you were recording to a share. That doesn't appear to apply for you, so the message may be a misinterpretation of the cause for a particular set of symptoms. Again, I can't say more than that without access to the other log files.</blockquote>

[QUOTE="mm1352000, post: 1161179, member: 82144"] There are no codecs involved in the recording process, so I'm not sure whether this explanation works. "The thing doing RTSP" is called the streaming server. It definitely does not send a signal to the client. Rather, the client sends a duration update request every 5 seconds or so: 15-11-2015 14:19:49.779 generateSDPDescription() duration 6058.841797 : a=range:npt=0-6058.842 15-11-2015 14:19:54.29 generateSDPDescription() duration 6063.064941 : a=range:npt=0-6063.065 15-11-2015 14:19:58.278 generateSDPDescription() duration 6067.326172 : a=range:npt=0-6067.326 Using that information, the client is able to know how much of the recording is left to play etc. A loop is a single thread, so it is more likely to only max out one core. If your CPU only has one core then that would translate to 100% CPU; on the other hand if your CPU has 8 cores that would translate to 12.5% CPU (100 / 8). In other words, TV Server may well have been stuck in a loop. Without access to all the log files that I asked for (especially the TVService.log for the relevant period) I'm not able to say more than that. Sure it's suspicious, but It's hard to know if it is really relevant without access to the other log files (particularly TsWriter). Note SMB may be used if you were recording to a share. That doesn't appear to apply for you, so the message may be a misinterpretation of the cause for a particular set of symptoms. Again, I can't say more than that without access to the other log files. [/QUOTE]

Verification