VideoWall only publishes to one screen out of 2x2 matrix

  • 2 Replies
  • 3790 Views

0 Members and 1 Guest are viewing this topic.

*

Offline stupidboy123

  • Newbie
  • *
  • 2
  • 2
VideoWall only publishes to one screen out of 2x2 matrix
« on: August 18, 2010, 09:37:15 PM »
The project i am working on has a 2x2 videowall.  All screens will publish correctly if addressed individually, but once a videowall workspace is created and an image is published to them, the image appears only on the first screen in the list, scaled up ( which is correct) so you can only see 1 quater of the image, but the other 3 screen are completely black.

Please does anyone have any ideas of how i may resolve this. 

Many thanks in advance

DIGITAL SIGNAGE HELP AND SUPPORT

VideoWall only publishes to one screen out of 2x2 matrix
« on: August 18, 2010, 09:37:15 PM »

*

Offline HandyMAN

  • Newbie
  • *
  • 11
  • 4
Re: VideoWall only publishes to one screen out of 2x2 matrix
« Reply #1 on: August 29, 2010, 07:36:31 PM »
It could be that you have the screens configured using the OSD setup.
In MagicInfo, check the workspace and each client screen setting to make sure it is configured the same.
If this doesn't resolve, I need to know what version of MagicInfo are you using on your PC and on each client display.

*

Offline stupidboy123

  • Newbie
  • *
  • 2
  • 2
Re: VideoWall only publishes to one screen out of 2x2 matrix
« Reply #2 on: August 29, 2010, 10:08:55 PM »
Thanks for your post....it turns out the problem was the XP (embedded) on the screens 460 uxn-2 ( i think ) had windows firewall switched on, which seemed fine when publishing a single screen but caused problems when trying to publish to a video wall.  I can only assume that Magic Info Pro uses a different method of broadcasting to each screen when using the videowall feature and therefore the firewall exceptions for a single screen are different than the one used for multiple screens....my solution was to just turn the firewall off on each of the screens. 
A simple remedy that suprisingly Samsung's support desk never suggested ( although they were very helpful and tried very hard to rectify my problem :-) ).

I hope this is of help to anyone else who encounters this problem, and unlike myself, they don't waste days trying to find a fix :-)