Professional Documents
Culture Documents
The Manual
Version: 7.0.0.118
Date: December 2018 © 2018 APP Helmond
Page 2
Content
• Starting the application + Registering your license
• Appendices
• Quick Start + File Formats + Folder Structures + EOS Support + Main Menu
• Guidelines
• Calligram Station views + Feature detection + Calligram presets + Chromakey guidelines +Emojigram guidelines + Error messages
Disclaimer: the content of this Manual is carefully checked and tested with the application. The user may encounter different views as depicted in this Manual. APP Helmond cannot guarantee a 100%
reflection of all situations, customizations and for all the different systems. The Manual will however explain most of the functionality, where some details of the inner workings and of some controls are not
explained in detail. For more details, please consult the (legacy) web help from previous versions of Calligram Creator, or contact us to help you in understanding how the application works.
ADMIN FUNCTIONS
General Settings + Reprint and Size +
Event Management + E-mail + Webcam +
Booth Mode + Canon EOS + License
Page 7
Restore a previously
stored Event
Page 10
C:\Users\Public\Documents\APP\Calligram Creator\Resources\Mail
• This mail text is used by default. You can always change the mail body text. Several tools are available:
• Save: save the current lay-out in the file ‘MailBody.htm’
• Reload: discard any unsaved changes by reloading the ‘MailBody.htm’ file
• Embed Calligram: the Calligram image will be placed in the mail itself, as an image
• Insert picture: you can insert a picture ate the cursor
location (a pop-up windows will help you locating the
target image)
• Hyperlink: add a hyperlink to the word that is currently
selected
• Load custom HTML: see next page
HOMEWORK STUDIO
Calligram Settings + Emojigram Settings +
Legogram Settings
Page 25
• 808B3C
• F36C95 The colour selection pop-up window
• FF00FE to select the colour you want to use
• FF7F00
A visual representation of
the image library
Create your own library of emoji
images (.PNG format only)
can be set
• Type of brick:
• LEGO or Ministeck
• For Ministeck also an option to avoid 1x1 parts,
and to apply the famous L-shape parts
Additional options for
Ministeck parts
Page 33
BRANDING STUDIO
Templates + Borders + Icons
Page 34
Double-click on a
template to load it
CALLIGRAM STATION
Shapshot queue + Customizations +
History
Page 39
GUIDELINES
Calligram Station views + Feature detection
+ Calligram presets + Chromakey guidelines
+Emojigram guidelines
Page 45
• Calligram Station has the possibility to see 4 different views. In the above image three of these are shown. Each view is
represented by a little icon, under which a yellow line is see, showing which view is active. You can click on this icon to change
the view. The four are:
• Snapshot view: the original snapshot image is shown. The icon is a camera. You can also pan and zoom the snapshot with your mouse, to
create the best view of the snapshot from which to create the Calligram. The size of the image is set in the printer settings, where the
paper size is defined, and the image in the Calligram Station follows this size.
• Calligram view: this view only becomes available when the actual Calligram is created. When inactive, the ‘Aa’ icon becomes grayed out. In
case of an Emojigram or Legogram, the image shown here is the result from these methods.
• Colour view: you can see a preview of the colours by clicking on the palette image. This view is the unprocessed snapshot, but already
outlined where the Calligram text will be put. Each change of colour is reflected in this view.
• When a new snapshot has loaded, the Snapshot view will be updated, and when clicking on the palette icon, it might take a
second to update the colour view. However, the Calligram view still remains, because the new snapshot wasn’t yet processed.
Page 46
Feature Detection
Left: original (no detection)
Middle: skin detected
Right: face detection
• Feature detection is an exciting function to detect (facial) features. The features that are identified are:
• None: it shows the original image.
• Skin: it tries to find the colour of skin and centers the outline of it.
• Face: it tries to find the face, focusing on typical face features as eyes, mouth, nose, and ears.
• It is somewhat unpredictable, because of how the features can be obscured: people might be wearing attributes (hat, glasses) or
have a different face angle (tilted), and other distracting features (hand on mouth, two people in one image). The approach that
is used to detect the skin is by colour where almost every skin colour in the world can be traced – but this is not a 100%
guarantee, for instance because of different lighting environment (sunset, TL-lighting, direct flash).
• The face detection follows the analysis approach from Intel, called ‘OpenCV’, where facial features are analyzed using empirical
data. This approach is very reliable, but when attributes are found, the application might not be able to detect a face.
Page 47
• In the Homework Station, the Calligram filling and lines can quickly be assessed by using the 8 presets. Each of the preset has a
typical effect, created from snapshot lines thickness and the areas being filled. Since the Calligram is created from two
parameters (outlines and areas in the snapshot), you can pretty accurately set the default for the type of face, posture and
lighting.
• These 8 presets are meant for quick assessment, and the actual settings can be fine-tuned further by using the two sliders in the
interface. These two sliders will also become available in the Calligram Station, so additional ‘micro-tuning’ during an event per
snapshot is still possible. Please be aware that the change only happens when the mouse sends a button-up signal, so the
change will not occur while moving the slider itself, but only at the end of the slider change.
Page 48
• In the image above a blue screen image is shown. Since the background is pretty much homogeneous, clicking on any place in
the blue area will automatically select the correct chromakey. It will also reflect this key colour in the colour-picker control, while
at the same time deleting the chroma parts of the chromakey (here: the blue pixels). These parts are now shown as transparent
pixels, but these will become white in the Calligram, where no text is shown (right image).
• The green screen example above follows the same approach as the blue screen image, but because the green background is not
homogeneous enough you should now also use the sensitivity slider to select similar chroma pixels, and correct for the
differences in green shade (e.g. because of the lighting, shadows, folds in the screen background, etc).
Page 49
APPENDICES
Quick Start + File Formats + Folder
Structures + EOS Support + Main Menu
Page 51
Quick Start
Calligram Creator is preconfigured with example snapshots and settings. The user can immediately create a Calligram after
installation. In short these steps are typically made for a Calligram. First prepare your necessary data:
Since all input data is already preconfigured, the user can immediately start creating a Calligram:
Finally, wait for the mail to be sent, and open your mailbox to find the mail.
• Optionally: print the Calligram image (it will be sent to the default printer in your system)
File Formats
• The application requires certain files to be input, where these files must have specific formats to be read correctly.
• Text file: this can be any file, saved as an ASCII test file (Unicode it not recognized in the current version), e.g. by saving the text
in Notepad (ANSI, .TXT file extension). Assure sufficient words to be available (a minimum of 100 words is recommended).
Alternatively the admin can prepare a special input file, where individual words are used, and the target size of each word. An
example is show here:
the: 120
and: 106
right: 33
Everyone: 30
has: 28
shall: 27
rights: 21
his: 21
any: 18
for: 17
human: 12
• Colour file: the colour file can be an image (jpg, png, bmp file format) or a text file with HEX codes of each colour. An example is
shown here:
EE0707
433FD7
116506
056862
• Fonts list file: the admin can select one font for the entire Calligram, or offer a predefined set of fonts. An example is shown here:
Arial
Black Chancery
Bookman Old Style
Century Gothic
Lucinda Console
Page 53
Folder Structures
• Calligram Creator requires a few folders to be structured to a strict format. This is needed to save, manage and read certain
essential data.
• Resources: this is a Calligram Creator specific preinstalled
set of folders. These are required for storing artwork and
mail data, and other application relevant information. In
most of these the user can add customized files, e.g. for
backdrops and icons, and colour files for the Calligram
colours. The user can also replace the content, but there
should be at least one file present, and the names of these
folder must not be changed.
• Libraries, Projects and Settings: do not change or rename
these folders, nor its content. They are required to run the
application properly. The projects folders will be the
default to read and save projects, so the content might be
changed during the preparation of an event.
• Records: this file structure is required to save and process
data during an event. Although the ‘Store’ and ‘Booth’
folders can be changed (referred to as the ’Save Folder’
and the ‘Watched Folder’ in the application’s home tab),
the ‘Backup’ folder cannot be changed. When creating a
backup the folder structure in the zip file can be hard to
restore when folders are typically local and not existing
when a restore action is done.
Page 54
EOS Support
• The installed Canon EOS files are only supporting a limited series of EOS cameras. The reason for it is that we have tested this
feature with a 1100D (or Rebel T3) camera from 2015. later cameras may require a different DLL file. According to the Canon
specification, the following EOS systems are reported to work with the installed DLL file:
• EOS 1000D • EOS 450D • EOS 600D • EOS 700D • EOS-1D C
• EOS 100D • EOS 500D • EOS 60D • EOS 70D • EOS-1D Mark III
• EOS 1100D • EOS 50D • EOS 60Da • EOS 7D • EOS-1D Mark IV
• EOS 1200D • EOS 550D • EOS 650D • EOS 7D Mark II • EOS-1D X
• EOS 40D • EOS 5D Mark II • EOS 6D • EOS M • EOS-1Ds Mark III
• More cameras may be supported, but only the 1100D camera was tested. The list above was provided by Canon, where the SDK
of Canon was used that supported these cameras. It is expected that the Canon SDK files indeed include support for these EOS
cameras. If A later camera than 2015 is required, please let us now (sybren@apphelmond.com), we might be able to provide the
correct DLL from the Canon SDK.
• One word of caution: better not activate the webcam at the same time (for laptops: deactivate automatic webcam activity),
because the application will only trigger the first camera that it found in the Windows system. It's not predictable which camera
this will be. It will very much depend on the admin’s ability to manage a tethered camera. Since the EOS camera is usually
attached via USB, the selection of camera should be plug and play.
Page 55
Error messages
The application has many built-in consistency checks, error checks, and similar, to assure that in the rare case of an error, the
application not only continues to work properly, but also informs the user about the issue that was experienced.
There are two type of error messages: generated by Windows, and generated by the application. The application messages are
typically in the interface colours (‘skin’), while the Windows messages are like any other message style when working in Windows.
The Windows messages are typically generated by the Windows system, the application has built-in ‘catch-all’ approaches, and with
an error it will show a message in the message log (see remarks in the second bullet above).
Page 57
1. Get acquainted with the application. Preferably a few days before the actual event take place. This way the features and
functions are experienced in a safe environment, by e.g. by studying the help documentation for details and background.
2. Use the tutorials to learn. In the extensive online help documentation we have provided quite some tutorials. This way the user
gets a fairly complete experience of the major functions and features, and is able to quickly resolve situations.
3. Test, test, test. Please test the application with images and files that the user would like to use in the actual event. The
application has certain limits (size, speed), and by thorough experimenting the user will understand these limitations, and in a
safe environment.
4. Use a high-end system. Always use the best possible system to run the application. Our applications require a fast, healthy
system, so we discourage to use older systems in the live sessions.
5. Assure an up-to-date Windows. In addition, Windows should not be in a state of being updated, because some system
functions might have been disabled because of the updating process.
6. Connect to a high-speed internet. The application requires internet connection to send e-mails and these mails can easily be
some MB in size. Also exclude the virus software for this application and close all applications that are not required in the live
session.
Although APP Helmond aims for a 24/7 support, global time differences and off-line periods will always occur. APP Helmond
cannot be held responsible for issues during live sessions if the user did not fully prepare (e.g. as described in the points above).
APP Helmond is committed to support our customers. Nevertheless, support during a live session may not always be possible.
Team APP Helmond wishes you good events and great fun!
Page 58
END OF MANUAL
More detailed information can be found in
the legacy help documentation via the Main
Menu -> Tools -> Show web help (legacy)