Here are some examples of our standard addons:
digital picture processing
continuous conversion of all photos from a source directory using various adjustable methods and storage in a destination directory
Sephia, Chromakey, image enhancement, fog filter, crop, rotate
This solution has two parts, the client software on your central unit, and our photo server with a set of PHP-scripts using a my sql database for customer settings and thousands of photos. The access to the photos can be done by several methods.
picture calendar or by code or “scan & post”
- publishing all photos on your homepage in a calendar view or by typing an individual code (printed on the picture) or
- generating an individual image code for online personalization; this is printed on the photo as a string or QR code; (only) these photos (selectable) are transferred to our photo server and can be accessed directly from there (by entering code on a landing page or in an image calendar
- from there download, eCARD shipping or posting (Facebook, Google+) possible
- amin login to set variable data (design, posting texts, functions)
- automatic admin mails for exception messages and
- user statistics evaluations via integrated MySQL database and Google Analytics
Access by code:
Test this here:
Access by code (8619057089002112)
Access by calendar:
Photo assignment to a code that is read by a connected RFID reader in a certain time window. This is technically the most personal personalization so far: At the start of an attraction the guest reads in his chip, some time later he releases a photo via sensor and we automatically add the filename to his RFID-ID. This allows a personalized image display at a point of sale / photo booth even hours later – after re-reading the appropriate RFID chip. We already have this procedure several times with different RFID-readers.
It happens again and again that certain customer requirements are (still) not or only partially coverable with our standard modules. Then we classically classify, often using existing libraries. If it is foreseeable that we will not be able to use this new function for other later projects in the context of release planning, we have to process this additional service as an independent project (specifications, cost estimate, programming, acceptance). This has happened only once in the last 4 years, when implementing an XML interface to the existing cash register system in the fun pool area. Otherwise, since then we have been able to make all the necessary adjustments using simple parameter settings – instead of individual programming.