0

Image select panel for slave screen/projection Museum

Ckwak

October 20, 2019 19:41

None

Follow

Hi, 

I'm trying to setup a display where there is several thumbnail pages on 1 brightsign unit (HD220) using a touch screen to select an image to display really large on a projector (second HD220) (so the first player is just a page of thumbnails attached to a touch screen) the second player is just showing full size images (as selected by the first)

I know I can do this with the sync command and have each image on the second unit listening for the sync command to go to another image, but I have over 50 images and I need each one to be able to go to any of the other 50 images which means setting up 50+ sync commands for each of the 50+ images. using this method. (painful process as I'll only have a day or 2 to program this once I get the final images)

is there a way to have one event listening for sync commands and controlling which image is up on the screen? Superstate? or Event handler? 

I don't mind setting up 50+ sync commands but I don't want to do it for each of the 50+ images individually. 

Any ideas? 

Cheers! 

• Facebook
• Twitter
• LinkedIn

2 comments

• 0
  
  Ckwak October 20, 2019 22:34

  I think I've sorted it, I just used a black image as my starting state on the slave/ 2nd screen and can send sync commands (from the master unit/screen) for each of the 50+ images to that one black slide. each of the 50+ images go back to the blackslide on a sync command of "return" 

  on my master/ 1st player each touch zone sends first a "return" sync command then pauses for 5ms then sends the sync command (i.e. 001,002 etc) to go to whatever image is selected. it means I get a short fade to black between each image selection but that's not really a problem. I can also add time out functions so the images loop if there's been no touch input for a while.

  Still a lot of sync commands to enter but less than having to do it for every image. 

   

   

   

   

• 0
  
  Brandon October 21, 2019 15:52

  Does work in all situations, but definitely look at using a Super State to apply "global" events (for the states in it) to reduce the number of redundant events required.