<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Florian Bemmann on Medium]]></title>
        <description><![CDATA[Stories by Florian Bemmann on Medium]]></description>
        <link>https://medium.com/@florianbemmann?source=rss-98320dcc57be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vbhgz1mOLL3rWqvSYeli1g.jpeg</url>
            <title>Stories by Florian Bemmann on Medium</title>
            <link>https://medium.com/@florianbemmann?source=rss-98320dcc57be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:46:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@florianbemmann/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[5 Take-Aways From My Dissertation That You Should Know]]></title>
            <link>https://florianbemmann.medium.com/5-take-aways-from-my-dissertation-that-you-should-know-a1b8ce6dcd43?source=rss-98320dcc57be------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1b8ce6dcd43</guid>
            <category><![CDATA[smartphones]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[hci]]></category>
            <category><![CDATA[human-comuter-interaction]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Florian Bemmann]]></dc:creator>
            <pubDate>Fri, 07 Mar 2025 09:16:35 GMT</pubDate>
            <atom:updated>2025-03-07T09:16:35.934Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YCvPAZ1IYFbsMEZoeT-Zlw.jpeg" /></figure><p>In summer 2024, I finally handed in my dissertation, after 5 years of research on privacy in human-computer interaction, as well as many more or less related topics. 331 pages, 11 incorporated research projects — lets be honest, nobody will ever read all of this. Thus, lets point out my main findings here in this article — hopefully you make it through this 🙂</p><h3><em>Privacy-Preserving User-Quantification with Smartphone Sensing</em> — What’s That?</h3><p>Although that might seem different at first sight, people (maybe not all, but many) want <strong>User-Quantification </strong>— i.e., quantifying themselves through smartwatch sensors to measure their fitness and sports progress, or allowing their smartphone to use contextual data to adapt automatically to their situation and prompt intelligent suggestions when necessary. Doing this in a <strong>privacy-preserving </strong>way is essential; otherwise, people will start feeling bad or neglect service usage (a.k.a. uninstall apps again).</p><p>You may now ask: Is this really new and deserves a whole dissertation? Well, privacy is not new, of course. But with smartphones and intelligent applications, the situation has become different. Nowadays, ubiquitous technology is omnipresent (i.e., people take it with them everywhere: home, work, toilet, sleeping room, …) and constantly connected (i.e., they are, with most people, never off or offline). These two factors yield novel challenges that past privacy concepts are not tailored to.</p><p>But I promised takeaways instead of 331 pages of text, so let’s jump directly in!</p><h3>#1 Agency Matters</h3><p>„<em>Agency, the abstract principle that autonomous beings, agents, are capable of acting by themselves.</em>“ — Wikipedia</p><p>Smartphones make us lose our agency. Did you ever find yourself scrolling through Instagram Reels for half an hour without wanting to do so? That’s a loss of agency. Your smartphone, most often some content recommendation algorithm, decides for you what content you consume; you do not even decide on some topic or category anymore. Stopping this so-called <em>Mobile Phone Rabbit Hole</em> sometimes is difficult, although it theoretically would be just one easy tap to leave the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/1*I_L19kPzU8vjJ0X5_dMs_g.png" /></figure><p>Consuming social media content is not necessarily bad; one can also strive for that as a means to relax. And here is the difference: In that case there is agency. In <a href="https://www.medien.ifi.lmu.de/forschung/publikationen/detail?pub=terzimehic2023mobilehci">our research on the mobile phone rabbit hole</a> we collected quantitative data on context of and behaviors in rabbit hole smartphone usage sessions. Furthermore we conducted a qualitative expert focus group. Our analyses showed that agency is what matters! If users are aware of and feel in control of their behavior, they are doing good. But if they rather feel steered by some algorithm, i.e., are not in agency anymore, their behaviors finally make them feel bad — leading to severe issues such as depression and other mental disorders which are nowadays fostered by „bad“ technology use.</p><p>This theme of agency is central in most privacy aspects — people want to be in control. Maybe they are not consciously aware of that, but offloading yourself to some system is rarely good.</p><h3>#2 Technical Security Measures Hardly Mitigate Privacy Concerns</h3><p>It is great if you build a system that is safe, processes most data locally on the user’s device, and handles all remaining data that is sent to a remote server anonymously. However, this does not automatically yield a great perception of privacy among your users. Users don’t know about your technical details and data processing procedures. And even if you tell them, they first need to trust you before they perceive your application as actually privacy-friendly.<br>System designers need to develop concepts that keep their users in the loop and convey the privacy-enhancing technologies they’ve incorporated.</p><h3>#3 If you make your app’s data practices transparent to your users, they will honor it with rejection. Control is, what they want!</h3><p>In <a href="https://www.medien.ifi.lmu.de/forschung/publikationen/detail?pub=bemmann2022mobilehci">a quantitative field study</a>, we measured whether people install an app more or less frequently, depending on the offered privacy-enhancing features. I.e., we compared versions of an app with especially detailed Transparency features, one with fine-grained Control features, and one that implements both, with a baseline version that only incorporates the legal minimum.</p><p>The interesting finding: That version of the app that implemented a great privacy dashboard, thus being very transparent about what data it uses, was least appreciated! Users installed it significantly less frequently than all other versions — even less than the minimal baseline version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x0yNDaa_H95b5Ft1aoZapA.png" /><figcaption>A line chart that shows results from one of our experiments on app adoption: Apps that provide Transparency are installed less frequently than apps that remain silent about their data practices.</figcaption></figure><p>At first sight surprising. On the second, it makes sense. As long as people are unaware of bad things happening, they don’t worry. But if you show them the plethora of data that a system uses without giving them any option to react, they start to be afraid. And helpless, powerless.</p><p>This effect is mitigated, and even surpassed, if you add Control features. The app version that gave users detailed control over what is logged at which point of time was appreciated most — and installed most often.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hXntOcDC0ON_v384OLgUkw.png" /></figure><h3>#4 The sole presence of Control makes the difference.</h3><p>We also measured how our participants used the offered Control features. And interestingly, they rarely used them. Deducting initial tryouts directly after advertising these features, I could count the total number of data logging disabling actions with my fingers.</p><p>Thus, The presence of control makes the actual difference. The feeling and knowledge that one could change something anytime.</p><h3>#5 We have to rethink opportune moments for privacy decisions.</h3><p>Privacy interfaces act on the edge of user annoyance and warning fatigue. Simply spoken: Privacy is boring; users don’t want to spend time on that (with some exceptions. Indeed, the user population is quite polarized here).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/1*cJZn7gBPm_B_L59zFFTRjg.png" /></figure><p>And to make it worse, our privacy prompts often occur in moments when we really don’t want to spend time on privacy decisions. That means, in moments when we are pursuing some task. For example: I am buying a public transport ticket using a smartphone app. Location access is requested to determine my starting location; access to my wallet is requested to manage the payment. At that moment, I simply want to get my ticket fast. Thus, I don’t want to spend time considering different location granularities or limits and contextual access restrictions to my wallet. This entanglement of privacy decisions with concrete user actions makes sense and has advantages. Without this so-called <em>contextualized privacy</em>, we hardly understand the relationship between a data access request and its real-world relation and necessity. But it also comes with downsides.</p><p>We need to think about different ways to have contextualized privacy, i.e., users understanding the real-world context of a data request while prompting them in a more opportune moment, i.e., when they have time for that.</p><p>You want to read more? Then feel free to check out the full 331 pages of <a href="https://edoc.ub.uni-muenchen.de/34691/">my dissertation</a>, or follow me on <a href="https://bsky.app/profile/florianbe.bsky.social">Bluesky</a>, <a href="https://www.linkedin.com/in/dr-florian-bemmann-a18609128/">LinkedIn</a>, or <a href="https://medium.com/@florianbemmann">Medium </a>to be notified about future blog posts being released!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b8ce6dcd43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LanguageLogger: How to Study Smartphone Language Use  in the Wild with an Android Keyboard App]]></title>
            <link>https://florianbemmann.medium.com/languagelogger-how-to-study-smartphone-language-use-in-the-wild-with-an-android-keyboard-app-9d2eb0934577?source=rss-98320dcc57be------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d2eb0934577</guid>
            <category><![CDATA[mobile-sensing]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[research-tools]]></category>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[language-studies]]></category>
            <dc:creator><![CDATA[Florian Bemmann]]></dc:creator>
            <pubDate>Thu, 07 Jan 2021 08:36:20 GMT</pubDate>
            <atom:updated>2021-01-07T08:36:20.165Z</atom:updated>
            <content:encoded><![CDATA[<h3>LanguageLogger: How to Study Smartphone Language Use in the Wild with an Android Keyboard App</h3><p>The words people type into their smartphone everyday can tell a lot about their personality, mood, relation to the person they are texting with, and much more. This makes data of real-world language use a valuable source for researchers in many fields — psychology, sociology, human-computer interaction — to name just a few. But this also brings many challenges: The typed content contains lots of private information, making it very difficult to work with it as a researcher. Potential participants are (for good reasons) not willing to provide you all their text messages, and even if you’d get them, a secure and thus cumbersome workflow in data analysis is of utmost importance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*4A5xdu1LczrtHfy5X9zTNg.jpeg" /></figure><p>But don’t worry — there are smarter ways to solve this problem. What if you could conduct your data preprocessing on the participants’ smartphone, and only transmit the abstracted, anonymous data you really need to your researcher computer?</p><p>In our recent paper “<a href="https://dl.acm.org/doi/pdf/10.1145/3397872">LanguageLogger: A Mobile Keyboard Application for<br>Studying Language Use in Everyday Text Communication in the Wild</a>” we tackle this issue: We developed an Android keyboard app that brings word categorization, word frequency counting, and matching regular expressions to your participants smartphone. The resulting data does thus not contain raw contents anymore making your study less privacy invasive and easier to recruit for. And the first step of your data preprocessing is already done, nice! (Nobody likes data preprocessing, really.)</p><p>This article will show you what LanguageLogger exactly is capable of and what it does, so that you can judge how it could facilitate your next research project.</p><h3>What does LanguageLogger?</h3><p>LanguageLogger is an Android keyboard app that abstracts the typed words directly on the participant’s device. Only abstracted, thus anonymous data is logged. It incorporates three core-concepts of language analysis:</p><p><strong>Whitelist Counting</strong><br>You as researcher define a list of words. LanguageLogger will count how often the user types these words during the study.</p><p><strong>Word Categorization</strong><br>You define a set of categories, and words that belong to those categories. Whenever the user types a word that belongs to a category, an event for the category is logged. Events contain timestamps, are related to the “typing session” (e.g. text message) they were entered in, and contain meta data like the target app (e.g. WhatsApp), character count, …</p><p><strong>Custom Regex Filtering</strong><br>Can be used to log words that match a specific pattern, defined as regular expression.</p><h3>Example: Where do people buy animal-related stuff?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kgA3sASuOMt-FGThHi3s8w.png" /><figcaption>The LanguageLogger abstraction concept: Only the desired categories and word counts are logged. Privacy-invasive data like names and other details are discarded.</figcaption></figure><p>Imagine you are interested in animal-related shopping behaviour. You could create categories for animal-words and shopping-words. To get details on which shops people talk about, you further collect a list of possible shops. And lets say you love emojis and want to log them too — therefore you configure a regular expression that matches all emojis.</p><p>What is LanguageLogger now actually logging? Only the contents relevant to your research. Other, privacy-invasive contents, e.g. the information that the message recipient might go shopping tomorrow and that Thomas will join, is not stored.</p><h4>The resulting data</h4><p>You can find the log data resulting of the above example as <a href="https://github.com/Flo890/languagelogger-backend/blob/master/demodata/demo-resulting-logdata.sql">database dump here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-zFo0Z7zbC3QZou02ZqMg.png" /><figcaption>SQL log data (category events) of the above example. Can you spot the word categories we were looking for and the emoji?</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9sSCkH0l05lb3vvpHWxVPQ.png" /><figcaption>The entry for that one typing session.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tBjI4wEH4Ao4z253Xx4vyg.png" /><figcaption>And the updated word count table, containing just one count so far.</figcaption></figure><p>For details on the resulting data please consult the <a href="https://github.com/Flo890/languagelogger-backend#the-log-data-structure">README</a>, where further data like the touch events and sensors are listed as well.</p><h3>Getting Started — How To Setup LanguageLogger</h3><p>To make the Android App work you have to setup the accompanying backend, one some online-accessible machine. The code for both Android App and the backend can be found on GitHub:</p><ul><li>Android App: <a href="https://github.com/Flo890/languagelogger-app">https://github.com/Flo890/languagelogger-app</a></li><li>Java Play Backend: <a href="https://github.com/Flo890/languagelogger-backend">https://github.com/Flo890/languagelogger-backend</a></li></ul><h4>Step 1: Setup the Backend</h4><p>Follow the <a href="https://github.com/Flo890/languagelogger-backend#setup-server">steps 1 and 2 in the backend project’s repository</a> to setup the backend with a database. For testing purposes you can simply do that on your local computer, for a real study you need a server / virtual machine that is accessible from the web via HTTPS. For real studies you should further consider an encrypted database, like the MySQL derivative <a href="https://mariadb.org/">MariaDB </a>and its <a href="https://mariadb.com/kb/en/file-key-management-encryption-plugin/">File Key Management Encryption plugin</a>.</p><p>To let your smartphone access your local backend, we recommend to use a tunnel service like <a href="https://ngrok.com/">ngrok</a> (<a href="https://github.com/Flo890/languagelogger-backend#step-3-eventually-reverse-proxy">README Step 3</a>). It creates a URL that is accessible worldwide, which you will need to run the Android app.</p><p><em>For a real study:</em> This step is only intended for local testing; For production we instead recommend to install <a href="https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/?_ga=2.115123650.454379022.1609595670-2052318470.1609595670">nginx </a>on your server and create a SSL certificate via <a href="https://letsencrypt.org/getting-started/">letsencrypt</a>.</p><h4>Step 2: Configure your Study</h4><p>If you just want to get started quickly to give it a try, import the demo configuration as described in the <a href="https://github.com/Flo890/languagelogger-backend#step-4-configure-languagelogger-abstraction-logic">README’s step 4</a>.</p><p><em>For a real study</em>: Carefully think about what you want to log. Do you need events or are word counts enough? If you need categories, which words should be mapped to which categories? If you want word counts, which words are interesting for you?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/1*-tj2_1LWf4whbeDUU34UVA.png" /><figcaption>Example configuration files for word categorization (left) and word frequency counting (right).</figcaption></figure><p>You could also use a predefined list, for example the <a href="https://www1.ids-mannheim.de/kl/projekte/methoden/derewo.html">DeReWo dictionary</a> of German words to count all dictionary-words. Or the <a href="http://linkeddatacatalog.dws.informatik.uni-mannheim.de/de/dataset/sentiws">SentiWS dataset</a>, which assigns common words a sentiment score (you could use the score values as categories).</p><p>The configuration happens through the UI of the backend. You have to create word / category lists in text files with the file ending <em>*.rime</em> as shown in the figure to the left, and import them in the backend’s UI. For the word categorization the configuration file should contain a word with its category per line (tab separated!); for the word frequency counting simply list one word per line.</p><p>Via the UI you can a.o. also configure the study duration and keyboard layouts. Please read the <a href="https://github.com/Flo890/languagelogger-backend#research-configuration">Section Research Configuration in the backend’s README</a> for details and examples on how to do that.</p><h4>Step 3: The Android App</h4><p>Having a running backend, it is time for the Android app. Checkout the <a href="https://github.com/Flo890/languagelogger-app">app project repository</a> and open it in Android Studio. There is just one important adaptation you have to make: Set your backend’s URL. Go to the file researchime-app/ResearchIME-Module/src/main/res/values/strings.xml</p><p>and paste the HTTPS url of your backend here (e.g. <a href="https://dd02e086701f.ngrok.io/">https://dd02e086701f.ngrok.io</a> if you use ngrok for local testing). After that, you can run the app via Android Studio.</p><p><em>For a real study:</em> Additionally to setting your URL, you should place your server’s certificate in <em>research_cert.crt</em> , and uncomment the certificate check in <em>RestClient</em>. Details on these steps again are listed in the <a href="https://github.com/Flo890/languagelogger-app#getting-started-with-the-android-app">README</a>.</p><h4>Step 4: Distribute your App to Conduct the Study!</h4><p>You are ready to go (after some testing of course…). As we doubt that our app might be accepted for the PlayStore, we recommend to distribute it as APK download. Providing a short how-to-setup video or instruction page might be helpful for some participants, because they have to give one special Android security setting to be able to install the downloaded APK.</p><h3>What else can I do with LanguageLogger?</h3><p>The above example is just a basic one, demonstrating LanguageLogger’s core concept. Digging deeper, LanguageLogger has some more features. To get to know then in detail we recommend to check out our two latest papers related to LanguageLogger:</p><p>B<a href="https://dl.acm.org/doi/pdf/10.1145/3397872">emmann, Buschek 2020: LanguageLogger: A Mobile Keyboard Application or Studying Language Use in Everyday Text Communication in the Wild</a></p><p><a href="https://dl.acm.org/doi/abs/10.1145/3173574.3173829">Buschek, Bisinger, Alt 2018. ResearchIME: A mobile keyboard application for studying free typing behaviour in the wild</a></p><p>Some more capabilities of LanguageLogger:</p><p><strong>ADDED, CHANGED, REMOVED</strong>. Unlike the above example, LanguageLogger does not only log added words. If a user changes an existing word or deletes an existing word entirely, events of type <em>CHANGED </em>and <em>REMOVED </em>are created.</p><p><strong>Message Difference Analysis vs. Full Message Analysis</strong>. The events <em>ADDED</em>, <em>CHANGED </em>and <em>REMOVED </em>model the real-world user actions, however if you are only interested in the final message sent to a recipient you might not care how often the user changed a word. To also tackle this, LanguageLogger analyzes each message twice:</p><ul><li>Message Difference: The sequence of user actions is modeled with <em>ADDED</em>, <em>CHANGED </em>and <em>REMOVED </em>events.</li><li>Full Message: The final message (at the time when the user closed the keyboard) is taken, split into words, and for each word a <em>CONTAINS </em>event is logged.</li></ul><p><strong>Lemmatization</strong>. In real-world language you have to deal with many possible conjugations. For example the word <em>buy </em>will also occur as <em>bought</em>. The avoid that you would have to add all possible conjugations to your word / category lists, LanguageLogger uses the tool <a href="https://cis.uni-muenchen.de/~schmid/tools/TreeTagger/">TreeTagger created by Helmut Schmid </a>which lemmatizes words back to their base. (E.g. if a user types <em>bought</em>, LanguageLogger will treat it as <em>buy</em>). This functionality is optional of course (can be configured) and currently only implemented for German language. However it would be fairly easy to add parameter files for other languages (provided on the <a href="https://cis.uni-muenchen.de/~schmid/tools/TreeTagger/">TreeTagger website</a>). We plan to implement this in the future.</p><p><strong>Touch Biometrics</strong>. As demonstrated in the 2018 paper <a href="https://dl.acm.org/doi/abs/10.1145/3173574.3173829">ResearchIME: A mobile keyboard application for studying free typing behaviour in the wild</a> , LanguageLogger also can logs touch events. Leveraging those, one could also run analyses regarding typing speeds, touch accuracy, usage of auto correction.</p><p><strong>Integration Into Other Data Sources</strong>. Our main contribution is bringing these language abstraction concepts to the client device. The keyboard is only one possible data source for this. Due to LanguageLogger’s modular architecture one can also integrate it into other apps. <a href="https://github.com/Flo890/languagelogger-modules-demoapp">A third GitHub repository</a> demonstrates how to integrate LanguageLogger’s language abstraction logic into a simple Mobile Sensing app. If you are interested in feeding LanguageLogger with notification contents, incoming SMS messages, or anything else you collect on your participants smartphones, please follow the <a href="https://github.com/Flo890/languagelogger-modules-demoapp/blob/master/README.md#steps-to-use-languagelogger-modules-in-a-separate-application">step-by-step guide in the repo’s README</a>.</p><p>Do you have any questions about LanguageLogger? Will it facilitate your next research project, or is there something important missing? Feel free to let us know your questions, ideas and opinions <a href="/service/mailto:florian.bemmann@ifi.lmu.de">via E-Mail</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n05uqrMHta_0h5oDw03hOQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d2eb0934577" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Shoot Lightpainting Timelapse]]></title>
            <link>https://medium.com/how-to-shoot-lightpainting-timelapse/how-to-shoot-lightpainting-timelapse-5dd2e88b4a09?source=rss-98320dcc57be------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dd2e88b4a09</guid>
            <category><![CDATA[light-painting]]></category>
            <category><![CDATA[timelapse]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[after-effects]]></category>
            <category><![CDATA[videography]]></category>
            <dc:creator><![CDATA[Florian Bemmann]]></dc:creator>
            <pubDate>Sun, 30 Dec 2018 19:44:01 GMT</pubDate>
            <atom:updated>2018-12-30T20:05:41.954Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Lightpainting Timelapse?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKR9BL6i_MgQ&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKR9BL6i_MgQ&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FKR9BL6i_MgQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/86b10c3a3e6bf5f4a9145163d279e556/href">https://medium.com/media/86b10c3a3e6bf5f4a9145163d279e556/href</a></iframe><p>Lightpainting Timelapses combine drawing colorful lines into an image with the fast and interesting movement of Timelapse videos. In a Lightpainting video you can watch the „light lines“ drawed by moving lights in a dark scene growing with the time. All lights that are moving through your video pull a bright line behind them.<br>Lightpainting photos are awesome — but Lightpainting videos let you watch the light-lines growing! While Lightpainting photos „compress“ the happenings of a timerange into one single image, Lightpainting videos capture each moment separately. This allows a wide range of creative editing possibilities!</p><h3>What do I need to shoot Lightpainting videos?</h3><ul><li>a camera that allows you to set exposure time manually in video mode</li><li>tripod</li><li>a video editing software like Adobe Premiere (a simple one like Magix Movie Maker should work as well)</li><li>additional software to create the Lightpainting effect. As a software developer I built one on my own, I provide it to everyone for free <a href="https://github.com/Flo890/oev/releases">here on my GitHub page</a></li></ul><h3>The Basic Workflow: Lightpainting Video at normal speed</h3><p><strong>Taking the footage</strong><br>Mount your camera on the tripod. Possible settings:</p><ul><li>25 fps</li><li>exposure time as close to 1/25s as possible!</li><li>set ISO and aperture so that the lights appear bright but not completely white. The background and other objects should be dark, but still clearly visible. Most important: There has to be a <strong>clear difference between the brightness of lights and other objects</strong> in the image (for pros: the darkest part of the lights must be brighter than the brighter points of all other objects and the background</li></ul><p>Now start recording your scene. The camera mustn’t move while shooting!</p><p><strong>Post Processing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*JIOgSoHS05HkjIeMLbaS1Q.jpeg" /><figcaption>possible settings for post processing in OEV</figcaption></figure><ul><li>Import the clip into your editing software</li><li>cut start and end so that the scene has the length you want</li><li>export it as png sequence (file naming does not matter since version 1.4.0)</li><li>launch <a href="https://github.com/Flo890/oev/releases/download/1.4.4/oev-1.4.4-all.jar">my software OEV</a>: by double click on the jar file<br>(if that doesn’t work use the command prompt window. E.g. if the jar file called oev-<em>1.4.4-all.jar</em> is saved on your Desktop (and you’re called Florian</li><li>) then call <em>java -jar C:\Users\Florian\Desktop\oev-1.4.4-all.jar</em> )</li><li>in OEV select all PNG source files</li><li>as destination select a empty folder where the output files shall be saved in later</li><li>set the mode to <em>Lightpainting Video</em></li><li>click <em>Start</em> and wait until the finish message appears</li><li>go back to your video editing software and import the result1.png,result2.png,… files (you find in the destination folder which you have set in OEV) as image sequence</li></ul><p>When you now play this image sequence video you can watch the result! The Lightpainting effect should be visible.</p><h3>The Advanced Workflow: Lightpainting with Timelapse speed</h3><p>Here are some tips and <strong>additions to the basic workflow</strong> to improve your Lightpainting Timelapse:</p><p><strong>Taking the footage</strong></p><p>To make a Timelapse instead of normal speed video you just have to set a lower framerate (e.g. 0.5fps). When afterwards playing back this at 25fps, your scene moves 50 times faster as usual.<br>I use a Canon DSLR running with <a href="http://www.magiclantern.fm/">Magic Lantern Firmware</a>. Why? Remember the basic workflow. I said you should set the exposure time as close to 1/25s as possible. Mathematically (and framerate independent) we could say: the product <em>framerate * exposure time</em> should be as close to 1 as possible. If it is 1, I call it „gap-less recording“. Because when this product is smaller than 1 (my Canon can shoot at maximum with 1/33s at 25fps =&gt; 1/33 *25 = 0.76), your camera does not record every moment of your scene. It takes an 1/33s long image 25 times per seconds -&gt; between each frame the camera waits 0.0096 seconds. Sounds not much, but results in gaps in the light lines in the final video.<br>Magic Lantern has two main advantages when shooting Lightpainting timelapse:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Ptr4O0U09IcG2qYCHKQtRg.jpeg" /><figcaption>zscreenshot of my Canon DSLR running Magic Lantern firmware: my favorite settings</figcaption></figure><ul><li>You can set the frame rate to less than 25fps (=Timelapse)</li><li>when shooting with 6fps or less, you can shoot nearly gapless. Selecting 1/6s exposure time is possible at 6fps (the real framerate it shoots is around 5.882fps, that’s why I have to say nearly). Calculating the product again we get 0.98. That’s very close to 1, especially compared to 0.76 what is the maximum using Canon’s original firmware.</li></ul><p><strong>coming to a conclusion about Magic Lantern (I could write about lots of other awesome features as well…):</strong></p><ul><li><strong>use it!!</strong></li><li><strong>set a framerate of 6fps or less, depending on your scene. A faster object requires faster framerates.</strong></li><li><strong>set the exposure time fitting to the framerate. At 6fps set 1/6s ; 0.5fps = 2s ; and so on</strong></li><li>in very slow scenes you can use photo mode instead of video mode (continuous burst shooting). Main advantage: you can produce footage in full sensor resolution and uncompressed RAW quality; and you can benefit from the post processing power of tools like Adobe Lightroom!</li></ul><p><strong>Post Processing</strong></p><p>Do some brightness corrections before processing in OEV. I am still experimenting with how to get the most out of my OEV software. But I think the most important is to have a clear separation between lights and other objects/background. So what I usually do in Adobe Premiere before processing the footage in OEV, is some color corrections. Lights should not be to bright, but clearly brighter than everything else in the image.</p><p>If you launched the OEV software, maybe you recognized that there 3 modes can be selected. I recommend you to try the mode <em>Lighttrailing Video</em> as well. What it does: The light lines get a maximum length. When selecting <em>Lighttrailing Video</em> you have to set the value <em>light-trail length</em> as well. This defines how long the lines should be (in frames). E.g. setting an <em>light-trail length</em> of 50, in each image lines will be created out of the last 50 frames. This is nice for longer scenes with multiple fast moving objects, because in the <em>Lightpainting Video</em> mode the image gets brighter and brighter with the time, until it is completely bright and you can’t see anything. However in <em>Lighttrailing Video</em> mode each light line ends after a certain time and there is space for new ones.<br>You can see some samples for each mode on the <a href="https://github.com/Flo890/oev/blob/master/README.md">OEV Github Readme</a>. (When using <em>Lighttrailing Video</em>mode don’t wonder if there doesn’t happen anything in OEV after starting, this mode needs a lot of time (higher <em>light-trail length</em> -&gt; more time). Maybe in the future I will do some performance improvements to this mode.)</p><h3>That’s it!</h3><p>There are a lot more things you can do with Lightpainting video than I described here. I am always about to develop new workflows for new result effects. I think in addition with some advanced Adobe After Effects knowledge might be possible a lot.<br>If you tried this and created some Lightpainting video or Timelapse, it was great if you could let me know an send me your YouTube link! I’m always interested in what you can do with this tool or workflow! So if you have any questions, ideas, bugs, or great results feel free to contact me or use the comments!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEX8sVS9z3kSFL454JjLkg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dd2e88b4a09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-shoot-lightpainting-timelapse/how-to-shoot-lightpainting-timelapse-5dd2e88b4a09">How to Shoot Lightpainting Timelapse</a> was originally published in <a href="https://medium.com/how-to-shoot-lightpainting-timelapse">Flo’s Photography</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>