Beruflich Dokumente
Kultur Dokumente
Our purpose is to make the software package “I2F MediaBrick”, the core of I2F Media Products,
accessible for a broad group of users.
I2F MediaBrick is like a multi-storey shopping mall. Some users will find all they need on
the ground floor; others will want to explore the whole building.
We intend to assist especially the less experienced user in making a few basic applications and
getting concrete results. From that point on the user can discover further aspects of the software
by himself.
When you master I2F MediaBrick, you will have no trouble at all working with I2F
MediaDisplay. Indeed, the latter is a passive version of the former, lacking features for
control and interactivity.
I2F MediaController and I2F MediaComm’s can be useful for more complex applications.
Apart from this handbook, different forms of assistance are available, whether your goal is simple
or complex:
The “help” button in the top right corner gives access to a structured manual.
When you hover for a few seconds with your mouse over a specific button or sub-
ject in the software, a popup message will explain you its purpose.
3. When making your programming definitions, you can send us your .i2d files at any time.
We verify them for you and, if necessary, correct them free of charge.
2 GENERAL REMARKS
1) We assume you have read the “Technical Leaflet” available on our website under
http://www.inter2face.com/english/productsI2F.htm before getting started.
2) For a complete lexicon of terms used in the software, we refer to the manual (help
button in the software, chapter 2, Definitions).
3) The software asks you to Store or Abandon and to choose or at every step you
take, to confirm or discard your most recent definition, at least when you finish working
within a specific chapter.
Constantly confirming or discarding may seem superfluous. Our experience tells us however
that a constant awareness of these decisions is a good protection against errors in stressful
situations. One thoughtless command during the altering/testing phase may cause a
tremendous waste of time.
3 FIRST ITINERARY:
AUTOMATE PLAYBACK & LOOP OF A VIDEO CLIP
As you installed the software I2F MediaBrick, you have chosen a location for it on your computer.
The standard location is C:\Program Files\Inter2Face\MediaBrick.
You get the option to name and save a new “i2d” definition and add “file comments”, personal
reminder notes related to this I2F MediaBrick application. Place the newly created file with exten-
sion “.i2d” in your Definitions directory (see tip 2 below).
Once saved, the active i2d file is shown in the title section of the graphical user interface.
Tip 1: This title section is an all time indication of the file you are working with!
Tip 2: We suggest you store the media files you are going to use in a dedicated directory, any-
where on your hard disk. Use a clear classification, with subdirectories such as Definitions, Clips,
Backgrounds, Overlays, Sounds.
At this point you are going to assign a name to a video file (*) that you want to use and that you
have saved in your directory Clips (See tip on page 5).
Note 1 Make sure your computer can playback this file! The technical leaflet available on our website,
explains about Codec’s. Avoid conflicting playback programs.
Note 2: Name conflicts are automatically discovered and a warning pop-up appears:
Click on Clips, Add Clip, Browse. Select your file and choose a unique name which will later be
used when assigned in a playlist.
7
When you click on Preview/Setup, you open a basic non-linear editor for this media file.
In this section you can modify beginning and end of the clip amongst other features.
Use the controls to change the initial parameters.
Note 1: It is not our intention to burden this program with a full editing suite. We assume you receive
your media files properly prepared for display.
The editing features in I2F MediaBrick are merely meant for small on site corrections or for modifications
specifically related to the software, e.g. resizing for screen cut-out.
Note 2: Allow for decompression and seek time especially when large media files are used on a rather
slow computer. Each click on a control can add up to the delay.
Move your mouse to the Elements field and click right to Add an element. Select as your Clip the
previously defined media file, e.g. “clip 1”.
Click right again in the same Elements field but this time choose Add control. From the Add
control command list choose <Playlist Wait>
Before we can see the result of our work, we must define Startup, still in the chapter Assign
Definitions.
Note: Confirming these intermediary steps does not save the changes on the hard disk yet!
At this stage you might find it wise to save the latest changes in your file.i2d on the hard disk.
See chapter 1.1. Every time you save your file.i2d with the same name, you replace the previous defini-
tions by the new ones. Repeat this action on a regular basis!
9
Activate the Test the program link in the main menu (see picture on the left).
After you made sure you have saved all your settings, click on Start Test.
Note 1: If you are working with the free demo version of the software, a banner will lie on top of your
content.
Note 2: The option Enable Scheduler allows you to test the schedule defined in Autostart. We get back
to that in the third itinerary.
Note 3: Whilst your clip is running, use Alt+F4 to end test and return to the editor pages.
4 SECOND ITINERARY:
CREATE AN EVENT - START /STOP LOOPING USING THIS EVENT AS
AN INTERACTION
By closing the RUN modus (Alt+F4), we get back to the editor pages. If you were not in RUN
modus, initiate I2F MediaBrick as explained in chapter 1.1 and Load the previously saved file.i2d.
That opens the window Add MediaProduct. We complete this dialog with a local IP address
127.0.0.1 and give it a name, e.g. “local”.
This will be a stand-alone node by default.
127.0.0.1 named local is the port that can be used later when
assigning Events & Actions definitions in our playlist.
Any name can be given at this stage or later when it is required.
Note: We use a local IP address in case you do not have a working network at hand. This prevents the
system to seek needlessly for an IP address on your network. Sending out a command to seek for a non
responding IP node can slow down or even momentarily halt the system.
11
Open the Define events chapter in the main menu. Click on the TCP/IP Events button.
Here we add two different events: run the clip and stop the clip.
Note: At this stage the definition of the input string can be anything.
When the event is really sent from a different computer, this definition will become relevant!
Now we can assign these two events in different stages of the program.
Open the Assign definitions page and click on the Startup button.
After adding the “run the clip” event and keeping it highlighted, place the mouse in the action
field and right click to add a Control parameter.
In order to activate the “stop the clip” event, stay in the Assign definitions page and click on
Playlists.
Select play list 1 and click on Edit playlist. Now the panes below become available. Move the
mouse into the Events pane and click right.
Select <Add Event> from the drop down options menu.
Note: Since the program at this stage is playing the video clip in loop, any event, whether it is “stop the
clip” or another interaction, has a direct effect on the current play list, causing it to stop or pause!
13
Next we need to assign an Action to the event. Make sure the event “stop the clip” is highlighted.
Then place the cursor in the Actions pane and click right. Select <Add Control> from the drop
down list.
You have now completed the Playlist definition. To save it on the hard disk, save your definition
file in the chapter Setup your program in the main menu.
As you don’t always have peripheral apparatus available to test “events” and “actions”
definitions and thus the reliability of your definition file, it can come in handy to “fake” incoming
events. As substitutes for events, we use keyboard keys.
Open the Test the program chapter in the main menu. Place the mouse in the large white field
and click right to add 2 substitute keys.
Choose <Add event> from the list and follow the instructions: swiftly press and release the letter R
for “run the clip”.
Now we invite you to test and/or save the application in whatever order you prefer (see chapter
3.5).
Tip: when you start testing this application you will notice that the screen turns black. This is logic,
because the program starts in Idle modus and awaits your event interaction to “run the clip”. Hit
the R key to start the playlist and the S key to stop playing it. You can repeat these actions as
often as you like.
15
5 THIRD ITINERARY:
AUTOMATE THE START AND STOP PROCEDURE OF THIS SHOW &
INITIATE THE AUTOMATED BOOT OF YOUR COMPUTER
This allows you to find and assign the filename of the show.i2d of your choice.
Other parameters like start and stop time for each day of
the week can complete your specific activation agenda.
The menu under “On Power On” offers you the possibility
to postpone the start of the show after power is switched
on. E.g. you can ask the computer to boot at 08:00 AM
and the show not to start sooner than 09:00 AM.
Similarly, the “End of Day” parameter allows you to de-
fine what should happen when the given end time of a
day has arrived. Three options are available; see picture
on the right.
Trouble shooter: If a selected show.i2d appears to cause an error and you find yourself in a
deadlock, we suggest temporarily saving this particular show.i2d in another
directory or under another name.
Confirming this message will bring you back to the I2F MediaBrick editor pages. This gives you
the opportunity to remove the Autostart parameter which caused the problem and to place
the show.i2d file back in its original folder for correction and testing.
If the problem remains, we invite you to send us your i2d file by email and to inform us about
your aim.
17
This section is beyond the scope of our own software package but entirely relies on the BIOS
options of the hardware that you have installed I2F MediaBrick on.
1) Daily automated boot time: can be used to start the computer each day. This will
initiate the start up show.i2d defined in your Autostart page. Verify the help pages on BIOS
settings supplied by your hardware manufacturer.
2) Wake on LAN: WOL is an instruction that travels through the TCP/IP network and can be
initiated, amongst others by an “I2F MediaBrick computer”. This can be done by
assigning an Action Control parameter in a playlist or event list/actionlist!
If you don’t find the answers to your questions in this handbook or in the technical leaflet, feel free
to contact us.
Contact persons:
Mark Schueremans – product manager
Linda Pollers - communication