SoC 2017

This page summarize the current list of ideas for VideoLAN project, for Google Summer Of Code 2017.

The list is not exhaustive, and is not limitative. Feel free to apply with your own idea!

Introduction & Information

This wiki page covers the attempt by the VideoLAN project to act as a mentoring organization for Google Summer of Code, in order to improve VLMC and the libVLC engine.

VideoLAN was a mentoring organization in 2007, 2008, 2009, 2010, 2011, 2013 and 2016.

This page list the ideas for VLMC and libVLC.

VideoLAN Movie Creator

VLMC is a cross-platform non-linear video editing software based on libVLC technology. It was started as a final year student project at the French IT school EPITECH.

VLMC currently awaits a transition to the current libvlc API and it's actual 1.0 release!

libVLC

VLC media player is a cross-platform multimedia player, encoder and streamer application. It is one of the most successful open-source projects without any professional structure underneath.

VLC media player is downloaded at an approximate monthly rate of 23 millions from the main website and that's not including third-party distributions (Linux)!

You can find more information on VLC on Wikipedia or on this wiki.

The engine of VLC is libVLC, and is used by VLMC.

Summer of Code

If selected and developed, SoC projects for VLMC and VLC will be included in later releases.

All projects are covered by the GPL (v2+) or LGPL (v2.1+) licenses depending on the module.

Compile libVLC or VLMC

This may sound trivial, but it's harder than many expect. See https://wiki.videolan.org/Category:Building/ for more informations.

Provide a small patch

To demonstrate your skills, share a small patch with us. This will let you become familiar with Git, in case you don't know it already and our process on merging patches.

Let's get in touch

If you have a doubt, are not sure about anything or want clarification, please get in touch with us.

We have 3 major communication channels: Our mailing-lists to discuss patches and further development related topics. Furthermore, we have our web forums for VLC-related end-user support - a VLMC section will be created once the product is published. Finally, there is our IRC channel #videolan (for libVLC) and #vlmc on the Freenode network. It's open to any kind of discussion. Usage issues, questions how to compile VLC/VLMC, getting to know the fellow developers, etc.

Ideas for VLMC

Port to Android

Project Description: VLMC is now working on the desktop. It would be nice to port it also to the mobile world, starting by Android.

This project would require to adapt to smaller screens, and simplify the UI to fit the Android workflow.

Tasks to do:

1. Fix the VLMC build on Android. As libVLC works fine on Android, this is more focused on compiling the Qt part for Android.
2. Split more parts of the UI in components that are reusable on mobile.
3. Change the components to fit the small resolutions of the Android devices.
4. Rewrite some UI components in QML.
5. Write a simpler timeline widget for Mobile workflows.

Requirements: This project requires C++/Qt/qml knowledge, and access to Android devices.

Proposed mentors: Geoffrey/Hugo

Media Workflow rework

Project Description: VLMC is now working on the desktop, but the media workflow is quite slow and is missing some common use cases.

This should be fixed in MLT framework backend for libVLC and is the continuation from the work from the previous Summer of Code.

Tasks to do:

1. Understand the MLT libVLC backend codebase,
2. Clean the backend and port it to a cleaner code state in C++,
3. Benchmark the code and make it more efficient,
4. Work to merge this backend upstream,
5. Implement all the missing features in libVLC.

Requirements: This project requires C/C++ knowledge, and understanding of multimedia concepts is a good positive point.

Proposed mentors: Hugo

Workflow audio filters

Project Description: VLMC is now working on the desktop, but we need to have a good setup of audio filters to make it usable for most people.

Tasks to do:

1. Understand the VLMC and MLT codebase interactions,
2. Add audio filters on the MLT framework backend using the LADSPA library or a similar open source library,
3. Code the interface corresponding to those filters, and their options,
4. Prepare visualizations, and notably for soundwave filters,
5. Integrate those inside the timeline UI,
6. Optimize.

Requirements: This project requires C++/Qt/qml knowledge, and enough understanding of audio.

Proposed mentors: J-B

Workflow video filters

Project Description: VLMC is now working on the desktop, but we need to have a good setup of video filters to make it usable for most people.

Tasks to do:

1. Understand the VLMC and MLT codebase interactions,
2. Add video filters on the MLT framework backend using the movit library or a similar open source library,
3. Code the interface corresponding to those filters, and their options,
4. Add transitions between clips
5. Code the interface to manage those transitions,
6. Optimize the code.

Requirements: This project requires C/C++ knowledge.

Proposed mentors: Felix

Key ideas for libVLC

Fuzz libVLC with LibFuzzer

