Charmed Quark Systems, Ltd. - Support Forums and Community
Sage Media Server driver (beta) - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: Driver Development (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=13)
+--- Thread: Sage Media Server driver (beta) (/showthread.php?tid=5497)



Sage Media Server driver (beta) - batwater - 11-26-2010

Fonceur Wrote:Which confirms that the TCP connection keeps getting interrupted, and is thus where you should concentrate your effort... Possibilities include:

- SageTV services keeps getting restarted. (check the sagetv_0.txt)

- Router keeps dropping/re-adding either PCs. (check the router's log)

- PC's network adapter keeps dropping/reconnecting. (check the router's log)

Thanks for the feedback, however, at this point I am not convinced that this is a network issue. Snippets of logs pasted here, I'm sending to you directly the full logs as they are fairly large.

CQC Log, both sage drivers in hi logging mode, this repeats over and over
Code:
11/26 10:09:17-bob, CQCServer, CQCDrv_HD200TVRoom_Thread0
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SagePlayer.DriverImpl_Dev.691, Status/App Status
    SageTCP (ProcessMsg): Msg received.  Item: PlayMode Data: Stop
}
11/26 10:09:19-bob, CQCServer, CQCDrv_HD200TVRoom_Thread0
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SagePlayer.DriverImpl_Dev.691, Status/App Status
    SageTCP (ProcessMsg): Msg received.  Item: PlayMode Data: Stop
}
11/26 10:09:19-bob, CQCServer, CQCDrv_HD200Mbr_Thread9
{
    CQCKit, CQCKit_DriverBase.cpp.4978, Status/App Status
    Driver 'HD200Mbr' has lost its communcations resource
}
11/26 10:09:20-bob, CQCServer, CQCDrv_HD200TVRoom_Thread0
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SagePlayer.DriverImpl_Dev.691, Status/App Status
    SageTCP (ProcessMsg): Msg received.  Item: PlayMode Data: Stop
}
11/26 10:09:21-bob, CQCServer, CQCDrv_HD200TVRoom_Thread0
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SagePlayer.DriverImpl_Dev.691, Status/App Status
    SageTCP (ProcessMsg): Msg received.  Item: PlayMode Data: Stop
}
11/26 10:09:24-bob, CQCServer, CQCDrv_HD200Mbr_Thread9
{
    CQCKit, CQCKit_DriverBase.cpp.2789, Status/App Status
    Driver 'HD200Mbr' is trying to get its comm resource
}
11/26 10:09:24-bob, CQCServer, CQCDrv_HD200Mbr_Thread9
{
    CQCKit, CQCKit_DriverBase.cpp.2827, Status/App Status
    Driver 'HD200Mbr' has its comm resource
}

Snippt of log from SageTV (same time slice)
Code:
Fri 11/26 10:09:17.160 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: There is 1 message to be sent.
Fri 11/26 10:09:17.160 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: Sending data: PLM:Stop
Fri 11/26 10:09:17.850 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: There is 1 message to be sent.
Fri 11/26 10:09:17.851 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: Sending data: PLM:Stop
Fri 11/26 10:09:18.662 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: There is 1 message to be sent.
Fri 11/26 10:09:18.662 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: Sending data: PLM:Stop
Fri 11/26 10:09:19.359 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: There is 1 message to be sent.
Fri 11/26 10:09:19.359 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: Sending data: PLM:Stop
Fri 11/26 10:09:19.750 [Thread-8@eddac] [[SageTCPServer-SageServer(0023a50008c8:9100)]]: Now listening for client connection requests.
Fri 11/26 10:09:20.162 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: There is 1 message to be sent.
Fri 11/26 10:09:20.163 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: Sending data: PLM:Stop
Fri 11/26 10:09:20.664 [Fork-HRHGH-108186@a63aad] NotPass
Fri 11/26 10:09:20.721 [ActiveRender-0023a50008c8@1ae79eb] ZRoot is aborting this draw because its unnecessary
Fri 11/26 10:09:21.164 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: There is 1 message to be sent.
Fri 11/26 10:09:21.165 [Thread-9@7ae6d] [[SageTCPServer-SageServer(001d6a4bfb95:9101)]]: Sending data: PLM:Stop
Fri 11/26 10:09:21.615 [Thread-14@1d83cf4] [[SageTCPServer-SageServer(0023a50008c8:9130)]]: Now listening for client connection requests.
Fri 11/26 10:09:22.360 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: There is 1 message to be sent.
Fri 11/26 10:09:22.360 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: Sending data: PLM:Stop
Fri 11/26 10:09:23.861 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: There is 1 message to be sent.
Fri 11/26 10:09:23.861 [Thread-15@41b635] [[SageTCPServer-SageServer(001d6a4bfb95:9131)]]: Sending data: PLM:Stop



Sage Media Server driver (beta) - batwater - 11-27-2010

I am experiencing significant Lost Comm Res errors on my SageTV - TCP Media Server driver; I'm running v 1.13.

I am wondering if anyone else is seeing the same thing. If you have a moment please check your Server Admin to see if you are seeing anything. Trying to narrow down whether it is just my system or if there is a larger issue. I've tried relocating the driver to the master server from the WHS where SageTV is installed, the result is the same.

