cleavelam

Hello there, We have set up our own RTSP streaming server for server network video to WATCHOUT. When playing the same h264 encoded RTSP video, it works fine on VLC player, but when fed into the WATCHOUT it couldn't be played, and yet there isn't any error message displayed in the WATCHOUT MESSAGE window. Any suggestion that how can we fix it? Any special configuration needed on the server setting / codec setting? Thanks very much for the help. Cleave

Thanks very much for the information. After changing all the Video to HAP and updated to 6.1.5, the video can be played smoothly for longer time. Yet after a pretty long time (say 24 hours), some of the video cannot be played. We have 4 4K display, after playing long time - sometimes video cannot be played on all 4 display - sometimes video can be played on 1 display but not the other 3 - sometimes video can be played on 2 displays but not the other 2 - All video are triggered by the same timeline. It seems to us that it might be same ram issue, maybe the software is taking too much memory after long time of running? Is there commands to purge the memory that WO is using on the display computer? What would you suggest us to try / look into? As in our application, the display will be always on and thus we don't have down time to restart the software. Is there any settings we can do to improve the performance? Thanks very much.

Here's the spec of the Display Computer we are using - LGA2011-V3 ASUS WORKSTATION MOTHERBOARD (X99-E WS/USB 3.1) SIX CORE CPU - INTEL CORE I7-6850K 3.4GHz 128GB DDR4-2400MHz RAM 2X 256GB SAMSUNG 850PRO SSD FOR OS (RAID 1) 4X 500GB SAMSUNG 850PRO SSD FOR MEDIA (RAID 10) NIVIDIA GEFORCE 1070 8GB RAM (2x HDMI + 2xDP) 2X DATAPATH VISION SD HD4+ CAPTURE CARD (TOTAL 8 LIVE FEED) And the display computer is connected to 4 x 4K Display. The Show we are testing have 2 x 4K video that keep on running and will be changed to other 4K video after some amount of time, with 3-5 HD video clip playing on top of it, each lasting around 10-15 second, randomly selected from a pool of 30 timeline with different HD video. The HD video clip is triggered through Telnet to turn on and off, which is triggered between 10-60 seconds. The Video is encoded with HAP. And the show have 8 live feed in it. We have done benchmarked our Graphic card too - it have 8 gb of memory, and when the show is playing only under 2GB of Graphic card memory is used - so we are really confused by the Low Video Memory error. Also, if there is indeed not enough video memory, shouldn't it be crashed right after the show starts to play those video? Or it will occupy more and more graphic memory as the time goes or when the time is played and stopped? And sometimes when it crashes it doesn't even send out the "Error" feedback message.. What aspect would you suggest us to look into the error? Thanks very much. And yes we will try the 6.1.5 soon.

Hello all, I am doing a stress test on the WATCHOUT Display Computer, and I've got a few videos running together at several layer. It worked fine in the beginning, and after an hour or two it would crashed out, and the following error has been shown on the Telnet. Error 3 3 "Not enough video memory; Video \"_root/Y_/Test.mov\" of Media Folder \"Test\" of Media List" And i've got a few question - 1. The first "3" after the "Error" means "Rendering API error", what about the second "3"? As specified in the manual it said "Error number or description string. May be zero." If it's error number is there any reference that we can reference to? 2. The show ran fine at the beginning but it would crash after running for a while - does it mean the video memory is not released sometimes? Or can it be other causes? What would be the best way to look into this error? Any suggestion? 3. Is there any other logs that we can refer to in order to find out the root cause the issue? Thanks very much for the help. We have been doing stress test for quite a while and this issue appear "randomly" - sometimes after 2 hours, sometimes after 14 hours - really hoping we can find out the reason behind this.

Thank you very much for the information. I've taken a look at the Systems Manager - and yes it seems that it can have full control over the WATCHOUT at the flex application through the package - i suppose it is drive by the Telnet command too? As we would like to control WATCHOUT more remotely, we've looked into the Manager codes and the API documentation of the WATCHNET - seems it's the API documentation of com.dataton.watchout.* - of which is a flex application package i suppose? Is there a manual of all Telnet commands / operation available to control WATCHOUT at the moment that we can reference on? It seems that the Telnet Command list in the WATCHOUT 6 manual is not comprehensive - just like the "getAuxTimelines" telnet commands are not discussed in the Manual.

Thanks very much for the all the help. We are using watchout 6.1 and I've gone through the manual (WATCHOUT_Users_Guide_6.1) and seems the telnet commands listed in the Appendix C are mostly control, but not fetching the task list information from the WATCHOUT. (Except querying for a task status explicitly, but seems there ain't commands that we can query for all information - and the getAuxTimelines are not found in the manual too.) Seems we'll need the "WATCHOUT Systems Manager developers kit" to know more about the remote access / API etc - may I ask where can I obtain it? Can I download it from the website?

I would like to ask is it possible to retrieve the task list information from Watchout through telnet? E.g. what are the existing task list / task name / task duration , time of pauses and other control related information etc. Thanks very much.