<?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 CANAL TECH TEAM 📺📱🎬 on Medium]]></title>
        <description><![CDATA[Stories by CANAL TECH TEAM 📺📱🎬 on Medium]]></description>
        <link>https://medium.com/@canal.tech?source=rss-bf954c2f4e09------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Q58EcRCk_RT-BbhLlUQoFQ.png</url>
            <title>Stories by CANAL TECH TEAM 📺📱🎬 on Medium</title>
            <link>https://medium.com/@canal.tech?source=rss-bf954c2f4e09------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:03:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@canal.tech/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[Retour sur notre Hackathon !]]></title>
            <link>https://medium.com/canal-tech/retour-sur-notre-hackathon-271192677ca5?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/271192677ca5</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 14:05:21 GMT</pubDate>
            <atom:updated>2020-02-14T14:05:21.660Z</atom:updated>
            <content:encoded><![CDATA[<h3>Retour sur notre Hackathon !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GxdIZUGq2ZQqwpTZ.jpeg" /></figure><p>La fin d’année 2019 était autour de l’ <strong>innovation</strong> pour les équipes CANAL+ en France.</p><p>Un <strong>hackathon</strong> a été organisé dans nos locaux, et s’adressait à l’ensemble de nos équipes volontaires.<br> Des participant·e·s de métiers multiples… marketing, tech, créatifs, business, juridique… tous et toutes ont apporté leur <strong>passion</strong> et leur <strong>motivation</strong> au service des projets proposés.</p><h3>Le Hackaton CANAL+, c’est comment ?</h3><p>Pendant 2 jours les participant·e·s, mélangés et rassemblés en équipe, ont imaginé et prototypé un projet sur un de ces 4 thèmes (au choix) :<br> — Le Green<br> — Notre marque<br> — Le futur de l’Entertainment<br> — Sujet libre<em>(oui. Toute bonne idée est bonne à prendre.)</em></p><p>Chaque projet imaginé a été <strong>validé</strong> puis <strong>pitché</strong> en amont, devant l’ensemble des participant·e·s. Une fois les équipes réparties, <strong>une journée complète</strong> était consacrée à développer le projet.<br> Selon les <strong>compétences</strong> de chacun, chaque équipe développait son projet à sa manière : prototype d’application mobile, lignes de code, maquettes, vidéo, PowerPoint…</p><p>Le lendemain de cette (intense) journée de rush, chaque équipe présentait son projet <strong>devant un jury</strong>, et l’ensemble de la communauté <em>CANAL</em>. L’occasion pour nos stagiaires et alternants de prouver leur vivacité et leur force de persuasion face à des collaborateur.ices plus expérimentés !</p><h3>Retour en images sur l’édition 2019</h3><p><em>Le jury l’a avoué… c’était très difficile de choisir un gagnant.</em><br> Les gagnant.es ont par la suite pitché leur projet devant <strong>Maxime Saada</strong> (Président de CANAL+), <strong>Frank Cadoret</strong> (Directeur Général du groupe en charge de la France), <strong>Valérie Languille</strong> (DRH du groupe).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.dailymotion.com%2Fembed%2Fvideo%2Fx7ogc4v&amp;display_name=Dailymotion&amp;url=https%3A%2F%2Fwww.dailymotion.com%2Fvideo%2Fx7ogc4v&amp;image=https%3A%2F%2Fs1.dmcdn.net%2Fv%2FRhJLl1UGtP7oibSgj%2Fx240&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=dailymotion" width="480" height="269" frameborder="0" scrolling="no"><a href="https://medium.com/media/201bfd86b39c25e2a6ceeb544d8f217a/href">https://medium.com/media/201bfd86b39c25e2a6ceeb544d8f217a/href</a></iframe><p><em>By Guillaume DE SAINT SERNIN</em><br><em>Originally published at </em><a href="https://jobs.canalplus.com/articles/toutes-nos-histoires/retour-sur-notre-hackathon"><em>https://jobs.canalplus.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=271192677ca5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/retour-sur-notre-hackathon-271192677ca5">Retour sur notre Hackathon !</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[1ère Mondiale : CANAL+ propose du Dolby Atmos sur Apple !]]></title>
            <link>https://medium.com/canal-tech/1%C3%A8re-mondiale-canal-propose-du-dolby-atmos-sur-apple-bf55c8b4827a?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf55c8b4827a</guid>
            <category><![CDATA[atmos]]></category>
            <category><![CDATA[mycanal]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 15:54:37 GMT</pubDate>
            <atom:updated>2018-03-19T15:55:24.874Z</atom:updated>
            <content:encoded><![CDATA[<h3>1ère Mondiale : CANAL+ propose du Dolby Atmos sur iOS et AppleTV !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*GXoOVC9N_1vGUoFwNSxnAw.png" /></figure><blockquote><strong>CANAL+ propose, en première mondiale, du son Dolby Atmos sur iPhone, iPad et Apple TV et le démocratise ainsi en le rendant accessible sur équipement mobile et en particulier à tous les possesseurs d’équipements Apple.</strong></blockquote><h3>Dolby Atmos</h3><p>Le Dolby Atmos est une nouvelle technologie de reproduction du son qui apporte la gestion de la verticalité.</p><p>Alors que le Dolby Digital, propose une expérience horizontale à 360° via du 5.1 ou du 7.1, le Dolby Atmos exploite en moyenne 64 canaux !</p><p>Ainsi, un équipement Dolby Atmos permet de ressentir du son provenant de toutes les directions de l’espace. <br>Cette technologie peut par exemple permettre de faire ressentir le passage d’un avion de chasse au-dessus de la tête… ou encore, d’immerger complètement un spectateur dans un concert de Gorillaz ! ;-)</p><h4>En salle et à la maison</h4><p>Pour une écoute via une installation Dolby Atmos, la piste audio numérique Atmos est envoyée au processeur audio qui décode le signal et l’envoi à chaque haut-parleur en s’adaptant à la configuration.</p><p>La technologie Atmos, en plus d’introduire la verticalité, a introduit la notion d’objet sonore à la place des canaux.</p><p>Sur un système 5.1 ou 7.1 classique, chaque enceinte correspond à un canal et donc à un signal audio qui lui est propre.</p><p>La plupart des installations Atmos, n’utilisent plus de canaux : les sons sont traités comme des objets sonores qui intègrent dans leur description et via des metadata, leur position, leur trajet dans l’espace sonore et leurs variations de traitement.</p><p>C’est cet objet qui est analysé par le processeur sonore afin de générer le flux audio envoyé à chacun des haut-parleurs.</p><h4>Au casque</h4><p>Au casque, la technologie Dolby utilise des effets psycho-acoustiques-pour faire vivre la même expérience que celle que l’on peut retrouver en salle de cinéma ou via des équipements de home cinéma compatibles Atmos.</p><blockquote><strong>L’expérience est possible avec n’importe quel casque ou écouteurs !</strong></blockquote><p>Ces effets psycho-acoustique forment ce que l’on appelle un son binaural.</p><p>Pour mieux comprendre, n’oubliez pas qu’au cinéma, même s’il y a plusieurs dizaines de haut-parleur, vous n’avez que 2 oreilles !<br>Il suffit d’envoyer aux 2 oreilles le même son que celui que vous auriez eu en salle de cinéma pour susciter le même effet et la même immersion.</p><p>Dans la solution sur étagère Dolby pour générer le son binaural, le passage de Atmos à stéréo est effectué directement dans l’appareil.<br>Ceci permet de profiter de la source Atmos pour proposer le meilleur son possible dans toutes les configurations (écoute au casque, mais aussi via haut-parleur).</p><p>Actuellement, il est techniquement impossible de réaliser ceci sur des contenus chiffrés. <br>En effet, l’AppleTV et les appareils iOS ne gèrent pas encore le Dolby Atmos.</p><p>Or nos contenus sont chiffrés! <br>Il a donc fallu ruser pour rendre le Dolby Atmos possible via myCANAL.</p><h3>Comment ça marche sur myCANAL</h3><p>L’astuce trouvée consiste à préparer directement, à la source, le contenu Atmos pour le rendre possible au casque.</p><p>Pour cela, une piste audio neuronale spéciale est générée côté serveur et mise à disposition comme s’il s’agissait d’une langue différente.</p><p>En contrepartie, le son est optimisé uniquement pour une écoute au casque…</p><blockquote><strong>Le jour où l’AC–4 (le nouveau codec Dolby) sera décodé sur iOS, Android et autres, l’Atmos sera disponible dans toutes les configurations possibles !</strong></blockquote><p>Bien entendu, meilleur est le casque et meilleur est l’expérience, et les casques qui appliquent trop de traitements réduisent l’effet (ils détruisent les effets psycho-acoustiques).</p><h4>Le binaural</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F280031904%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Flucie-hardoin%2Fpresentation-du-binaural&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000227395149-wlz3ld-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/b0cec9a43a7266d4e69ce29cc57e79e4/href">https://medium.com/media/b0cec9a43a7266d4e69ce29cc57e79e4/href</a></iframe><h4>Cas du concert de Gorillaz</h4><p>Aujourd’hui, seul un concert de Gorillaz est disponible en Dolby Atmos via l’application iOS mais d’autres contenus sont à venir.</p><p>Pour ce concert, la captation a nécessité 14 micros supplémentaire ! <br>Les enregistrements ont ensuite été mixés par un professionnel Dolby Atmos via l’outil propriétaire Dolby pour construire la piste neuronale.</p><blockquote><strong>Il aura fallu une semaine de travail — post captation — à l’ingénieur du son pour obtenir le résultat disponible sur myCANAL.</strong></blockquote><h3>Testez le Dolby Atmos sur myCANAL</h3><p>Vous pouvez en profiter dès à présent via myCANAL sur iOS et AppleTV.</p><p>Pour cela, rien de plus simple :</p><ul><li>Mettez à jour votre application myCANAL</li><li>Recherchez le contenu « Gorillaz »</li><li>Branchez votre casque</li><li>Lancez la lecture</li><li>Sélectionnez la piste audio « Binaural VF »</li><li>Profitez ! ;-)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kdA0GeXt_8ZIVh3nL1SO-A.png" /><figcaption>Concert de Gorillaz avec un son Dolby Atmos sur #myCANAL</figcaption></figure><p>En passant d’une piste à l’autre, vous devriez ressentir une différence flagrante !</p><h3>Et les autres devices ?</h3><p>Aujourd’hui, Apple est le seul à avoir rendu disponible le Dolby Digital+ sur 100% de ses équipements depuis iOS 10 et macOS Sierra.<br>Le Dolby Digital+ est nécessaire pour générer ce rendu, c’est pour cela que les appareils Apple sont idéals pour introduire ces nouveaux formats.</p><blockquote><strong>Bien entendu, l’objectif est de généraliser la fonctionnalité sur l’ensemble des contenus en Dolby Atmos, y compris les films d’action !</strong></blockquote><p>De nouveaux programmes en Dolby Atmos seront disponibles dans le courant de l’année, entre autre parce qu’il y a maintenant un nombre de conséquent de films qui sortent en salle dans ce format.</p><p>Ils seront proposés, d’abord en binaural, au casque, comme pour Gorillaz, puis en AC–4 compatible avec les enceintes externes quand les terminaux prendront en charge le codec.</p><p>Le binaural sera également utilisé pour reproduire les bandes sons 5.1 et 7.1 de notre catalogue (dont la très grande majorité est en 5.1).</p><p>Le dernier décodeur CANAL, le <a href="https://medium.com/canal-tech/g9-nouveau-d%C3%A9codeur-de-canal-eb4d0c0f76e6">G9</a>, est d’ores et déjà compatible Dolby Atmos!</p><h3>Conclusion</h3><p>CANAL+, en plus d’avoir été les seuls au monde à proposer de la 4K le jour du lancement de l’Apple TV 4K avec Netflix et Apple, est cette fois ci seul au monde à proposer du Dolby Atmos sur device mobile.</p><p>L’objectif de CANAL+ est de proposer une expérience immersive peu importe le mode de consommation, et de proposer chaque fois la meilleure image et le meilleur son.</p><blockquote><strong>Sur les produits Apple, CANAL+ est donc fier de proposer la meilleure expérience image+son possible au monde !</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oz323m4BThhArbtFselY6A.png" /></figure><h3>Pour en savoir plus</h3><ul><li><a href="https://www.son-video.com/guide/dolby-atmos-le-son-home-cinema-en-3d">Dolby Atmos : le son home-cinéma en 3D</a></li><li><a href="https://www.cnet.com/news/dolby-atmos-why-its-cool-how-it-works-and-how-to-get-it/">Dolby Atmos: Why it’s cool, how it works and how to get it</a></li><li><a href="http://sonbinaural.com/son-binaural/">Présentation du binaural</a></li><li><a href="http://idfrancetv.fr/audio/binaural/">La technologie du binaural</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf55c8b4827a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/1%C3%A8re-mondiale-canal-propose-du-dolby-atmos-sur-apple-bf55c8b4827a">1ère Mondiale : CANAL+ propose du Dolby Atmos sur Apple !</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retours sur React-Europe 2016]]></title>
            <link>https://medium.com/canal-tech/retours-sur-react-europe-2016-cc2657f1cebc?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc2657f1cebc</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Mon, 13 Jun 2016 22:00:00 GMT</pubDate>
            <atom:updated>2018-01-10T12:35:22.430Z</atom:updated>
            <content:encoded><![CDATA[<p>Chez <a href="http://www.canalplus.fr/">Canal+</a> nous aimons et utilisons <a href="https://facebook.github.io/react/">React</a> dans de nombreux services.</p><p>Nous avons eu la chance de pouvoir assister cette année à la conférence <a href="https://www.react-europe.org/">React Europe</a> — LA conf européenne sur React — qui s’est déroulée le 2 et 3 juin à Paris et a rassemblé quelques centaines des passionnés venus du monde entier. Cette année étaient présents — entre autres — <a href="https://twitter.com/vjeux">Christopher Chedeau</a>, <a href="https://twitter.com/_chenglou">Cheng Lou</a> et <a href="https://twitter.com/dan_abramov">Dan Abramov</a> de la React Core Team, <a href="https://twitter.com/brindelle">Bonnie Eisenman</a> de Twitter ou <a href="https://twitter.com/jhusain">Jafar Husain</a> de Netflix — du beau monde donc — venus nous présenter les avancées de la stack Facebook et nous permettre de découvrir les grandes orientations des prochains mois/années.</p><p>L’édition précédente avait été l’occasion de découvrir en profondeur l’architecture Flux et notamment de vivre la naissance de <a href="http://redux.js.org/">Redux</a> par Dan Abramov. Les équipes de Facebook avaient aussi présenté deux nouveautés : <a href="http://graphql.org/">GraphQL</a> et <a href="https://facebook.github.io/react-native/">React-Native</a>.</p><p>Cette année peu de découvertes mais Facebook nous a conforté dans l’idée que GraphQL et React-Native sont leurs deux sujets du moment. Deux sujets qui changent en profondeur la manière de concevoir des applications. Et il semble que ça va durer.</p><h3>GraphQL</h3><p>GraphQL est un langage <a href="http://facebook.github.io/graphql/">une spécification</a> de requêtage de données se positionnant entre l’interface et le serveur. Il permet notamment d’agréger de façon “intelligente” des données éparses et les formater dans un json ayant une structure qui sied aux besoins du front. Nous l’utilisons chez Canal+ dans ce but, avec des résultats très satisfaisants (qui feront l’objet d’un prochain article (sourire)). En production chez Facebook depuis quelques années, GraphQL est aujourd’hui implémenté dans une douzaine de langages (javascript, Java, ruby, go ou .NET …).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TEOSP_goudgbGaAE.png" /></figure><p>Facebook semble vraiment croire en ce nouveau paradigme de communication client/serveur et le nombre impressionnant de projets (la gestion des caches, l’intégration avec React etc…) que propose la communauté montre un engouement réel.</p><p>Jafar Husain en a d’ailleurs profité pour présenter <a href="https://github.com/Netflix/falcor">Falcor</a>, la solution proposée par Netflix pour répondre aux mêmes problématiques. La philosophie reste globalement la même mais l’implémentation semble plus souple et nous a personnellement conquis !</p><p>GraphQL et Falcor remettent donc en cause l’architecture REST, ce qui n’est pas rien ! Mais un changement encore plus profond semble prendre forme avec React-Native…</p><h3>React-Native</h3><p>React-Native est né d’une volonté féroce de Facebook de simplifier et améliorer leurs développements sur mobile. On se souvient du virage à 180 degrés qu’a opéré la société californienne il y a 4 ans en abandonnant le HTML5 sur mobile au profit d’applications natives et laissant <a href="http://techcrunch.com/2012/09/11/mark-zuckerberg-our-biggest-mistake-with-mobile-was-betting-too-much-on-html5/">un souvenir douloureux</a> à Mark Zuckerberg. Ce traumatisme est sans doute à la base de nombreuses expérimentations en interne pour trouver une solution qui permettrait de développer des applications exécutables sur plusieurs plateformes et de manière homogène : Le fameux “Learn once, run everywhere”, fortement inspiré par le slogan de Sun Microsystems.</p><p>Après plus d’un an en open-source, React-Native est en passe de réussir son pari tant les améliorations et la création d’outils autour du framework présentés à ce React Europe sont nombreux. Facebook investit énormément d’énergie pour améliorer l’expérience et architecturer les développements. Limité initialement à iOS puis ouvert à Android, React-Native est aujourd’hui portable sur Tizen et Windows grâce aux <a href="http://techcrunch.com/2016/04/13/facebooks-react-native-open-source-project-gets-backing-from-microsoft-and-samsung/">travaux de Samsung et Microsoft</a> et d’autres développements sont en cours pour supporter OSX et…. le web !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Weh1VnALS6k0vCrp.png" /></figure><p>C’est ici qu’on prend la mesure de l’ambition de Facebook de créer un framework qui nous permettrait de créer des interfaces web &amp; native pour un nombre illimité de plateformes avec une même logique de développement. On imagine le gain en coûts et en temps de développements que cela implique ! Cette promesse fait grand écho chez Canal aux vus de nos produits cross-pateform (TV, WEB, MOBILE, BOX) ou la recherche d’optimisations est permanante.</p><h3>En conclusion</h3><p>D’autres talks nous ont aussi inspirés, comme <a href="https://www.youtube.com/watch?v=mVVNJKv9esE">la présentation</a> de Cheng Lou qui nous invite à réfléchir sur la notion d’abstraction dans nos applications.</p><p>Cette édition a été l’occasion pour Facebook de s’affirmer encore un peu plus comme un acteur de premier plan dans le monde du développement et l’absence de grosses nouveautés est finalement une bonne nouvelle en montrant la maturité de leurs solutions dans un monde JS en révolution perpétuelle.</p><p>PS : les vidéos des conférences sont déjà disponibles sur la <a href="https://www.youtube.com/channel/UCorlLn2oZfgOJ-FUcF2eZ1A">chaîne Youtube</a> de React-Europe (en anglais)</p><p><em>Originally published at </em><a href="http://developers.canal-plus.com/blog/feedback-react-europe/"><em>developers.canal-plus.com</em></a><em> on June 13, 2016 by </em><a href="https://medium.com/u/d96a6d807aae"><em>Florent DUVEAU</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc2657f1cebc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/retours-sur-react-europe-2016-cc2657f1cebc">Retours sur React-Europe 2016</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jenkins 2: Pipeline as Code]]></title>
            <link>https://medium.com/canal-tech/jenkins-2-pipeline-as-code-3b012055ab53?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b012055ab53</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[continous-integration]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Wed, 13 Apr 2016 22:00:00 GMT</pubDate>
            <atom:updated>2018-01-10T12:37:22.697Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last month, we tested the newest (and still sometime unstable) Jenkins version with a state-of-the-art development workflow in mind. It includes strong Github integration (i.e. with the Status API), Docker usage (for on-demand and versatile slaves) and user-friendly Jobs configuration and bootstrapping (i.e. build steps should be part of the code and focus on reusability).</p><p><strong>Note : this blog post relate our Jenkins 2 experience as of the Alpha &amp; beta release of the 2.0 version. Your mileage may vary with the release of the recent RC and the future stable version.</strong></p><h3>Jenkins 2.0</h3><p>Do you remember when Jenkins was the way to go for building your CI environment ? Down the road, many other tools went into the CI / CD race, adding their own awesome feature and helping redefine what Continuous Integration means.</p><p>Compared to , say, Travis-CI, Jenkins lacks some major features like easy, builit-in integrations with other CI / CD / code quality tools, volatile &amp; on-demand slave management or the ability to describe your job in a simple, versionned text file.</p><p>This is where Jenkins 2 comes, bringing “Pipeline as code, a <a href="https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog">new setup experience</a> and other UI improvements” mainly to the job configuration pages. Sticking to the Jenkins philosophy, the new Jenkins verison if fully compatible with older jobs &amp; plugins. This is, as stated in the release announcement, a “drop-in replacement” for Jenkins 1.x and you don’t have to worry about existing configuration.</p><p>The killer feature is the ability for a developer to provide the build steps from a text file (a “Jenkinsfile”), exactly like a .travis.yml file with a touch of Groovy. Take this example :</p><pre>node { // The &quot;node&quot; directive tells Jenkins to run commands on the same slave. checkout scm stage &#39;test&#39; sh &#39;make test&#39; stage &#39;publish&#39; sh &#39;make publish&#39; }</pre><p>Simple, right ? I’ve just declared 2 build steps, “test” and “publish” both using the sh directive to launch my test/build scripts (and a Makefile under the hood, for brevity). Such stages are stored in Jenkins. They are logged, timed and replayable anytime one-by-one or by group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*A2fNe4WDrgIuRKKs.png" /></figure><p>The available documentation contains a <a href="https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md">great tutorial</a> to get started with the Groovy DSL used by Jenkins. Many plugins developers already have ported their code to be usable from a Jenkinsfile and the <a href="https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md">list of Pipeline-compatible plugins</a> is growing quickly.</p><p>These directives can easily be extended with your own scripts (check out the <a href="https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md">dedicated docs</a> — more on that later).</p><p>The rest of this article focuses on configuration decisions we made to achieve our workflow objectives.</p><h3>Light, efficient GitHub workflow</h3><p>Ok, now for a hands on with this new version. After installing some smart plugins like the <a href="https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+GitHub+Branch+Source+Plugin">CloudBees GitHub Branch Source Plugin</a>, we are able to create a “folder” project (“Multibranch Pipeline Job”) based on any repository in your GitHub organisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Yt4SY81u_tpyG7ta.png" /></figure><p>Note : Jenkins will need valid credentials to access your organization’s private repositories. I strongly suggest you to use a <a href="https://developer.github.com/guides/managing-deploy-keys/#machine-users">Github Machine User</a> for Jenkins &lt;-&gt; GitHub integration.</p><p>After configuring the plugin so Jenkins use the Github Commit Status API to check ever commit/branches/PR of our repositories, it’s time to see it in action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5NlsuDeYVQP587z4.png" /></figure><p>Let’s create a branch to work on a new feature. Jenkins will automagically detect this new branch, create a job based on the Jenkinsfile it find inside the tree. The same behavior applies for the PR created on GitHub. If I want to, I can edit the Jenkinsfile for this new branch only, without breaking the build for other branches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/0*Our7K0NzjPGBb0ca.png" /></figure><p>Additionally, if you delete the branch (i.e. after a successful merge), Jenkins will simply delete the branch-related job.</p><p>On the GitHub side, Jenkins now checks our work and tell us if it’s good or not — like Travis-CI would do. We’re close to our ideal CI workflow!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r4y6zc9Ven-nO1zA.png" /></figure><h3>Let it be Dockerized</h3><p>Now that we have good GitHub integration, let’s push our CI workflow forward with Docker. Thanks to the <a href="https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Pipeline+Plugin">CloudBees Docker Pipeline Plugin</a> (and its great <a href="https://documentation.cloudbees.com/docs/cje-user-guide/docker-workflow.html">user guide</a>), we can easily tell Jenkins to use a Docker image (either pull or build one from a versionned Dockerfile) to handle a job. Let us slightly change our first job definition :</p><pre>node(&#39;docker&#39;) { // I want a slave labeled &quot;Docker&quot; (i.e. with Docker installed) docker.image(&#39;python:latest&#39;).inside { // Let&#39;s use the latest Python image checkout scm // Run the job normally... stage &#39;test&#39; sh &#39;make test&#39; stage &#39;publish&#39; sh &#39;make publish&#39; } }</pre><p>What’s happening here ? Well, docker.image(&#39;python:latest&#39;).inside tells docker to instanciate a container with the python:latest image and mount the workspace inside it! Note that if all your nodes have Docker installed, you can omit the node directive, as all the job will be run in one container.</p><p>Going further, if you want to test your code with multiple version of a Docker image, simply create a branch, change the version in the Jenkinsfile, and that’s it. You can even parameterize the version tag in Jenkins for run-time changes!</p><p>Note: You can use this Docker logic with old jobs with the <a href="https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Custom+Build+Environment+Plugin">CloudBees Docker Custom Build Environment Plugin</a>.</p><h3>Wrapping it up</h3><p>I definetely suggest you to test the newest version of Jenkins. This is making Jenkins a real, state-of-the-art competitor again in the CI/CD competition. It’s your good ol’ tools, but under steroids.</p><p>We achieved a clean workflow with ease in days rather than weeks. We don’t go often on the Jenkins UI anymore, since all the logic is in the repository. We gave back developer the power of CI. It’s our code, our build directives.</p><p>Have anything to say ? Please tell us in the comments or <a href="https://twitter.com/plusdedev">tweet us</a> !</p><p><em>Originally published at </em><a href="http://developers.canal-plus.com/blog/jenkins-2-pipeline-as-code/"><em>developers.canal-plus.com</em></a><em> on April 13, 2016 by </em><a href="https://medium.com/u/3903c93579b5"><em>Julien Tanay</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b012055ab53" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/jenkins-2-pipeline-as-code-3b012055ab53">Jenkins 2: Pipeline as Code</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Bob : conversation-driven development]]></title>
            <link>https://medium.com/canal-tech/meet-bob-conversation-driven-development-449ccd0824ce?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/449ccd0824ce</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Thu, 25 Feb 2016 23:00:00 GMT</pubDate>
            <atom:updated>2018-01-10T12:37:55.344Z</atom:updated>
            <content:encoded><![CDATA[<p>Many teams here at Canal+ use their own ChatOps software to handle repetitive tasks and/or notifications through their favorite chat app (from IRC to Slack). From Hubot to custom solutions, they vary on user’s affinites with programming languages (Hubot scripts are written in CoffeeScript, Lita’s ones are in Ruby) and chat platform (some bots are not compatible with the XMPP protocol).</p><p>The idea of a bot spamming an IRC channel is not new. We (developers) are used to this good old funny Quizz bot hanging around in our chatroom at the end of the day. What’s new here is that theses bots are connected to real-life, developer-oriented stuff : think test tools, deployment orchestrators or nerdy webcomics.</p><p>For the last couple of months, I’ve been working on providing my team (the CANAL+ Innovation team) with some cool DevOps tools and practices. Last week, we adopted a new robotic gentleman in the family, which was loosely name Bob*. Let’s introduce him.</p><h3>The urgent need for automation</h3><p>Today, major parts of our jobs tend to be automated. Many companies making their digital shift try to make conversation between coworkers easier. Most of the time they begin by trying to reduce the amount of email we send/receive every days (from dozens to hundreds, depending on what your job consist of on a daily basis). Softwares like <a href="https://slack.com/">Slack</a>, <a href="https://www.hipchat.com/">Hipchat</a> or <a href="https://discordapp.com/">Discord</a> are good candidates for this job. People spend less time typing long emails and just “chat” with their colleagues.</p><p>At the same time, the DevOps guys are trying to automate the testing and deployment (among other things) of our applications. But this automation comes with a trade-off : you have to learn new tools (with their own CLI or web-UI), new dialects, etc. Why can’t we just use the tool everybody already knows ?</p><p><strong>Here come the ChatOps magic thing, bringing your shiny tools into the conversation</strong>. You will never have to ask your favorite developer to “Open your browser, go to the [devops_tool] webUI, click here, and here, and on that big green button” again (true story). Let him chat with the tool!</p><p>From a developer’s point of view, it allows you to stay focused on the important things : the code and the value it creates for the people (customers?) who use the underlying services. Code-centric companies like Github went “officially” into the ChatOps world <a href="https://github.com/blog/968-say-hello-to-hubot">five years ago or so</a> and use these little robotic dudes on a daily basis to tackle annoying, repetitive tasks. It’s not too late to offer your team a virtual, smart and (not-so-)polite friend.</p><h3>A DevOps’ best friend : Err</h3><p>Err was created by <a href="https://twitter.com/gbin">@gbin</a> and maintained by a bunch of cool guys around the world (come and say hello on <a href="https://gitter.im/errbotio/errbot">gitter</a>!). Quoting from the official website, it is “a chatbot, a daemon that connects to your favorite chat service and bring your tools into the conversation.”</p><p>Errbot is written in Python. DevOps are (often) native Python speakers. It makes it really easy to port large amount of handcrafted scripts to Errbot “plugins”. The anatomy of a minimal Errbot plugin looks like this snippet :</p><pre>from errbot import BotPlugin, botcmd class MeetBob(BotPlugin): &quot;&quot;&quot;Bob is a polite plugin for Errbot&quot;&quot;&quot; @botcmd def hello(self, msg, args): &quot;&quot;&quot;Wish you a good day&quot;&quot;&quot; return &quot;Good day, Sir!&quot;</pre><p>See ? Really simple! Errbot provides you with the @botcmd decorator for standard messaging functions and a bunch of other cool APIs like a Scheduler for periodic tasks (polling, message broadcasting, …), an embedded Webserver to handle custom webhooks (from Github, Jenkins, …) and <a href="http://errbot.io/features.html#core-features">much more</a>. For a more complete example, check out the <a href="https://github.com/Djiit/err-meetup">err-meetup</a> plugin I wrote to interact with the <a href="https://meetup.com/">meetup.com</a> API, i.e :</p><pre>me : !meetup next Paris-py-Python-Django-friends BOB : No upcoming events. me : ;-(</pre><p>Our very own Errbot (“Bob”) help us be more productive by joining the conversation in our chatrooms, listening everything we say and eventually triggering a Python function. You don’t need to bring your geeky terminal here : just ask Bob and he will politely execute your order or answer your question (about life, the universe and everything).</p><h3>Making working with Jenkins fun again</h3><p>Working with Jenkins is most of the time a pain in the *** for the average, code-focused, non-Jenkins’-old-fashion-UI-savvy developer. You can’t force people to use your new shiny tool if they don’t want — even if you think it will automate some part of their job, like testing and building their code in the case of Jenkins. Using ChatOps software allows them to, well, “chat” with Jenkins.</p><p>There was an old and un-maintained Errbot&lt;-&gt;Jenkins plugin, only compatible with Python2. So I decided to fork it and make it usable with the latest version of Python, Errbot and Jenkins, adding some cool features on the way. This was a sort of test-run to see how easy it was to hack a plugin for Errbot. Basically, it uses the great python-jenkins package available to PyPI to communicate with Jenkins, and the Errbot embedded webserver to handle incoming webhooks. You’ll find the complete source <a href="https://github.com/Djiit/err-jenkins">here</a>.</p><p>Here is an example of our daily workflow for small-sized projects :</p><pre>me :	Bob, build myProject {&#39;branch&#39;: &#39;feature-mysuperfeature&#39;} BOB :	Your job should begin shortly: [link-to-myproject-build] (...) BOB :	Build #42 SUCCESS for Job myProject! Yeah! me :	thx mate!</pre><p>And voila! Everybody can chat with Bob, in our chatrooms or in a 1to1 conversation over Slack or IRC. This is just a starting point. We can enable Bob to do many, many more things, using just plain Python scripts, and it sounds terribly funny (to me ;-) ).</p><p>Have any idea or comments about Bob ? Please tell us on <a href="https://twitter.com/plusdedev">Twitter</a></p><ul><li>Errbot : <a href="http://errbot.io/">http://errbot.io</a></li><li>Plugins created by the Errbot community : <a href="https://github.com/errbotio/errbot/wiki">https://github.com/errbotio/errbot/wiki</a></li><li>ChatOps at Github : <a href="https://www.youtube.com/watch?v=NST3u-GjjFw">https://www.youtube.com/watch?v=NST3u-GjjFw</a></li><li>ChatOps everywhere : <a href="https://www.reddit.com/r/chatops/">https://www.reddit.com/r/chatops/</a></li></ul><p><em>Julien Tanay </em><a href="/service/mailto:julien.tanay@canal-plus.com"><em>julien.tanay@canal-plus.com</em></a></p><p>* I admit it : he takes his name from Bob the Builder. Shame on me.</p><p><em>Originally published at </em><a href="http://developers.canal-plus.com/blog/meet-bob/"><em>developers.canal-plus.com</em></a><em> on February 25, 2016 by </em><a href="https://medium.com/u/3903c93579b5"><em>Julien Tanay</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=449ccd0824ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/meet-bob-conversation-driven-development-449ccd0824ce">Meet Bob : conversation-driven development</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analysing the state of a set-top box using it’s video output]]></title>
            <link>https://medium.com/canal-tech/analysing-the-state-of-a-set-top-box-using-its-video-output-fcb26525de2e?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcb26525de2e</guid>
            <category><![CDATA[cable-tv]]></category>
            <category><![CDATA[arduino]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Tue, 22 Sep 2015 22:00:00 GMT</pubDate>
            <atom:updated>2018-01-10T12:39:45.746Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the challenges that the software validation team faces is knowing what is the state of a given set-top box without having to look at its output, this is specially useful when automating tests since we’ll be sending a command to the box and then looking at its state to check if the command was successfully executed. A software called R7Valid was developed for this purpose, it is used to run multiple tests automatically on set-top boxes using an infrared LED to emulate remote control commands and then it retrieves the state of the set-top box using external APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*4UMia0H2qiat1zTy.png" /></figure><p>The problem of this approach is that the set-top box has only a limited amount of information available through its API, we can for example retrieve what is the view displayed in the screen, or if we paused the video or not, but we can’t know for sure what is being displayed on the screen.</p><p>For this problem we developed a solution capable of giving us the state of the video being displayed in a given moment using a few photo resistors, an Arduino and an Ethernet shield.</p><p>The photo resistors used were TinkerKit LDR Sensors, that were plugged directly into the Analog inputs of arduino, the output of these sensors varies from 0V to 5V depending of the intensity of light that they’re exposed to, we then proceeded to fixing one of these sensors to a TV screen using a cardboard box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*B5nKIPrfGW16OpVq.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*1OeFVNqO-ynBc1_9.jpg" /></figure><p>We then developed a simple HTTP server and API to run on the Arduino so we would be able to send and receive data from it and started analyzing the signal that we received for different scenarios:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*-iUxhWtayTUcBV-w.png" /></figure><p>As we can see by these signals it’s not hard to make a difference of the these situations, the first signal shows us that there are changes in the intensity of the light being received and therefore that the image is moving, the second one shows us that we have a fixed intensity of light that doesn’t change and we either are seeing a freeze in the video or a menu being shown, and the last case would be having a dark screen, which is a low intensity constant value in the sensor.</p><p>Since sometimes we might have a part of the screen that doesn’t move, it would be possible to misclassify a live signal as a freeze if that happened on the area under the cardboard, to minimize this problem we added another sensor to the screen covering a peripheral area, this has minimized the errors in classification.</p><p>This approach can be used for multiple purposes as checking if the set-top box has executed a command, checking if there is a live stream on the TV and even measuring the time for switching from a channel to another. The next step now is to integrate this solution to R7Valid and improve the automatic tests and create a more reliable tool for testing our software automatically.</p><p>You can also easily modify the source code to create your own REST server on arduino for any application where connectivity is needed, this is the main file of the project, as you can see it is really eassy to create your own routes for the API.</p><pre>void getVideo(EthernetClient *client, char args[]){ int v1 = analogRead(A4); int v2 = analogRead(A5); client-&gt;print(&quot;{\&quot;video1\&quot;:&quot;); client-&gt;print(v1); client-&gt;print(&quot;,\&quot;video2\&quot;:&quot;); client-&gt;print(v2); client-&gt;println(&quot;}&quot;); } void setup() { Serial.begin(9600); myServer = new restServer(mac, ip, gateway, subnet,80); delay(1000); //create routes on our rest server myServer-&gt;addRoute(&quot;/video&quot;, GET, &amp;getVideo); myServer-&gt;addRoute(&quot;/getlivestatus&quot;, POST, &amp;getLiveStatus); myServer-&gt;addRoute(&quot;/status&quot;, POST, &amp;stbState); } void loop() { myServer-&gt;serve(); }</pre><p>To add new methods all you have to do is to create a new callback function:</p><pre>void newcallback(EthernetClient *client, char args[]){ TODO: your code here! }</pre><p>And then on the <em>setup()</em> method you can add a new route:</p><pre>myServer-&gt;addRoute(&quot;/newroute&quot;, GET, &amp;newcallback);</pre><p>The source code of the software and libraries are available on GitHub: <a href="https://github.com/canalplus/tvduino">TVduino</a></p><p><em>Originally published at </em><a href="http://developers.canal-plus.com/blog/analysing-the-state-of-a-set-top-box-using-its-video-output/"><em>developers.canal-plus.com</em></a><em> on September 22, 2015 by Filipe Caldas</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcb26525de2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/analysing-the-state-of-a-set-top-box-using-its-video-output-fcb26525de2e">Analysing the state of a set-top box using it’s video output</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DASHme — The rx-player companion]]></title>
            <link>https://medium.com/canal-tech/dashme-the-rx-player-companion-474a6f2cb99e?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/474a6f2cb99e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <category><![CDATA[video-player]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Tue, 14 Jul 2015 22:00:00 GMT</pubDate>
            <atom:updated>2017-12-22T15:07:55.951Z</atom:updated>
            <content:encoded><![CDATA[<p>As you’ve probably seen, we released a few weeks ago an HTML5 player based on reactive programming : <a href="https://github.com/canalplus/rx-player">RX Player</a>. This is quite nice if you want to play your own content on your website, if you have some, but if you don’t, well, it’s kind of useless.</p><p>This is where DashMe come in handy.</p><p>The idea behind DashMe is to convert any video encoded with H264 into DASH content. It generates a DASH manifest and MP4 chunks from any type of video format (AVI, MOV, MKV, Smooth Streaming, …) and expose them through a simple REST interface. Therefore, combined with RX player, you can stream and play your own content converted and served by DashMe directly on your website with practically no hassle.</p><p>This project started when we needed to test our player, we needed to generate some content to use with RX Player without having to use GPAC and install a new HTTP server to serve it to the player. It then evolved as an experimentation platform to play around with DASH.</p><p>Behing the curtain, DashMe works using <a href="https://www.ffmpeg.org/">FFMPEG</a> or <a href="https://libav.org/">LIBAV</a> with <a href="https://golang.org/">Golang</a>. Golang is a new and interresting language especially for its concurrency primitives and its complete standard library. For example, all the HTTP serving is done using only the standard library. The built-in concurrency primitive helps a lot to spawn concurrents tasks and retrieve their results easily. Also, because it’s a compiled language its performances are quite better than nodejs or python (generally) but also it enables to link easily to C code and shared libraries. Therefore, thanks to this language we could integrate FFMPEG/LIBAV and benefit from their video formats parsing and extract easily the H264 samples before rapacking it to fragmented MP4. Nevertheless, it has a few drawbacks, some you can go around, some you can’t. For example its standard library can be considered as heavy and there’s nothing you can do about that. Also it has a really simple (dumb ?) garbage collector. In our case where we parse potentially heavy video it can be disastrous. Hopefully, with some tweeking in the code you can reduce this issue.</p><p>So why would you be interrested in DashMe ? Well, I can think of a few reasons :</p><ul><li>To test or use RX Player but you don’t have any content.</li><li>To discover Golang and what can be done with this new language</li><li>To better understand the DASH format</li></ul><p>Whatever is your reason, don’t hesitate to <a href="https://github.com/canalplus/DashMe">take a look</a>.</p><p><em>Originally published at </em><a href="http://developers.canal-plus.com/blog/dashme-the-rx-player-companion/"><em>developers.canal-plus.com</em></a><em> on July 14, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=474a6f2cb99e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/dashme-the-rx-player-companion-474a6f2cb99e">DASHme — The rx-player companion</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing rx-player]]></title>
            <link>https://medium.com/canal-tech/introducing-rx-player-cd78a56d6019?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd78a56d6019</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Mon, 29 Jun 2015 22:00:00 GMT</pubDate>
            <atom:updated>2017-12-22T15:06:50.952Z</atom:updated>
            <content:encoded><![CDATA[<p>A few months ago, as Google announced the tearing down of Silverlight support in Chrome, CANAL+ started working on a new player, using the new HTML5 API (MSE, EME, …) to play video.</p><p>This player is now used by the CANAL+ users within <a href="http://live.mycanal.fr/tv/">myCANAL website</a>.</p><p>Today, we are excited to open source it and hope that it will help the community to play video contents on the web.</p><p>Building a streaming video player in javascript is a complex task due to the numerous interactions with the outside world it has to deal with. Whether they come from the user seeking at a particular moment of its movie, changing the current channel or the network congestion. The video player being the centerpiece of our applications, it needs to adapt very quickly to any of these inputs and stay resilient to various errors.</p><p>Many current video player implementations rely on classical object-oriented hierarchy and imperative event callbacks with shared mutable objects to manage all these asynchronous tasks and states. We found this approach to be the wrong abstraction to handle the complexity of a video player.</p><p>Rx on the contrary provides gracious interfaces and operators to compose asynchronous tasks together by representating changing states as observable stream of values. It also comes with a <strong>cancelation</strong> contract so that every asynchronous side-effect can be properly disposed when discarded by the system (this is still <a href="https://github.com/whatwg/fetch/issues/27">a controversial issue in the JS community</a>).</p><p>This allowed us to implement some nice features quite easily. For instance, because in the rx-player all asynchronous tasks are encapsulated in observable data-structures, we were able to add a transparent <a href="https://github.com/canalplus/canal-js-utils/blob/master/rx-ext.js#L73-L100">retry system</a> with a simple observable operator to declaratively handle any failure and replay the whole process.</p><p>Another example is the way we abstracted our transport layer into an observable pipeline, allowing us to support different type of streaming systems with its own asynchronous specifities. And because Rx is message-driven, this encapsulation allows us isolate the transport I/O into a WebWorker without any effort, or add an offline support for any pipeline implementation.</p><p>We will write more about it in the next weeks. For now, just have a look on <a href="https://github.com/canalplus/rx-player">github</a>.</p><p><em>Originally published at </em><a href="http://developers.canal-plus.com/blog/introducing-rx-player/"><em>developers.canal-plus.com</em></a><em> on June 29, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd78a56d6019" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/introducing-rx-player-cd78a56d6019">Introducing rx-player</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[About CANAL]]></title>
            <link>https://medium.com/canal-tech/about-canal-9409735f6283?source=rss-bf954c2f4e09------2</link>
            <guid isPermaLink="false">https://medium.com/p/9409735f6283</guid>
            <category><![CDATA[television]]></category>
            <category><![CDATA[live-streaming]]></category>
            <category><![CDATA[channel]]></category>
            <dc:creator><![CDATA[CANAL TECH TEAM ]]></dc:creator>
            <pubDate>Thu, 01 Jan 2015 14:23:15 GMT</pubDate>
            <atom:updated>2018-08-03T13:25:26.337Z</atom:updated>
            <content:encoded><![CDATA[<p>CANAL is the french equivalent of Hulu or Sky. We are an aggregator, meaning we distribute live TV, replay, SVOD (like Netflix or Amazon), TVOD (like Itunes or Google play) and even some news : e-sports, musical news, urban culture, …</p><p>We own premium and free channels and we produce original contents for them : movies, tv shows, programs, … People subscribe to watch sports, movies / tv shows, humorous programs and even some adult contents ! 😉</p><p>CANAL is more than 30 years old and available in 36 countries. We distribute our content over internet but also via satellites to be able to reach territories with low bandwidth. That means you can even watch our content in 4k resolution without internet access !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9409735f6283" width="1" height="1" alt=""><hr><p><a href="https://medium.com/canal-tech/about-canal-9409735f6283">About CANAL</a> was originally published in <a href="https://medium.com/canal-tech">CANAL+ TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>