Category: Tech

Telekom Hotspot im ICE

Da ich nicht weiß, wohin mit meinem Ärger über das löchrige Wlan im ICE 276 (Surfen Sie bei 300 km/h…) paste ich hier mal einen durchlaufenden Ping vom 26.12.13 von ca. Braunschweig bis Berlin. Für Hinweise, wem man bei der Telekom das mal unter die Nase halten sollte, bin ich natürlich immer dankbar. Dieser Service kostet übrigens 4,95€/Tag…


The Live-Recording-Workflow

For all of you who are interested in the video recording workflow used at Reject.JS and in Berlin, September 2013: Here is a short wrap-up.

Video FOH

Jakob preparing the setup.

For all who haven’t seen the videos yet, check out the 2013 Playlist and the Reject.JS 2013 Playlist

We recorded and edited all talks live, so they were ready to be uploaded right after the event. No editing or post-production (inserting lower-thirds, corner-logos, intro-slides) was needed.

We used a video mixer to switch between three different sources: Two cameras and the live capture from the presentation laptop of the speakers to show either slides or live coding examples. One camera was operated while an intercom enabled the communication between the live editor and the camera operator during the talks. This means that the live editor was able to tell the camera operator exactly which images or movements he needed.

The basic video set-up included:

  • 2 HD Cameras (Sony EX1)
  • 1 video-mixer (Blackmagic)
  • 1 Multi-Image-Processor (scaling and conversion of the live-capture from the laptop of the speakers)
  • 1 H264 Encoder
  • 1 ProRes Recorder
  • 1 Audio-Mixer
  • 2 Displays
  • 2 Laptops

Audio was provided by decibel Sounds, who did an amazing jobin providing us with a nicely leveled stereo mix (headsets, handheld mics and sound embedded in presentations). The stereo mix was then embedded in the video stream via SDI.


The venue

We simultaneously recorded a H264 quicktime file (720p, 8Mbit/s, 48khz) as well as a ProRes (61Mbit/s) file. The H264 was trimmed and uploaded to Youtube. The ProRes recording was used as a backup and to enable re-encoding for special purposes or to use the high-quality footage for e.g. for editing a trailer later on.

We had an awesome time recording the talks. Thanks to the Reject.JS & team for their trust and cooperation!

If you want to work with us, please get in touch!

Jakob & Martin

Martin Schmidt @elicee ; ; +491631765288
Jakob Storm

Eimer Richtlinien – Amazon S3 Bucket Policies

Himmelherrgott war das ein Akt: Raue Mengen Dokumentation, die man als Nicht-Coder kaum versteht und die einem dann auch nicht erklärt, wie man ein sehr simples Vorhaben umsetzt. Amazon S3 macht es mir nicht grade einfach…

Sollte also jemand mal eine Amazon S3 Bucket Policy brauchen, die per default alle Files nur dem Besitzer des Buckets rausgibt (egal wie die einzelnen File-Permissions gesetzt sind), hier eine passende Policy:

“Id”: “<eine_id>”,
“Statement”: [
“Sid”: “<eine_id>”,
“Action”: “s3:*”,
“Effect”: “Deny”,
“Resource”: “arn:aws:s3:::<bucket>/*”,
“NotPrincipal”: {
“AWS”: [