Tech Workshop/replay
From Steeple
Contents |
[edit] 1 Replay at the steeple tech workshop
Introduction, Installing and Testing Replay Practical and Experimentation lead by Tobias Wunden from the Replay development team at ETH Zurich. This may run on into the afternoon session.
[edit] 1.1 Installation overview
Run the installer.
Installation depends on 3rd part installer svn (for ffmpeg, mediainfo), which is often blocked. So need to have better ways of distributing the third part tools. At the moment, make sure the svn tcp/udp ports are open, and the installation should work. (Port 3690). ffmpeg is only available via the svp protocol, so you must make sure that the svn port is open. (Errors and bugs can be posted here: http://replay.origo.ethz.ch/issues) Also install perian.
[edit] 1.2 Start replay
Replay has been preinstalled on the iMacs, so to start replay:
cd /Applications/Replay bin/startup.sh
Start the igestor application
http://localhost:8080/replay-ingestor
[edit] 1.3 Create a media bundle
- Upload the file (grabber.mp4) by using "upload"
- Add file metadata
- Add series metadata (or click the cross next to "series metadata")
- Then click create bundle.
[edit] 1.4 Look at the dashboard
http://localhost:8080/replay-dashboard
It should say
All system components connected.
You should be able to find your bundle. When the bundle has finished transcoding, go to the next step
[edit] 1.5 View your output
http://localhost:8080/replay-store/
[edit] 2 Configuration
[edit] 2.1 siteformats.properties
To add additional formats. Any command-line driven encoder can be used.
[edit] 2.2 site.properties
manager.address = localhost
Can change this.
node.threads = auto
workspace.dir = replay/workspace
Shared storage.
store.url = ... store.entry.url = ... scheduler.url = ...
[edit] 2.3 sqldb.properties
Can run replay with different databases, e.g. MySql or postgres. ETH uses postgres. But the demo installation of replay uses different db for demo purposes.
[edit] 3 Distributing nodes
You'd copy the whole /Applications/replay folder to a new server, and then (e.g.) just keep the composer node to set up a composer node.
On the composer node, open
web.xml
Change the name of the node:
<param-name>node.name</param-name> <param-value>Composer</param-value>
The name of the node most be unique. A few lines below:
node.address node.port
need to be configured, so that the replay manager can contact those nodes.
Then edit
site.properties
to point at the manager.
Might need to make adjustments in the Composer.properties, kept in a file like
<nodetype>.properties Composer.properties
If on a particular machine (e.g. OS X) the composer has a different work dir (where the shared space is mounted, e.g. /Volumes/something vs. /mount/something) you can adjust node.workdir
node.workdir = replay/replay-composer
