Roadmap.md 3.86 KB
Newer Older
1 2 3 4 5
# Roadmap

This is intended to be a **general overview** of the very
important or big features/improvements we are working on, or planning.
For a list of smaller features see [fun tasks for
6
newcomers](https://gitlab.gnome.org/GNOME/pitivi/issues?label_name%5B%5D=4.+Newcomers).
7 8 9 10 11

What keeps us busy in general?

-   **Fixing bugs**. Improving reliability and ease of use is never
    “done”. We have
12
    [tons](https://gitlab.gnome.org/GNOME/pitivi/issues) of work.
13 14 15 16 17 18 19 20 21 22 23 24
    [Help](http://www.Pitivi.org/?go=contributing) is very welcome!
-   **Improving GStreamer**. This benefits not only Pitivi, but other
    multimedia applications as well.
-   **Working on features**: Until we reach [1.0](releases/1.0.md), only
    if they improve stability.

# High-level roadmap

Any time estimates here are mostly wild guesses. Do not treat them as
hard deadlines. This aims mostly at giving an idea of how milestones
follow each other.

25
-   2018 Q4: release [1.0](releases/1.0.md) with ponies and rainbows
26 27 28 29 30 31 32

See [Current events](Current_events.md) for past items.

# Major features

## Plugin system

33 34 35 36 37
-   Status: [done](https://gitlab.gnome.org/GNOME/pitivi/issues/1480),
    but we still need a [developer
    console](https://gitlab.gnome.org/GNOME/pitivi/issues/2055), and
    [documentation with
    examples](https://gitlab.gnome.org/GNOME/pitivi/issues/2089).
38 39 40 41 42
-   **This is very important**. A plugin would have access to the entire
    app. Being in Python, it will be extremely easy to quickly write
    useful plugins without having to compile anything. Pitivi plugins
    will allow manipulating the timeline clips and clip effects
    automatically, thus allowing great flexibility for custom solutions.
43 44 45
    See for example [audio
    normalization](https://gitlab.gnome.org/GNOME/pitivi/issues/638)
    or the [autoaligner
luz.paz's avatar
luz.paz committed
46
    resurrection](https://gitlab.gnome.org/GNOME/pitivi/issues/1345).
47

48
## Motion ramping, time stretching
49 50

-   Status: started
51
-   See [issue 632](https://gitlab.gnome.org/GNOME/pitivi/issues/632)
52

53
## Effects UI
54

55 56 57 58 59 60 61
-   Status: some effects like
    [alphaspot](https://gitlab.gnome.org/GNOME/pitivi/issues/2098) and
    [color corrector](https://gitlab.gnome.org/GNOME/pitivi/issues/660)
    already have a custom UI. The overall experience can be smoother.
-   Still to do: [green screen
    compositing](https://gitlab.gnome.org/GNOME/pitivi/issues/966),
    [audio equalizer](https://gitlab.gnome.org/GNOME/pitivi/issues/1551)
62 63 64

## Advanced layer management

65
-   See [issue 930](https://gitlab.gnome.org/GNOME/pitivi/issues/930#note_68393)
66 67 68 69

## A better title editor

-   The current title editor UI is very simple. Please join us to make
70 71
    it work up to your expectations! See the existing [title editor
    issues](https://gitlab.gnome.org/GNOME/pitivi/issues?label_name%5B%5D=titles+editor).
72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93

## MAM/DAM

-   [Digital asset
    management](http://en.wikipedia.org/wiki/Digital_asset_management)
    is the ability to manage huge amounts of media (video clips, sounds,
    images, etc.). This feature is very much needed for professional
    editing; it allows handling multiple simultaneous camera angles,
    multiple takes of the same scene, multiple sound sources, etc.
-   Potentially being addressed by the Novacut team with
    [dmedia](https://launchpad.net/dmedia)

## Hardware-accelerated decoding and encoding

-   Since GStreamer 1.2, the basic infrastructure allowing us to cleanly
    take advantage of the video decoding capabilities of modern graphic
    cards is there. We need to ensure that our planned usecases are
    properly supported with the most common graphic drivers (through
    VA-API) and to make the integration work in Pitivi.

## Proxy editing

94 95
-   Status: [done](https://gitlab.gnome.org/GNOME/pitivi/issues/743) but
    the proxy experience can be better
96 97 98
-   See [proxy editing
    requirements](design/Proxy_editing_requirements.md) for the “spec”
    of how this feature should behave