Lost another day due to sick kids - but alas, was able to do a little in house reading - brushing up on html.
Said that I wanted to crack on with html5 but since deadlines are starting to approach, I am going to refresh my xhtml instead - no point in making it more complicated.
But very simply, have set up a page with a coveritlive iframe in the center. Will get this onto the screens and then play. I think it will be better to play with it on the screens rather than making a mock up on the laptop and then transferring that. Since I have the opportunity to build the set up in the warehouse, I should take advantage of the space and the time that will be afforded to me next week.
The image is of the basic set up of the system -
In the set up there is a computer which receives the feed via wifi. This is then scanned and injected into the media server which itself cannot process realtime feed (but there is a difference here in terminology since "realtime" means something different when talking about motion graphics - will find out what. To me, realtime also has a sense of interaction. perhaps this is the same, but when I propose interaction, it is with multiple users via the internet, whereas in media server terms, it is with the technician controlling the different pre-rendered graphics(?)). What is important here, is that the media server can "serve" the feed into the alloted position on the screens, whatever the screen set up (mentioned in the diagram itself). Within the media server, we place the feed onto its own layer and can then add it to other graphics - either produced within the media server or imported by other means.
Questions of screen resolution will arise and be answered in tandem of positioning.
No comments:
Post a Comment