libFuzzer ((http://llvm.org/docs/LibFuzzer.html).) is a library for coverage-guided fuzz testing.

• The first step of this GSoC project is to implement Fuzz Targets (http://llvm.org/docs/LibFuzzer.html#fuzz-target) to test various parts of the libVLC project. The non exhaustive parts will be the following libVLC modules API: "decoder", "encoder, "access", "packetizer", "demuxer". For each parts, the student will have to understand the module API in order to effectively implement the target.

• The second step is to find valid corpus (http://llvm.org/docs/LibFuzzer.html#corpus) for every module types and for every modules (mkv input for mkv demuxer, mp4 input for mp4 demuxer, h264 input for h264 decoder...).

• The third step is to host and run the fuzzer. It's not decided yet if the fuzzer will be hosted by google (https://github.com/google/oss-fuzz) or by the VideoLan association.

• If there is enough time, the fourth and final step is to fix the issues that has emerged during the previous steps.

This project requires C and C++ knowledge.

Proposed mentor: tguillem

libVLC AirPlay support

libVLC is now able to send video to the ChromeCast devices. We want to be able to do the same using the Airplay protocol, for Apple devices.

We want to be able to cast from any device, including Android or Windows machines, on all support Airplay devices, like Apple TV, iOS devices and audio amplificators.

This will use the new renderer APIs added in libVLC 3.0. Those APIs will need to be extended to allow the renderer to kick in during the playback.

Please have a look at the following files:

• modules/stream_out/chromecast/chromecast_ctrl.cpp (Chromecast)

• include/vlc_renderer_discovery.h (renderer API)

A motivated and fast enough student could pair this task with the UPnP renderer!

The work will consist of the following tasks:

• documentation on the AirPlay protocol,
• implementation of the detection/discovery of the supported devices,
• implementation of the protocol to discuss with the device,
• modify the control to transcode on demand,
• polish and release.

This project requires C knowledge and access to some Airplay devices.

Proposed mentor: steve

libVLC UPnP renderer support

libVLC is now able to send video to the ChromeCast devices. We want to be able to do the same using the UPnP Renderer protocol, for all the connected TV devices that support this protocol.

We want to be able to do that from any device, including Android, iOS or Windows machines.

This will use the new renderer APIs added in libVLC 3.0. Those APIs will need to be extended to allow the renderer to kick in during the playback.

Please have a look at the following files:

• modules/stream_out/chromecast/chromecast_ctrl.cpp (Chromecast)

• include/vlc_renderer_discovery.h (renderer API)

A motivated and fast enough student could pair this task with the Airplay renderer!

This project requires C knowledge and access to some connected TV supporting this protocol.

Proposed mentor: tguillem

VLC web interface modern look

The Web interface of VLC is a very ugly player and we want to improve that quite a bit.

This can be done in React, RxJS or Vue.JS to achieve a modern look, with transparency and cross-platform support.

This project requires JavaScript knowledge and experience. The choice of the Framework can be changed if needed.

Proposed mentor: David Loiret

libVLC 3D video support

libVLC is able to play most 2D and Side-By-Side videos, but the support of 3D is very limited.

Because of 360 and VR support, the attention about 3D is getting very popular those days. We need to support that in libVLC.

This project requires C knowledge.

Proposed mentor: adrien

libVLC VR support

libVLC is able to play most 2D and 360 videos, but the support of VR is very limited.

Because of 360 and VR support, the attention about VR is getting very popular those days. We need to support that in libVLC.

This project is mostly connecting a new headset to libVLC to get support in all libVLC applications.

This project requires C knowledge.

Proposed mentor: adrien

VLC macOS interface rework

The VLC interface is quite outdated on macOS.

This project for the summer is to rework heavily this interface to make it beautiful and useful again.

This project requires Obj-C knowledge.

Proposed mentor: David F

VLC Qt interface rework

The VLC interface is quite outdated on Linux and Windows. It has a lot of features, but some are not properly exposed.

This project for the summer is to rework heavily this interface to make it beautiful and useful again.

Ultimately, the idea is to get closer to what the WinRT/UWP interface looks like. It is simpler, more user friendly, and has a better "media center" feel into it.

Qml is the preferred way of improving the UI, but switching to Qml directly is probably too steep of a road at start.

This project requires Qt/C++ knowledge.

Proposed mentor: J-B

VLC cryptographic updates

VLC is already using GPG signatures to achieve secure updates on the Windows platform. But the updates are currently signed with a single master key which is pinned into the source code and VLCs in the wild aren't able to check for revocations of this key.

Therefore we would like to improve this situation by:

• being able to sign developers' keys that can sign VLC binaries on behalf of this master key
• support revocations of these developer's key
• provide a master key upgrade path

This project requires solid notions of C and Crypto.

Proposed mentor: geal