<?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 Bruno Celeste on Medium]]></title>
        <description><![CDATA[Stories by Bruno Celeste on Medium]]></description>
        <link>https://medium.com/@brunoceleste?source=rss-9bb649a407dd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4KglE2W6IkxAjVKN7dsSxg.jpeg</url>
            <title>Stories by Bruno Celeste on Medium</title>
            <link>https://medium.com/@brunoceleste?source=rss-9bb649a407dd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:16:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brunoceleste/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[Become a French Nomad in September!]]></title>
            <link>https://medium.com/french-nomad/become-a-french-nomad-in-september-e47c941d3e9e?source=rss-9bb649a407dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e47c941d3e9e</guid>
            <category><![CDATA[marseille]]></category>
            <category><![CDATA[digital-nomads]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Bruno Celeste]]></dc:creator>
            <pubDate>Thu, 11 May 2017 13:58:01 GMT</pubDate>
            <atom:updated>2017-05-11T15:00:03.000Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MU0dAys4CSvVULxk0ZOzPg.jpeg" /><figcaption>Vieux-Port, Marseille</figcaption></figure><h4>30 days to experience Marseille and the French Riviera while working remotely.</h4><p>Bonjour tout le monde,</p><p>We, at <a href="http://frenchnomad.com/">French Nomad</a>, are glad to announce that the very first session is now open. It will start on <strong>September 3rd </strong>until<strong> October 4th</strong>. You can apply online <a href="http://frenchnomad.com/">here</a>. Only 12 seats are available!</p><p>We are really excited because we’ve been working so hard for the past few months. We took time to find the right offer for you guys because we want you to be amazed by Marseille and fully enjoy the French Nomad experience.</p><p>People within a small group will get to know each other more quickly and easily and the overall experience will be more pleasant for everyone. That’s why we decided to limit the session to only 12 people to be part of this adventure, so better be quick!</p><h3>What’s included?</h3><p>We will provide a cool coworking space, cosy private rooms, a concierge service to get sh*t done, transfer from Airport to Downtown, Sim card with data, public transport card, first food supplies, laundry service, apartment cleaning service every week and awesome insights and tips from local people!</p><p>The cost is USD $2,000 for this session. Don’t hesitate to contact us for any questions you may have <a href="/service/mailto:hello@frenchnomad.com">hello@frenchnomad.com</a>.</p><p>We can’t wait to meet you guys!</p><p>À bientôt.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e47c941d3e9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/french-nomad/become-a-french-nomad-in-september-e47c941d3e9e">Become a French Nomad in September!</a> was originally published in <a href="https://medium.com/french-nomad">French Nomad</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using FFmpeg with Docker]]></title>
            <link>https://medium.com/coconut-stories/using-ffmpeg-with-docker-94523547f35c?source=rss-9bb649a407dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/94523547f35c</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Bruno Celeste]]></dc:creator>
            <pubDate>Mon, 29 Feb 2016 15:09:57 GMT</pubDate>
            <atom:updated>2016-02-29T18:17:30.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92vHLOKqS3BHMzNSMCVMsA.jpeg" /></figure><h4>Docker containers: the easiest way to distribute softwares</h4><p>What is interesting with Docker containers is that you can use them not only for deploying services to the cloud, but also to distribute softwares that you just need to run locally. It is especially useful when the software has a lot of dependencies and requires to be compiled like <a href="http://ffmpeg.org/">FFmpeg</a>. With Docker containers, everything is inside and with just one command line, it just works!</p><h4>FFmpeg dockerized</h4><p><a href="http://ffmpeg.org/">FFmpeg</a> is a free software project and is the leading software for everything related to multimedia like video encoding, streaming and muxing.</p><p>The problem with FFmpeg is that it is not easy to install. You have to compile it which implies that you need to install a ton of dependencies and have a development environment setup! I’ve been doing this for a decade and it’s not that simple.</p><p>A typical FFmpeg image on Docker Hub is +350MB and I wanted it to be as small as possible. So I choose <a href="http://www.alpinelinux.org/">Alpine Linux</a> which is a lightweight Linux distribution, and I ended up with <a href="https://hub.docker.com/r/opencoconut/ffmpeg/">an image</a> of <strong>106MB only</strong>. 70% smaller, not bad!</p><p>Here is the FFmpeg build configuration used in this image:</p><pre>ffmpeg version 3.0 Copyright (c) 2000-2016 the FFmpeg developers<br>  built with gcc 5.3.0 (Alpine 5.3.0)<br>  configuration: --enable-version3 --enable-gpl --enable-nonfree --enable-small --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libvpx --enable-libtheora --enable-libvorbis --enable-libopus --enable-libass --enable-libwebp --enable-librtmp --enable-postproc --enable-avresample --enable-libfreetype --enable-openssl --disable-debug<br>  libavutil      55. 17.103 / 55. 17.103<br>  libavcodec     57. 24.102 / 57. 24.102<br>  libavformat    57. 25.100 / 57. 25.100<br>  libavdevice    57.  0.101 / 57.  0.101<br>  libavfilter     6. 31.100 /  6. 31.100<br>  libavresample   3.  0.  0 /  3.  0.  0<br>  libswscale      4.  0.100 /  4.  0.100<br>  libswresample   2.  0.101 /  2.  0.101<br>  libpostproc    54.  0.100 / 54.  0.100<br><br>  configuration:<br>    --enable-version3<br>    --enable-gpl<br>    --enable-nonfree<br>    --enable-small<br>    --enable-libmp3lame<br>    --enable-libx264<br>    --enable-libx265<br>    --enable-libvpx<br>    --enable-libtheora<br>    --enable-libvorbis<br>    --enable-libopus<br>    --enable-libass<br>    --enable-libwebp<br>    --enable-librtmp<br>    --enable-postproc<br>    --enable-avresample<br>    --enable-libfreetype<br>    --enable-openssl<br>    --disable-debug</pre><h4>How to use FFmpeg with Docker</h4><p><em>If you don’t have Docker installed yet, follow this </em><a href="https://docs.docker.com/engine/installation/"><em>guide</em></a><em>.</em></p><p>Once Docker is properly setup, it is pretty straightforward to use the FFmpeg image. Instead of using the <em>ffmpeg </em>command line, you call docker to run the <em>opencoconut/ffmpeg</em> image in a container. That’s it!</p><pre>$ docker run opencoconut/ffmpeg -i http://files.coconut.co.s3.amazonaws.com/test.mp4 -f webm -c:v libvpx -c:a libvorbis - &gt; test.webm</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*QKhqo6-M9bi0CRt8EVvebg.gif" /><figcaption>It’s simple as that!</figcaption></figure><p>You should be aware of 2 caveats by using FFmpeg from a container:</p><ol><li>The input file must be publicly available on a web server since the container doesn’t have access to the local file system.</li><li>The FFmpeg command must pipe the result to STDOUT, again for the same reason of not accessing the local file system.</li></ol><p>The #2 is a big issue, because there are some technical limitations depending on the format you want to use. For instance, MP4, which is the most popular video format out there, can’t be used with a pipe as output. You will get this message if you try:</p><blockquote>[mp4 @ 0x556c59f21260] muxer does not support non seekable output</blockquote><p>To work around this problem, we can use the current path on the Docker host’s filesystem (your computer) as a volume inside the container with the “-<em>v”</em> option. So now we can access files on our local disk for input / output and use FFmpeg without these limitations.</p><pre>$ docker run -v=`pwd`:/tmp/ffmpeg opencoconut/ffmpeg -i localfile.mp4 out.webm</pre><p>This command is too long, so let’s create an alias by adding this line at the end of your <em>~/.bashrc</em> or <em>~/.zshrc</em> file:</p><pre>alias ffmpeg=&#39;docker run -v=`pwd`:/tmp/ffmpeg opencoconut/ffmpeg&#39;</pre><p>Now FFmpeg can be used like it’s installed on your computer:</p><pre>$ ffmpeg -i<br>ffmpeg version 3.0 Copyright (c) 2000-2016 the FFmpeg developers<br>  built with gcc 5.3.0 <strong>(Alpine 5.3.0)</strong><br>  configuration: --enable-version3 --enable-gpl --enable-nonfree --enable-small --enable-libmp3lame --enable-libx264 --enable-libx265 --enable-libvpx --enable-libtheora --enable-libvorbis --enable-libopus --enable-libass --enable-libwebp --enable-librtmp --enable-postproc --enable-avresample --enable-libfreetype --enable-openssl --disable-debug<br>  libavutil      55. 17.103 / 55. 17.103<br>  libavcodec     57. 24.102 / 57. 24.102<br>  libavformat    57. 25.100 / 57. 25.100<br>  libavdevice    57.  0.101 / 57.  0.101<br>  libavfilter     6. 31.100 /  6. 31.100<br>  libavresample   3.  0.  0 /  3.  0.  0<br>  libswscale      4.  0.100 /  4.  0.100<br>  libswresample   2.  0.101 /  2.  0.101<br>  libpostproc    54.  0.100 / 54.  0.100<br>Missing argument for option &#39;i&#39;.<br>Error splitting the argument list: Invalid argument</pre><h4>Docker image versioning</h4><p>The FFmpeg team releases a new version every 3 months on average and I wanted this Docker image to follow their version numbering scheme for sake of simplicity.</p><p>At this time, we only have two versions: <strong>3.0</strong> and<strong> git. </strong>The version <em>3.0</em> is the latest stable version and was released on February 15th, 2016. When using <em>git</em>, you will use the development version which is working fine 99% of the time.</p><p>By using <em>docker run opencoconut/ffmpeg, </em>you will use the latest stable version by default. To use a specific FFmpeg version, just run it like this:</p><pre>$ docker run opencoconut/ffmpeg:<strong>3.0</strong></pre><p>You can find all versions on the <a href="https://hub.docker.com/r/opencoconut/ffmpeg/tags/">Docker Hub</a> tag page.</p><p>If you have any feedbacks, you can send me a message on <a href="http://twitter.com/brunoceleste">Twitter</a> or by <a href="http://bruno@coconut.co/">email</a>. The project is on <a href="https://github.com/opencoconut/ffmpeg">Github</a>, so feel free to contribute!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94523547f35c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coconut-stories/using-ffmpeg-with-docker-94523547f35c">Using FFmpeg with Docker</a> was originally published in <a href="https://medium.com/coconut-stories">Coconut Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why HEVC is even better than you think]]></title>
            <link>https://medium.com/coconut-stories/why-hevc-is-even-better-than-you-think-bb3215c845d0?source=rss-9bb649a407dd------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb3215c845d0</guid>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Bruno Celeste]]></dc:creator>
            <pubDate>Mon, 15 Feb 2016 13:41:17 GMT</pubDate>
            <atom:updated>2016-02-15T13:41:17.011Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SEZiLv4X8FfPJU0owdHYMw.gif" /></figure><h4>A comparison between H264 and HEVC at low bitrate</h4><p>A couple of days ago, I decided to make a very simple comparison between the H264 and HEVC (or H265) codecs. <em>Everybody</em> knows that HEVC is (far) superior, and my guess is it will be the future most popular codec in the video industry despite the <a href="http://blog.streamingmedia.com/2016/02/technicolor-pulls-out-of-hevc-advance-patent-pool.html">patent nightmare</a> around it.</p><p>But I wanted to know how the <strong>user experience</strong> will improve when this codec will be mainstream. I don’t know for you but, I’d rather watch a degraded version of a video instead of a “buffering” message popping up every 5 seconds destroying the whole experience.</p><h4>The Test</h4><p>I choose the well known <a href="https://peach.blender.org/">Big Buck Bunny</a> movie as the source video for the test which consists of encoding the video at<strong> 800kbit/s </strong>with H264 and HEVC codecs in <strong>Full HD.</strong></p><p>So I’ll make this quick, here is<strong> </strong>the result in one GIF:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nw_-pVlA_6sVdTC6iu5P8Q.gif" /><figcaption>H264 1080p @ 800kbps (pixelated) | HEVC 1080p @ 800kbps</figcaption></figure><p>It doesn’t come as a surprise: the <strong>HEVC codec is way better</strong>. It is so superior that I wanted to try again with an even lower bitrate just because I’m curious!</p><h4>A crazy test at 400kbit/s</h4><p>To get an <em>okay quality</em> with H264 1080p, I advise to use 1500–2000kbps as the <em>bare minimum</em>. At 800bkps, the quality is still very good to me, so let’s try with an impossible low bitrate of <strong>400kbps</strong>.</p><p>I’ve found the result quite surprising:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YikFyeqrtRY4UhG3Evn8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vyZjlS-ZzMTcLRgo1qfVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gc-FwTP9Xz4OYL_E8gdtCA.png" /><figcaption>H264 1080p @ 400kbps | HEVC 1080p @ 400kbps</figcaption></figure><p>Wow the HEVC quality is <strong>impressive</strong>, I didn’t expect such a difference! Look at the H264 version, the pictures are very pixelated compared to HEVC. The grass and hair are still very clear with the HEVC codec! It‘s like H264 @ 1500k.</p><p>To go further, I compared the same images with different bitrates. Mind blown 💥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-croX4B9SJ7dbQg147wgQ.png" /><figcaption>H264 1080p @ 800kbps | HEVC 1080p @ <strong>400kbps</strong></figcaption></figure><h4>In motion ☄</h4><p>The HEVC codec is doing an amazing job with static scenes at very low bitrate but needless to say that it isn’t that performant when the scenes have a lot of motion. In this example, the trunk is still clear but the leafs are not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EvKuJE7_7k8KfETtLnBGOQ.png" /><figcaption>HEVC 1080p @ 400kbps in a scene with motion</figcaption></figure><h4>What will change with HEVC</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0HROTI-Mpqz9fnJKYuop7A.jpeg" /><figcaption>Photo by Ninara <a href="https://flic.kr/p/o8ssAu">https://flic.kr/p/o8ssAu</a></figcaption></figure><p>As we saw with the test, the HEVC codec is pretty good at a very low bitrate and I am sure it will change a lot for both people around the world and companies really soon:</p><ol><li>The overall quality will be dramatically increased. We will watch videos in Full HD on our phone most of the time, if not <em>all the time</em>.</li><li>Video services like YouTube, Vimeo and Facebook will save <strong>~40% of bandwidth and storage. </strong>HUGE.</li><li>Emerging countries with a poor Internet connection will finally enjoy Full HD streaming quality.</li></ol><h4>Links</h4><p>Here are the download links of the videos so you can see by yourself:</p><ul><li><a href="http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_1080p_30fps_normal.mp4">Source 1080p @ 3M</a></li><li><a href="http://files.coconut.co.s3.amazonaws.com/h264vshevc/h264_400k.mp4">H264 1080p @ 800k</a></li><li><a href="http://files.coconut.co.s3.amazonaws.com/h264vshevc/hevc_800k.mp4">HEVC 1080p @ 800k</a></li><li><a href="http://files.coconut.co.s3.amazonaws.com/h264vshevc/h264_400k.mp4">H264 1080p @ 400k</a></li><li><a href="http://files.coconut.co.s3.amazonaws.com/h264vshevc/hevc_400k.mp4">HEVC 1080p @ 400k</a></li></ul><p><em>Tests made with </em><a href="http://coconut.co/"><em>Coconut encoding service</em></a><em> </em>🌴</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb3215c845d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coconut-stories/why-hevc-is-even-better-than-you-think-bb3215c845d0">Why HEVC is even better than you think</a> was originally published in <a href="https://medium.com/coconut-stories">Coconut Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>