Morning everyone,
I'll start by saying that I am using @DJBlu modifications, however I am not using any softcams while trying to understand this issue.
To give some back ground, I have a virtualized server which consists of an AMD FX 6100, 14Gb Ram, HDDs with 2 TBS 6981s. I'm currently running ESXi 5.5 as the hypervisor. This is connected to the Gb network via a 1Gb network card.
On top of this I'm currently running windows server 2012 essentials as the AD DC; I have no other server running at the moment as I want to sort the media side out first.
The problem I have is that TVserver can due to the FTA channels fine BUT once TVServer is set to timeshift, the client (connected to the domain without the essentials connector) takes around 15-20s to connect to the UNC timeshift file. It takes even longer if you connect via RTSP.
I've attached what I think are the most useful logs from both the client and the server. Can someone have a look and see what might be causing the client to take a very long time to connect?
Thanks,
Chris
EDIT: also what does this mean:
02-11-2013 11:25:24.991 [16fb0048] [ fc] CTsReaderFilter:
uration - correction to predicted duration: 1619267.000
as TV playback stopped after about 20 minutes but TVserver is still writing to the timeshift file as the client hasn't closed it down, it just stopped playing...
I'll start by saying that I am using @DJBlu modifications, however I am not using any softcams while trying to understand this issue.
To give some back ground, I have a virtualized server which consists of an AMD FX 6100, 14Gb Ram, HDDs with 2 TBS 6981s. I'm currently running ESXi 5.5 as the hypervisor. This is connected to the Gb network via a 1Gb network card.
On top of this I'm currently running windows server 2012 essentials as the AD DC; I have no other server running at the moment as I want to sort the media side out first.
The problem I have is that TVserver can due to the FTA channels fine BUT once TVServer is set to timeshift, the client (connected to the domain without the essentials connector) takes around 15-20s to connect to the UNC timeshift file. It takes even longer if you connect via RTSP.
I've attached what I think are the most useful logs from both the client and the server. Can someone have a look and see what might be causing the client to take a very long time to connect?
Thanks,
Chris
EDIT: also what does this mean:
02-11-2013 11:25:24.991 [16fb0048] [ fc] CTsReaderFilter:
as TV playback stopped after about 20 minutes but TVserver is still writing to the timeshift file as the client hasn't closed it down, it just stopped playing...