[Announce] MPTvClient V1.2.5 (20.12.2007) II (2 Viewers)

[Krazz]

Works like a charm for me now. You da man gemx!

 

[camoura]

It works for me too, but....

31456 TCP TvService Remote Control OK
554 TCP RTSP Streaming OK
1433 TCP MS SQL (TCP) FAILED
1434 UDP MS SQL (UDP) OK

Perhaps that's the cause of the sliguish behavior?

Can anybody help??

 

[Al_Capone]

the latest build connects to DB just fine - thanks.
It closes just fine as well..

"connect" button gives the same error message as before.. so I cannot use it.

 

[ravenrocks]

Works like it should.


Thanks

 

[level20peon]

gemx: It just came into my mind that it would be great if your Applikation would update the channel-list every 5 minutes (or in custom intervals). Have you thought about such a feature, yet ? At least I cannot find anything about it in this thread.


-level20peon

 

[camoura]

Does anybody know what can cause this?

It works for me too, but....

31456 TCP TvService Remote Control OK
554 TCP RTSP Streaming OK
1433 TCP MS SQL (TCP) FAILED
1434 UDP MS SQL (UDP) OK

Perhaps that's the cause of the sliguish behavior?

Can anybody help??

 

[Krazz]

I have the same phenomena when I run on LAN, but it works anyways. If I run over the loopback all the port checks return OK.

 

[camoura]

I have the same phenomena when I run on LAN, but it works anyways. If I run over the loopback all the port checks return OK.

no sluguish behavior when connected?

 

[Krazz]

No, everything works fine for me.

 

[SciDoctor]

Works here apart from this with VISTA 32 server.see attached.

The other intermittant bug NETWORK clients reciving no stream ( RTSP streamer not being initialized ) was down to a bug in the SERVER Powerscheduler setting 'reinitialize service on start-up' when the server had just returned from standby/hibernation. Turn this off and all is ok with network clients.