Jump to content

Search the Community

Showing results for tags 'file transfer'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type



Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. I have a problem with the file transfer to the display PC. Specs display workstation W10 - 64Bit LTSC Enterprise 2019 Build 17763.rs5 release 180914-1434 Watchout 6.7 Mainboard: Shuttle SZ270R8 GPU: AMD RadeonPro WX7100 + Synchboard S400 CPU: Intel i7-7700K RAM_ 32GB Datadrive: NVMe SSD Samsung 1TB Windows up to date all drivers up to date On board intel-i211 Networkadapter and Intel 2-X550 10Gbit-Networkadapter Case 1: In my timeline there are only some images (jpg,png). When I start the transfer (CTRL+L), the display computer needs up to 20 minutes for an HD image or freezes or the network connection breaks off by itself after some time. Watchout Display only shows "Caching". In Explorer, however, I can see that the content has been transferred. The content is only displayed after restarting the display software. Case 2: In my timeline there are the same images and also movies. The transfer of the images as well as the movies is as fast as usual and completely error-free. How can this be? Case 3: I insert another image into the timeline and start the transfer. Now the same error occurs as in Case 1. In summary, images are only transferred if movies are also transferred to the display workstation at the same time. It does not matter whether I address the display workstation by name or IP. My DELL 5820 display workstation works perfectly with the same image (LTSC 2019). If I use Windows10 LTSB 2016 (tweaked) or even W10 Professional (tweaked or non tweaked) instead of LTSC2019, Watchout works flawlessly on my Shuttle workstation using the same hardware (display computer, cable and switch). The transfer of individual images runs quickly and smoothly. Does anyone have a solution? The error is reproducible. Thank you for your help. Andreas Grunewald
  2. Hi, We recently had a show that we updated from watchout 4.3 to 5.1 to use the multiple outputs per display computer and we ran into a couple issues. We had 1 production and 2 display each driving 3 outputs. Watchout machine specs CPU-Core i5 750 @2.66 Ram-4GB GFX-AMD Radeon HD 6970 2GB GDDR5 Mem Win 7 32bit HDD-Solid State drives Rack Mount cases First and main issue was: every time we would change the output # on a display computer it would re-send all of file into the computer even though there files were already there. This certainly caused some slow down in the production. We had to change output # for troubleshooting purposes. But this would also be done if we would need to switch to a back up display computer in which case it would be a problem. 2nd: The auto-detect of the alpha type for stills wasn't detecting properly. This use to work just fine in watchout 4 but in 5.1 I had to go specify the type of alpha for each media. That only seemed to happen on stills. 2nd and 1/2: Hard to say exactly what happened here but 1 night we made some very specific masks and put them into the show. All was well then but the next day when we turned on everything the masks were not the same anymore. (I do not have all the details because we had left by then) I asked the watchout technician onsite to try to play with the alpha modes, I also re-sent him the files because maybe they had been corrupted but in the end he had to re make the masks from scratch. Very strange. Any thoughts on that? 3rd: The production computer is getting TCP command from a medialon machine in this installation and at one point i turned off the triggering so I can work without being triggered but I was still receiving the commands. What do you think? Thank you.
  • Create New...