Log of cycle:
Code:
11/27 10:49:40-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCKit, CQCKit_DriverBase.cpp.4978, Status/App Status
    Driver 'SageRepo' has lost its communcations resource
}
11/27 10:49:45-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCKit, CQCKit_DriverBase.cpp.2789, Status/App Status
    Driver 'SageRepo' is trying to get its comm resource
}
11/27 10:49:45-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCKit, CQCKit_DriverBase.cpp.2827, Status/App Status
    Driver 'SageRepo' has its comm resource
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCKit, CQCKit_DriverBase.cpp.2845, Status/App Status
    Driver 'SageRepo' is trying to connect to its device
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.1584, Status/App Status
    SageTCP: Connected to server, version 1.7.9
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.682, Status/App Status
    SageTCP: Sending message: MOD:Media
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.682, Status/App Status
    SageTCP: Sending message: ANS:XML
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.682, Status/App Status
    SageTCP: Sending message: MAX:100
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.682, Status/App Status
    SageTCP: Sending message: INI
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.682, Status/App Status
    SageTCP: Sending message: ACH
}
11/27 10:49:50-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCKit, CQCKit_DriverBase.cpp.2886, Status/App Status
    Driver 'SageRepo' has connected to its device
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.961, Status/App Status
    Name = IsTVFile
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.913, Status/App Status
    Received everything...
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.1513, Status/App Status
    Received a lineup...
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.928, Status/App Status
    name = St. Louis - Local Broadcast
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.939, Status/App Status
    Done processing channels...
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.1516, Status/App Status
    Processed the lineup...
}
11/27 10:49:55-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCGenDrvS, MEng.User.CQC.Drivers.SageTCP.SageMediaServer.DriverImpl_Dev.1518, Status/App Status
    Writing to lineups field...
}
11/27 10:51:51-bob, CQCServer, CQCDrv_SageRepo_Thread7
{
    CQCKit, CQCKit_DriverBase.cpp.4978, Status/App Status
    Driver 'SageRepo' has lost its communcations resource
}

Thanks!
-Ben


Sage Media Server driver (beta) - batwater - 11-27-2010

SomeWhatLost Wrote:just as a FWIW, I have had horrible luck with dropping/micro-dropping with Realtek LAN chips... if possible, and if yours is Realtek, you may want to try adding an Intel based LAN NIC... might fix this problem for you...

Interesting theory, I'll dig in my closet of parts to see if I have a GB intel card. The ASUS MB I'm using does have the Realtek LAN chipset on it, it is GB also. Something is certainly causing this issue. I'm not seeing Comm drops on the Sage HD200, HD300 media players though.

Not clear what "micro-dropping" is, are you suggesting that only certain sockets / sessions but not the whole port is dropping?

Thanks,
-Ben


Sage Media Server driver (beta) - SomeWhatLost - 11-27-2010

to be honest I am not sure how I would describe it...
on a scope, the whole physical layer goes down/dead for a fraction of a second... or a 'blip' or something... most connected devices don't really even notice it, they just throw away that one packet, get it resent and everyone just goes on like nothing ever happened... but that can't be good...
Intel doesn't do that... broadcom doesn't do that... neither do SMSC... so far Realtek is the only one I found that does that...
probably has more effect of just slowing down large transfers... probably really isn't the issue that you are seeing... but I just dislike realtek...


Sage Media Server driver (beta) - sic0048 - 11-27-2010

I have the Sage Server driver installed as well as 2 extender drivers installed on both my system and my parents system. Neither system experiences these timeouts that you see. Therefore I have to lean towards it being something in your system and not the drivers themselves.


Sage Media Server driver (beta) - Fonceur - 11-27-2010

I suspect the CQC Sage Media server driver might be choking on his lineup, just haven't had time to look more into it yet... Wink


Sage Media Server driver (beta) - optix - 11-28-2010

At the risk of sounding retarded, where is the SageTCP server? Am I supposed to use the one on the following thread? http://www.charmedquark.com/vb_forum/showthread.php?t=7634

I see some templates on this thread but not the SageTCPServer file.


Thanks


Sage Media Server driver (beta) - batwater - 11-28-2010

optix Wrote:At the risk of sounding retarded, where is the SageTCP server? Am I supposed to use the one on the following thread? http://www.charmedquark.com/vb_forum/showthread.php?t=7634

I see some templates on this thread but not the SageTCPServer file.

Thanks

That is the original thread, which was superseded by this thread. There is a link to the SageTCPServer Wiki which contains the installation instructions, reference the download link block.
-Ben


Sage Media Server driver (beta) - batwater - 11-28-2010

Fonceur Wrote:I suspect the CQC Sage Media server driver might be choking on his lineup, just haven't had time to look more into it yet... Wink

Looks like the problem was found. I am beta testing a new SageTCPServer driver that addresses a handshake issue between SageTV and CQC. Just installed and thus far all is well, no more comm drops.

Thanks Fonceur!!! :-D
-Ben


Sage Media Server driver (beta) - optix - 11-28-2010

batwater Wrote:That is the original thread, which was superseded by this thread. There is a link to the SageTCPServer Wiki which contains the installation instructions, reference the download link block.
-Ben


Thanks for the help!