[pitivi-web] Update style and include News
- From: Alexandru Băluț <alexbalut src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [pitivi-web] Update style and include News
- Date: Wed, 30 Jun 2021 00:15:32 +0000 (UTC)
commit e9d942457ad1d63960537ab8fbdf3514ec52a6f0
Author: Alexandru Băluț <alexandru balut gmail com>
Date: Wed Jun 30 02:13:03 2021 +0200
Update style and include News
README.md | 4 +-
_redirects | 12 +-
config.toml | 15 +-
content/contact.html | 18 +-
content/contribute.html | 25 +-
content/donators/index.html | 7 +-
content/download/index.html | 13 +-
.../news/2014-02-21-give-some-love-to-pitivi-2.md | 22 +
...5-votes-a-tool-of-engagement-and-development.md | 41 ++
...6-using-gstreamer-to-make-smooth-slow-motion.md | 14 +
...er-week-one-update-and-a-great-piece-of-news.md | 30 ++
...e-first-beta-release-of-pitivi-ra-is-a-happy.md | 16 +
...fundraiser-universal-daily-bundles-for-linux.md | 20 +
content/news/2014-06-23-june-development-update.md | 20 +
.../5fe97145-8637-1242-173c-bcfc039183e2.jpg | Bin 0 -> 200 bytes
.../656c04f9-95e1-8efd-388b-49ff99a5b9cd.jpg | Bin 0 -> 120 bytes
.../9824a9c6-f30c-71b6-5d6e-027573718f4c.jpg | Bin 0 -> 144 bytes
.../eb62d114-ba52-e102-1c71-f3f885184b3f.jpg | Bin 0 -> 43006 bytes
...owship-of-the-ring-gandalf-35160271-900-380.jpg | Bin 0 -> 47091 bytes
.../gtttrider6.jpg | Bin 0 -> 39275 bytes
.../image01.png | Bin 0 -> 154238 bytes
.../image03.png | Bin 0 -> 38857 bytes
.../image04.png | Bin 0 -> 88474 bytes
.../image06.png | Bin 0 -> 24813 bytes
.../image07.png | Bin 0 -> 7006 bytes
.../image08.png | Bin 0 -> 3625 bytes
.../image09.png | Bin 0 -> 32486 bytes
.../index.md | 112 +++++
...-18-get-pitivi-directly-from-us-with-flatpak.md | 23 +
.../news/2016-12-07-pitivi-0-98-getting-there.md | 39 ++
...ree-gsoc-students-hack-on-pitivi-this-summer.md | 18 +
.../news/2017-09-22-pitivi-0-99-ocean-big-chair.md | 22 +
.../news/2018-02-27-migrating-to-gnomes-gitlab.md | 12 +
.../index.md | 36 ++
.../video_settings2.jpg | Bin 0 -> 31043 bytes
...iting-services-applies-to-the-season-of-docs.md | 47 ++
...019-05-10-call-for-testing-the-pitivi-1-0-rc.md | 39 ++
...0-05-02-pitivi-applies-to-the-season-of-docs.md | 48 ++
...resenting-our-google-summer-of-code-students.md | 17 +
.../news/2020-10-11-pitivi-2020-09-hocus-focus.md | 112 +++++
content/news/_index.md | 3 +
content/showcase.html | 12 +-
content/tour.html | 29 +-
layouts/_default/list.html | 15 +-
layouts/_default/single.html | 1 +
layouts/index.html | 54 ++-
layouts/partials/footer.html | 22 +-
layouts/partials/head.html | 6 +-
layouts/partials/header.html | 12 +-
layouts/partials/metadata.html | 18 +-
static/.htaccess | 12 -
static/css/pitivi.css | 499 ++++++---------------
static/i/accordion_toggle.jpg | Bin 1412 -> 0 bytes
static/i/accordion_toggle_active.jpg | Bin 1416 -> 0 bytes
static/i/h_accordion_toggle.jpg | Bin 1488 -> 0 bytes
static/i/h_accordion_toggle_active.jpg | Bin 1481 -> 0 bytes
static/i/header-radial-bg.svg | 429 ------------------
static/i/screenshots/2020.05.png | Bin 0 -> 343320 bytes
static/i/seasonofdocs_logo_secondarygrey.png | Bin 0 -> 21357 bytes
static/i/webicon-facebook.svg | 14 -
static/i/webicon-git.svg | 22 -
static/i/webicon-rss.svg | 18 -
static/i/webicon-twitter.svg | 24 -
static/planet/atom.xml | 26 +-
static/planet/feeds.html | 27 +-
static/planet/index.html | 24 +-
66 files changed, 998 insertions(+), 1051 deletions(-)
---
diff --git a/README.md b/README.md
index 1e76f37..051eb20 100644
--- a/README.md
+++ b/README.md
@@ -32,8 +32,8 @@ The tree below gives a picture of the [directory structure].
│ │ ├── footer.html # The bottom of the pages
│ │ ├── head.html # The <head> of the pages
│ │ └── header.html # The top of the pages
- │ ├── shortcodes # Something small easy to include in other pages
- │ │ └── donation_notice.html
+ │ ├── shortcodes # Small parts ready to include in any page
+ │ │ └── videos_site.html
│ └── index.html # The content of the top page
├── static # Static content
│ ├── i # Stuff
diff --git a/_redirects b/_redirects
index 8de06e4..80a76cf 100644
--- a/_redirects
+++ b/_redirects
@@ -1,7 +1,7 @@
# https://docs.gitlab.com/ee/user/project/pages/redirects.html
-/?go=contact /contact/ 301
-/?go=contributing /contributing/ 301
-/?go=donators /donators/ 301
-/?go=download /download/ 301
-/?go=showcase /showcase/ 301
-/?go=tour /tour/ 301
+/Infrastructure/pitivi-web/?go=contact /Infrastructure/pitivi-web/contact/ 301
+/Infrastructure/pitivi-web/?go=contributing /Infrastructure/pitivi-web/contribute/ 301
+/Infrastructure/pitivi-web/?go=donators /Infrastructure/pitivi-web/donators/ 301
+/Infrastructure/pitivi-web/?go=download /Infrastructure/pitivi-web/download/ 301
+/Infrastructure/pitivi-web/?go=showcase /Infrastructure/pitivi-web/showcase/ 301
+/Infrastructure/pitivi-web/?go=tour /Infrastructure/pitivi-web/tour/ 301
diff --git a/config.toml b/config.toml
index aaf2e22..def5b1b 100644
--- a/config.toml
+++ b/config.toml
@@ -1,19 +1,12 @@
baseURL = "https://www.pitivi.org/";
languageCode = "en-us"
+[params]
+ gitlab = "https://gitlab.gnome.org/Infrastructure/pitivi-web";
+
[menu]
[[menu.main]]
- name = "Tour"
- url = "/tour/"
- title = "See why Pitivi is so popular"
- weight = 1
- [[menu.main]]
- name = "Showcase"
- url = "/showcase/"
- title = "Watch some of our conference presentations, demos, or watch movies that have been made with
Pitivi"
- weight = 2
- [[menu.main]]
- name = "Get it"
+ name = "Get it!"
url = "/download/"
title = "Learn how to get or build Pitivi"
weight = 3
diff --git a/content/contact.html b/content/contact.html
index 7a214fe..f11d565 100644
--- a/content/contact.html
+++ b/content/contact.html
@@ -1,11 +1,13 @@
---
title: "Contact"
-date: 2021-06-11T23:04:08+02:00
---
-<section class="auto-column-third">
+<section class="auto-column-half">
+ <h1>Reporting problems</h1>
+ <p>We track enhancement requests and bug reports in GitLab. Our bug tracker is well-organized and issues
are investigated systematically. See our <a href="https://developer.pitivi.org/Bug_reporting.html";>bug
reporting</a> info page for useful links and details.</p>
+
<h1>Chatting</h1>
- <p>Grab a <a href="https://matrix.org/clients/";>Matrix client</a> and join the room
<b>#pitivi:matrix.org</b>. Our Matrix room keeps the history of the messages, so if you lose the connection
you can see the entire conversation when you reconnect.</p>
+ <p>You can find us in the our Matrix room at <a
href="https://matrix.to/#/#pitivi:matrix.org";>#pitivi:matrix.org</a>. Our Matrix room keeps the history of
the messages, so if you lose the connection you can see the entire conversation when you reconnect.</p>
<p>For those still attached to their IRC clients, connect to <a href="https://oftc.net/";>OFTC</a> and
join the channel <b>#pitivi</b>. The channel is bridged to the Matrix room. The IRC channel should be used as
a last resort, most of us are in the Matix room.</p>
@@ -15,15 +17,9 @@ date: 2021-06-11T23:04:08+02:00
</section>
-<section class="auto-column-third">
- <h1>Reporting problems</h1>
- <p>We track enhancement requests and bug reports in GitLab. Our bug tracker is well-organized and issues
are investigated systematically. See our <a href="https://developer.pitivi.org/Bug_reporting.html";>bug
reporting</a> info page for useful links and details.</p>
-</section>
-
-
-<section class="auto-column-third" style="min-width: 450px; /* hack to force column wrapping in order to
prevent horizontal scrolling due to the Google calendar, but this is still error-prone */">
+<section class="auto-column-half">
<h1>At a public event</h1>
<p>We attend various conferences and hackfests. To know where and when you might be able to meet us in
person, follow us on <a href="https://www.pitivi.org/planet/";>Pitivi planet</a>, <a
href="https://twitter.com/pitivi";>on Twitter</a>, or take a look at our public calendar below:</p>
- <iframe
src="https://www.google.com/calendar/embed?showTitle=0&showPrint=0&showCalendars=0&height=300&wkst=1&bgcolor=%23FFFFFF&src=m4r5pf5da7c8kdba1cjq2d3jb4%40group.calendar.google.com&color=%23AB8B00&";
style=" border-width:0 " width="450" height="300" frameborder="0" scrolling="no"></iframe>
+ <iframe
src="https://www.google.com/calendar/embed?showTitle=0&showPrint=0&showCalendars=0&height=300&wkst=1&bgcolor=%23FFFFFF&src=m4r5pf5da7c8kdba1cjq2d3jb4%40group.calendar.google.com&color=%23AB8B00&";
style=" border-width:0 " width="440" height="300" frameborder="0" scrolling="no"></iframe>
</section>
\ No newline at end of file
diff --git a/content/contribute.html b/content/contribute.html
index 4b51bfb..ba01488 100644
--- a/content/contribute.html
+++ b/content/contribute.html
@@ -1,6 +1,5 @@
---
title: "Contributing"
-date: 2021-06-13T21:43:56+02:00
---
<section class="centered-introduction">
@@ -11,10 +10,10 @@ date: 2021-06-13T21:43:56+02:00
</div>
<ul>
- <li>COMMUNITY — Pitivi is an <b>active project</b> used by thousands of people and developed
<b>100% in the open</b> by <a href="https://www.openhub.net/p/pitivi/contributors";><b>many</b>
contributors</a>. We offer <b>excellent mentorship</b> for GSoC students or anyone interested in getting
involved seriously.</li>
- <li>TECHNOLOGY — Pitivi is written in Python, which makes frontend development fun and easy.
We use the brilliant <a href="https://en.wikipedia.org/wiki/GStreamer";>GStreamer</a> multimedia framework,
through which we also benefit from improvements in other libraries like FFmpeg/libav, frei0r and many
others.</li>
- <li>BEING GOOD CITIZENS — The multimedia community loves us because we push the boundaries of
what can be accomplished with GStreamer, and we stay true to the "upstream first" approach: we fix problems
directly in the projects we depend on, instead of piling up nasty hacks in our application.</li>
- <li>EXPERTISE — We're an <b>established project</b> with deep expertise that younger projects
do not have, and <b>we are here to stay</b>. Don't make the mistake of "reinventing the wheel" like <a
href="/i/history.png">countless others</a>.</li>
+ <li>COMMUNITY — Pitivi is an <b>active project</b> used by thousands of people and developed <b>100% in
the open</b> by <a href="https://www.openhub.net/p/pitivi/contributors";><b>many</b> contributors</a>. We
offer <b>excellent mentorship</b> for GSoC students or anyone interested in getting involved seriously.</li>
+ <li>TECHNOLOGY — Pitivi is written in Python, which makes frontend development fun and easy. We use the
brilliant <a href="https://en.wikipedia.org/wiki/GStreamer";>GStreamer</a> multimedia framework, through which
we also benefit from improvements in other libraries like FFmpeg/libav, frei0r and many others.</li>
+ <li>BEING GOOD CITIZENS — The multimedia community loves us because we push the boundaries of what can
be accomplished with GStreamer, and we stay true to the "upstream first" approach: we fix problems directly
in the projects we depend on, instead of piling up nasty hacks in our application.</li>
+ <li>EXPERTISE — We're an <b>established project</b> with deep expertise that younger projects do not
have, and <b>we are here to stay</b>. Don't make the mistake of "reinventing the wheel" like <a
href="/i/history.png">countless others</a>.</li>
</ul>
</section>
@@ -35,17 +34,12 @@ date: 2021-06-13T21:43:56+02:00
<li>Proceed to fix the issue according to our <a
href="https://developer.pitivi.org/Development_workflow.html";>Development Workflow</a>.</li>
</ol>
-<p>See <a href="https://developer.pitivi.org";>our documentation for contributors</a> in case you have a
question.</p>
+<p>See our <a href="https://developer.pitivi.org";>documentation for contributors</a> in case you have a
question.</p>
<p>Most importantly, come <a href="/contact/">hang out with us</a> in our Matrix room. We'll be happy to
help.</p>
-
-<h2>Testing & Reporting bugs</h2>
-<p>We use GitLab to track enhancement requests and bug reports. Our bug tracker is well-organized and issues
are investigated systematically. See our <a href="https://developer.pitivi.org/Bug_reporting.html";>bug
reporting</a> info page for useful links and details.</p>
-<p>Quality releases require regular testers! So please <a href="/download/">download</a> our latest daily
build and report any issues you encounter.</p>
</section>
-
<section class="auto-column-half">
<h2>Spreading the word</h2>
<p>Keeping people informed of the progress we're making is the resposibility of our PR department. If you
love explaining and storytelling, you could help in many ways: writing blog posts, preparing announcements
and release notes, making videos, etc.</p>
@@ -53,12 +47,11 @@ date: 2021-06-13T21:43:56+02:00
<h2>Improving the user manual</h2>
<p>We use <a href="http://projectmallard.org/";>Mallard</a> to provide a high-quality, topic-oriented <a
href="/manual/">user manual</a> bundled with the application. Help us by writing new topics, refining
existing ones, or simply by reviewing and keeping the user manual up-to-date and ready for the next
release.</p>
-<h2>Maintaining the contributors' documentation</h2>
-<p><a href="https://developer.pitivi.org";>Our documentation for contributors</a> has many pages that need to
be updated, cleaned or made obsolete. Having an up-to-date and consistent set of documentation for
contributors is important. Of course, we will provide guidance and help you towards this glorious goal.</p>
-
<h2>Translating</h2>
<p>Translations are kindly handled by dedicated translation teams from the GNOME community. To be able to
commit translations to Pitivi in an organized fashion, you must join the <a
href="https://wiki.gnome.org/TranslationProject";>GNOME translation</a> team for your native language.
-<h2>Donations</h2>
-{{< donation_notice >}}
+
+<h2>Testing & Reporting bugs</h2>
+<p>We use GitLab to track enhancement requests and bug reports. Our bug tracker is well-organized and issues
are investigated systematically. See our <a href="https://developer.pitivi.org/Bug_reporting.html";>bug
reporting</a> info page for useful links and details.</p>
+<p>Quality releases require regular testers! So please <a href="/download/">download</a> our latest daily
build and report any issues you encounter.</p>
</section>
diff --git a/content/donators/index.html b/content/donators/index.html
index 9b5f492..043a01c 100644
--- a/content/donators/index.html
+++ b/content/donators/index.html
@@ -1,17 +1,16 @@
---
title: "Donators"
-date: 2021-06-14T02:09:33+02:00
---
<section class="centered-introduction">
- <p>Pitivi is a community-run project. One of the things we value the most is our community of
contributors (wanna <a href="/contribute/">join us</a>?). For us, time is usually more precious and scarce
than money.</p>
+ <p>Pitivi is a community-run project. One of the things we value the most is our community of
contributors (<a href="/contribute/">join us!</a>). For us, time is usually more precious and scarce than
money.</p>
<p>Nevertheless, if you still want to contribute financially to the project, you can do so here.</p>
</section>
<section class="auto-column-half">
- <h1>I want to donate as an individual</h1>
- <a href="https://liberapay.com/Pitivi/";>
+ <a href="https://liberapay.com/Pitivi/"; class="discreet hidden">
+ <h1>I want to donate as an individual</h1>
<img src="shut-up-and-take-my-money.png" style="width:auto;" alt="donation motivational" />
</a>
<p>You can support us <a href="https://liberapay.com/Pitivi/";>through Liberapay</a>, a Free/libre and
ethical donation system owned by a non-profit organization based in France. Currently, for simplicity,
Liberapay donations are handled by <a href="https://developer.pitivi.org/The_people.html";>Alexandru</a>.</p>
diff --git a/content/download/index.html b/content/download/index.html
index 348cd91..6189c83 100644
--- a/content/download/index.html
+++ b/content/download/index.html
@@ -1,6 +1,5 @@
---
title: "Download"
-date: 2021-06-14T00:42:14+02:00
---
<section class="centered-introduction">
@@ -11,18 +10,16 @@ date: 2021-06-14T00:42:14+02:00
</section>
<section class="auto-column-half">
- <h1 style="text-align: center;">Pre-built, distro-agnostic packages</h1>
- <a href="https://flathub.org/apps/details/org.pitivi.Pitivi";>
- <img src="flatpak.png" alt="Flatpak package icon" class="centered-image" />
+ <a href="https://flathub.org/apps/details/org.pitivi.Pitivi"; class="hidden">
+ <h1 style="text-align: center;">Pre-built, distro-agnostic packages<img src="flatpak.png"
alt="Flatpak package icon" class="centered-image" /></h1>
</a>
<p>In order to eliminate dependency problems we provide a convenient package using Flatpak. The flatpak
package can be installed with minimal effort and is updated as soon as we release new versions.</p>
<p>Please <a href="https://flathub.org/apps/details/org.pitivi.Pitivi";>install Pitivi from
Flathub</a>.</p>
</section>
-<section class="auto-column-half">
- <h1 style="text-align: center;">Development version</h1>
- <a href="https://developer.pitivi.org/Install_with_flatpak.html";>
- <img src="applications-development.png" alt="dev icon" class="centered-image" />
+<section class="auto-column-half not_first">
+ <a href="https://developer.pitivi.org/Install_with_flatpak.html"; class="hidden">
+ <h1 style="text-align: center;">Development version<img src="applications-development.png" alt="dev
icon" class="centered-image" /></h1>
</a>
<p>For testing purposes, the <b>development version</b> can be <a
href="https://developer.pitivi.org/Install_with_flatpak.html";>installed using flatpak</a>.</p>
diff --git a/content/news/2014-02-21-give-some-love-to-pitivi-2.md
b/content/news/2014-02-21-give-some-love-to-pitivi-2.md
new file mode 100644
index 0000000..96276c6
--- /dev/null
+++ b/content/news/2014-02-21-give-some-love-to-pitivi-2.md
@@ -0,0 +1,22 @@
+---
+title: 'Give some love to Pitivi !'
+date: Fri, 21 Feb 2014 21:30:00 +0000
+tags:
+ - Fundraiser
+---
+
+Today we're thrilled to announce a [crowdfunding](http://fundraiser.pitivi.org/) campaign to support the
development of Pitivi!
+
+We have made the choice not to use one of the major crowdfunding platforms such as kickstarter for [multiple
reasons](http://fundraiser.pitivi.org/faq), and instead partner with the [GNOME
foundation](http://www.gnome.org/foundation/), which is ideologically aligned with us and will support our
financial infrastructure.
+
+We are proud of that partnership, as we share their objective of "creating a free software computing
platform for the general public", and the foundation is excited as well:
+
+> "GNOME is proud to host the Pitivi campaign. Pitivi fills a real need for stable and approachable high
quality video editing. Its software architecture and UI design share the same sleek and forward-thinking
approach that we value in the GNOME project." — _Karen Sandler, executive director of the GNOME Foundation_
+
+With that campaign, our aim is to provide everyone with a rock-solid Free Software video editor, based on
the awesome technology that is GStreamer. We have spent a lot of time working on the campaign website, and it
holds a lot more content than a simple blogpost could.
+
+We know that what we want to do is the right thing, and requesting money for quality and stabilization first
is the correct and honest thing to do. We obviously encourage you to
[donate](http://fundraiser.pitivi.org/donate) to the campaign, but we also hope that you will be willing to
spread the message, and explain why what we do is important and good.
+
+Free and Open Source video editing is something that can help make the world a better place, as it gives
people all around the world one more tool to express themselves creatively, fight oppression, create
happiness and spread love.
+
+Hoping you'll spread the love too, thanks for reading!
\ No newline at end of file
diff --git a/content/news/2014-02-25-votes-a-tool-of-engagement-and-development.md
b/content/news/2014-02-25-votes-a-tool-of-engagement-and-development.md
new file mode 100644
index 0000000..4af2f20
--- /dev/null
+++ b/content/news/2014-02-25-votes-a-tool-of-engagement-and-development.md
@@ -0,0 +1,41 @@
+---
+title: 'Votes: a tool of engagement and development.'
+date: Tue, 25 Feb 2014 21:29:00 +0000
+tags:
+ - Fundraiser
+---
+
+During the creation of the [campaign](http://fundraiser.pitivi.org/), we debated what kind of perks we
should offer. The thing is, we are not t-shirt creators, we are software developers and UI designers.
+
+We believe people who give us money do so in order for us to develop a **good software**, and thus we tried
to focus on perks that made real sense. What could we offer to the community that would help us in making the
software that they truly want? Our answer to that question: _a voice_, simple as that.
+
+Though we already have a very active community and listen to feedback from our users, we were missing a way
to quantify the priority of feature requests for the people to whom our software matters enough to sponsor
our work.
+
+We decided on two types of perks we would offer: invitations to hangouts organized monthly (we'll tell you
more about that in a future post), and the subject of today's post, our voting system!
+
+We wanted to grant the possibility of voting to anyone who donated, from the lowest amount available, and
decided to weigh the vote proportionally to the amount given, with steps at which the curve flattens a bit,
to make sure people who can't donate 300 euros still have a reasonable chance to have their voice heard.
+
+Later I'll post implementation details for those interested, on my personal blog. Suffice to say that it
works, and more exciting that people are already making good use of it!
+
+This brings me to the exciting news we want to share: we made the current vote results public! Obviously, as
we're in the early stages of the campaign, they're not nearly as significant as they will be later, but we
think it's already interesting data, and you can have a look at them live right
[now](http://fundraiser.pitivi.org/vote/results/).
+
+Now to our own analysis of the data so far:
+
+The first exciting figure for us is that even though we're not yet guaranteed to reach a funding point that
can put vote results into development (you can help us get there
[faster](http://fundraiser.pitivi.org/donate)), one third of our backers already took the time to go through
the form and rate features on the 0 to 10 scale, and we clearly expect that ratio to grow if we reach the
35,000 bar.
+
+We interpret that as a sign that our voting system answers a real demand. This figure is a clear success in
our effort to create sustainable community engagement to support responsive and dynamic Pitivi development,
alongside the growing number of people who choose to put their faith in us and donate.
+
+Some points in the feature ranking results caught our attention:
+
+* The clear first place of hardware accelerated decoding and encoding. This is really interesting to the
engineers among us, who already salivate at the possible prospect of implementing it!It also goes to show
that performance is critical to people using video editing software, and reassures us in our architectural
choices: the decision to ally with GStreamer means a lot of the heavy lifting is done as part of a partner
project that doesn't have to be written by Pitivi developers from scratch. Instead, we contribute to
GStreamer while also reaping the huge benefits of it -- and that means we can focus better on the video
editing side of our code (making sure dynamic pipelines work with hardware-accelerated decoders/encoders,
adapting and extending our integration test suites to ensure it keeps on being true)
+* The very pragmatic second place of copy paste, a small but oh-so-helpful feature, which goes to show
that our backers are sensible, productivity and detail-oriented people.
+* The low ranking of Windows and Mac ports, which is certainly due in part to the fact that awareness
about our campaign is pretty much limited to the Free Software community for now.
+* Finally, something we don't really know how to interpret on the spot, but that is interesting to remark
nevertheless is that the three last spots are occupied at the time of writing by external project formatters,
such as Final Cut projects.
+
+I'll repeat that these rankings are absolutely not definitive, as already existing backers can change their
votes and new backers should hopefully continue to give their opinion on what matters to them.
+
+The conclusion is: "Don't like these rankings ? [Donate](http://fundraiser.pitivi.org/donate) and you can
contribute in changing them!"
+
+We're really interested in your analysis of these early results, and hoping that discussion will occur about
them in the comments section or on our IRC channel (#pitivi on freenode)!
+
+Thanks for reading, the Pitivi team
\ No newline at end of file
diff --git a/content/news/2014-02-26-using-gstreamer-to-make-smooth-slow-motion.md
b/content/news/2014-02-26-using-gstreamer-to-make-smooth-slow-motion.md
new file mode 100644
index 0000000..eaf18b6
--- /dev/null
+++ b/content/news/2014-02-26-using-gstreamer-to-make-smooth-slow-motion.md
@@ -0,0 +1,14 @@
+---
+title: 'Using GStreamer to make smooth slow motion!'
+date: Wed, 26 Feb 2014 21:29:00 +0000
+---
+
+This is a very good example of what our developers can do! There has been some preliminary work on bringing
slow and fast motion to GStreamer and Pitivi, and a plugin has been created to allow for frame interpolation,
which means you and I with our regular 24 frames per second cameras will be able to get **smooth slowmotion**
from Pitivi in the future!
+
+All that work has not yet been merged and thoroughly tested, and we need your
[help](http://fundraiser.pitivi.org/donate) to make it happen!
+
+To help you understand the difference between regular and smooth slowmotion, here is a video showing both
types side by side, created by Alexandre Prokoudine. The difference is quite stunning!
+
+Thanks to [Alexandre Prokoudine](http://vimeo.com/prokoudine) for the "Slowmo video effect with GStreamer"
video below:
+
+{{< vimeo 76288762 >}}
diff --git a/content/news/2014-03-03-pitivi-fundraiser-week-one-update-and-a-great-piece-of-news.md
b/content/news/2014-03-03-pitivi-fundraiser-week-one-update-and-a-great-piece-of-news.md
new file mode 100644
index 0000000..92db4fc
--- /dev/null
+++ b/content/news/2014-03-03-pitivi-fundraiser-week-one-update-and-a-great-piece-of-news.md
@@ -0,0 +1,30 @@
+---
+title: 'Pitivi Fundraiser Week One Update (And A Great Piece Of News)'
+date: Mon, 03 Mar 2014 21:28:00 +0000
+tags:
+ - Fundraiser
+---
+
+**Greetings Pitivi supporters!**
+================================
+
+We hope everyone had a great week! We've had a rather hectic one, and hopefully that's just the beginning.
This is the first update for our fundraising [campaign](http://fundraiser.pitivi.org/), be sure to check our
blog weekly for more ;)
+
+Announcement!
+-------------
+
+We are happy to announce that the GStreamer maintainers decided to show us their faith and support, by
allocating 2 500 € to our project from GStreamer funds! This is great news for several reasons:
+
+* It's obviously nice to get such an amount of money as it represents **seven percent** of the total
needed to get a 1.0 release or, to put it another way, **three weeks** of full time development!
+* GStreamer is the central component of our architecture, and it is the one on which we plan to spend most
of our time during the push to 1.0. Pitivi really is just the tip of the iceberg, to put things in
perspective, it now only is a mere 25,000 lines of Python code, whereas GStreamer and its plugins represent
around 1.5 _million_ lines of code.Our work really benefits every other project that uses GStreamer (for
example, accurate seeking in ogg files? That was [us](https://bugzilla.gnome.org/show_bug.cgi?id=700537)!),
and it is meaningful to see the GStreamer maintainers acknowledge that "officially", many thanks to them! And
then many more for the road. They're awesome and a big reason why we love working on Pitivi.
+* We really hope this donation will help everyone that cares about Open Source, be they individuals
craving for flawless multimedia handling on Linux or companies interested in building products around
GStreamer, to see that we are an integral part of the community, and that donating to the campaign is not
only about getting a great video editor, but also about improving the core multimedia engine shared by most
if not all the Linux distributions!
+
+Acknowledgement!
+----------------
+
+We would like to thank each and everyone of the 350+ backers that already donated to the campaign and helped
us break the 10 000 euros bar during this last week. 11 000 € is a great amount of money, sufficient to cover
our expenses for **three months** of full-time development! With your help, we already made it to a third of
our first goal, and with your help we can make it to Pitivi 1.0 and beyond. Anything helps, be it blogging,
tweeting and sharing on social networks, or getting the word out to journalists. DistroWatch also decided to
make [us](http://distrowatch.com/weekly.php?issue=20140303#donation) the recipient of their monthly donation,
and granted us 280 euros, it's a great honor for us to be listed among the previous recipients of that
donation!
+
+Appetizement!
+-------------
+
+The dictionary doesn't seem to agree that this word should exist, but it's here nevertheless. Next week
should see an interesting announcement for all the fans of Python, Romania and clean code, make sure to stay
tuned on our [twitter](https://twitter.com/Pitivi) or to add this blog to your RSS feeds ;)
\ No newline at end of file
diff --git a/content/news/2014-03-21-gstreamer-hackfest-and-the-first-beta-release-of-pitivi-ra-is-a-happy.md
b/content/news/2014-03-21-gstreamer-hackfest-and-the-first-beta-release-of-pitivi-ra-is-a-happy.md
new file mode 100644
index 0000000..d33a064
--- /dev/null
+++ b/content/news/2014-03-21-gstreamer-hackfest-and-the-first-beta-release-of-pitivi-ra-is-a-happy.md
@@ -0,0 +1,16 @@
+---
+title: 'GStreamer Hackfest and the first Beta release of Pitivi, "Ra is a happy"'
+date: Fri, 21 Mar 2014 21:27:00 +0000
+tags:
+ - Release
+---
+
+Last week-end, part of the Pitivi Team went to the GStreamer Hackfest in Google's offices in Munich to work
with twenty other GStreamer hackers on various important technical issues. A big thanks to Google and Stefan
Sauer for hosting the event! Keep your eyes peeled: we will soon blog the results of the work the Pitivi team
has accomplished during the hackfest.
+
+During the hackfest a very important milestone has been reached: the first [GStreamer Editing
Services](http://gstreamer.freedesktop.org/releases/gst-editing-services/1.2.0.html),
[GNonLin](http://gstreamer.freedesktop.org/releases/gnonlin/1.2.0.html) and
[gst-python](http://gstreamer.freedesktop.org/releases/gst-python/1.2.0.html) stable versions in the 1.X
branch have been released. That means that these very central components of the Pitivi project are now
considered stable.
+
+While this backend work was essential to the [beta release](http://wiki.pitivi.org/wiki/0.93), we also want
to specifically thank Alexandru Balut for his impressive involvement during the 0.92 -> 0.93 cycle. He
provided an impressive amount of bug fixing and cleanup patches in Pitivi itself, and has greatly helped the
project reach a beta state. Any inquiries regarding the 0.93 release codename must be sent in his general
direction.
+
+This release will be the basis on which we will start our work for our ongoing
[fundraiser](http://fundraiser.pitivi.org/). We've done that work in our spare time, and we're excited about
what we'll be able to accomplish once we start working full time! Thibault Saunier has already been preparing
bundles for the release, more on that in the next post!
+
+Once again, you can [help](http://fundraiser.pitivi.org/donate) us in producing a rock solid stable release,
by donating and spreading the message!
\ No newline at end of file
diff --git
a/content/news/2014-04-14-first-delivery-of-the-pitivi-fundraiser-universal-daily-bundles-for-linux.md
b/content/news/2014-04-14-first-delivery-of-the-pitivi-fundraiser-universal-daily-bundles-for-linux.md
new file mode 100644
index 0000000..4b6107a
--- /dev/null
+++ b/content/news/2014-04-14-first-delivery-of-the-pitivi-fundraiser-universal-daily-bundles-for-linux.md
@@ -0,0 +1,20 @@
+---
+title: 'First delivery of the Pitivi fundraiser: universal daily bundles for Linux'
+date: Mon, 14 Apr 2014 21:26:00 +0000
+tags:
+ - Fundraiser
+---
+
+The Pitivi community is very happy to announce the availability of easy to use, distro-independent Linux
bundles to test latest version of the application. This eliminates dependency problems and allows quicker
testing cycles. Our entire [stack](https://developer.pitivi.org/Architecture.html) is bundled, so the only
requirement is glibc ≥ 2.13.
+
+Simply [Download the bundle](http://fundraiser.pitivi.org/download-bundles) and run it!
+
+This is the first delivery of the Pitivi Fundraiser—as you can see, we are already well on our way to
deliver what has been promised in our [detailed planning](http://fundraiser.pitivi.org/the-plan). You can
have a look at what is happening with the "daily build" bundles on [on our Jenkins
instance](https://jenkins.arracacha.collabora.co.uk/view/pitivi/job/pitivi-bundling/) (main server hosting
donated by Collabora—thanks!).
+
+To build the bundles we use
[Cerbero](http://docs.gstreamer.com/display/GstSDK/Multiplatform+deployment+using+Cerbero), which is the
build and packaging system used by Collabora and Fluendo to construct the [GStreamer
SDK](https://gstreamer.freedesktop.org/), and is also used by the GStreamer community to deliver [GStreamer
1.x binaries for Android, iOS, Mac OS X and Windows](https://gstreamer.freedesktop.org/data/pkg/). It is a
very useful and well-designed technology, which will allow us to easily create packages for Windows and Mac
OS X in the future.
+
+This does not only apply to us, of course: work that has been made for creating Linux distro bundles allows
anyone to easily create bundles for their applications with Cerbero. This has not been merged just yet, but
that should happen quite soon. If you want to bundle your app using Cerbero, do not hesitate to ask us, even
if it should already be **really** straight forward!
+
+We raised half of the amount we are targeting for the Pitivi fundraising campaign, and we are in very good
shape to be able to deliver everything on time. We need your help to reach that target.
+
+Please [donate now](http://fundraiser.pitivi.org/donate) to make sure we will be able to provide the
community with the great video editing app it deserves!
\ No newline at end of file
diff --git a/content/news/2014-06-23-june-development-update.md
b/content/news/2014-06-23-june-development-update.md
new file mode 100644
index 0000000..cdb3286
--- /dev/null
+++ b/content/news/2014-06-23-june-development-update.md
@@ -0,0 +1,20 @@
+---
+title: 'June 2014 development update'
+date: Mon, 23 Jun 2014 21:24:00 +0000
+---
+
+Good news everyone !
+
+This is the first blog post of a series of updates about our latest development efforts in GStreamer /
gst-editing-services / Pitivi.
+
+This post's focus will be on [MPEG transport stream](http://en.wikipedia.org/wiki/MPEG_transport_stream), a
format now nearly twenty years old, originally developed and still widely used for and by the broadcasting
industry. In the mid-2000s, [some people](http://www.avchd-info.org/) decided it would be a great idea to use
this format in camcorders, stuffed a rather useless timestamp in there for good measure and started to ship
AVCHD camcorders like it was the greatest thing since sliced bread.
+
+It was not. See, most modern video codecs such as h264 rely on the notion of keyframes: to compress video
streams as much as possible, most frames are encoded as their difference with the previous frame, we call
these frames delta units. Sparsely distributed in the encoded stream are keyframes. These frames can be
decoded without any reference to past frames, and when trying to seek in such a stream, decoding has to start
from a keyframe and progress through all the delta units up to the requested frame.
+
+Video editing implies accurate seeking, for example if you only want to include the 10 last frames of a
2-hour clip, decoding the whole file to obtain these few frames would be a pointless waste of time.
+
+Failing to start decoding from a keyframe when seeking creates artefacts, garbled frames : the decoder is
missing information to decode the delta unit, tries to provide a frame nevertheless and fails in doing so,
until the next keyframe has been reached. Containers that are readily usable for editing contain information
about the location of keyframes, in one form or another. This is not the case of MPEG TS, of which AVCHD is a
subset. Locating the keyframes thus becomes a rather involved process, as one needs to parse the video
streams in order to do so.
+
+Backtracking to the introduction of this post, good news everyone ! We just [did
that](https://bugzilla.gnome.org/show_bug.cgi?id=675132), and here is a before / after video to demonstrate
our changes. We can now ensure full support of AVCHD, enjoy :D
+
+The next two posts will be respectively focused on our refactoring of our video / audio mixing stack, and
our ongoing work on gnonlin, our non-linear editing engine.
\ No newline at end of file
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/5fe97145-8637-1242-173c-bcfc039183e2.jpg
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/5fe97145-8637-1242-173c-bcfc039183e2.jpg
new file mode 100644
index 0000000..d198de9
Binary files /dev/null and
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/5fe97145-8637-1242-173c-bcfc039183e2.jpg differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/656c04f9-95e1-8efd-388b-49ff99a5b9cd.jpg
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/656c04f9-95e1-8efd-388b-49ff99a5b9cd.jpg
new file mode 100644
index 0000000..aef872e
Binary files /dev/null and
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/656c04f9-95e1-8efd-388b-49ff99a5b9cd.jpg differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/9824a9c6-f30c-71b6-5d6e-027573718f4c.jpg
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/9824a9c6-f30c-71b6-5d6e-027573718f4c.jpg
new file mode 100644
index 0000000..c4539c1
Binary files /dev/null and
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/9824a9c6-f30c-71b6-5d6e-027573718f4c.jpg differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/eb62d114-ba52-e102-1c71-f3f885184b3f.jpg
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/eb62d114-ba52-e102-1c71-f3f885184b3f.jpg
new file mode 100644
index 0000000..375e9c1
Binary files /dev/null and
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/eb62d114-ba52-e102-1c71-f3f885184b3f.jpg differ
diff --git
a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/gandalf-the-grey-fellowship-of-the-ring-gandalf-35160271-900-380.jpg
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/gandalf-the-grey-fellowship-of-the-ring-gandalf-35160271-900-380.jpg
new file mode 100644
index 0000000..c2143b7
Binary files /dev/null and
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/gandalf-the-grey-fellowship-of-the-ring-gandalf-35160271-900-380.jpg
differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/gtttrider6.jpg
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/gtttrider6.jpg
new file mode 100644
index 0000000..e3825bc
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/gtttrider6.jpg differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image01.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image01.png
new file mode 100644
index 0000000..a2aed16
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image01.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image03.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image03.png
new file mode 100644
index 0000000..a367f03
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image03.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image04.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image04.png
new file mode 100644
index 0000000..8813a32
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image04.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image06.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image06.png
new file mode 100644
index 0000000..748679b
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image06.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image07.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image07.png
new file mode 100644
index 0000000..c422e45
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image07.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image08.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image08.png
new file mode 100644
index 0000000..2937b57
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image08.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image09.png
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image09.png
new file mode 100644
index 0000000..6699b7c
Binary files /dev/null and b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/image09.png differ
diff --git a/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/index.md
b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/index.md
new file mode 100644
index 0000000..877792b
--- /dev/null
+++ b/content/news/2016-06-30-pitivi-0-96-cogito-ergo-proxy/index.md
@@ -0,0 +1,112 @@
+---
+title: 'Pitivi 0.96 — Cogito Ergo Proxy'
+date: Thu, 30 Jun 2016 22:02:32 +0000
+tags:
+ - Release
+---
+
+Besides the usual cleanup and bug squashing, this release brings a fundamental feature which greatly
improves the edit experience. Now you can edit and render a video project with any video files with great
accuracy, thanks to proxy files.
+
+Proxy editing: fast and accurate editing with any video format
+--------------------------------------------------------------
+
+The harsh reality of this world is that there is only a limited set of formats that really work well for
video editing. Without those, rendering a project could have been inaccurate at times\*. The user experience
degrades when using container formats not designed for fast & accurate seeking. For example, seeking a video
format where the keyframes are followed by one or more
[inter-frames](https://en.wikipedia.org/wiki/Inter_frame) (such as in VP8, H.264) is often slow.
+
+To provide the best experience, we decided to give you the ability to seamlessly work with media formats
suitable for video editing. This is accomplished with what we call “proxy” files. Other video editors
advertise the use of downscaled proxy files which, besides the improved reliability, also provide better
performance when the system is not powerful enough to handle high-quality video files in real-time. We do
not cover the the downscaled proxy files case yet—that’s [planned](http://fundraiser.pitivi.org/) for post
1.0. For now, our proxies are high-quality proxies intended to be used instead of the original, when editing
and also when rendering the project.
+
+Oh, and since we’re so smart, we now also generate the audio waveforms and filmstrip thumbnails at the same
time as we are processing proxies. Super efficient.
+
+So what is the difference between an original and its “proxy”? The proxy is a slightly degraded but
easier-to-work-with version of the original:
+
+
+
+
+
+Okay, okay, we might be stretching the analogy a little bit, but you get the picture.
+
+### When are proxies needed for stability?
+
+The whitelist below shows the formats we officially support—which can be used safely without proxying them.
For the rest, we recommend using proxy files to guard against bugs in the decoders and demuxers. Depending on
how popular other formats get, we will consider officially supporting them. The intention is to keep the list
short to avoid spending too much time on decoders and demuxers.
+
+At the moment, the whitelist is comprised of the following:
+
+* Containers: QuickTime, Ogg, Matroska, WebM
+* Video codecs: H.264, MJPEG, VP8, Theora, raw
+* Audio codecs: Opus, MP3, Vorbis, FLAC, raw
+
+### How does it work?
+
+When you import an asset with an unsupported format, it is by default transcoded using a codec suitable for
video editing. You can disable or force the proxy creation on a per-asset basis, when you import or later at
any time. Finally, when rendering, you can specify whether to use the proxies or the original files. You are
always in control.
+
+{{< figure src="image07.png" title="Options when importing files" >}}
+
+{{< figure src="eb62d114-ba52-e102-1c71-f3f885184b3f.jpg" title="Options for already imported video files"
}}
+
+{{< figure src="image08.png" title="Options when rendering a project" >}}
+
+As seen in the screenshots above, the state of an asset’s proxy is shown by an icon in the bottom-left
corner of the asset thumbnail, in the Media Library. The icon can be one of:
+
+* none The original is used.
+*  The proxy is being created by transcoding the asset.
+*  The proxy is ready and is used automatically.
+*  The proxy creation failed and the original is used.
+
+The main disadvantage of using the intermediate proxy files for rendering is that some quality is lost when
transcoding, but this is not noticeable in most cases. Other than that, transcoding the originals takes a bit
of time and they take some disk space (around 10 times more for H.264 content, for example). In practice, we
think that using proxy files is the best option. You decide what works for you but take into account what is
considered safe and officially supported, and what is not.
+
+It was very important to [pick](https://phabricator.freedesktop.org/T3405) a codec that preserves the visual
quality of the originals, so that final renders can be done out of the intermediate proxy files with no
perceived quality loss. The other requirement was that seeking should be fast, meaning it had to be an
[intra-frames](https://en.wikipedia.org/wiki/Intra-frame)\-only codec, where a frame is encoded and decoded
independently of any other frame. Currently Pitivi uses [MJPEG](https://en.wikipedia.org/wiki/Motion_JPEG) or
[ProRes](https://en.wikipedia.org/wiki/Apple_ProRes) for the proxy files, depending on which is available on
the system.
+
+For now, the audio is transcoded using [Opus](https://en.wikipedia.org/wiki/Opus_(audio_format)), even
though it’s a lossy format, because the codec is very good. We’ll most probably switch to
[FLAC](https://en.wikipedia.org/wiki/FLAC) when it will be more supported in GStreamer because it loses no
quality and has a pretty good compression ratio.
+
+Scrubbing the timeline easily
+-----------------------------
+
+Currently the user is able to select, move and edit clips by using the left mouse button. This is exactly
how a user expects to interact with a GTK UI and it works very well. In addition to that, when clicking using
the left mouse button, a seek is performed and the playhead is moved to that position. Some users were
annoyed by this combined behavior so we added an option for disabling seek on left-click, but this was not
enough.
+
+Inspired by Blender’s different functionality assignation for left and right mouse buttons, we added the
ability to seek by right-clicking. Now you can quickly and safely scrub on the timeline as well on the ruler
using the right mouse button. Since Pitivi did not provide a context menu when right-clicking on the
timeline, it was easy to make this possible. Try it out and let us know what you think. More details on the
reasoning that led to this are visible in [T3158](https://phabricator.freedesktop.org/T3158).
+
+Transformation box
+------------------
+
+The transformation box is back, thanks to Collabora and Lubosz Sarnecki! This is the third implementation of
the transformation box, first one being hacky and second one being available only for users with GL video
cards. Now it works great due to the almighty GtkSink, GStreamer’s latest GTK widget for displaying video.
+
+The new transformation box fits great with Pitivi by making clips selectable from the viewer, so you can
manage multiple overlapping clips quite easily. But the best part of this implementation may be its
extensibility, an example being the [module for the title clips](https://phabricator.freedesktop.org/D727).
+
+{{< figure src="image01.png" title="Transformation box around Alex's parents' cat's best friend" >}}
+
+Project settings: letting the computer figure things out
+--------------------------------------------------------
+
+At least one of our contributors felt intimidated when he first saw the project settings dialog which used
to show up when creating a new project. The project settings define how you preview the project while
editing. You might want for example to choose a small video size if your computer is not very powerful, then
at render time change that to get the best quality. These settings can be changed safely at any time.
+
+The question was whether showing that dialog is really necessary at that point in time. Well, not really.
Now, when you create a new project, some default values are set and then when you import the first video
file, its properties are transposed to the project settings.
+
+The logic is thus: either users don’t really care about the project settings and the “Project Settings”
dialog showing up when creating a new project overwhelms them, or the user is an experienced videographer, in
which case they'll know when they need to change the project settings and where to find them. A very nice
touch is that when the project settings are changed automatically, an infobar appears, so the user has the
chance of opening the project settings and correct them if need be. More details in
[T3161](https://phabricator.freedesktop.org/T3161).
+
+{{< figure src="image06.png" title="Infobar when the first clip is imported" >}}
+
+New project settings and rendering UI
+-------------------------------------
+
+The widgets in the project settings dialog and the rendering dialog were split into multiple tabs, to fit on
1024x768 screens. Unfortunately this required clicking the tabs to see or edit the settings. Moving the eye
is faster than clicking so we looked into this and came up with a solution to get rid of the tabs and keep
the dialogs as small as possible.
+
+The preset selection UI is now composed of a ComboBox plus a MenuButton. This way the preset selection UI
takes extra vertical space instead of extra horizontal space. We find it works pretty good. More details
about how it works and more screenshots in [this
doc](https://docs.google.com/document/d/1f4XS6H-fmESWDjj0vXeDWB3oF7DWyX25LxmxThO9z2g/edit#heading=h.bt5dzxi19d3f).
+
+{{< figure src="image09.png" title="The Project Settings dialog" >}}
+
+{{< figure src="image03.png" title="The Render dialog" >}}
+
+Keyboard shortcuts window
+-------------------------
+
+Jakub Brindza joined us as a GSoC student. The first step of his project is already done, a brand new
keyboard shortcuts window built dynamically, to be able to support custom shortcuts. Next will be allowing
users to customize the keyboard shortcuts.
+
+{{< figure src="image04.png" title="The Keyboard Shortcuts window" >}}
+
+Other noteworthy changes
+------------------------
+
+* The [user manual](https://www.pitivi.org/manual/) has been updated to reflect the changes since we
switched to the headerbar, about one year and a half ago.
+* The undo/redo removal has been undone.
+* We switched from AppImage to Flatpak to distribute our own builds. A big advantage is that due to
Flatpak’s sandboxing we can use it for the development environment while previously we needed a separate
complex script to take care of that.
+
+\* There was a very high chance of ending up with artifacts at the start of a clip with an inpoint.
\ No newline at end of file
diff --git a/content/news/2016-07-18-get-pitivi-directly-from-us-with-flatpak.md
b/content/news/2016-07-18-get-pitivi-directly-from-us-with-flatpak.md
new file mode 100644
index 0000000..c891799
--- /dev/null
+++ b/content/news/2016-07-18-get-pitivi-directly-from-us-with-flatpak.md
@@ -0,0 +1,23 @@
+---
+title: 'Get Pitivi directly from us with Flatpak'
+date: Mon, 18 Jul 2016 22:05:45 +0000
+---
+
+Distributing apps as packages (deb, rpm, etc) is problematic. For example, the Pitivi package depends on the
GTK package and Pitivi 0.95 [broke](https://bugs.archlinux.org/task/49301) in the distributions which updated
to GTK version 3.20, because of the incorrect way we were using a virtual method. This is not the first time
something like this happens. To avoid the slippery dependencies problem, two years ago we started making
[universal daily
builds](https://pitivi.wordpress.com/2014/04/14/first-delivery-of-the-pitivi-fundraiser-universal-daily-bundles-for-linux/).They
allowed everybody to run the latest Pitivi easily by downloading a large binary containing the app and all
the dependencies.
+
+A few problems still remained:
+
+* It was complicated to set up the Pitivi development environment. We had a huge script for setting up the
development environment and new contributors always had problems. We tried to reuse the daily builds for
preparing a development environment but it was hacky and we failed to make it work correctly.
+* Users were notified about available updates through a custom mechanism and updating was not ideal,
requiring to download a huge binary blob.
+* Maintaining the AppImageKit based bundle required following many dependencies (security) updates and
maintaining the build for them (even though we were sharing the burden with the whole GStreamer community, as
we were using the [Cerbero](https://cgit.freedesktop.org/gstreamer/cerbero/) build system).
+
+Recently [Flatpak](http://flatpak.org/) got our attention as it set out to fix these problems. Flatpak’s
sandboxing allowed us to create a nice development environment. Our new [dev env
script](https://git.gnome.org/browse/pitivi/tree/bin/pitivi-env) reuses [the one which flatpaks
Pitivi](https://git.gnome.org/browse/pitivi/tree/build/flatpak/pitivi-flatpak) so we [got rid of the old
ones](https://git.gnome.org/browse/pitivi/commit/bin?id=603f52aed54fa1d7100894ecd403776fe7e02cc6). Also,
Flatpak allows the user to only download binary diffs for updates. Moreover, the Gnome community already
provides builds for their SDK and Runtimes, which contains almost everything we need for Pitivi; now, we only
have to build a [few
libraries](https://phabricator.freedesktop.org/diffusion/PTV/browse/master/build/flatpak/pitivi.template.json;9dc539717e1ac04d159f9276d2990f82d57c6c25),
which makes it much simpler for us to maintain the new bundles.
+
+We're enthusiastic about Flatpak. Jakub Steiner
[summarized](http://jimmac.musichall.cz/blog/2016-05-23-year-of-the-linux-desktop/) Flatpak's advantages very
nicely:
+
+> Flatpak aims to solve the painful problem of the Linux distribution—the fact that the OS is intertwined
with the applications. It is a pain to decouple the two to be able to:
+>
+> * Keep a particular version of an app around (and working, our note), regardless of OS updates. Or vice
versa, be able to run an uptodate application on an older OS.
+> * Allow application authors distribute binaries they built themselves. Binaries they can support and
accept useful bug reports for. Binaries they can keep updated.
+
+For now you need to use the command line to [install Pitivi with
Flatpak](http://wiki.pitivi.org/wiki/Install_with_flatpak). In the near future, it should be trivial for you
to install and manage our Flatpak build of Pitivi in your favorite software manager. GNOME Software is a
[good example](https://blogs.gnome.org/hughsie/2016/07/05/flatpak-and-gnome-software/).
\ No newline at end of file
diff --git a/content/news/2016-12-07-pitivi-0-98-getting-there.md
b/content/news/2016-12-07-pitivi-0-98-getting-there.md
new file mode 100644
index 0000000..80aba18
--- /dev/null
+++ b/content/news/2016-12-07-pitivi-0-98-getting-there.md
@@ -0,0 +1,39 @@
+---
+title: 'Pitivi 0.98 — Getting there'
+date: Wed, 07 Dec 2016 17:37:08 +0000
+tags:
+ - Release
+---
+
+This is another [release](http://wiki.pitivi.org/wiki/0.98) focused on fixing bugs and improving stability.
+
+Improved timeline
+-----------------
+
+We switched our [official build](http://wiki.pitivi.org/wiki/Install_with_flatpak) to use GTK 3.22 and the
framework did not like how we were using it, spamming us with warnings in the console. We fixed those and
improved the timeline in the process and added more unit tests.
+
+> It was [quite a journey](https://phabricator.freedesktop.org/T7573). Initially, the GTK Inspector was
useful to figure out which widgets the widget IDs in the warnings identified. Then we had to go back between
the GTK documentation and the #gtk+ IRC channel until we figured out we were changing the size of some
containers in their do\_draw methods, which was not good.
+
+Accelerated development
+-----------------------
+
+Taking advantage of an opportunity, with the last money from our [coffers](https://www.pitivi.org/donators/)
(the remaining 2014 fundraiser donations and the GSoC mentor stipends) we hired Alexandru Băluț, a long-time
Pitivi contributor, so he can focus better on fixing issues blocking the 1.0 release. Alex worked on Pitivi
in Oct, Nov, and will allocate more time in Dec 2016. Thanks again to everybody who donated!
+
+Customizable keyboard shortcuts
+-------------------------------
+
+Jakub Brindza, our GSoC 2016 student, finished the [customizable keyboard
shortcuts](http://www.jakubbrindza.com/2016/08/gsoc-with-pitivi.html) feature. See how it works in the
screencast below.
+
+{{< youtube RSUOFEpHpH4 >}}
+
+Supported muxers and encoders
+-----------------------------
+
+In the previous version, 0.97, we picked a set of [supported muxers, audio encoders, video
encoders](https://github.com/pitivi/pitivi/blob/0ae789140bd28f96e91fb53c4df2d7168473f665/pitivi/render.py#L91),
added integration tests for them in GES, and changed the rendering dialog to show very clearly the ones
which are unsupported.
+
+1.0
+---
+
+See what's left to do for 1.0 in the [0.99 and 1.0 columns in
Phabricator](https://phabricator.freedesktop.org/tag/pitivi/). If you want to
[help](https://www.pitivi.org/contributing/) in any way, come to our [IRC
channel](https://www.pitivi.org/contact/). We prepared a nice [list of tasks suitable for
newcomers.](https://phabricator.freedesktop.org/project/view/111/) These are good also for students
interested to [apply for a GSoC with us](http://wiki.pitivi.org/wiki/Google_Summer_of_Code).
+
+The build system has been ported to [meson](http://mesonbuild.com/), no more autogen! ;)
\ No newline at end of file
diff --git a/content/news/2017-05-11-three-gsoc-students-hack-on-pitivi-this-summer.md
b/content/news/2017-05-11-three-gsoc-students-hack-on-pitivi-this-summer.md
new file mode 100644
index 0000000..c5986a3
--- /dev/null
+++ b/content/news/2017-05-11-three-gsoc-students-hack-on-pitivi-this-summer.md
@@ -0,0 +1,18 @@
+---
+title: 'Three GSoC students hack on Pitivi this summer'
+date: Thu, 11 May 2017 22:58:34 +0000
+tags:
+ - GSoC
+---
+
+We're excited to have three students that will contribute to Pitivi this summer. Congratulations, Fabián
Orccón, Suhas Nayak and Ștefan-Adrian Popa!
+
+* [Fabián](http://teetux.com/) already had an internship with us two years ago. He'll focus on a plugin
system with great documentation for video hackers, and a first plugin for inspecting the timeline of the
currently opened project in a Python console ([T3193](https://phabricator.freedesktop.org/T3193)).
+* [Suhas](https://suhas2go.github.io) will focus on a modern color correction UI for the corresponding
GStreamer plugin, and lay the path for similar changes to other effects
([T2372](https://phabricator.freedesktop.org/T2372)).
+* [Ștefan](https://stefanpopablog.wordpress.com) will focus on allowing users to apply [Ken-Burns
effects](https://en.wikipedia.org/wiki/Ken_Burns_effect) by manipulating the placement and zoom of the clips
on the viewer ([T7340](https://phabricator.freedesktop.org/T7340)).
+
+You can follow the linked blogs or subscribe to the Phabricator tasks to stay up-to-date with the progress,
or keep an eye on the [Pitivi planet](https://www.pitivi.org/planet/). Feel free to make suggestions about
these projects on the corresponding tasks, or chat with us about them in our [IRC
channel](https://www.pitivi.org/contact/). The official start of the coding period is May 30.
+
+Besides mentoring for GSoC, the Pitivi maintainers are busy ironing out the last stability problems we're
aware of. We made great progress, expect version 0.99 sometime soon, followed by some more testing towards
1.0!
+
+Thanks to Google for [GSoC](https://developers.google.com/open-source/gsoc/) and to the [GNOME
Foundation](https://www.gnome.org) for allowing us to have these projects under their umbrella this year!
\ No newline at end of file
diff --git a/content/news/2017-09-22-pitivi-0-99-ocean-big-chair.md
b/content/news/2017-09-22-pitivi-0-99-ocean-big-chair.md
new file mode 100644
index 0000000..3e19f17
--- /dev/null
+++ b/content/news/2017-09-22-pitivi-0-99-ocean-big-chair.md
@@ -0,0 +1,22 @@
+---
+title: 'Pitivi 1.0 Release Candidate — "Ocean Big Chair"'
+date: Fri, 22 Sep 2017 11:40:35 +0000
+tags:
+ - Release
+---
+
+We’re proud to release the first Pitivi 1.0 release candidate “Ocean Big Chair” (0.99). This release has
many bug fixes and performance improvements, and is a release candidate for 1.0. Our test suite grew
considerably, from 164 to 191 meaningful unit tests.
+
+You can [install it](https://developer.pitivi.org/Install_with_flatpak.html) right away using Flatpak.
+
+### GSoC
+
+Early on this year, we got caught up in the Google Summer of Code. A lot of students hacked on Pitivi this
spring, to get to know Pitivi better. As a result quite a few important fixes and improvements have been
made. A big thank you to all of the students who contributed!
+
+This summer we had three GSoC Pitivi projects. The GSoC work has been merged on the “master” branch and we
made a separate “1.0” branch where we implement or backport the relevant fixes. A special thank you to Suhas
Nayak and Ștefan-Adrian Popa, two of our GSoC students who contributed a large number of bugfixes and made
possible this release.
+
+### 1.0
+
+As you might know, we're focused on bug fixing until Pitivi 1.0. See what’s left to do for 1.0 in
[Phabricator](https://phabricator.freedesktop.org/project/view/125/).
+
+We need people to test Pitivi (the Flatpak "stable" branch) and report back any crash or stability issue
they notice, so we fix it. — If you want to [help](https://www.pitivi.org/contributing/) in any way, come to
our [IRC channel](https://www.pitivi.org/contact/).
\ No newline at end of file
diff --git a/content/news/2018-02-27-migrating-to-gnomes-gitlab.md
b/content/news/2018-02-27-migrating-to-gnomes-gitlab.md
new file mode 100644
index 0000000..3d3754c
--- /dev/null
+++ b/content/news/2018-02-27-migrating-to-gnomes-gitlab.md
@@ -0,0 +1,12 @@
+---
+title: 'Migrating to GNOME''s GitLab'
+date: Tue, 27 Feb 2018 13:03:36 +0000
+---
+
+Three years ago we [switched](http://blog.aleb.ro/2015/10/pitivi-moves-from-bugzilla-to.html) our bug
tracker from Bugzilla to Freedesktop's Phabricator instance. As very few projects were using it, the
maintenance cost was too high for the gain, so the current plan is to obsolete it. Phabricator worked well
for us, but now we say bye.
+
+Luckily for us, GNOME hosts a GitLab instance since last year. We just migrated the Phabricator tasks to it
and now we're at [https://gitlab.gnome.org/GNOME/pitivi](https://gitlab.gnome.org/GNOME/pitivi).
+
+This was possible thanks to [Thibault](https://wiki.gnome.org/ThibaultSaunier) for extending the
[bztogl](https://gitlab.gnome.org/Incubator/bztogl) tool used to migrate the tasks, to
[Carlos](https://wiki.gnome.org/CarlosSoriano) for carefully running it, and to the GNOME community for
everything.
+
+We'll certainly benefit a lot from the tighter integration with GNOME. This makes it much easier for GNOME
contributors of all kinds to take part in our awesome video editor.
\ No newline at end of file
diff --git a/content/news/2018-04-27-dropping-support-for-non-square-pixels/index.md
b/content/news/2018-04-27-dropping-support-for-non-square-pixels/index.md
new file mode 100644
index 0000000..cc0e2a3
--- /dev/null
+++ b/content/news/2018-04-27-dropping-support-for-non-square-pixels/index.md
@@ -0,0 +1,36 @@
+---
+title: 'Dropping support for non-square pixels in Pitivi'
+date: Fri, 27 Apr 2018 20:06:28 +0000
+---
+
+Emerging from the long history of the video broadcast industry, there are legacy standards which specify
_rectangular_ pixels instead of square pixels. Yes, really! According to
[Wikipedia](https://en.wikipedia.org/wiki/Pixel_aspect_ratio), non-square pixels originate in early digital
TV standards:
+
+> The term _pixel aspect ratio_ was first coined when [ITU-R BT.601](https://en.wikipedia.org/wiki/Rec._601
"Rec. 601") (commonly known as "[Rec. 601](https://en.wikipedia.org/wiki/Rec._601 "Rec. 601")") specified
that standard-definition television pictures are made of lines of exactly 720 non-square pixels.
+
+Today, we're announcing that we will no longer support rendering non-square pixels. It will still be
possible to use videos with non-square pixels in your projects, though.
+
+Pitivi allowed creating projects with non-square pixels, but there were quality and behavior issues, such as
this [inconsistent viewer and renderer
behavior](https://gitlab.gnome.org/GNOME/pitivi/issues/1406#note_70802) related to them.
+
+GStreamer Editing Services (GES), the library used by Pitivi for video processing, is very flexible and
allows using videos of any video format in the same project. However, normally, in a "pro" setup, most video
editing applications are very strict about the formats they accept as input, so Pitivi and GES were a bit
unconventional with the "anything goes" approach.
+
+This might give a clue as to why it was rather complicated and not very rewarding to "properly" fix the
rectangular pixels problems in GES. The following question arose in our IRC channel (#pitivi on freenode):
+
+> \[2017-10-30 14:37:38\] <thiblahute> nekohayo: So my main question would be, do we really care these
days to be able to produce non square output?
+
+And we mostly came to the conclusion that only dinosaurs are producing content with rectangular pixels, and
that with our limited resources we can't afford to spend time and effort on this:
+
+> \[2017-10-30 14:44:06\] <nekohayo> so... it seems that non-square only matters for older formats
+>
+> \[2017-10-30 14:44:45\] <nekohayo> and since we gave up on handling DV tapes/firewire anyway... we
could as well declare PAR dead. Because f\*\*\* the 1990-2000's
+>
+> \[2017-10-30 14:45:29\] <nekohayo> Mathieu\_Du's only got love for you if you were born in the 80's
+>
+> \[2017-10-30 14:46:58\] <Mathieu\_Du> the what again ?
+>
+> \[2017-10-30 16:36:38\] <nekohayo> pixel aspect ratio ([acceptable in the
80's](https://www.youtube.com/watch?v=Ckff_bkA5z8))
+>
+> \[2017-10-30 16:37:28\] <Mathieu\_Du> aha, knew that song from lubosz though :)
+
+As a result of this simplification, the aspect ratio controls in the project settings dialog have been
removed—one less thing for the user to worry about—and so the project width and height are now the only
settings defining the display aspect ratio.
+
+{{< figure src="video_settings2.jpg" title="The aspect ratio settings removed from the project settings
dialog" >}}
diff --git a/content/news/2018-04-27-dropping-support-for-non-square-pixels/video_settings2.jpg
b/content/news/2018-04-27-dropping-support-for-non-square-pixels/video_settings2.jpg
new file mode 100644
index 0000000..ba8d342
Binary files /dev/null and
b/content/news/2018-04-27-dropping-support-for-non-square-pixels/video_settings2.jpg differ
diff --git a/content/news/2019-04-16-gstreamer-editing-services-applies-to-the-season-of-docs.md
b/content/news/2019-04-16-gstreamer-editing-services-applies-to-the-season-of-docs.md
new file mode 100644
index 0000000..e122d5d
--- /dev/null
+++ b/content/news/2019-04-16-gstreamer-editing-services-applies-to-the-season-of-docs.md
@@ -0,0 +1,47 @@
+---
+title: 'GStreamer Editing Services applies to the Season of Docs'
+date: Tue, 16 Apr 2019 07:06:28 +0000
+tags:
+ - Season of Docs
+---
+
+The Pitivi video editor is [based](https://developer.pitivi.org/GES.html) on the [GStreamer Editing
Services](https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html) library. GES makes
it easy to manage the timeline of a video project and export it to a new video file, and is carefully built
to be reusable by other projects, not only Pitivi.
+
+Since a few years ago, while not [mentoring](https://developer.pitivi.org/Past_GSoCs.html) students for
GSoC, we've been busy working on Pitivi 1.0, about to be released. A large part of this was spent on fixing
and improving the GES library. Time has come for the GES documentation to also be improved, to attract new
users and contributors to the GStreamer ecosystem.
+
+We're applying to the [Season of Docs](https://developers.google.com/season-of-docs/) program, where Google
pays technical writers to contribute to open-source projects. Check out the [technical writer
guide](https://developers.google.com/season-of-docs/docs/tech-writer-guide) for details and the program
timeline, and read below if you are interested in working with us!
+
+**UPDATE**: We've been accepted, see the [list of accepted open-source
organizations](https://developers.google.com/season-of-docs/docs/participants/).
+
+
+
+Project ideas
+-------------
+
+As GES is a relatively small project, we have a single project idea, composed of multiple smaller tasks.
+
+### Write overviews and clarify the API reference
+
+What GES is missing the most is a set of easy to understand high-level **overviews** for newcomers. You
could write for example overviews about:
+
+* Assets and proxy management in a project
+* Timeline composed of Layers, and the output a/v tracks
+* Layers composed of various Clip types, and how these can be created
+* Effects which can be applied to Clips, and controllable properties
+
+While preparing the high-level overviews you'll dive into the **API reference**. The current API
documentation is usable, but is not in the best shape. As you notice gaps, unclear sentences, missing
details, you would either fix them on the spot or take note and fix them later. The entire API reference can
then be reviewed and refreshed in this second step.
+
+A stretch goal would be writing one or more **tutorials**, to exemplify easy video tasks which can be
automated. The base code for these would be provided by us, and be most probably written in Python:
+
+* Cutting every third second of a video to produce a shorter video with skips,
+* Creating a photos slideshow with random transitions between the photos,
+* Displaying multiple videos at the same time in mosaics,
+* Animating a title clip in the center of the image from 0% to full size.
+
+The GES overviews and tutorials would be kept in the [GES git
repository](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs) as markdown
files. The API is documented in the [source
code](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/ges) written in C.
+
+To get a better idea about the GES API, check the [hierarchy of
classes](http://lazka.github.io/pgi-docs/#GES-1.0/hierarchy.html).
+
+The current [GES
documentation](https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html) is integrated
into the GStreamer documentation. The structure is specified in
[docs/sitemap.txt](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/blob/master/docs/sitemap.txt),
and the HTML is generated with [Hotdoc](https://hotdoc.github.io) out of the C files and [other markdown
bits](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs).
+
+If interested, [get in touch](https://www.pitivi.org/contact/) with us as soon as possible, so we can
prepare.
\ No newline at end of file
diff --git a/content/news/2019-05-10-call-for-testing-the-pitivi-1-0-rc.md
b/content/news/2019-05-10-call-for-testing-the-pitivi-1-0-rc.md
new file mode 100644
index 0000000..e823c88
--- /dev/null
+++ b/content/news/2019-05-10-call-for-testing-the-pitivi-1-0-rc.md
@@ -0,0 +1,39 @@
+---
+title: 'Call for testing the Pitivi 1.0 RC'
+date: Fri, 10 May 2019 06:58:47 +0000
+---
+
+Pitivi 1.0 is scheduled to be released on Monday, May 20th. All the important bugs we were aware of have
been fixed.
+
+To fix one of the last issues, Thibault very recently rewrote the timeline/layers/clips management in GES,
and this might have introduced new bugs. While we have lots of tests which all pass, they don't cover
everything.
+
+We ask you to test the 1.0 RC! Grab a bunch of video files shot with your phone or camera and make some
video out of them, trying various features. Tell us if you notice problems, and if you can reproduce them
please file an issue describing the steps to reproduce the bug.
+
+You can find us in the [Pitivi Matrix room](https://matrix.to/#/#pitivi:matrix.org).
+
+How to install
+--------------
+
+To install the Pitivi 1.0 RC, simply run:
+
+```
+flatpak install http://flatpak.pitivi.org/pitivi.flatpakref
+```
+
+If there are conflicts, you can uninstall the conflicting installation.
+
+How to test
+-----------
+
+Start Pitivi from the console, and keep it in view to notice any warnings or errors which might show up:
+```
+flatpak run org.pitivi.Pitivi//stable
+```
+
+You should be able to use any video file supported by GStreamer, but we officially support only a limited
set of formats. If the file appears in the media library with a warning sign, right-click it and select proxy
to create an optimized media file used automatically instead of the original.
+
+Most useful would be to test the timeline editing, which should be responsive and precise. Try for example
[splitting](https://www.pitivi.org/manual/splitting.html) and
[trimming](https://www.pitivi.org/manual/trimming.html) clips, moving them around. Try ungrouping audio-video
clips to make the respective video shorter than the audio. Overlap clips to create cross-fade
[transitions](https://www.pitivi.org/manual/transitions.html).
+
+If time allows, you can also try adding effects, for example adding a background to a green screen. Mix
diverse footage formats in the same timeline. Make a slideshow and include title clips and background music.
+
+For reference, see the [user manual](https://www.pitivi.org/manual/). At the end, please render it and show
us what you did!
\ No newline at end of file
diff --git a/content/news/2020-05-02-pitivi-applies-to-the-season-of-docs.md
b/content/news/2020-05-02-pitivi-applies-to-the-season-of-docs.md
new file mode 100644
index 0000000..b35b871
--- /dev/null
+++ b/content/news/2020-05-02-pitivi-applies-to-the-season-of-docs.md
@@ -0,0 +1,48 @@
+---
+title: 'Pitivi applies to the Season of Docs'
+date: Sat, 02 May 2020 12:40:20 +0000
+tags:
+ - Season of Docs
+---
+
+The Pitivi video editor is [based](https://developer.pitivi.org/GES.html) on the [GStreamer Editing
Services](https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html) library (GES).
Various projects use GES to manage audio or video projects and export the project to a new file to be
distributed.
+
+Pitivi is developed in very close contact with GES. Both Pitivi and GES would benefit a lot from better
documentation.
+
+We’re applying to the [Season of Docs](https://developers.google.com/season-of-docs/) program, where Google
pays technical writers to contribute to open-source projects. Check out the [technical writer
guide](https://developers.google.com/season-of-docs/docs/tech-writer-guide) for details and the program
timeline. Read below the project ideas if you are interested in working with us!
+
+**UPDATE:** Pitivi is taking part in the Season of Docs under GNOME's umbrella. If interested to update
Pitivi's user manual check the [Update app
help](https://www.gnome.org/news/2020/05/gnome-season-of-docs-2020/) project idea and see below for details.
+
+Project ideas
+-------------
+
+### GES: Write overviews and clarify the API reference
+
+What GES is missing the most is a set of easy to understand high-level **overviews** for newcomers. You
could write for example overviews about:
+
+* Assets and proxy management in a project
+* Timeline composed of Layers, and the output a/v tracks
+* Layers composed of various Clip types, and how these can be created
+* Effects which can be applied to Clips, and controllable properties
+
+While preparing the high-level overviews you’ll dive into the **API reference**. The current API
documentation is usable, but is not in the best shape. As you notice gaps, unclear sentences, missing
details, you would either fix them on the spot or keep track of them so they can be fixed. The entire API
reference can then be reviewed and refreshed in this second step. A stretch goal would be writing one or more
**tutorials**, to exemplify easy video tasks which can be automated. The base code for these would be
provided by us, and be most probably written in Python:
+
+* Cutting every third second of a video to produce a shorter video with skips,
+* Creating a photos slideshow with random transitions between the photos,
+* Displaying multiple videos at the same time in mosaics,
+* Animating a title clip in the center of the image from 0% to full size.
+
+The GES overviews and tutorials would be kept in the [GES git
repository](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs) as markdown
files. The API is documented directly in the [source
code](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/ges) written in C.
+
+To get a better idea about the GES API, check the [hierarchy of
classes](http://lazka.github.io/pgi-docs/#GES-1.0/hierarchy.html).
+
+The current [GES
documentation](https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html) is integrated
into the GStreamer documentation. The structure is specified in
[docs/sitemap.txt](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/blob/master/docs/sitemap.txt),
and the HTML is generated with [Hotdoc](https://hotdoc.github.io) out of the C files and [other markdown
bits](https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs).
+
+### Pitivi: Update the user manual
+
+The user manual is available both [online](https://www.pitivi.org/manual/) and in Pitivi by pressing F1. The
latest Pitivi features should be documented in the user manual and the current content should be brought up
to date. The user manual is kept in the [Pitivi git
repository](https://gitlab.gnome.org/GNOME/pitivi/-/tree/master/help/C) as
[mallard](http://projectmallard.org/about/learn/tenminutes.html) files.
+
+How to contact us
+-----------------
+
+If interested, get in touch with us [on Matrix](https://matrix.to/#/#pitivi:matrix.org), so we can prepare.
You are expected to ask a lot of questions.
\ No newline at end of file
diff --git a/content/news/2020-05-09-presenting-our-google-summer-of-code-students.md
b/content/news/2020-05-09-presenting-our-google-summer-of-code-students.md
new file mode 100644
index 0000000..715ca7c
--- /dev/null
+++ b/content/news/2020-05-09-presenting-our-google-summer-of-code-students.md
@@ -0,0 +1,17 @@
+---
+title: 'Presenting Our Google Summer of Code Students!'
+date: Sat, 09 May 2020 07:00:38 +0000
+tags:
+ - GSoC
+summary: Welcome to Abhishek, Ayush and Vivek who join Pitivi as part of the Google Summer of Code.
+---
+
+Google has published the list of students accepted in the [Google Summer of
Code](https://summerofcode.withgoogle.com) program. The accepted students work on open-source software.
Pending monthly evaluations, the students receive a stipend from Google. Like [last
year](https://developer.pitivi.org/Past_GSoCs.html), we're mentoring [three
students](https://summerofcode.withgoogle.com/organizations/5677249036025856/)!
+
+[Abhishek Kumar Singh](https://gitlab.gnome.org/gaharavara) will improve the Media Library. The current
implementation will be initially simplified to deal with a single Gtk.FlowBox container. Asset tagging will
provide the info to display in a new Folder View. The stretch goal is to display the assets by date.
+
+[Ayush Mittal](https://gitlab.gnome.org/ayush9398) will improve the Render experience. The current UI will
be simplified, allowing the user to select a meaningful preset. Specifying the export quality for the
[officially supported
encoders](https://gitlab.gnome.org/GNOME/pitivi/-/blob/413abf1f83bdac7d70863b91d820962b39cb9cac/pitivi/render.py#L89)
will be possible using a slider widget. The advanced options will still be available but not directly
visible.
+
+[Vivek R](https://gitlab.gnome.org/123vivekr) will implement face/object tracking and blurring. A new
GStreamer plugin will allow tracking a specified region in the video using OpenCV. The obtained tracking
information is presented to the user to be reviewed and adjusted in a new UI Perspective. The user can apply
the adjusted positions to a blur effect applied to the clip.
+
+Please get in touch if you are interested in working with us. You can find us in
[https://matrix.to/#/#pitivi:matrix.org](https://matrix.to/#/#pitivi:matrix.org)
\ No newline at end of file
diff --git a/content/news/2020-10-11-pitivi-2020-09-hocus-focus.md
b/content/news/2020-10-11-pitivi-2020-09-hocus-focus.md
new file mode 100644
index 0000000..2f8cb3f
--- /dev/null
+++ b/content/news/2020-10-11-pitivi-2020-09-hocus-focus.md
@@ -0,0 +1,112 @@
+---
+title: Pitivi 2020.09 — Hocus focus
+date: Sun, 11 Oct 2020 14:05:54 +0000
+tags:
+ - Release
+summary: The Pitivi team proudly presents Pitivi version **2020.09**, a new milestone towards the most
reliable video editor.
+---
+
+The Pitivi team proudly presents Pitivi version **2020.09**, a new milestone towards the most reliable video
editor.
+
+New features
+------------
+
+Since the 2014 fundraiser and until Pitivi 0.999 released in 2018, we included only critical features to
focus on quality. For example, the proxy functionality which allows precise editing by seamlessly using the
optimized media when the original media format is not supported officially.
+
+Life and GSoC happens and we developed many good features over this period. Most of these originate from the
Google Summer of Code program in which we took part, but not only. The new features came with accompanying
unit tests and they have been merged only after careful code reviews. Even so, we kept them in the
development branch.
+
+This approach led to extra work for taking care of two branches. In addition to a "stable" branch out of
which we were making releases, we also maintained a "development" branch in which we were merging cool
features. Luckily, despite not much appearing to be happening with the project due to releases containing
only bug fixes, contributors kept showing up, and not only because of GSoC.
+
+Since the previous release we came to our senses and reconsidered the earlier decision. Pitivi 2020.09
includes a ridiculous number of new features, for your delight. Read the full list below and get ready to be
blown away by what our contributors built.
+
+Quality
+-------
+
+The user survey we conducted in 2013 revealed the most important point was to have a “stable as hell” basic
editor. Since the previous release two years ago, we fixed the last outstanding bugs in [GStreamer Editing
Services](https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html) (GES), Pitivi's
reusable video editing backend.
+
+At this point, the extensive GES and Pitivi unit tests and the gst-validate testing framework developed for
GStreamer/GES allow us to make changes without being too afraid of introducing regressions. Thanks to the
quality assurance we have in place, we are now switching to a date-based versioning scheme for Pitivi. The
intention is to release often what we have at that point and make gradual changes.
+
+Even though there won't be a Pitivi 1.0, after 15 years of hard work we are proud GES has reached the "1.0"
level. We are very happy to finally reach this essential milestone in the project life!
+
+This was possible thanks to contributions from [Igalia](https://www.igalia.com/) who has been sponsoring the
development of the GStreamer Editing Services by stabilizing it and implementing many features such as the
integration with [OpenTimelineIO](https://opentimelineio.readthedocs.io/en/latest/) from Pixar, implementing
timeline nesting, and clip speed control (yet to be leveraged in Pitivi).
+
+We'll be looking for ways of creating a constant stream of money to fund development by drawing interest
from institutions backed by public money. Until this will happen, if ever, we'll play with occasional
fundraisers for improving stability. More about this in a separate blog post.
+
+What's new
+----------
+
+This release includes lots of new features, originating from GSoC internships spanning four years, from
University of Nebraska-Lincoln's SOFT-261 class Spring 2020 and from individual contributors.
+
+#### GSoC 2017
+
+* A plugin system allows extending the Pitivi functionality medium-term, targeted for teams of editors.
+* A developer console plugin allows interacting with the project in a Python console.
+* Mechanism for supporting custom UI for effects issues of the automatically generated UI.
+* Custom UI for the frei0r-filter-3-point-color-balance and alpha effects.
+* Easy Ken-Burns effect.
+
+#### GSoC 2018
+
+* The new Greeter perspective replaces the Welcome wizard dialog and allows a slick selection of a
recently opened project.
+* When being resized, the Viewer shows the percent of the actual widget size in relation to the project
video size.
+* The Viewer size snaps at 50% when being resized.
+* Scaled proxies if optimized media is too much for your machine.
+
+#### GSoC 2019
+
+* Timeline markers.
+* Support for nested timelines by importing entire XGES files as a clip.
+* The Effects Library has been redesigned to allow quick access to effects.
+* Ability to favorite effects in the Effects Library.
+* Improved workflow for adding effects.
+* The refreshed clip effects UI allows working on multiple effects at a time.
+
+#### GSoC 2020
+
+* Refactored Media Library to use the same logic for the different view modes.
+* Refactored Render Dialog UI to avoid overwhelming people. Tell us what you think about it.
+
+#### University of Nebraska-Lincoln's SOFT-261 class, Spring 2020
+
+* Restoring the editing state when reopening a project.
+* Safe areas visualization in the Viewer.
+* Easy alignment for video clips.
+* Composition guidelines in the Viewer.
+* Solid color clips.
+* Ability to mute an entire layer.
+
+#### Individual hackers
+
+* Custom UI for the frei0r-filter-alphaspot effect.
+* Interactive Intro for newcomers to get familiar with the UI elements.
+* The action search is a shortcut to everything possible in the timeline, if you can find it. Press "/".
+* Ability to hide an entire layer.
+* New keyboard shortcuts for pros.
+
+Under the hood
+--------------
+
+Since the Pitivi 0.15.2 release that came at the time of our 2014 crowdfunding campaign, we have basically
changed everything under the hood, with too many bug fixes to count:
+
+* We rewrote the timeline canvas twice due to the changing technological landscape around us.
+* We've redone the clip transformation UI in the viewer twice.
+* We've redone the undo-redo system.
+* We've redone the Media Library.
+* We've redone the Effects Library.
+
+Please see the corresponding [2020.09 milestone](https://gitlab.gnome.org/GNOME/pitivi/-/milestones/1) for
details.
+
+Download
+--------
+
+You can install Pitivi 2020.09 right away with flatpak. Follow the [installation
instructions](https://flathub.org/apps/details/org.pitivi.Pitivi) from flathub.
+
+What's next
+-----------
+
+We keep the highest priority issues in the [2020.12
milestone](https://gitlab.gnome.org/GNOME/pitivi/-/milestones/7). Basically a mix of bugfixing, cleanup and
features.
+
+Thanks
+------
+
+Many thanks to all the contributors!
\ No newline at end of file
diff --git a/content/news/_index.md b/content/news/_index.md
new file mode 100644
index 0000000..6e5145a
--- /dev/null
+++ b/content/news/_index.md
@@ -0,0 +1,3 @@
+---
+Title: News
+---
\ No newline at end of file
diff --git a/content/showcase.html b/content/showcase.html
index 4fd12f4..d911294 100644
--- a/content/showcase.html
+++ b/content/showcase.html
@@ -1,6 +1,5 @@
---
title: "Showcase"
-date: 2017-05-21T19:04:08+02:00
---
<section class="centered-introduction">
@@ -25,12 +24,6 @@ date: 2017-05-21T19:04:08+02:00
<video controls preload="none" poster="{{< videos_site >}}/videos/showcase/Pitivi hackfest in Berlin -
SD.jpg"><source src="{{< videos_site >}}/videos/showcase/Pitivi hackfest in Berlin - SD.webm"
type='video/webm; codecs="vp8, vorbis"' /></video>
</div>
-<div class="box">
-<h2>Dragons Dream</h2>
-<p>A mashup of <a href="https://en.wikipedia.org/wiki/Sintel";>Sintel</a> and <a
href="https://en.wikipedia.org/wiki/Elephants_Dream";>Elephants Dream</a>. The input video footage was in
2048x872 resolution and the sound track was mashed up by separating the surround audio channels of the two
movies.</p>
-<video controls preload="none" poster="{{< videos_site >}}/videos/showcase/Dragons Dream.jpg"><source
src="{{< videos_site >}}/videos/showcase/Dragons Dream.webm" type='video/webm; codecs="vp8, vorbis"'
/></video>
-</div>
-
<div class="box">
<h2>Snowy hackfest & Boston Summit 2010</h2>
<p>Edited with Pitivi 0.14, this video uses effects to correct the color balance in some shots. Shot with a
Canon S95.</p>
@@ -54,10 +47,7 @@ date: 2017-05-21T19:04:08+02:00
<p>Patrick Trettenbrein's footage, shot in 2009 with a Porst Reflex ZR 148 (a Super 8 camcorder from the
70's), is a refreshing video in these days of razor-sharp HD images. As one commenter said, "this is how
skateboarding should be, HD is ruining the skateboard scene" ☺</p>
<video controls preload="none" poster="{{< videos_site >}}/videos/showcase/Morning Sun.jpg"><source src="{{<
videos_site >}}/videos/showcase/Morning Sun.webm" type='video/webm; codecs="vp8, vorbis"' /></video>
</div>
-<!--
-<h2>Texture</h2>
-<p>An artsy movie edited with Pitivi 0.13.1 as a test case, shot with a 100$ high definition camcorder.</p>
--->
+
</section>
diff --git a/content/tour.html b/content/tour.html
index 41c5ef2..952781d 100644
--- a/content/tour.html
+++ b/content/tour.html
@@ -1,6 +1,5 @@
---
title: "Tour"
-date: 2021-06-14T01:40:39+02:00
---
<section class="centered-introduction">
@@ -16,17 +15,13 @@ date: 2021-06-14T01:40:39+02:00
<section>
-
-<h2>Stunning elegance</h2>
-<a href="/i/screenshots/0.94.png">
-<!-- Watch out, the embedded version is more compressed than the one we link to -->
-<img src="/i/screenshots/0.94.jpg" alt="Main window" style="width: 90%; max-width: 1000px;">
+<a href="/i/screenshots/2020.05.png" class="discreet">
+ <h2>Stunning elegance<img src="/i/screenshots/2020.05.png" alt="Main window" style="width: 100%;"></h2>
</a>
</section>
-<section class="full-width-gallery">
-<div class="box">
+<section class="auto-column-half">
<h2>Free and Open Source</h2>
<p>Pitivi respects your freedom and keeps getting better with each new release. It will never require
licensing fees or use <a href="https://en.wikipedia.org/wiki/Digital_rights_management"; title="Wikipedia:
Digital Rights Management">DRM</a> to prevent you from using it whenever, wherever and however you like.
Developed collaboratively by people from all around the world, its sole purpose is to be a fantastic video
editor to empower people to express themselves through video. Like GStreamer and <a
href="https://developer.pitivi.org/GES.html"; title="GStreamer Editing Services">GES</a>, Pitivi is
distributed under <a href="https://www.gnu.org/copyleft/lesser.html"; title="GNU Lesser General Public
License">LGPL</a>.</p>
@@ -45,25 +40,22 @@ date: 2021-06-14T01:40:39+02:00
<h2>Flexible and efficient</h2>
<p>Packed with time-saving features such as realtime trimming previews, ripple and roll editing, grouping
and snapping, realtime assets management and searching, playhead-centric zooming and editing, non-modal
cutting, detachable interface components, smooth scrolling, automatic zoom adjustment, Pitivi allows you to
cut with ease. Like a ninja with a vibroblade.</p>
-</div>
-
-<div class="box">
<h2>Beautiful audio waveforms</h2>
<p>Visuals are only a tiny part of the story. A movie without balanced and well-timed sound is amateur at
best. Pitivi provides you with a clear and accurate representation of loudness, so you can balance things out
or easily detect patterns for beat matching, clap synchronization or simply cutting to the music.</p>
<h2>Speaks many languages</h2>
<p>Thanks to the tireless work of the GNOME translation and localization teams, Pitivi is available in <a
href="https://l10n.gnome.org/module/pitivi/";>many languages</a>. Your language is not listed there? <a
href="https://wiki.gnome.org/TranslationProject";>Make it happen</a>.</p>
+</section>
+
+<section class="auto-column-half">
<h2>Easy to learn. Exciting to master</h2>
<p>You have better things to do than dealing with cumbersome user interfaces or reading through books just
to get started. Resulting from years of experience and analysis, our user interface is
<strong>intuitive</strong> and <strong>self-documenting</strong>: it provides you with all the contextual
hints you need to grasp the essentials without needing to dive into the user manual all the time. But if you
want to do something more complicated or want to better understand the tenets of our design, our
fully-searchable, topic-oriented and multilingual user manual is right there, at your fingertips.</p>
<h2>It grows on you and grows with you</h2>
-<p>In addition to providing you with the best video editing software possible, nothing is more important to
us than encouraging you to adapt and improve Pitivi and <a href="https://developer.pitivi.org/GES.html";
title="GStreamer Editing Services">GES</a>. After all, you should truly <em>own</em> your software. The
reason we can keep improving with each release is because <em>you</em> <a href="/contributing/">get
involved</a>.</p>
-</div>
-
+<p>In addition to providing you with the best video editing software possible, nothing is more important to
us than encouraging you to adapt and improve Pitivi and <a href="https://developer.pitivi.org/GES.html";
title="GStreamer Editing Services">GES</a>. After all, you should truly <em>own</em> your software. The
reason we can keep improving with each release is because <em>you</em> <a href="/contribute/">get
involved</a>.</p>
-<div class="box">
<h2>Natural desktop environment integration</h2>
<p>Pitivi integrates best with the <a href="https://gnome.org";>GNOME</a> desktop — or any Linux desktop
environment, really. We don't just look pretty alongside other GTK applications though: we help redefine the
desktop experience by working closely with toolkit and theme designers to suit our needs and push the whole
ecosystem forward.</p>
@@ -75,20 +67,17 @@ date: 2021-06-14T01:40:39+02:00
<h2>No need to reinvent the wheel</h2>
<p>With the <a href="https://developer.pitivi.org/GES.html";>GStreamer Editing Services</a> library, we are
laying solid foundations for the future based upon over a decade of experience. Built atop the <a
href="https://www.openhub.net/p/gstreamer";>giant</a> shoulders of the industry-standard GStreamer multimedia
framework, GES reduces fragmentation and risk while allowing diversity for application writers and
adaptability for all kinds of purposes.</p>
-
-</div>
</section>
-<section id="raw-features-list">
+<section style="clear: both;">
<div>
<h2>See what others have to say about it!</h2>
<p>Take a look at some of the <a href="https://developer.pitivi.org/Praise.html";>praises/positive
comments</a> we have received so far.</p>
</div>
-
</section>
-<section id="raw-features-list">
+<section style="clear: both;">
<h1>What, you wanted a boring list of features?</h1>
<div class="auto-text-columns">
<ul>
diff --git a/layouts/_default/list.html b/layouts/_default/list.html
index 8aa02e3..ae08495 100644
--- a/layouts/_default/list.html
+++ b/layouts/_default/list.html
@@ -1,10 +1,11 @@
{{ define "main" }}
+
<h1>{{ .Title }}</h1>
- {{- range .Pages.ByPublishDate.Reverse }}
- <p>
- <a class="title" href="{{ .RelPermalink }}">{{ .Title }}</a>
- {{ partial "metadata.html" . }}
- <p>{{ .Summary }}</p>
- </p>
- {{- end }}
+{{- range .Pages.ByPublishDate.Reverse }}
+<article class="article">
+ <h2><a class="title discreet" href="{{ .RelPermalink }}">{{ .Title }}</a></h2>
+ {{ partial "metadata.html" . }}
+ <div>{{ .Summary }}</div>
+</article>
+{{- end }}
{{ end }}
\ No newline at end of file
diff --git a/layouts/_default/single.html b/layouts/_default/single.html
index cdb4a08..8ee3808 100644
--- a/layouts/_default/single.html
+++ b/layouts/_default/single.html
@@ -1,3 +1,4 @@
{{ define "main" }}
+ {{ if eq .Section "news" }}<h1>{{ .Title }}</h1>{{ end }}
{{ .Content }}
{{ end }}
\ No newline at end of file
diff --git a/layouts/index.html b/layouts/index.html
index 3fad03f..3f1ebc2 100644
--- a/layouts/index.html
+++ b/layouts/index.html
@@ -1,37 +1,33 @@
{{ define "main" }}
-<section id="mission">
- <h1>We believe in allowing everyone on the planet to express themselves through filmmaking, with tools
that they can own and improve.</h1>
- <p>We do that by harnessing challenging ideas, pushing the latest open-source technologies forward, and
collaborating with artists and developers all around the world.</p>
- <p>Pitivi <a href="/i/pitivi%20pronounciation.ogg" title="[pronounciation]"><img
src="/i/audio-volume-medium-symbolic.svg" alt="pronounciation" style="width:16px; height:16px; border:0px;"
/></a> is a Free video editor with a beautiful and intuitive user interface, a clean codebase and a fantastic
community. <a href="/contributing/">Join us</a>?</p>
+<section class="centered-introduction">
+ <p>Pitivi <a href="/i/pitivi%20pronounciation.ogg" title="[pronounciation]"><img
src="/i/audio-volume-medium-symbolic.svg" alt="pronounciation" style="width:16px; height:16px; border:0px;"
/></a> is a Free video editor with a beautiful and intuitive user interface, a clean codebase and a fantastic
community. <a href="/contribute/">Join us!</a></p>
</section>
+<section id="frontpage_splash" class="auto-column-half">
+ <h1>We believe in allowing everyone on the planet to <a href="/showcase/">express themselves</a> through
filmmaking, with tools that they can own and improve.</h1>
-<section id="frontpage_splash">
- <img src="/i/screenshots/0.94.jpg" alt="Pitivi screenshot" />
-</section>
-
-
-
-<section id="news">
-<h2>Development news</h2>
-<ul><li><a href="https://pitivi.wordpress.com/2020/10/11/pitivi-2020-09-hocus-focus/";>Pitivi 2020.09 — Hocus
focus</a></li><li><a href="https://gaharavara.github.io/gsoc-2020-final-report/";>Google Summer Of Code 2020
Final Report</a></li><li><a href="https://ayush9398.github.io/blog/GSOC'20-work-product">GSoC 2020 @ Pitivi:
Work Product</a></li><li><a
href="https://123vivekr.github.io/123vivekr.github.io/2020/08/29/pitivi-gsoc-work-product.html";>GSoC 2020:
Pitivi: Work Product</a></li><li><a
href="https://123vivekr.github.io/123vivekr.github.io/2020/08/16/pitivi-object_track_editing.html";>Pitivi:
Edit Object Tracking</a></li><li><a
href="https://123vivekr.github.io/123vivekr.github.io/2020/07/28/pitivi-object_tracking.html";>Pitivi: Object
Tracking</a></li><li><a href="https://gaharavara.github.io/refactoring-pitivi-%20medialibrary/";>Refactoring
Pitivi's Media Library</a></li><li><a href="https://ayush9398.github.io/blog/pitivi";>Pitivi: Making the
Render dialog usable: Render profi
les</a></li><li><a
href="https://cfoch.github.io/tech/2020/05/20/playing-back-arbitrary-frames-with-appsrc.html";>Playing back
arbitrary frames with appsrc</a></li><li><a
href="https://pitivi.wordpress.com/2020/05/09/presenting-our-google-summer-of-code-students/";>Presenting Our
Google Summer of Code Students!</a></li></ul>
-<p>See the <a href="planet/">Pitivi planet</a> for archives.</p>
-
-<!-- The following icons are CC-Attrib, made by Adam Fairhead -->
-<a href="http://www.pitivi.org/planet/atom.xml";><img src="/i/webicon-rss.svg" alt="syndication feed"
title="Subscribe to Pitivi Planet with your syndication feed reader" class="frontpage_social_media_icon"
/></a>
+ <div style="margin-left: auto; margin-right: auto; margin-top: 1em;">
+ <a href="/tour/" class="discreet">
+ <h1 style="margin-bottom: 0.5em;">Take the tour...<img src="/i/screenshots/2020.05.png"
alt="Pitivi screenshot"/></h1>
+ </a>
+ </div>
-<a href="https://twitter.com/pitivi";><img src="/i/webicon-twitter.svg" alt="Twitter account" title="Follow
us on Twitter" class="frontpage_social_media_icon" /></a>
-
-<a href="https://www.facebook.com/Pitivi-190937657784190/";><img src="/i/webicon-facebook.svg" alt="Facebook
account" title="Follow us on Facebook" class="frontpage_social_media_icon" /></a>
-
-<a href="https://gitlab.gnome.org/GNOME/pitivi";><img src="/i/webicon-git.svg" alt="GitLab repository"
title="View our GitLab project management page, including the issues tracker and Git code repository"
class="frontpage_social_media_icon" /></a>
-
-<script type="text/javascript" src="https://www.openhub.net/p/3757/widgets/project_users_logo.js";></script>
+</section>
-<div style="font-size:80%;">
- <p>If you really like the work we do,
-<!--please consider donating for <a href="http://fundraiser.pitivi.org";>our fundraising campaign</a>!-->
-you may consider donating once in a while. See the <a href="/donators/">donators</a> page for more
details.</p>
-</div>
+<section id="news" class="auto-column-half">
+<h1><a href="/news/" class="hidden">News</a></h1>
+<ul>
+{{ $news := .Site.GetPage "news" }}
+{{- range first 5 $news.Pages.ByPublishDate.Reverse }}
+{{- $dateTime := .PublishDate.Format "2006-01-02" }}
+{{- $dateFormat := .Site.Params.dateFormat | default "Jan 2, 2006" }}
+<article class="article">
+ <h2 class="title"><a class="discreet" href="{{ .RelPermalink }}">{{ .Title }}</a></h2>
+ {{ partial "metadata.html" . }}
+ <div class="summary">{{ .Summary }}</div>
+</article>
+{{- end }}
+</ul>
+<p style="text-align: right; margin-right: 0;"><a href="/news/">Archive...</a></p>
</section>
{{ end }}
\ No newline at end of file
diff --git a/layouts/partials/footer.html b/layouts/partials/footer.html
index f383f30..9e77649 100644
--- a/layouts/partials/footer.html
+++ b/layouts/partials/footer.html
@@ -1,5 +1,25 @@
<footer>
- <span style="color:gray; font-size:8px;"><b>Page last modified:</b> {{ .Lastmod.Format "January 2 2006
15:04:05" }}.</span>
+ <div style="font-size: 300%;">
+ <a href="/planet/atom.xml"><i class="fas fa-rss-square"></i></a>
+
+ <a href="https://twitter.com/pitivi";><i class="fab fa-twitter-square"></i></a>
+
+ <a href="https://www.facebook.com/Pitivi-190937657784190/";><i class="fab fa-facebook-square"></i></a>
+
+ <a href="https://gitlab.gnome.org/GNOME/pitivi";><i class="fab fa-gitlab"></i></a>
+ </div>
+
+ <p>If you really like the work we do, you may consider <a href="/donators/">donating</a> once in a
while.</p>
+
+ {{ $editPath := "" }}
+ {{- if .File }}
+ {{- $editPath = printf "content/%s" .Path }}
+ {{- else if .IsHome }}
+ {{- $editPath = "layouts/index.html" }}
+ {{- end }}
+ {{- with $editPath -}}
+ <a style="color: gray; font-size: smaller;" href="{{ $.Site.Params.gitlab }}/-/blob/master/{{ . }}">Edit
this</a>
+ {{- end }}
</footer>
diff --git a/layouts/partials/head.html b/layouts/partials/head.html
index bb85d00..4d15080 100644
--- a/layouts/partials/head.html
+++ b/layouts/partials/head.html
@@ -1,19 +1,15 @@
<head>
<title>{{ if .IsHome }}Pitivi, a free and open source video editor for Linux{{ else }}Pitivi — {{ .Name
}}{{ end }}</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
- <meta name="author" content="Jean-François Fortin Tam"/>
<meta name="revisit-after" content="10 days" />
<meta name="robots" content="index, follow" />
<meta name="viewport" content="initial-scale=1.0,
width=device-width" />
- <link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,200"; rel="stylesheet"
type="text/css">
- <link href="https://fonts.googleapis.com/css?family=Droid+Sans"; rel="stylesheet" type="text/css">
- <link href="https://fonts.googleapis.com/css?family=Droid+Sans+Mono"; rel="stylesheet" type="text/css">
<link rel="stylesheet" type="text/css" href="/css/pitivi.css" />
<!-- https://stackoverflow.com/questions/2268204/favicon-dimensions -->
<link rel="icon" type="image/png" href="/i/pitivi-2019-icon-16.png" sizes="16x16" />
<link rel="icon" type="image/png" href="/i/pitivi-2019-icon-32.png" sizes="32x32" />
<!-- Allow feed readers to pick up our Planet feed from any page !-->
- <link rel="alternate" type="application/atom+xml" title="Planet Pitivi Atom 1.0"
href="http://pitivi.org/planet/atom.xml";>
+ <link rel="alternate" type="application/atom+xml" title="Planet Pitivi Atom 1.0"
href="https://www.pitivi.org/planet/atom.xml";>
<script src="https://kit.fontawesome.com/762a6b0d58.js"; crossorigin="anonymous"></script>
</head>
diff --git a/layouts/partials/header.html b/layouts/partials/header.html
index b67cab7..24cf211 100644
--- a/layouts/partials/header.html
+++ b/layouts/partials/header.html
@@ -1,14 +1,10 @@
<header>
<nav id="menu">
- <div id="logotype">
- <a href="/" title="Go back to the home page">
- <img src="/i/pitivi-2019-icon.svg" alt="logo" />Pitivi</a>
- </div>
+ <a href="/" title="Go back to the home page" class="logo hidden">Pitivi</a>
<ul>
- {{ range .Site.Menus.main }}
- <li><a class="nav-link" href="{{ .URL }}" title="{{ .Title }}">
- {{- $text := print .Name | safeHTML -}}
- {{- $text -}}
+ {{- range .Site.Menus.main }}
+ <li><a href="{{ .URL }}" title="{{ .Title }}" class="hidden">
+ {{- .Name | safeHTML -}}
</a></li>
{{- end }}
</ul>
diff --git a/layouts/partials/metadata.html b/layouts/partials/metadata.html
index fdbc8be..b030b7a 100644
--- a/layouts/partials/metadata.html
+++ b/layouts/partials/metadata.html
@@ -1,4 +1,14 @@
-{{ $dateTime := .PublishDate.Format "2006-01-02" }}
-{{ $dateFormat := .Site.Params.dateFormat | default "Jan 2, 2006" }}
-<i class="fas fa-calendar-day"></i>
-<time datetime="{{ $dateTime }}">{{ .PublishDate.Format $dateFormat }}</time>
+<ul class="article-meta">
+ {{- $dateTime := .PublishDate.Format "2006-01-02" }}
+ {{- $dateFormat := .Site.Params.dateFormat | default "Jan 2, 2006" }}
+ <li class="article-meta-date"><time datetime="{{ $dateTime }}">{{ .PublishDate.Format $dateFormat
}}</time></li>
+ {{- if .Params.tags }}
+ {{- range .Params.tags }}
+ <li class="article-meta-tag">
+ <a href="{{ "/" | relURL }}tags/{{ . | urlize }}/" class="hidden">
+ <i class="fas fa-tag"></i>{{ . }}
+ </a>
+ </li>
+ {{- end }}
+ {{- end }}
+</ul>
diff --git a/static/css/pitivi.css b/static/css/pitivi.css
index 20b9a91..e257991 100644
--- a/static/css/pitivi.css
+++ b/static/css/pitivi.css
@@ -1,107 +1,93 @@
-/******************************
-DESIGN BY JEFF (NEKOHAYO)
-jeff.ecchi.ca
-
-Rsponsive and mobile first. No hacks. IE has <6% market share.
-Feel free to suggest improvements
- ******************************/
-
-/* NOTE: dumbass CSS doesn't understand "or" for media queries,
- you need to use commas, and do NOT forget parentheses. */
-
-
-/* LAYOUT BASE - mobile first, from which higher resolutions derive */
+/* Fonts from https://fonts.google.com */
+@import
url('https://fonts.googleapis.com/css2?family=Nunito:wght@200&family=Roboto+Mono&family=Roboto:wght@300;400&family=Source+Sans+Pro&display=swap');
+
body {
- font-family: "Droid Sans", Sans;
+ font-family: 'Roboto', sans-serif;
color: black;
background-color: white;
- margin: 0;
- padding: 0;
+ margin: 0 auto;
}
-header{
- width: 100%;
- /* "Pitivi Yellow": the SVG's transparent gradient will fade into this */
- background-color: #ffbe3b;
- background-image: url("/i/header-radial-bg.svg");
- background-repeat: no-repeat;
- /*
- This is the usual "Pitivi Yellow", but with a "groove" border
- instead of solid, which darkens it and creates a second "shadow" line: */
- border-bottom: 2px groove #ffbe3b;
+header > nav {
+ margin-left: auto;
+ margin-right: auto;
+ max-width: 950px;
+ padding-top: 1em;
}
- nav{
- margin-left: auto;
- margin-right: auto;
- font-weight: 200;
- width: 95%;
- min-height: 0; /* on mobile, don't use more space than necessary;
- the wrapped menu items automatically request more height anyway */
- }
+header > nav > .logo {
+ font-family: 'Nunito', sans-serif;
+ font-size: 250%;
+ font-weight: 400;
+ margin: 10em 0px 0.3em 8px;
- #logotype{
- float: left;
- margin-right: 1%;
- color: #fdfdfd;
- font-family: "Source Sans Pro";
- font-weight: 400;
- font-size: 200%;
- text-shadow: 1px 1px white;
- }
- #logotype img{
- width: 24px;
- }
- #logotype a{
- /*
- Almost black but not exactly; pure blacks don't exist in nature.
- Match the logo colors instead. */
- color: #2d2d2d;
- text-decoration: none;
- }
- #logotype a:hover{
- text-decoration: underline;
- }
+ background-image: url('/i/pitivi-2019-icon.svg');
+ background-position-x: left;
+ background-position-y: center;
+ background-size: 64px;
+ background-repeat: no-repeat;
+ padding-left: 70px;
+ padding-top: 12px;
+}
- nav ul{
- clear: left;
- padding: 0; /* no distanciation from the top */
- margin: 0; /* no offset from the logotype on the left */
- }
- nav ul li{
- display: inline;
- padding-left: 1%;
- padding-right: 1%;
- font-size: 120%;
- text-shadow: 1px 1px white;
- }
- nav li a{
- color: #004b6c; /* close to Navy Blue but less saturated */
- text-decoration: none;
- font-family: "Droid Sans", Sans;
- }
- nav li a:hover{
- color: #5891aa; /* lighter blue */
- text-decoration: underline;
- }
+header > nav > ul {
+ float: right;
+ padding: 0px;
+ margin: 1.1em 1em 2em 0px;
+}
+header > nav > ul > li {
+ display: inline;
+ margin-left: 1em;
+}
+header > nav > ul > li > a {
+ text-decoration: none;
+ font-size: 150%;
+ font-weight: 300;
+ font-family: 'Roboto', sans-serif;
+}
-footer{
- padding: 2%;
+#content {
+ max-width: 960px;
+ margin-left: auto;
+ margin-right: auto;
+}
+
+footer {
+ padding: 3em;
clear: both;
color: gray;
text-align: center;
}
-section{
- padding: 2%; /* For each column edge, substract this to calculate col size */
+section {
+ margin: 0em 1em;
+}
+
+section#frontpage_splash h1 {
+ font-family: 'Source Sans Pro', sans-serif;
}
-img{ /* Upscaling screenshots and such is not a good idea */
+section.centered-introduction {
+ max-width: 665px;
+ margin-left: auto;
+ margin-right: auto;
+ padding-left: 1em;
+ padding-right: 1em;
+ clear: both;
+}
+
+section.auto-column-half {
+ max-width: 440px;
+ float: left;
+}
+
+img {
+ /* Prevent upscaling which is particularly bad for screenshots. */
max-width: 100%;
height: auto;
}
-video{
+video {
/* Contrary to images, we can rarely predict the resolution of our videos
And they usually look better/more uniform when occupying the whole space */
width: 100%;
@@ -110,313 +96,100 @@ video{
}
/* Generic text styles */
-h1, h2, h3, h4, h5{
- font-family: "Source Sans Pro";
- font-weight: normal; /* Surprising, you actually HAVE to specify this thing */
-}
- h2{
- color: #94ac41;
- }
- h3{
- color: #8e8e8e;
- border-bottom-style: dotted;
- border-bottom-width: 1px;
- }
-a{
+a.hidden {
+ color: black;
+}
+
+a.discreet, a.hidden {
+ text-decoration: none;
+}
+a.discreet:hover, a.hidden:hover {
+ text-decoration: underline;
+ text-decoration-thickness: 1px;
+}
+
+h1, h2, h3, h4, h5 {
+ font-family: 'Source Sans Pro', sans-serif;
+ font-weight: 400;
+}
+h2 {
+ color: #94ac41;
+}
+
+h1 > img {
+ padding-top: 0.5em;
+}
+
+a {
color: #7590ae;
text-decoration: underline;
}
- a:hover{
- color: #90cf58;
- text-decoration: none;
- }
+a:hover {
+ color: #90cf58;
+ text-decoration: none;
+}
-ul{
- list-style-type: square;
+ul {
+ list-style-type: disc;
+ padding: 0;
}
-li{
+li {
margin-bottom: 0.5em;
}
-code{
- font-family: "Droid Sans Mono";
+time {
+ font-style: italic;
+}
+
+code {
+ font-family: 'Roboto Mono', monospace;
font-weight: bold;
color: white;
background-color: black;
padding: 3px;
}
-.frontpage_social_media_icon{
- border-style: none;
- /* 4 icons is 4x25%, but #news is a "section" with 2% padding (-2x2%/4) */
- width: 24%; height: 24%;
-}
-
-.centered-image{
+.centered-image {
display: block;
margin-left: auto;
margin-right: auto;
}
-/* SPECIFIC (ID) STYLES */
-#mission{
- clear: both;
- width: 80%;
- margin-left: auto; margin-right: auto;
- font-family: "Source Sans Pro";
- font-size: 110%;
- font-weight: normal; /* 400 */
-}
- #mission h1{
- margin-top: 0;
- font-size: 110%;
- font-weight: normal; /* 400, to be overridden at high resolutions */
- }
-
-#raw-features-list{
- clear: left;
+/* article */
+.article {
+ margin-bottom: 2em;
}
-
-/*--------------------------------------------------------------------------
- Progressive-enhancement of the responsive design, for higher resolutions
- -------------------------------------------------------------------------*/
-
-/* Anything bigger than ultra-small resolutions: */
-@media (min-width: 500px){
- nav ul li{
- font-size: 150%;
- }
- #mission{
- font-size: 130%;
- }
- #mission h1{
- font-size: 150%;
- }
- .frontpage_social_media_icon{
- max-width: 5em;
- }
-}
-@media (min-width: 850px){
- #mission{
- font-size: 150%;
- }
- #mission h1{
- font-size: 180%;
- font-weight: 200; /* slim glyphs to compensate the big font size */
- }
- .full-width-gallery{
- /* Fitting more text in less vertical space makes box floats easier */
- font-size: 90%;
- }
- /* We can fit roughly three "regular" boxes. Since we're in a section,
- we lose about 2*2% in padding, so 96% available. */
- .full-width-gallery .box{
- float: left;
- padding: 1%;
- width: 30%; /* 96% - 3 boxes * 2*1% = 90%, divided by 3 */
- }
- .full-width-gallery .box-huge{
- float: left;
- padding: 1%;
- /* roughly two boxes-wide: 96% - 2*1% padding - (30% + 1*2% padding) */
- width: 62%;
- }
- .auto-text-columns{
- column-count: 2;
- column-gap: 5%;
- /* Bitches. Please. This is 2013. */
- -moz-column-count: 2;
- -webkit-column-count: 2;
- -moz-column-gap: 5%;
- -webkit-column-gap: 5%;
- }
- .auto-column-half{
- /* A column part of a layout made of two columns when possible.
- Used for the Downloads page */
- float: left;
- width: 46%; /* 100% - 2*2*2% padding, divided by 2 columns */
- }
-
- .auto-column-third{
- /* A column part of a layout made of three columns when possible.
- Used for the Contribute and Contact pages */
- float: left;
- width: 29.333333333%; /* 100% - 3*2*2% padding, divided by 3 columns */
- }
+.article > .title {
+ margin-bottom: 0;
}
-@media (min-width: 1024px){
- nav{
- min-height: 80px;
- }
- nav #menu-links{
- /* The only way to actually have the menu items shifted downwards: */
- padding-top: 15px;
- }
- nav ul{
- clear:none; /* wrap around to the right of the logotype */
- margin-top: 0;
- padding-top: 30px; /* align with the pitivi logotype */
- margin-left: 20%;
- }
- #logotype{
- font-size: 400%;
- text-shadow: 1.5px 1.5px white;
- }
- #logotype img{
- width: 48px;
- }
- #news ul li{
- font-size: 90%;
- margin-left: -5%;
- }
- .frontpage_social_media_icon{
- max-width: 3em;
- }
+.article > .summary {
+ line-height: 1.5;
}
-
-/* Change the content layout for normal (sub-HD) computer screens,
- between 1024 and 1600 */
-@media screen and (min-width: 1024px) and (max-width: 1600px){
- /* There's 2% padding * 4 edges, so deduct 8%+ from the total.
- Also deduct whatever border width if present. */
- #frontpage_splash{
- float: left;
- width: 54%;
- /* Hack to regain 2% space between the columns,
- as the second column acts as psychovisual whitespace: */
- padding-right: 0;
- }
- #news{
- float: right;
- width: 40%;
- }
-}
-/* Middle-range screens */
-@media screen and (min-width: 1200px){
- nav{
- width: 80%;
- }
- #showcase_movies{
- float: left;
- /* This overrides "section"'s 100% width, but not the 2% padding,
- so the 70% feels like 74% of the page */
- width: 70%;
- padding: 1%; /* for the gallery: tighter padding than the default 2% */
- font-size: 80%;
- }
- #showcase_movies .box{ /* two "columns" of pitivi-made movies */
- float: left;
- margin-left: 0.5%;
- margin-right: 1%;
- width: 48.5%;
- }
- #showcase_talks{ /* only a single column of presentations */
- float: right;
- font-size: 80%;
- padding: 1%;
- border-left: 2px dotted gray;
- /* We get the remaining space after the 70% eaten by showcase_movies...
- 100% - 70% - padding around both sections (2*2*1%) - border */
- width: 25.5%;
- }
- .full-width-gallery .box{
- /* With 1% padding * 4 boxes: 2*4*1% = 8% eaten out of 96% available,
- so 88% left to divide by 4 boxes. */
- width: 31%;
- }
- .full-width-gallery .box-huge{
- /* roughly two boxes-wide (2 more on the right):
- 96% - 2*1% padding - 2*(22% + 2% padding) */
- width: 46%;
- }
- .auto-text-columns{
- column-count: 3;
- /* Bitches. Please. This is 2013. */
- -moz-column-count: 3;
- -webkit-column-count: 3;
- }
- #content{
- margin-left: 4em;
- margin-right: 4em;
- }
- .centered-introduction{
- max-width: 80%;
- margin-left: auto;
- margin-right: auto;
- border-bottom: 2px dotted #ccc;
- }
- .centered-non-responsive-contents{
- max-width: 1000px;
- margin-left: auto;
- margin-right: auto;
- }
+.article-meta {
+ list-style-type: none;
+ padding: 0;
+ margin: 5px 0 15px 0;
+ display: -webkit-flex;
+ display: flex;
+ -webkit-align-items: flex-end;
+ align-items: flex-end;
+ -webkit-flex-wrap: wrap;
+ flex-wrap: wrap;
+}
+.article-meta > li {
+ padding: 0;
+ padding-right: 4px;
+ margin: 0;
}
-
-
-
-
-/* Change the layout again for the full HD widescreen version */
-@media screen and (orientation: landscape) and (min-width: 1600px){
- /* 3 columns with 2% padding on each side means only 88% available,
- except that we'll hack the columns to regain 4+2+2%, so 96% available. */
- #mission{
- float: left;
- width: 25%;
- /* Regain 2% for frontpage_splash */
- padding-left: 1%;
- padding-right: 1%;
- }
- #frontpage_splash{
- float: left;
- width: 50%;
- /* Regain 4% space: */
- padding-left: 0;
- padding-right: 0;
- }
- #news{
- float: right;
- width: 20%;
- /* Regain 2% space for frontpage_splash */
- padding-right: 1%;
- padding-left: 1%;
- }
- .full-width-gallery .box{
- /* With 1% padding * 5 boxes: 2*5*1% = 10% eaten,
- so from a 96% available we go to 86% left to divide by 5 boxes. */
- width: 17.2%;
- }
- .full-width-gallery .box-huge{
- width: 55.5%; /* 3 boxes-wide, but saves 2*2*1% in padding so can be 4% larger */
- }
- .auto-text-columns{
- column-count: 4;
- /* Bitches. Please. This is 2013. */
- -moz-column-count: 4;
- -webkit-column-count: 4;
- }
-}
-/* Special case for a particular set of semi-HD resolutions where the missing text is too big and wraps too
much; we therefore knock back down to the size of the sub-850px media query. This will reset back to the
850px size when going full-HD. */
-@media screen and (min-width: 1600px) and (max-width: 1900px){
- #mission{
- font-size: 130%;
- }
- #mission h1{
- font-size: 150%;
- }
+.article-meta > li.article-meta-date {
+ padding: 0;
+ padding-right: 24px;
}
-
-
-/* TODO: figure out what we want to do with ridiculously big screens.
- This media query probably doesn't work anyway. */
-@media screen and (min-width: 1920px) and (min-resolution: 200dpi){
- .full-width-gallery{
- max-width: 2000px;
- margin-left: auto;
- margin-right: auto;
- }
+.article-meta > li.article-meta-tag > a > i {
+ margin-right: 0.2em;
}
diff --git a/static/i/screenshots/2020.05.png b/static/i/screenshots/2020.05.png
new file mode 100644
index 0000000..d0ca011
Binary files /dev/null and b/static/i/screenshots/2020.05.png differ
diff --git a/static/i/seasonofdocs_logo_secondarygrey.png b/static/i/seasonofdocs_logo_secondarygrey.png
new file mode 100644
index 0000000..0a9feaf
Binary files /dev/null and b/static/i/seasonofdocs_logo_secondarygrey.png differ
diff --git a/static/planet/atom.xml b/static/planet/atom.xml
index 4b34c65..fb680eb 100644
--- a/static/planet/atom.xml
+++ b/static/planet/atom.xml
@@ -775,7 +775,7 @@ The second step is to extend it to manage possible operations on tags in case mu
<p><a href="https://gitlab.gnome.org/gaharavara";>Abhishek Kumar Singh</a> will improve the Media Library.
The current implementation will be initially simplified to deal with a single Gtk.FlowBox container. Asset
tagging will provide the info to display in a new Folder View. The stretch goal is to display the assets by
date.</p>
<p><a href="https://gitlab.gnome.org/ayush9398";>Ayush Mittal</a> will improve the Render experience. The
current UI will be simplified, allowing the user to select a meaningful preset. Specifying the export quality
for the <a
href="https://gitlab.gnome.org/GNOME/pitivi/-/blob/413abf1f83bdac7d70863b91d820962b39cb9cac/pitivi/render.py#L89";>officially
supported encoders</a> will be possible using a slider widget. The advanced options will still be available
but not directly visible.</p>
<p><a href="https://gitlab.gnome.org/123vivekr";>Vivek R</a> will implement face/object tracking and
blurring. A new GStreamer plugin will allow tracking a specified region in the video using OpenCV. The
obtained tracking information is presented to the user to be reviewed and adjusted in a new UI Perspective.
The user can apply the adjusted positions to a blur effect applied to the clip.</p>
-<div>Please get in touch if you are interested in working with us. You can find us in <a
href="https://riot.im/app/#/room/%23pitivi:matrix.org"; rel="noopener"
target="_blank">https://riot.im/app/#/room/#pitivi:matrix.org</a></div></div>
+<div>Please get in touch if you are interested in working with us. You can find us in <a
href="https://matrix.to/#/#pitivi:matrix.org"; rel="noopener"
target="_blank">https://matrix.to/#/#pitivi:matrix.org</a></div></div>
</content>
<updated>2020-05-09T07:00:38Z</updated>
<category term="Non classé"/>
@@ -831,7 +831,7 @@ The second step is to extend it to manage possible operations on tags in case mu
<p>The latest Pitivi features should be documented in the user manual and the current content should be
brought up to date.</p>
<p>The user manual is kept in the <a
href="https://gitlab.gnome.org/GNOME/pitivi/-/tree/master/help/C";>Pitivi git repository</a> as <a
href="http://projectmallard.org/about/learn/tenminutes.html";>mallard</a> files.</p>
<h2>How to contact us</h2>
-<p>If interested, get in touch with us <a href="https://riot.im/app/#/room/#pitivi:matrix.org";>on
Matrix</a>, so we can prepare. You are expected to ask a lot of questions.</p>
+<p>If interested, get in touch with us <a href="https://matrix.to/#/#pitivi:matrix.org";>on Matrix</a>, so we
can prepare. You are expected to ask a lot of questions.</p>
<p> </p></div>
</content>
<updated>2020-05-02T12:40:20Z</updated>
@@ -1127,7 +1127,7 @@ This summer I had an entirely new experience about software development, and in
<title>Google Summer of Code with Pitivi</title>
<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><p><a
href="https://summerofcode.withgoogle.com/organizations/5699264502562816/";><img alt="GSoC with Pitivi"
src="https://yatinmaan.github.io/assets/images/gsoc_pitivi.png"; title="GSoC with Pitivi" width="720"/></a></p>
-<p>This summer I am working under the mentorship of <a
href="https://wiki.gnome.org/AlexB%C4%83lu%C8%9B";>Alexandru Băluț</a> to improve the user experience of the
Effects feature in <a href="http://www.pitivi.org/";>Pitivi</a>.</p>
+<p>This summer I am working under the mentorship of <a
href="https://wiki.gnome.org/AlexB%C4%83lu%C8%9B";>Alexandru Băluț</a> to improve the user experience of the
Effects feature in <a href="https://www.pitivi.org/";>Pitivi</a>.</p>
<p>In the first phase of <a href="https://summerofcode.withgoogle.com/projects/#4521665294237696";>my
project</a>, I worked on redesigning Pitivi’s “Effect Library” to allow users to easily find, organise and
utilize their desired effects.</p>
@@ -1217,7 +1217,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><p>Pitivi 1.0 is scheduled to be
released on Monday, May 20th. All the important bugs we were aware of have been fixed.</p>
<p>To fix one of the last issues, Thibault very recently rewrote the timeline/layers/clips management in
GES, and this might have introduced new bugs. While we have lots of tests which all pass, they don’t cover
everything.</p>
<p>We ask you to test the 1.0 RC! Grab a bunch of video files shot with your phone or camera and make some
video out of them, trying various features. Tell us if you notice problems, and if you can reproduce them
please file an issue describing the steps to reproduce the bug.</p>
-<p>You can find us in the <a href="https://www.irccloud.com/irc/freenode/channel/pitivi";>#pitivi IRC
channel</a> on FreeNode, or in this bridged <a
href="https://riot.im/develop/#/room/#pitivi:matrix.org";>Pitivi Matrix room</a>.</p>
+<p>You can find us in the <a href="https://www.irccloud.com/irc/freenode/channel/pitivi";>#pitivi IRC
channel</a> on FreeNode, or in this bridged <a href="https://matrix.to/#/#pitivi:matrix.org";>Pitivi Matrix
room</a>.</p>
<h2>How to install</h2>
<p>To install the Pitivi 1.0 RC, simply run:</p>
<pre>flatpak install http://flatpak.pitivi.org/pitivi.flatpakref</pre>
@@ -1226,7 +1226,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<p>Start Pitivi from the console, and keep it in view to notice any warnings or errors which might show
up:</p>
<pre>flatpak run org.pitivi.Pitivi//stable</pre>
<p>You should be able to use any video file supported by GStreamer, but we officially support only a limited
set of formats. If the file appears in the media library with a warning sign, right-click it and select proxy
to create an optimized media file used automatically instead of the original.</p>
-<p>Most useful would be to test the timeline editing, which should be responsive and precise. Try for
example <a href="https://www.pitivi.org/manual/splitting.html";>splitting</a> and <a
href="http://www.pitivi.org/manual/trimming.html";>trimming</a> clips, moving them around. Try ungrouping
audio-video clips to make the respective video shorter than the audio. Overlap clips to create cross-fade <a
href="https://www.pitivi.org/manual/transitions.html";>transitions</a>.</p>
+<p>Most useful would be to test the timeline editing, which should be responsive and precise. Try for
example <a href="https://www.pitivi.org/manual/splitting.html";>splitting</a> and <a
href="https://www.pitivi.org/manual/trimming.html";>trimming</a> clips, moving them around. Try ungrouping
audio-video clips to make the respective video shorter than the audio. Overlap clips to create cross-fade <a
href="https://www.pitivi.org/manual/transitions.html";>transitions</a>.</p>
<p>If time allows, you can also try adding effects, for example adding a background to a green screen. Mix
diverse footage formats in the same timeline. Make a slideshow and include title clips and background
music.</p>
<p>For reference, see the <a href="https://www.pitivi.org/manual/";>user manual</a>. At the end, please
render it and show us what you did!</p></div>
</content>
@@ -1257,7 +1257,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><h1>GStreamer Editing Services
OpenTimelineIO support</h1>
<p><a href="https://github.com/PixarAnimationStudios/OpenTimelineIO";>OpenTimelineIO</a> is an Open Source
API and interchange format for editorial timeline information, it basically allows some form of
interoperability between the different post production Video Editing tools. It is being developed by <a
href="http://graphics.pixar.com/";>Pixar</a> and several other studios are contributing to the project
allowing it to <a href="https://github.com/PixarAnimationStudios/OpenTimelineIO/commits/master";>evolve
quickly</a>.</p>
<p>We, at <a href="https://igalia.com";>Igalia</a>, recently <a
href="https://github.com/PixarAnimationStudios/OpenTimelineIO/pull/41";>landed</a> support for the <a
href="https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-editing-services/html/ges-architecture.html";>GStreamer
Editing Services</a> (GES) serialization format in OpenTimelineIO, making it possible to convert GES
timelines to any format supported by the library. This is extremely useful to integrate GES into existing
Post production workflow as it allows projects in any <a
href="https://opentimelineio.readthedocs.io/en/latest/tutorials/adapters.html";>format supported by
OpentTimelineIO</a> to be used in the GStreamer Editing Services and vice versa.</p>
-<p>On top of that we are building a <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/merge_requests/67";>GESFormatter</a> that
allows us to transparently handle any file format supported by OpenTimelineIO. In practice it will be
possible to use cuts produced by other video editing tools in any project using GES, for instance <a
href="http://www.pitivi.org";>Pitivi</a>:</p>
+<p>On top of that we are building a <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/merge_requests/67";>GESFormatter</a> that
allows us to transparently handle any file format supported by OpenTimelineIO. In practice it will be
possible to use cuts produced by other video editing tools in any project using GES, for instance <a
href="https://www.pitivi.org";>Pitivi</a>:</p>
<p><video controls="controls" height="150"
src="https://gitlab.gnome.org/thiblahute/blog/raw/master/OpenTimelineIO/OpenTimelineIODemoScreencast.mov?inline=false#t=0.01";
style="background-color: #050505; width: 512px; height: 216px;" width="300"/></p>
<p>At <a href="https://igalia.com";>Igalia</a> we are aiming at making GStreamer ready to be used in existing
Video post production pipelines and this work is one step in that direction. We are working on additional
features in GES to fill the gaps toward that goal, for instance we are now implementing <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/issues/60";>nested timeline</a> support
and <a href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/issues/61";>framerate based
timestamps</a> in GES. Once we implement them, those features will enhance compatibility of Video Editing
projects created from other NLE softwares through OpenTimelineIO. Stay tuned for more information!</p></div>
</content>
@@ -1307,7 +1307,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<p>The GES overviews and tutorials would be kept in the <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs";>GES git repository</a>
as markdown files. The API is documented in the <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/ges";>source code</a> written
in C.</p>
<p>To get a better idea about the GES API, check the <a
href="http://lazka.github.io/pgi-docs/#GES-1.0/hierarchy.html";>hierarchy of classes</a>.</p>
<p>The current <a href="https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html";>GES
documentation</a> is integrated into the GStreamer documentation. The structure is specified in <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/blob/master/docs/sitemap.txt";>docs/sitemap.txt</a>,
and the HTML is generated with <a href="https://hotdoc.github.io";>Hotdoc</a> out of the C files and <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs";>other markdown
bits</a>.</p>
-<p>If interested, <a href="http://www.pitivi.org/?go=contact";>get in touch</a> with us as soon as possible,
so we can prepare.</p>
+<p>If interested, <a href="https://www.pitivi.org/contact/";>get in touch</a> with us as soon as possible, so
we can prepare.</p>
<p> </p></div>
</content>
<updated>2019-04-16T07:06:28Z</updated>
@@ -1336,7 +1336,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<link href="http://www.blogger.com/feeds/6715983774773260157/posts/default/4457433090348633114";
rel="self" type="application/atom+xml"/>
<link href="http://blog.aleb.ro/2019/02/polishing-pitivis-viewer.html"; rel="alternate" title="Polishing
Pitivi's viewer" type="text/html"/>
<title>Polishing Pitivi's viewer</title>
- <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><div dir="ltr" style="text-align:
left;"><div style="text-align: left;">In the <a href="http://www.pitivi.org/";>Pitivi</a> video editor, the
viewer is quite important, as it shows the video. Our viewer also shows a discreet frame around a clip
selected in the timeline, making it easy to <a
href="https://lubosz.wordpress.com/2016/09/26/making-viewer-uis-for-pitivi/";>resize and position the video of
the clip by dragging</a>. Below is the story of the viewer updates in the past year.<br/><h2
style="text-align: left;">Easy resizing</h2>It was a bit cumbersome to have to drag both the left and bottom
margins of the viewer container to resize it. We thought it would be easier to resize the viewer by simply
dragging the bottom-left corner of its container. Harish Fulara made time at the end of his GSoC 2018
internship for this, after he finished his main task, and it works great! —<a
href="https://gitlab.gnome.org/GNOME/
pitivi/commit/25609f3ab7996e865ec275298c70a384823cabe3"> 25609f3a</a><br/><h2 style="text-align: left;">Are
we 100% yet?</h2>In Pitivi, the project resolution is conveniently set for new projects to match the first
imported video file, and can be changed at any time. This project resolution applies to the video content,
which at the end is resized when displayed by the viewer, depending on the size of the viewer. Of course
resizing introduces artifacts, so we need a way to have the viewer display the video content at 100%, pixel
for pixel.<br/><br/>Without introducing any new confusing UI, the simplest thing we could do was to show the
resize status while the viewer is resized. Now the video dims when you resize the viewer, to see clearly the
resize percent, and then is restored after a timeout with no change in size.<br/><br/>By connecting to the
widget's width/height property-change signals, <b>any</b> size change is detected, irrespective of what
caused it: the corner being dragg
ed, or the window being maximized, etc. Thanks again to Harish and his GSoC for implementing this! —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/d91c1283a85b4041e57253f7086ac2706f42acdd";>d91c1283</a>
<br/><br/>Sometimes it can be fiddly to set the viewer to 100%, since one pixel more and it's not 1:1
anymore. We thought about improving it by introducing snapping.<br/><h2 style="text-align:
left;">Snapping</h2>Unfortunately, with snapping you won't be able to set your viewer size to 101%, but in
return it's much easier to target 100%. Now the 100..105% range is down-snapped to 100%, to make it easy to
display the video content without any resize artifacts. Harish researched how we can do this, but as school
took him over, yours truly recently made time to finish the implementation. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/371581a01ba7c3c147b7fe61482a2016e207aaf6";>371581a0</a><br/><br/><div
class="separator" style="clear: both; text-align: center;"><a href="
https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s1600/Peek%2B2019-02-15%2B00-34.gif";
style="margin-left: 1em; margin-right: 1em;"><img border="0" height="209"
src="https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s400/Peek%2B2019-02-15%2B00-34.gif";
width="400"/></a></div><br/><br/>Once merged, looking back at my commit, like everybody does from time to
time, ..closely, some code cleanup commits popped up, like mushrooms after rain. It's pretty cloudy in
Zurich.<br/><h2 style="text-align: left;">Better trimming preview</h2><div style="text-align: left;">Normally
the viewer is used to display the project video at the playhead position, but we also use it to display the
start or end margins of a clip when it is being trimmed.</div></div><div style="text-align: left;"><br/>A
long time ago it used to be the case that we had to limit the seek rate when trimming, for performance r
easons, but now the seek is done async and our pipeline is smart enough to skip scheduled seeks if new ones
come in. With the limit removed, now the trim preview is more precise and (up to 200ms) snappier. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/42a7dc01e642d642d48b55d4d40a2ccbcdddbe2a";>42a7dc01</a><br/><br/>The
code responsible for the switch between the project video widget and the clip video widget, when
starting/finishing a trim operation, was very complex. It was checking in quite a few places, which one are
we dealing with: the pipeline of the project or the pipeline of the trimmed clip. By keeping separate
references to both, the logic is now much easier to read. As a bonus, now when the trim is finished, we
directly display the project video, without having to wait for the pipeline state to go from NULL to PAUSED.
—<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/03e15b44e8878d9c24fbd47b9477a695d2a24a50";>03e15b44</a><br/><br/>When
a trim operation was
being started, the trim preview was flickering. This was more noticeable when the end of the clip was
trimmed. The first frame of the clip was being displayed for a split second before the first seek is done.
Now we simply wait for the first seek to be performed before switching the viewer to show the trimming
preview. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/6d49ee544c28d666a38be2b12a302f4f93492ca4";>6d49ee54</a><br/><br/>It
takes a very short time until the pipeline for a clip trim preview is ready, but why not have it instantly?
At least when the user is focused on a handful of clips adjusting and trimming them, a cheap cache now does
the job. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/ec9ca33bae2279d4e8cf1e6b6dfc1c0d3e10dcc7";>ec9ca33b</a><br/><h2
style="text-align: left;">Contributing to Pitivi </h2><div style="text-align: left;">Pitivi benefits from
the <a href="https://en.wikipedia.org/wiki/GStreamer";>GStreamer</a> multimedia framework used on mos
t Linux desktops and we contribute back in multiple ways. We could use some more hands on Pitivi.
Contributions of any type would be greatly appreciated. Come <a
href="http://www.pitivi.org/?go=contact";>chat</a> with us. If you're a student, you can join us doing a <a
href="https://developer.pitivi.org/Google_Summer_of_Code.html";>GSoC</a> internship this summer!</div><div
style="text-align: left;"><br/></div></div></div></div>
+ <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><div dir="ltr" style="text-align:
left;"><div style="text-align: left;">In the <a href="https://www.pitivi.org/";>Pitivi</a> video editor, the
viewer is quite important, as it shows the video. Our viewer also shows a discreet frame around a clip
selected in the timeline, making it easy to <a
href="https://lubosz.wordpress.com/2016/09/26/making-viewer-uis-for-pitivi/";>resize and position the video of
the clip by dragging</a>. Below is the story of the viewer updates in the past year.<br/><h2
style="text-align: left;">Easy resizing</h2>It was a bit cumbersome to have to drag both the left and bottom
margins of the viewer container to resize it. We thought it would be easier to resize the viewer by simply
dragging the bottom-left corner of its container. Harish Fulara made time at the end of his GSoC 2018
internship for this, after he finished his main task, and it works great! —<a
href="https://gitlab.gnome.org/GNOME
/pitivi/commit/25609f3ab7996e865ec275298c70a384823cabe3"> 25609f3a</a><br/><h2 style="text-align: left;">Are
we 100% yet?</h2>In Pitivi, the project resolution is conveniently set for new projects to match the first
imported video file, and can be changed at any time. This project resolution applies to the video content,
which at the end is resized when displayed by the viewer, depending on the size of the viewer. Of course
resizing introduces artifacts, so we need a way to have the viewer display the video content at 100%, pixel
for pixel.<br/><br/>Without introducing any new confusing UI, the simplest thing we could do was to show the
resize status while the viewer is resized. Now the video dims when you resize the viewer, to see clearly the
resize percent, and then is restored after a timeout with no change in size.<br/><br/>By connecting to the
widget's width/height property-change signals, <b>any</b> size change is detected, irrespective of what
caused it: the corner being drag
ged, or the window being maximized, etc. Thanks again to Harish and his GSoC for implementing this! —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/d91c1283a85b4041e57253f7086ac2706f42acdd";>d91c1283</a>
<br/><br/>Sometimes it can be fiddly to set the viewer to 100%, since one pixel more and it's not 1:1
anymore. We thought about improving it by introducing snapping.<br/><h2 style="text-align:
left;">Snapping</h2>Unfortunately, with snapping you won't be able to set your viewer size to 101%, but in
return it's much easier to target 100%. Now the 100..105% range is down-snapped to 100%, to make it easy to
display the video content without any resize artifacts. Harish researched how we can do this, but as school
took him over, yours truly recently made time to finish the implementation. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/371581a01ba7c3c147b7fe61482a2016e207aaf6";>371581a0</a><br/><br/><div
class="separator" style="clear: both; text-align: center;"><a href=
"https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s1600/Peek%2B2019-02-15%2B00-34.gif";
style="margin-left: 1em; margin-right: 1em;"><img border="0" height="209"
src="https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s400/Peek%2B2019-02-15%2B00-34.gif";
width="400"/></a></div><br/><br/>Once merged, looking back at my commit, like everybody does from time to
time, ..closely, some code cleanup commits popped up, like mushrooms after rain. It's pretty cloudy in
Zurich.<br/><h2 style="text-align: left;">Better trimming preview</h2><div style="text-align: left;">Normally
the viewer is used to display the project video at the playhead position, but we also use it to display the
start or end margins of a clip when it is being trimmed.</div></div><div style="text-align: left;"><br/>A
long time ago it used to be the case that we had to limit the seek rate when trimming, for performance
reasons, but now the seek is done async and our pipeline is smart enough to skip scheduled seeks if new ones
come in. With the limit removed, now the trim preview is more precise and (up to 200ms) snappier. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/42a7dc01e642d642d48b55d4d40a2ccbcdddbe2a";>42a7dc01</a><br/><br/>The
code responsible for the switch between the project video widget and the clip video widget, when
starting/finishing a trim operation, was very complex. It was checking in quite a few places, which one are
we dealing with: the pipeline of the project or the pipeline of the trimmed clip. By keeping separate
references to both, the logic is now much easier to read. As a bonus, now when the trim is finished, we
directly display the project video, without having to wait for the pipeline state to go from NULL to PAUSED.
—<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/03e15b44e8878d9c24fbd47b9477a695d2a24a50";>03e15b44</a><br/><br/>When
a trim operation wa
s being started, the trim preview was flickering. This was more noticeable when the end of the clip was
trimmed. The first frame of the clip was being displayed for a split second before the first seek is done.
Now we simply wait for the first seek to be performed before switching the viewer to show the trimming
preview. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/6d49ee544c28d666a38be2b12a302f4f93492ca4";>6d49ee54</a><br/><br/>It
takes a very short time until the pipeline for a clip trim preview is ready, but why not have it instantly?
At least when the user is focused on a handful of clips adjusting and trimming them, a cheap cache now does
the job. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/ec9ca33bae2279d4e8cf1e6b6dfc1c0d3e10dcc7";>ec9ca33b</a><br/><h2
style="text-align: left;">Contributing to Pitivi </h2><div style="text-align: left;">Pitivi benefits from
the <a href="https://en.wikipedia.org/wiki/GStreamer";>GStreamer</a> multimedia framework used on mo
st Linux desktops and we contribute back in multiple ways. We could use some more hands on Pitivi.
Contributions of any type would be greatly appreciated. Come <a
href="https://www.pitivi.org/contact/";>chat</a> with us. If you're a student, you can join us doing a <a
href="https://developer.pitivi.org/Google_Summer_of_Code.html";>GSoC</a> internship this summer!</div><div
style="text-align: left;"><br/></div></div></div></div>
</content>
<updated>2019-02-14T23:43:00Z</updated>
<published>2019-02-14T23:38:00Z</published>
@@ -1561,7 +1561,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<id>https://yatinmaan.github.io/2018/08/07/Pitivis-Proxy-Preparation-Procedure</id>
<link href="https://yatinmaan.github.io/2018/08/07/Pitivis-Proxy-Preparation-Procedure/"; rel="alternate"
type="text/html"/>
<title>Pitivi's Proxy Preparation Procedure</title>
- <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><p><a href="http://www.pitivi.org/";><img
alt="Pitivi Logo" src="https://yatinmaan.github.io/assets/images/pitivi_logo_circle.png";
title="Pitivi"/></a></p>
+ <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><p><a
href="https://www.pitivi.org/";><img alt="Pitivi Logo"
src="https://yatinmaan.github.io/assets/images/pitivi_logo_circle.png"; title="Pitivi"/></a></p>
<p>Internally, most of the code for handling proxies resides in <code
class="highlighter-rouge">proxy.py</code> which exposes the <code
class="highlighter-rouge">proxy_manager</code> class to create and monitor proxy assets.</p>
@@ -1596,7 +1596,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<title>Google Summer of Code with GNOME</title>
<content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><p><a
href="https://summerofcode.withgoogle.com/organizations/5900447454330880/";><img alt="GSoC with GNOME"
src="https://yatinmaan.github.io/assets/images/gsoc_gnome.png"; title="GSoC with GNOME"/></a></p>
-<p>This summer I , under the mentorship of <a href="https://wiki.gnome.org/ThibaultSaunier";>Thibault
Saunier</a>, will be working on adding scaled proxies to <a href="http://www.pitivi.org/";>Pitivi</a>. While
Pitivi already provides its users the option to use Optimized Media (aka HQ Proxies) for problematic file
formats, having scaled proxies would allow them to transcode their high resolution video assets to a more
manageable resolution at the time of editing which would make both editing and previewing much quicker.</p>
+<p>This summer I , under the mentorship of <a href="https://wiki.gnome.org/ThibaultSaunier";>Thibault
Saunier</a>, will be working on adding scaled proxies to <a href="https://www.pitivi.org/";>Pitivi</a>. While
Pitivi already provides its users the option to use Optimized Media (aka HQ Proxies) for problematic file
formats, having scaled proxies would allow them to transcode their high resolution video assets to a more
manageable resolution at the time of editing which would make both editing and previewing much quicker.</p>
<p>Some of the other editors allow users to attach externally transcoded assets as proxies, this approach is
flexible but not very user friendly. Pitivi, a bit like Final Cut Pro, provides a single unified experience
where user can create and manage proxies right there in the application itself.</p>
@@ -2219,7 +2219,7 @@ place Important buttons like “New Project”, “Open Project”, etc. in th
<link href="http://www.blogger.com/feeds/6715983774773260157/posts/default/771481541238712904";
rel="self" type="application/atom+xml"/>
<link href="http://blog.aleb.ro/2015/10/pitivi-moves-from-bugzilla-to.html"; rel="alternate"
title="Pitivi moves from Bugzilla to Phabricator" type="text/html"/>
<title>Pitivi moves from Bugzilla to Phabricator</title>
- <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><div dir="ltr" style="text-align:
left;"><div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span
style="font-family: inherit;"><span style="background-color: transparent; color: black; font-size:
14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none;
vertical-align: baseline; white-space: pre-wrap;">Using Bugzilla to manage <a
href="http://www.pitivi.org/";>Pitivi</a> was a bit painful and we were looking for a replacement. Many
projects seemed to switch to Phabricator lately, which looked like a very good platform for managing
projects. We experimented migrating Bugzilla bugs to Phabricator, and we are pretty content with the result.
The UI is nicer, we have a better search function, and the Git integration (with the </span><a
href="https://phabricator.freedesktop.org/diffusion/"; style="text-decoration: none;"><span style="backgro
und-color: transparent; color: #1155cc; font-size: 14.666666666666666px; font-style: normal; font-variant:
normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">code
review</span></a><span style="background-color: transparent; color: black; font-size: 14.666666666666666px;
font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline;
white-space: pre-wrap;"> component) </span><a href="https://phabricator.freedesktop.org/diffusion/GITPHAB/";
style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-size:
14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline;
vertical-align: baseline; white-space: pre-wrap;">works great</span></a><span style="background-color:
transparent; color: black; font-size: 14.666666666666666px; font-style: normal; font-variant: normal;
font-weight: 400; text-decoration: none
; vertical-align: baseline; white-space: pre-wrap;">.</span></span></div><div style="line-height: 1.38;
margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span style="background-color: transparent; color:
black; font-family: inherit; font-size: 14.666666666666666px; font-style: normal; font-variant: normal;
font-weight: 400; text-decoration: none; vertical-align: baseline; white-space:
pre-wrap;"><br/></span></div><div style="text-align: left;"><span
id="docs-internal-guid-a56034b1-85da-e5ca-b5cc-0f96b7e878a7" style="font-family: inherit;"><span
style="color: black; font-size: 14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">We
decided to make the switch official, so we updated the documentation on the </span><a
href="http://wiki.pitivi.org/"; style="text-decoration: none;"><span style="color: #1155cc; font-size:
14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">wiki</span></a><span style="font-size: 14.666666
6666667px; vertical-align: baseline; white-space: pre-wrap;"> and </span><a href="http://www.pitivi.org/";
style="text-decoration: none;"><span style="color: #1155cc; font-size: 14.6666666666667px; text-decoration:
underline; vertical-align: baseline; white-space: pre-wrap;">website</span></a><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;"> to link to </span><a
href="https://phabricator.freedesktop.org/tag/pitivi/"; style="text-decoration: none;"><span style="color:
#1155cc; font-size: 14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">Phabricator</span></a><span style="font-size: 14.6666666666667px; vertical-align: baseline;
white-space: pre-wrap;">, closed the Pitivi Bugzilla “product” and closed the remaining bugs in Bugzilla with
a custom made script. The script also linked each bug to the proper task in
Phabricator.</span></span><br/><span style="font-family: inherit;"><span style="fo
nt-size: 14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;"><br/></span></span><span
style="font-family: inherit;"><span style="font-size: 14.6666666666667px; vertical-align: baseline;
white-space: pre-wrap;">For those new to Phabricator, remember that instead of creating a “bug” you create a
“task”.</span></span></div></div></div>
+ <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><div dir="ltr" style="text-align:
left;"><div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span
style="font-family: inherit;"><span style="background-color: transparent; color: black; font-size:
14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none;
vertical-align: baseline; white-space: pre-wrap;">Using Bugzilla to manage <a
href="https://www.pitivi.org/";>Pitivi</a> was a bit painful and we were looking for a replacement. Many
projects seemed to switch to Phabricator lately, which looked like a very good platform for managing
projects. We experimented migrating Bugzilla bugs to Phabricator, and we are pretty content with the result.
The UI is nicer, we have a better search function, and the Git integration (with the </span><a
href="https://phabricator.freedesktop.org/diffusion/"; style="text-decoration: none;"><span style="backgr
ound-color: transparent; color: #1155cc; font-size: 14.666666666666666px; font-style: normal; font-variant:
normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">code
review</span></a><span style="background-color: transparent; color: black; font-size: 14.666666666666666px;
font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline;
white-space: pre-wrap;"> component) </span><a href="https://phabricator.freedesktop.org/diffusion/GITPHAB/";
style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-size:
14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline;
vertical-align: baseline; white-space: pre-wrap;">works great</span></a><span style="background-color:
transparent; color: black; font-size: 14.666666666666666px; font-style: normal; font-variant: normal;
font-weight: 400; text-decoration: non
e; vertical-align: baseline; white-space: pre-wrap;">.</span></span></div><div style="line-height: 1.38;
margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span style="background-color: transparent; color:
black; font-family: inherit; font-size: 14.666666666666666px; font-style: normal; font-variant: normal;
font-weight: 400; text-decoration: none; vertical-align: baseline; white-space:
pre-wrap;"><br/></span></div><div style="text-align: left;"><span
id="docs-internal-guid-a56034b1-85da-e5ca-b5cc-0f96b7e878a7" style="font-family: inherit;"><span
style="color: black; font-size: 14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">We
decided to make the switch official, so we updated the documentation on the </span><a
href="http://wiki.pitivi.org/"; style="text-decoration: none;"><span style="color: #1155cc; font-size:
14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">wiki</span></a><span style="font-size: 14.66666
66666667px; vertical-align: baseline; white-space: pre-wrap;"> and </span><a href="https://www.pitivi.org/";
style="text-decoration: none;"><span style="color: #1155cc; font-size: 14.6666666666667px; text-decoration:
underline; vertical-align: baseline; white-space: pre-wrap;">website</span></a><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;"> to link to </span><a
href="https://phabricator.freedesktop.org/tag/pitivi/"; style="text-decoration: none;"><span style="color:
#1155cc; font-size: 14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">Phabricator</span></a><span style="font-size: 14.6666666666667px; vertical-align: baseline;
white-space: pre-wrap;">, closed the Pitivi Bugzilla “product” and closed the remaining bugs in Bugzilla with
a custom made script. The script also linked each bug to the proper task in
Phabricator.</span></span><br/><span style="font-family: inherit;"><span style="
font-size: 14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;"><br/></span></span><span
style="font-family: inherit;"><span style="font-size: 14.6666666666667px; vertical-align: baseline;
white-space: pre-wrap;">For those new to Phabricator, remember that instead of creating a “bug” you create a
“task”.</span></span></div></div></div>
</content>
<updated>2018-04-12T14:51:24Z</updated>
<published>2015-10-20T15:31:00Z</published>
@@ -2338,7 +2338,7 @@ place Important buttons like “New Project”, “Open Project”, etc. in th
<link href="http://www.blogger.com/feeds/6715983774773260157/posts/default/5778595438816221362";
rel="self" type="application/atom+xml"/>
<link href="http://blog.aleb.ro/2016/01/polishing-pitivis-ruler.html"; rel="alternate" title="Polishing
Pitivi's ruler" type="text/html"/>
<title>Polishing Pitivi's ruler</title>
- <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><div dir="ltr" style="text-align:
left;"><br/><br/>In Pitivi, the ruler is displayed above the timeline to show the times corresponding with
the current view. A series of H:MM:SS.XXX timestamps on a ruler might leave the impression that only trained
professionals are supposed to use it. I had trouble reading the timestamps and looked for ways to make the
ruler more useful. Read below for the story.<br/><br/><div style="text-align: center;"><div class="separator"
style="clear: both; text-align: center;"><a
href="http://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"/></a></div>Pitivi
ruler, Dec 2013</div><br/><h2 style="text-align: left;">Relevant parts</h2>Around the New Year 2013-2014 I
thought about highlighting the rel
evant parts in the timestamp. For example, if you have 0:00:05.000 and then 0:00:10.000, you have to look
quite a bit until you notice what changes from one to the other. In this case the "10" should be highlighted
because that's different than the previous timestamp. This way it's easier to see what an interval
represents. Jeff liked the idea and the commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=a7cb639b8ac8750edd44125a7ea0a3fd0601a5bf";>went
in</a>.<br/><div><br/>The ruler being more useful, I started to look more at it while using Pitivi. One week
later, after 6 code cleanup commits, the millis were being displayed with a smaller font, so they can be
ignored more easily. One hour later though, the hours and millis were being displayed only when
useful:<br/><ul style="text-align: left;"><li>The hour is displayed only if greater than 0. </li><li>The
millis are displayed only when the zoom level is high enough that millis other than “.000��
� start to show up in the timestamps. This got improved later!</li></ul>The shorter timestamps looked good
so the changes <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=7a301c8787ce264efcb766e050ed7500ac5599f3";>went</a>
<a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3f78e856c4566712d3a5ccb161e40748ab08d3b6";>in</a>.<br/><br/>Guessing
most projects are less than one hour long and most of the time users don't use zoom levels where
milliseconds matter—this was already a big improvement, it’s much easier to see “MM:SS” than
“0:MM:SS.000”.<br/><br/><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png";><img
border="0"
src="https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"/></a></div><div
style="text-align: center;">Pitivi ruler zoomed out, Jan 2014</div><br/></div><h2 style="text-align: left;">D
ividing an interval</h2>An “interval” on the ruler is the interval at which the timestamps are shown. At
different zoom levels, the length of the interval is picked automatically out of a hardcoded list, so you see
an optimum number of timestamps. It was awkward that the displayed intervals were always divided in 10 parts.
While it makes sense for a 10 seconds interval to be divided by 10, it’s not very useful when a 30 minutes
interval is divided by 10.<br/><div><br/>It was easy to define the tick frequency for each of the hardcoded
intervals, but it looked awkward for most of the zoom levels. Previously we clearly preferred largish
interval sizes (so the interval can be divided in 10 smaller but still visible units) but it was not so nice
anymore when a large interval is divided only in 2 units. Some fine-tune of the minimum interval length and
the minimum division length was required. The smaller timestamps fit great with the smaller
intervals:</div><div><br/></div><div cla
ss="separator" style="clear: both; text-align: center;"><a
href="http://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s1600/interval.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png"/></a></div><div><div
style="text-align: center;">Dividing by 2 is enough for some intervals, Dec 2015</div><br/><h2
style="text-align: left;">Timestamp shape</h2>While fine-tuning the minimum interval and interval division
size, I realized that when displaying millis, it’s useful to display <b>only</b> the millis, except for the
full second timestamps when <b>only</b> [H:]MM:SS is displayed. This way it’s much easier to see where the
full seconds are, because “00:01” looks quite different shape-wise than “<span style="font-size:
x-small;">.500</span>” which is displayed with a smaller font. Luckily, by keeping all the timestamps short
(“<span style="font-
size: x-small;">.900</span>” is the shortest and “9:00:00” is the longest), it was possible to have a simple
formula for choosing the optimum interval per zoom level.<br/><br/><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s1600/second.png";><img
border="0"
src="https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png"/></a></div><div
style="text-align: center;">Pitivi ruler zoomed in, Jan 2016</div><br/>The commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=c5e5d11ae5230d59bd1a356d54961c45460e06cd";>went
in</a>, along with <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3c5859f0b22ae2f4f1daf69a7ffe27ccd025786b";>a
cherry</a>.<br/><br/>Some did not like the pear-shaped playhead though, so we later replaced it with an
empty diamond.<br/><br/><div style="text-align: center;"><a href="http://3.bp.blogspot.com/-yVjI
J-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s1600/new_playhead_500.png"><img
border="0"
src="https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png"/></a></div><div
style="text-align: center;">Pitivi playhead, Apr 2016</div><br/>Start Pitivi and look at the ruler, zooming
in and out, a nice feeling starts bubbling up inside.<br/><div><br/>Until we wrap up 0.96, you can already
see the ruler in action by downloading the Pitivi <a href="http://www.pitivi.org/?go=download";>bundle</a>!
BTW, the bundle already includes the proxy files functionality which allows using any video format reliably.
Read: no more artifacts when using MTS files. When compared, the ruler polishing I described above is just me
playing in the sand. The proxy files functionality brings Pitivi much closer to 1.0. Please try it out and
tell us how it works for you! :)<br/><div dir="ltr" style="line-height: 1.38; margin-b
ottom: 0pt; margin-top: 0pt;"/><div><br/></div><div>If you are still here, see maybe the entire <a
href="https://git.gnome.org/browse/pitivi/log/pitivi/timeline/ruler.py";>history</a> of Pitivi’s <a
href="https://git.gnome.org/browse/pitivi/tree/pitivi/timeline/ruler.py";>ruler</a>.</div></div></div></div></div>
+ <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml";><div dir="ltr" style="text-align:
left;"><br/><br/>In Pitivi, the ruler is displayed above the timeline to show the times corresponding with
the current view. A series of H:MM:SS.XXX timestamps on a ruler might leave the impression that only trained
professionals are supposed to use it. I had trouble reading the timestamps and looked for ways to make the
ruler more useful. Read below for the story.<br/><br/><div style="text-align: center;"><div class="separator"
style="clear: both; text-align: center;"><a
href="http://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"/></a></div>Pitivi
ruler, Dec 2013</div><br/><h2 style="text-align: left;">Relevant parts</h2>Around the New Year 2013-2014 I
thought about highlighting the rel
evant parts in the timestamp. For example, if you have 0:00:05.000 and then 0:00:10.000, you have to look
quite a bit until you notice what changes from one to the other. In this case the "10" should be highlighted
because that's different than the previous timestamp. This way it's easier to see what an interval
represents. Jeff liked the idea and the commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=a7cb639b8ac8750edd44125a7ea0a3fd0601a5bf";>went
in</a>.<br/><div><br/>The ruler being more useful, I started to look more at it while using Pitivi. One week
later, after 6 code cleanup commits, the millis were being displayed with a smaller font, so they can be
ignored more easily. One hour later though, the hours and millis were being displayed only when
useful:<br/><ul style="text-align: left;"><li>The hour is displayed only if greater than 0. </li><li>The
millis are displayed only when the zoom level is high enough that millis other than “.000��
� start to show up in the timestamps. This got improved later!</li></ul>The shorter timestamps looked good
so the changes <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=7a301c8787ce264efcb766e050ed7500ac5599f3";>went</a>
<a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3f78e856c4566712d3a5ccb161e40748ab08d3b6";>in</a>.<br/><br/>Guessing
most projects are less than one hour long and most of the time users don't use zoom levels where
milliseconds matter—this was already a big improvement, it’s much easier to see “MM:SS” than
“0:MM:SS.000”.<br/><br/><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png";><img
border="0"
src="https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"/></a></div><div
style="text-align: center;">Pitivi ruler zoomed out, Jan 2014</div><br/></div><h2 style="text-align: left;">D
ividing an interval</h2>An “interval” on the ruler is the interval at which the timestamps are shown. At
different zoom levels, the length of the interval is picked automatically out of a hardcoded list, so you see
an optimum number of timestamps. It was awkward that the displayed intervals were always divided in 10 parts.
While it makes sense for a 10 seconds interval to be divided by 10, it’s not very useful when a 30 minutes
interval is divided by 10.<br/><div><br/>It was easy to define the tick frequency for each of the hardcoded
intervals, but it looked awkward for most of the zoom levels. Previously we clearly preferred largish
interval sizes (so the interval can be divided in 10 smaller but still visible units) but it was not so nice
anymore when a large interval is divided only in 2 units. Some fine-tune of the minimum interval length and
the minimum division length was required. The smaller timestamps fit great with the smaller
intervals:</div><div><br/></div><div cla
ss="separator" style="clear: both; text-align: center;"><a
href="http://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s1600/interval.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png"/></a></div><div><div
style="text-align: center;">Dividing by 2 is enough for some intervals, Dec 2015</div><br/><h2
style="text-align: left;">Timestamp shape</h2>While fine-tuning the minimum interval and interval division
size, I realized that when displaying millis, it’s useful to display <b>only</b> the millis, except for the
full second timestamps when <b>only</b> [H:]MM:SS is displayed. This way it’s much easier to see where the
full seconds are, because “00:01” looks quite different shape-wise than “<span style="font-size:
x-small;">.500</span>” which is displayed with a smaller font. Luckily, by keeping all the timestamps short
(“<span style="font-
size: x-small;">.900</span>” is the shortest and “9:00:00” is the longest), it was possible to have a simple
formula for choosing the optimum interval per zoom level.<br/><br/><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s1600/second.png";><img
border="0"
src="https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png"/></a></div><div
style="text-align: center;">Pitivi ruler zoomed in, Jan 2016</div><br/>The commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=c5e5d11ae5230d59bd1a356d54961c45460e06cd";>went
in</a>, along with <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3c5859f0b22ae2f4f1daf69a7ffe27ccd025786b";>a
cherry</a>.<br/><br/>Some did not like the pear-shaped playhead though, so we later replaced it with an
empty diamond.<br/><br/><div style="text-align: center;"><a href="http://3.bp.blogspot.com/-yVjI
J-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s1600/new_playhead_500.png"><img
border="0"
src="https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png"/></a></div><div
style="text-align: center;">Pitivi playhead, Apr 2016</div><br/>Start Pitivi and look at the ruler, zooming
in and out, a nice feeling starts bubbling up inside.<br/><div><br/>Until we wrap up 0.96, you can already
see the ruler in action by downloading the Pitivi <a href="https://www.pitivi.org/download/";>bundle</a>! BTW,
the bundle already includes the proxy files functionality which allows using any video format reliably. Read:
no more artifacts when using MTS files. When compared, the ruler polishing I described above is just me
playing in the sand. The proxy files functionality brings Pitivi much closer to 1.0. Please try it out and
tell us how it works for you! :)<br/><div dir="ltr" style="line-height: 1.38; margin-bot
tom: 0pt; margin-top: 0pt;"/><div><br/></div><div>If you are still here, see maybe the entire <a
href="https://git.gnome.org/browse/pitivi/log/pitivi/timeline/ruler.py";>history</a> of Pitivi’s <a
href="https://git.gnome.org/browse/pitivi/tree/pitivi/timeline/ruler.py";>ruler</a>.</div></div></div></div></div>
</content>
<updated>2018-04-12T14:45:57Z</updated>
<published>2016-01-23T02:28:00Z</published>
@@ -2414,7 +2414,7 @@ place Important buttons like “New Project”, “Open Project”, etc. in th
<p>This summer we had three GSoC Pitivi projects. The GSoC work has been merged on the “master” branch and
we made a separate “1.0” branch where we implement or backport the relevant fixes. A special thank you to
Suhas Nayak and Ștefan-Adrian Popa, two of our GSoC students who contributed a large number of bugfixes and
made possible this release.</p>
<h3>1.0</h3>
<p>As you might know, we’re focused on bug fixing until Pitivi 1.0. See what’s left to do for 1.0 in <a
href="https://phabricator.freedesktop.org/project/view/125/";>Phabricator</a>.</p>
-<p>We need people to test Pitivi (the Flatpak “stable” branch) and report back any crash or stability issue
they notice, so we fix it. — If you want to <a href="http://www.pitivi.org/?go=contributing";>help</a> in any
way, come to our <a href="http://www.pitivi.org/?go=contact";>IRC channel</a>.</p></div>
+<p>We need people to test Pitivi (the Flatpak “stable” branch) and report back any crash or stability issue
they notice, so we fix it. — If you want to <a href="https://www.pitivi.org/contribute/";>help</a> in any way,
come to our <a href="https://www.pitivi.org/contact/";>IRC channel</a>.</p></div>
</content>
<updated>2017-09-22T11:40:35Z</updated>
<category term="release"/>
diff --git a/static/planet/feeds.html b/static/planet/feeds.html
index efb7ab0..fd793b1 100644
--- a/static/planet/feeds.html
+++ b/static/planet/feeds.html
@@ -1 +1,26 @@
-<ul><li><a href="https://gaharavara.github.io/pitivi-rss.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://gaharavara.github.io"; title="gaharavara's ScrapBook">Abhishek Kumar Singh</a></li><li><a
href="http://blog.aleb.ro/feeds/posts/default/-/pitivi"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://blog.aleb.ro/search/label/pitivi"; class="message" title="404: not found">Alexandru Băluț
(aleb)</a></li><li><a href="https://ayush9398.github.io/blog/feed/pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://ayush9398.github.io/blog/"; title="ayush9398 | Pitivi">Ayush Mittal</a></li><li><a
href="http://dotsony.blogspot.com/feeds/posts/default?alt=rss"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://dotsony.blogspot.com/"; title="
.sony">Brandon Lewis</a></li><li><a href="https://dthul.de/?feed=rss2&tag=pitivi"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="http://8na.de"; title="8na »
PiTiVi">Daniel Thul (daniel90)</a></li><li><a href="https://blogs.gnome.org/edwardrv/feed/";
title="Subscribe"><img src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://blogs.gnome.org/edwardrv"; title="Edward Hervey">Edward Hervey</a></li><li><a
href="http://cfoch-dev.tumblr.com/tagged/pitivi/rss"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://cfoch-dev.tumblr.com/"; title="cfoch-dev: non-confidential development files">Fabian Orccon
(cfoch)</a></li><li><a href="https://cfoch.github.io/tags/rss/pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="https://cfoch.github.io";
title="Fabián Orccón - pitivi">Fabia
n Orccon (cfoch)</a></li><li><a href="https://harishfulara07.wordpress.com/tag/pitivi/feed/";
title="Subscribe"><img src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://harishfulara07.wordpress.com"; title="pitivi – My Journey in Open Source World">Harish
Fulara</a></li><li><a href="http://www.jakubbrindza.com/feeds/posts/default/-/Pitivi/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://www.jakubbrindza.com/search/label/Pitivi"; title="GSoC by me, a curious enthusiast">Jakub
Brindza</a></li><li><a href="https://fortintam.com/blog/category/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="https://fortintam.com/blog";
title="Pitivi – The Open Sourcerer">Jean-François Fortin Tam (nekohayo)</a></li><li><a
href="https://lubosz.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-ic
on-10x10.png" alt="(feed)"></a> <a href="https://lubosz.wordpress.com"; title="pitivi – Lubosz's Blog">Lubosz
Sarnecki</a></li><li><a href="http://mathieuduponchelle.github.io/atom.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://http://mathieuduponchelle.github.io/"; title="Mathieu Duponchelle">Mathieu
Duponchelle</a></li><li><a href="http://mathieuduponchelle.blogspot.com/feeds/posts/default";
title="Subscribe"><img src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://mathieuduponchelle.blogspot.com/"; title="Mathieu Duponchelle">Mathieu Duponchelle</a></li><li><a
href="https://millancv.github.io/feed.category.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="https://millancv.github.io/";
title="m.castro - Pitivi">Millan Castro</a></li><li><a href="https://palango.wordpress.com/feed/";
title="Subscribe"><img src="http://planet
.gnome.org/img/feed-icon-10x10.png" alt="(feed)"></a> <a href="https://palango.wordpress.com"; title="Moving
pictures…">Paul Lange (palango)</a></li><li><a href="https://pitivi.wordpress.com/feed/";
title="Subscribe"><img src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://pitivi.wordpress.com"; title="Pitivi">Pitivi fundraiser news</a></li><li><a
href="https://stefanpopablog.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://stefanpopablog.wordpress.com"; title="pitivi – Sailing through the code">Stefan-Adrian Popa
(stefanzzz)</a></li><li><a href="https://suhas2go.github.io/feed.pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="http://suhas2go.github.io/";
title="suhas2go">Suhas Nayak (suhas2go)</a></li><li><a
href="https://swaynethoughts.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><i
mg src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://swaynethoughts.wordpress.com"; title="Pitivi – SWAYNE THOUGHTS">Swayamjeet Swain</a></li><li><a
href="https://blogs.gnome.org/tsaunier/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://blogs.gnome.org/tsaunier"; title="Thibault Saunier's blog">Thibault Saunier
(thiblahute)</a></li><li><a href="http://thiblahute.blogspot.com/feeds/posts/default"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://thiblahute.blogspot.com/"; title="Thibault Saunier">Thibault Saunier (thiblahute)</a></li><li><a
href="https://kargertom.wordpress.com/category/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://kargertom.wordpress.com"; title="Pitivi – TomKarger">Tomas Karger</a></li><li><a
href="https://123vivekr.git
hub.io/pitivi.xml" title="Subscribe"><img src="http://planet.gnome.org/img/feed-icon-10x10.png";
alt="(feed)"></a> <a href="https://123vivekr.github.io/123vivekr.github.io/"; title="123vivekr">Vivek
R.</a></li><li><a href="https://yatinmaan.github.io/pitivi-feed.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://yatinmaan.github.io/"; title="/dev/output">Yatin Maan</a></li></ul>
+<ul>
+ <li><a href="https://gaharavara.github.io/pitivi-rss.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://gaharavara.github.io"; title="gaharavara's ScrapBook">Abhishek Kumar Singh</a></li>
+ <li><a href="https://aleb.ro/tags/pitivi/index.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://aleb.ro/tags/pitivi/"; class="message" title="Notes">Alexandru Băluț (aleb)</a></li>
+ <li><a href="https://ayush9398.github.io/blog/feed/pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://ayush9398.github.io/blog/"; title="ayush9398 | Pitivi">Ayush Mittal</a></li>
+ <li><a href="http://dotsony.blogspot.com/feeds/posts/default?alt=rss"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://dotsony.blogspot.com/"; title=".sony">Brandon Lewis</a></li>
+ <li><a href="https://dthul.de/?feed=rss2&tag=pitivi"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="http://8na.de"; title="8na »
PiTiVi">Daniel Thul (daniel90)</a></li>
+ <li><a href="https://blogs.gnome.org/edwardrv/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://blogs.gnome.org/edwardrv"; title="Edward Hervey">Edward Hervey</a></li>
+ <li><a href="http://cfoch-dev.tumblr.com/tagged/pitivi/rss"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://cfoch-dev.tumblr.com/"; title="cfoch-dev: non-confidential development files">Fabian Orccon
(cfoch)</a></li>
+ <li><a href="https://cfoch.github.io/tags/rss/pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="https://cfoch.github.io";
title="Fabián Orccón - pitivi">Fabian Orccon (cfoch)</a></li>
+ <li><a href="https://harishfulara07.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://harishfulara07.wordpress.com"; title="pitivi – My Journey in Open Source World">Harish
Fulara</a></li>
+ <li><a href="http://www.jakubbrindza.com/feeds/posts/default/-/Pitivi/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://www.jakubbrindza.com/search/label/Pitivi"; title="GSoC by me, a curious enthusiast">Jakub
Brindza</a></li>
+ <li><a href="https://fortintam.com/blog/category/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="https://fortintam.com/blog";
title="Pitivi – The Open Sourcerer">Jean-François Fortin Tam (nekohayo)</a></li>
+ <li><a href="https://lubosz.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://lubosz.wordpress.com"; title="pitivi – Lubosz's Blog">Lubosz Sarnecki</a></li>
+ <li><a href="http://mathieuduponchelle.github.io/atom.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://http://mathieuduponchelle.github.io/"; title="Mathieu Duponchelle">Mathieu Duponchelle</a></li>
+ <li><a href="http://mathieuduponchelle.blogspot.com/feeds/posts/default"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://mathieuduponchelle.blogspot.com/"; title="Mathieu Duponchelle">Mathieu Duponchelle</a></li>
+ <li><a href="https://millancv.github.io/feed.category.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="https://millancv.github.io/";
title="m.castro - Pitivi">Millan Castro</a></li>
+ <li><a href="https://palango.wordpress.com/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://palango.wordpress.com"; title="Moving pictures…">Paul Lange (palango)</a></li>
+ <li><a href="https://stefanpopablog.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://stefanpopablog.wordpress.com"; title="pitivi – Sailing through the code">Stefan-Adrian Popa
(stefanzzz)</a></li>
+ <li><a href="https://suhas2go.github.io/feed.pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a href="http://suhas2go.github.io/";
title="suhas2go">Suhas Nayak (suhas2go)</a></li>
+ <li><a href="https://swaynethoughts.wordpress.com/tag/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://swaynethoughts.wordpress.com"; title="Pitivi – SWAYNE THOUGHTS">Swayamjeet Swain</a></li>
+ <li><a href="https://blogs.gnome.org/tsaunier/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://blogs.gnome.org/tsaunier"; title="Thibault Saunier's blog">Thibault Saunier (thiblahute)</a></li>
+ <li><a href="http://thiblahute.blogspot.com/feeds/posts/default"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="http://thiblahute.blogspot.com/"; title="Thibault Saunier">Thibault Saunier (thiblahute)</a></li>
+ <li><a href="https://kargertom.wordpress.com/category/pitivi/feed/"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://kargertom.wordpress.com"; title="Pitivi – TomKarger">Tomas Karger</a></li>
+ <li><a href="https://123vivekr.github.io/pitivi.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://123vivekr.github.io/123vivekr.github.io/"; title="123vivekr">Vivek R.</a></li>
+ <li><a href="https://yatinmaan.github.io/pitivi-feed.xml"; title="Subscribe"><img
src="http://planet.gnome.org/img/feed-icon-10x10.png"; alt="(feed)"></a> <a
href="https://yatinmaan.github.io/"; title="/dev/output">Yatin Maan</a></li>
+</ul>
diff --git a/static/planet/index.html b/static/planet/index.html
index 1db61fd..f64959d 100644
--- a/static/planet/index.html
+++ b/static/planet/index.html
@@ -801,7 +801,7 @@ The second step is to extend it to manage possible operations on tags in case mu
<p><a href="https://gitlab.gnome.org/gaharavara";>Abhishek Kumar Singh</a> will improve the Media Library.
The current implementation will be initially simplified to deal with a single Gtk.FlowBox container. Asset
tagging will provide the info to display in a new Folder View. The stretch goal is to display the assets by
date.</p>
<p><a href="https://gitlab.gnome.org/ayush9398";>Ayush Mittal</a> will improve the Render experience. The
current UI will be simplified, allowing the user to select a meaningful preset. Specifying the export quality
for the <a
href="https://gitlab.gnome.org/GNOME/pitivi/-/blob/413abf1f83bdac7d70863b91d820962b39cb9cac/pitivi/render.py#L89";>officially
supported encoders</a> will be possible using a slider widget. The advanced options will still be available
but not directly visible.</p>
<p><a href="https://gitlab.gnome.org/123vivekr";>Vivek R</a> will implement face/object tracking and
blurring. A new GStreamer plugin will allow tracking a specified region in the video using OpenCV. The
obtained tracking information is presented to the user to be reviewed and adjusted in a new UI Perspective.
The user can apply the adjusted positions to a blur effect applied to the clip.</p>
-<div>Please get in touch if you are interested in working with us. You can find us in <a
href="https://riot.im/app/#/room/%23pitivi:matrix.org"; rel="noopener"
target="_blank">https://riot.im/app/#/room/#pitivi:matrix.org</a></div> </div> <!--
/post-contents -->
+<div>Please get in touch if you are interested in working with us. You can find us in <a
href="https://matrix.to/#/#pitivi:matrix.org"; rel="noopener"
target="_blank">https://matrix.to/#/#pitivi:matrix.org</a></div> </div> <!--
/post-contents -->
<div class="post-footer">
<p><a
href="https://pitivi.wordpress.com/2020/05/09/presenting-our-google-summer-of-code-students/";>May 09, 2020
07:00 AM</a></p>
@@ -852,7 +852,7 @@ The second step is to extend it to manage possible operations on tags in case mu
<p>The latest Pitivi features should be documented in the user manual and the current content should be
brought up to date.</p>
<p>The user manual is kept in the <a
href="https://gitlab.gnome.org/GNOME/pitivi/-/tree/master/help/C";>Pitivi git repository</a> as <a
href="http://projectmallard.org/about/learn/tenminutes.html";>mallard</a> files.</p>
<h2>How to contact us</h2>
-<p>If interested, get in touch with us <a href="https://riot.im/app/#/room/#pitivi:matrix.org";>on
Matrix</a>, so we can prepare. You are expected to ask a lot of questions.</p>
+<p>If interested, get in touch with us <a href="https://matrix.to/#/#pitivi:matrix.org";>on Matrix</a>, so we
can prepare. You are expected to ask a lot of questions.</p>
<p> </p> </div> <!-- /post-contents -->
<div class="post-footer">
@@ -1147,7 +1147,7 @@ This summer I had an entirely new experience about software development, and in
<div class="post-contents ">
<p><a href="https://summerofcode.withgoogle.com/organizations/5699264502562816/";><img alt="GSoC with Pitivi"
src="https://yatinmaan.github.io/assets/images/gsoc_pitivi.png"; title="GSoC with Pitivi" width="720"
/></a></p>
-<p>This summer I am working under the mentorship of <a
href="https://wiki.gnome.org/AlexB%C4%83lu%C8%9B";>Alexandru Băluț</a> to improve the user experience of the
Effects feature in <a href="http://www.pitivi.org/";>Pitivi</a>.</p>
+<p>This summer I am working under the mentorship of <a
href="https://wiki.gnome.org/AlexB%C4%83lu%C8%9B";>Alexandru Băluț</a> to improve the user experience of the
Effects feature in <a href="https://www.pitivi.org/";>Pitivi</a>.</p>
<p>In the first phase of <a href="https://summerofcode.withgoogle.com/projects/#4521665294237696";>my
project</a>, I worked on redesigning Pitivi’s “Effect Library” to allow users to easily find, organise and
utilize their desired effects.</p>
@@ -1233,7 +1233,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<p>Pitivi 1.0 is scheduled to be released on Monday, May 20th. All the important bugs we were aware of have
been fixed.</p>
<p>To fix one of the last issues, Thibault very recently rewrote the timeline/layers/clips management in
GES, and this might have introduced new bugs. While we have lots of tests which all pass, they don’t cover
everything.</p>
<p>We ask you to test the 1.0 RC! Grab a bunch of video files shot with your phone or camera and make some
video out of them, trying various features. Tell us if you notice problems, and if you can reproduce them
please file an issue describing the steps to reproduce the bug.</p>
-<p>You can find us in the <a href="https://www.irccloud.com/irc/freenode/channel/pitivi";>#pitivi IRC
channel</a> on FreeNode, or in this bridged <a
href="https://riot.im/develop/#/room/#pitivi:matrix.org";>Pitivi Matrix room</a>.</p>
+<p>You can find us in the <a href="https://www.irccloud.com/irc/freenode/channel/pitivi";>#pitivi IRC
channel</a> on FreeNode, or in this bridged <a href="https://matrix.to/#/#pitivi:matrix.org";>Pitivi Matrix
room</a>.</p>
<h2>How to install</h2>
<p>To install the Pitivi 1.0 RC, simply run:</p>
<pre>flatpak install http://flatpak.pitivi.org/pitivi.flatpakref</pre>
@@ -1268,7 +1268,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<h1>GStreamer Editing Services OpenTimelineIO support</h1>
<p><a href="https://github.com/PixarAnimationStudios/OpenTimelineIO";>OpenTimelineIO</a> is an Open Source
API and interchange format for editorial timeline information, it basically allows some form of
interoperability between the different post production Video Editing tools. It is being developed by <a
href="http://graphics.pixar.com/";>Pixar</a> and several other studios are contributing to the project
allowing it to <a href="https://github.com/PixarAnimationStudios/OpenTimelineIO/commits/master";>evolve
quickly</a>.</p>
<p>We, at <a href="https://igalia.com";>Igalia</a>, recently <a
href="https://github.com/PixarAnimationStudios/OpenTimelineIO/pull/41";>landed</a> support for the <a
href="https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-editing-services/html/ges-architecture.html";>GStreamer
Editing Services</a> (GES) serialization format in OpenTimelineIO, making it possible to convert GES
timelines to any format supported by the library. This is extremely useful to integrate GES into existing
Post production workflow as it allows projects in any <a
href="https://opentimelineio.readthedocs.io/en/latest/tutorials/adapters.html";>format supported by
OpentTimelineIO</a> to be used in the GStreamer Editing Services and vice versa.</p>
-<p>On top of that we are building a <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/merge_requests/67";>GESFormatter</a> that
allows us to transparently handle any file format supported by OpenTimelineIO. In practice it will be
possible to use cuts produced by other video editing tools in any project using GES, for instance <a
href="http://www.pitivi.org";>Pitivi</a>:</p>
+<p>On top of that we are building a <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/merge_requests/67";>GESFormatter</a> that
allows us to transparently handle any file format supported by OpenTimelineIO. In practice it will be
possible to use cuts produced by other video editing tools in any project using GES, for instance <a
href="https://www.pitivi.org";>Pitivi</a>:</p>
<p><video controls="controls" height="150"
src="https://gitlab.gnome.org/thiblahute/blog/raw/master/OpenTimelineIO/OpenTimelineIODemoScreencast.mov?inline=false#t=0.01";
style="background-color: #050505; width: 512px; height: 216px;" width="300"></video></p>
<p>At <a href="https://igalia.com";>Igalia</a> we are aiming at making GStreamer ready to be used in existing
Video post production pipelines and this work is one step in that direction. We are working on additional
features in GES to fill the gaps toward that goal, for instance we are now implementing <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/issues/60";>nested timeline</a> support
and <a href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/issues/61";>framerate based
timestamps</a> in GES. Once we implement them, those features will enhance compatibility of Video Editing
projects created from other NLE softwares through OpenTimelineIO. Stay tuned for more information!</p>
</div> <!-- /post-contents -->
@@ -1316,7 +1316,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<p>The GES overviews and tutorials would be kept in the <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs";>GES git repository</a>
as markdown files. The API is documented in the <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/ges";>source code</a> written
in C.</p>
<p>To get a better idea about the GES API, check the <a
href="http://lazka.github.io/pgi-docs/#GES-1.0/hierarchy.html";>hierarchy of classes</a>.</p>
<p>The current <a href="https://gstreamer.freedesktop.org/documentation/gst-editing-services/index.html";>GES
documentation</a> is integrated into the GStreamer documentation. The structure is specified in <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/blob/master/docs/sitemap.txt";>docs/sitemap.txt</a>,
and the HTML is generated with <a href="https://hotdoc.github.io";>Hotdoc</a> out of the C files and <a
href="https://gitlab.freedesktop.org/gstreamer/gst-editing-services/tree/master/docs";>other markdown
bits</a>.</p>
-<p>If interested, <a href="http://www.pitivi.org/?go=contact";>get in touch</a> with us as soon as possible,
so we can prepare.</p>
+<p>If interested, <a href="https://www.pitivi.org/contact/";>get in touch</a> with us as soon as possible, so
we can prepare.</p>
<p> </p> </div> <!-- /post-contents -->
<div class="post-footer">
@@ -1338,7 +1338,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<h3 class="post-title"><a href="http://blog.aleb.ro/2019/02/polishing-pitivis-viewer.html";>Polishing
Pitivi's viewer</a></h3> </div> <!-- /post-header -->
<div class="post-contents ">
-<div dir="ltr" style="text-align: left;"><div style="text-align: left;">In the <a
href="http://www.pitivi.org/";>Pitivi</a> video editor, the viewer is quite important, as it shows the video.
Our viewer also shows a discreet frame around a clip selected in the timeline, making it easy to <a
href="https://lubosz.wordpress.com/2016/09/26/making-viewer-uis-for-pitivi/";>resize and position the video of
the clip by dragging</a>. Below is the story of the viewer updates in the past year.<br /><h2
style="text-align: left;">Easy resizing</h2>It was a bit cumbersome to have to drag both the left and bottom
margins of the viewer container to resize it. We thought it would be easier to resize the viewer by simply
dragging the bottom-left corner of its container. Harish Fulara made time at the end of his GSoC 2018
internship for this, after he finished his main task, and it works great! —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/25609f3ab7996e865ec275298c70a384823cabe3";> 25609f3a</
a><br /><h2 style="text-align: left;">Are we 100% yet?</h2>In Pitivi, the project resolution is conveniently
set for new projects to match the first imported video file, and can be changed at any time. This project
resolution applies to the video content, which at the end is resized when displayed by the viewer, depending
on the size of the viewer. Of course resizing introduces artifacts, so we need a way to have the viewer
display the video content at 100%, pixel for pixel.<br /><br />Without introducing any new confusing UI, the
simplest thing we could do was to show the resize status while the viewer is resized. Now the video dims when
you resize the viewer, to see clearly the resize percent, and then is restored after a timeout with no change
in size.<br /><br />By connecting to the widget's width/height property-change signals, <b>any</b> size
change is detected, irrespective of what caused it: the corner being dragged, or the window being maximized,
etc. Thanks again to Harish
and his GSoC for implementing this! —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/d91c1283a85b4041e57253f7086ac2706f42acdd";>d91c1283</a> <br
/><br />Sometimes it can be fiddly to set the viewer to 100%, since one pixel more and it's not 1:1 anymore.
We thought about improving it by introducing snapping.<br /><h2 style="text-align:
left;">Snapping</h2>Unfortunately, with snapping you won't be able to set your viewer size to 101%, but in
return it's much easier to target 100%. Now the 100..105% range is down-snapped to 100%, to make it easy to
display the video content without any resize artifacts. Harish researched how we can do this, but as school
took him over, yours truly recently made time to finish the implementation. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/371581a01ba7c3c147b7fe61482a2016e207aaf6";>371581a0</a><br
/><br /><div class="separator" style="clear: both; text-align: center;"><a
href="https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAA
AA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s1600/Peek%2B2019-02-15%2B00-34.gif" style="margin-left: 1em;
margin-right: 1em;"><img border="0" height="209"
src="https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s400/Peek%2B2019-02-15%2B00-34.gif";
width="400" /></a></div><br /><br />Once merged, looking back at my commit, like everybody does from time to
time, ..closely, some code cleanup commits popped up, like mushrooms after rain. It's pretty cloudy in
Zurich.<br /><h2 style="text-align: left;">Better trimming preview</h2><div style="text-align:
left;">Normally the viewer is used to display the project video at the playhead position, but we also use it
to display the start or end margins of a clip when it is being trimmed.</div></div><div style="text-align:
left;"><br />A long time ago it used to be the case that we had to limit the seek rate when trimming, for
performance reasons, but now the seek is done async and our pipel
ine is smart enough to skip scheduled seeks if new ones come in. With the limit removed, now the trim
preview is more precise and (up to 200ms) snappier. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/42a7dc01e642d642d48b55d4d40a2ccbcdddbe2a";>42a7dc01</a><br
/><br />The code responsible for the switch between the project video widget and the clip video widget, when
starting/finishing a trim operation, was very complex. It was checking in quite a few places, which one are
we dealing with: the pipeline of the project or the pipeline of the trimmed clip. By keeping separate
references to both, the logic is now much easier to read. As a bonus, now when the trim is finished, we
directly display the project video, without having to wait for the pipeline state to go from NULL to PAUSED.
—<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/03e15b44e8878d9c24fbd47b9477a695d2a24a50";>03e15b44</a><br
/><br />When a trim operation was being started, the trim preview was flickering.
This was more noticeable when the end of the clip was trimmed. The first frame of the clip was being
displayed for a split second before the first seek is done. Now we simply wait for the first seek to be
performed before switching the viewer to show the trimming preview. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/6d49ee544c28d666a38be2b12a302f4f93492ca4";>6d49ee54</a><br
/><br />It takes a very short time until the pipeline for a clip trim preview is ready, but why not have it
instantly? At least when the user is focused on a handful of clips adjusting and trimming them, a cheap cache
now does the job. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/ec9ca33bae2279d4e8cf1e6b6dfc1c0d3e10dcc7";>ec9ca33b</a><br
/><h2 style="text-align: left;">Contributing to Pitivi </h2><div style="text-align: left;">Pitivi benefits
from the <a href="https://en.wikipedia.org/wiki/GStreamer";>GStreamer</a> multimedia framework used on most
Linux desktops and we contribute back in mu
ltiple ways. We could use some more hands on Pitivi. Contributions of any type would be greatly appreciated.
Come <a href="http://www.pitivi.org/?go=contact";>chat</a> with us. If you're a student, you can join us doing
a <a href="https://developer.pitivi.org/Google_Summer_of_Code.html";>GSoC</a> internship this
summer!</div><div style="text-align: left;"><br /></div></div></div> </div> <!--
/post-contents -->
+<div dir="ltr" style="text-align: left;"><div style="text-align: left;">In the <a
href="https://www.pitivi.org/";>Pitivi</a> video editor, the viewer is quite important, as it shows the video.
Our viewer also shows a discreet frame around a clip selected in the timeline, making it easy to <a
href="https://lubosz.wordpress.com/2016/09/26/making-viewer-uis-for-pitivi/";>resize and position the video of
the clip by dragging</a>. Below is the story of the viewer updates in the past year.<br /><h2
style="text-align: left;">Easy resizing</h2>It was a bit cumbersome to have to drag both the left and bottom
margins of the viewer container to resize it. We thought it would be easier to resize the viewer by simply
dragging the bottom-left corner of its container. Harish Fulara made time at the end of his GSoC 2018
internship for this, after he finished his main task, and it works great! —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/25609f3ab7996e865ec275298c70a384823cabe3";> 25609f3a<
/a><br /><h2 style="text-align: left;">Are we 100% yet?</h2>In Pitivi, the project resolution is
conveniently set for new projects to match the first imported video file, and can be changed at any time.
This project resolution applies to the video content, which at the end is resized when displayed by the
viewer, depending on the size of the viewer. Of course resizing introduces artifacts, so we need a way to
have the viewer display the video content at 100%, pixel for pixel.<br /><br />Without introducing any new
confusing UI, the simplest thing we could do was to show the resize status while the viewer is resized. Now
the video dims when you resize the viewer, to see clearly the resize percent, and then is restored after a
timeout with no change in size.<br /><br />By connecting to the widget's width/height property-change
signals, <b>any</b> size change is detected, irrespective of what caused it: the corner being dragged, or the
window being maximized, etc. Thanks again to Haris
h and his GSoC for implementing this! —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/d91c1283a85b4041e57253f7086ac2706f42acdd";>d91c1283</a> <br
/><br />Sometimes it can be fiddly to set the viewer to 100%, since one pixel more and it's not 1:1 anymore.
We thought about improving it by introducing snapping.<br /><h2 style="text-align:
left;">Snapping</h2>Unfortunately, with snapping you won't be able to set your viewer size to 101%, but in
return it's much easier to target 100%. Now the 100..105% range is down-snapped to 100%, to make it easy to
display the video content without any resize artifacts. Harish researched how we can do this, but as school
took him over, yours truly recently made time to finish the implementation. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/371581a01ba7c3c147b7fe61482a2016e207aaf6";>371581a0</a><br
/><br /><div class="separator" style="clear: both; text-align: center;"><a
href="https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAA
AAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s1600/Peek%2B2019-02-15%2B00-34.gif" style="margin-left:
1em; margin-right: 1em;"><img border="0" height="209"
src="https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s400/Peek%2B2019-02-15%2B00-34.gif";
width="400" /></a></div><br /><br />Once merged, looking back at my commit, like everybody does from time to
time, ..closely, some code cleanup commits popped up, like mushrooms after rain. It's pretty cloudy in
Zurich.<br /><h2 style="text-align: left;">Better trimming preview</h2><div style="text-align:
left;">Normally the viewer is used to display the project video at the playhead position, but we also use it
to display the start or end margins of a clip when it is being trimmed.</div></div><div style="text-align:
left;"><br />A long time ago it used to be the case that we had to limit the seek rate when trimming, for
performance reasons, but now the seek is done async and our pipe
line is smart enough to skip scheduled seeks if new ones come in. With the limit removed, now the trim
preview is more precise and (up to 200ms) snappier. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/42a7dc01e642d642d48b55d4d40a2ccbcdddbe2a";>42a7dc01</a><br
/><br />The code responsible for the switch between the project video widget and the clip video widget, when
starting/finishing a trim operation, was very complex. It was checking in quite a few places, which one are
we dealing with: the pipeline of the project or the pipeline of the trimmed clip. By keeping separate
references to both, the logic is now much easier to read. As a bonus, now when the trim is finished, we
directly display the project video, without having to wait for the pipeline state to go from NULL to PAUSED.
—<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/03e15b44e8878d9c24fbd47b9477a695d2a24a50";>03e15b44</a><br
/><br />When a trim operation was being started, the trim preview was flickering
. This was more noticeable when the end of the clip was trimmed. The first frame of the clip was being
displayed for a split second before the first seek is done. Now we simply wait for the first seek to be
performed before switching the viewer to show the trimming preview. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/6d49ee544c28d666a38be2b12a302f4f93492ca4";>6d49ee54</a><br
/><br />It takes a very short time until the pipeline for a clip trim preview is ready, but why not have it
instantly? At least when the user is focused on a handful of clips adjusting and trimming them, a cheap cache
now does the job. —<a
href="https://gitlab.gnome.org/GNOME/pitivi/commit/ec9ca33bae2279d4e8cf1e6b6dfc1c0d3e10dcc7";>ec9ca33b</a><br
/><h2 style="text-align: left;">Contributing to Pitivi </h2><div style="text-align: left;">Pitivi benefits
from the <a href="https://en.wikipedia.org/wiki/GStreamer";>GStreamer</a> multimedia framework used on most
Linux desktops and we contribute back in m
ultiple ways. We could use some more hands on Pitivi. Contributions of any type would be greatly
appreciated. Come <a href="https://www.pitivi.org/contact/";>chat</a> with us. If you're a student, you can
join us doing a <a href="https://developer.pitivi.org/Google_Summer_of_Code.html";>GSoC</a> internship this
summer!</div><div style="text-align: left;"><br /></div></div></div> </div> <!--
/post-contents -->
<div class="post-footer">
<p><a
href="http://blog.aleb.ro/2019/02/polishing-pitivis-viewer.html";>February 14, 2019 11:43 PM</a></p>
@@ -1551,7 +1551,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<h3 class="post-title"><a
href="https://yatinmaan.github.io/2018/08/07/Pitivis-Proxy-Preparation-Procedure/";>Pitivi's Proxy Preparation
Procedure</a></h3> </div> <!-- /post-header -->
<div class="post-contents ">
-<p><a href="http://www.pitivi.org/";><img alt="Pitivi Logo"
src="https://yatinmaan.github.io/assets/images/pitivi_logo_circle.png"; title="Pitivi" /></a></p>
+<p><a href="https://www.pitivi.org/";><img alt="Pitivi Logo"
src="https://yatinmaan.github.io/assets/images/pitivi_logo_circle.png"; title="Pitivi" /></a></p>
<p>Internally, most of the code for handling proxies resides in <code
class="highlighter-rouge">proxy.py</code> which exposes the <code
class="highlighter-rouge">proxy_manager</code> class to create and monitor proxy assets.</p>
@@ -1588,7 +1588,7 @@ In the process, we also decided to move away from showing Audio and Video effect
<div class="post-contents ">
<p><a href="https://summerofcode.withgoogle.com/organizations/5900447454330880/";><img alt="GSoC with GNOME"
src="https://yatinmaan.github.io/assets/images/gsoc_gnome.png"; title="GSoC with GNOME" /></a></p>
-<p>This summer I , under the mentorship of <a href="https://wiki.gnome.org/ThibaultSaunier";>Thibault
Saunier</a>, will be working on adding scaled proxies to <a href="http://www.pitivi.org/";>Pitivi</a>. While
Pitivi already provides its users the option to use Optimized Media (aka HQ Proxies) for problematic file
formats, having scaled proxies would allow them to transcode their high resolution video assets to a more
manageable resolution at the time of editing which would make both editing and previewing much quicker.</p>
+<p>This summer I , under the mentorship of <a href="https://wiki.gnome.org/ThibaultSaunier";>Thibault
Saunier</a>, will be working on adding scaled proxies to <a href="https://www.pitivi.org/";>Pitivi</a>. While
Pitivi already provides its users the option to use Optimized Media (aka HQ Proxies) for problematic file
formats, having scaled proxies would allow them to transcode their high resolution video assets to a more
manageable resolution at the time of editing which would make both editing and previewing much quicker.</p>
<p>Some of the other editors allow users to attach externally transcoded assets as proxies, this approach is
flexible but not very user friendly. Pitivi, a bit like Final Cut Pro, provides a single unified experience
where user can create and manage proxies right there in the application itself.</p>
@@ -2154,7 +2154,7 @@ place Important buttons like “New Project”, “Open Project”, etc. in th
<h3 class="post-title"><a href="http://blog.aleb.ro/2015/10/pitivi-moves-from-bugzilla-to.html";>Pitivi moves
from Bugzilla to Phabricator</a></h3> </div> <!-- /post-header -->
<div class="post-contents ">
-<div dir="ltr" style="text-align: left;"><div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;
text-align: left;"><span style="font-family: inherit;"><span style="background-color: transparent; color:
black; font-size: 14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400;
text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Using Bugzilla to manage <a
href="http://www.pitivi.org/";>Pitivi</a> was a bit painful and we were looking for a replacement. Many
projects seemed to switch to Phabricator lately, which looked like a very good platform for managing
projects. We experimented migrating Bugzilla bugs to Phabricator, and we are pretty content with the result.
The UI is nicer, we have a better search function, and the Git integration (with the </span><a
href="https://phabricator.freedesktop.org/diffusion/"; style="text-decoration: none;"><span
style="background-color: transparent; color: #1155cc; font-size: 14.66666666666666
6px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align:
baseline; white-space: pre-wrap;">code review</span></a><span style="background-color: transparent; color:
black; font-size: 14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400;
text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> component) </span><a
href="https://phabricator.freedesktop.org/diffusion/GITPHAB/"; style="text-decoration: none;"><span
style="background-color: transparent; color: #1155cc; font-size: 14.666666666666666px; font-style: normal;
font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">works great</span></a><span style="background-color: transparent; color: black; font-size:
14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none;
vertical-align: baseline; white-space: pre-wrap;">.</span></span><
/div><div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span
style="background-color: transparent; color: black; font-family: inherit; font-size: 14.666666666666666px;
font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline;
white-space: pre-wrap;"><br /></span></div><div style="text-align: left;"><span
id="docs-internal-guid-a56034b1-85da-e5ca-b5cc-0f96b7e878a7" style="font-family: inherit;"><span
style="color: black; font-size: 14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">We
decided to make the switch official, so we updated the documentation on the </span><a
href="http://wiki.pitivi.org/"; style="text-decoration: none;"><span style="color: #1155cc; font-size:
14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">wiki</span></a><span style="font-size: 14.6666666666667px; vertical-align: baseline; white-space:
pre-wrap;"> and <
/span><a href="http://www.pitivi.org/"; style="text-decoration: none;"><span style="color: #1155cc;
font-size: 14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">website</span></a><span style="font-size: 14.6666666666667px; vertical-align: baseline;
white-space: pre-wrap;"> to link to </span><a href="https://phabricator.freedesktop.org/tag/pitivi/";
style="text-decoration: none;"><span style="color: #1155cc; font-size: 14.6666666666667px; text-decoration:
underline; vertical-align: baseline; white-space: pre-wrap;">Phabricator</span></a><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">, closed the Pitivi Bugzilla “product”
and closed the remaining bugs in Bugzilla with a custom made script. The script also linked each bug to the
proper task in Phabricator.</span></span><br /><span style="font-family: inherit;"><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space
: pre-wrap;"><br /></span></span><span style="font-family: inherit;"><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">For those new to Phabricator, remember
that instead of creating a “bug” you create a “task”.</span></span></div></div>
</div> <!-- /post-contents -->
+<div dir="ltr" style="text-align: left;"><div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;
text-align: left;"><span style="font-family: inherit;"><span style="background-color: transparent; color:
black; font-size: 14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400;
text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Using Bugzilla to manage <a
href="https://www.pitivi.org/";>Pitivi</a> was a bit painful and we were looking for a replacement. Many
projects seemed to switch to Phabricator lately, which looked like a very good platform for managing
projects. We experimented migrating Bugzilla bugs to Phabricator, and we are pretty content with the result.
The UI is nicer, we have a better search function, and the Git integration (with the </span><a
href="https://phabricator.freedesktop.org/diffusion/"; style="text-decoration: none;"><span
style="background-color: transparent; color: #1155cc; font-size: 14.6666666666666
66px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: underline;
vertical-align: baseline; white-space: pre-wrap;">code review</span></a><span style="background-color:
transparent; color: black; font-size: 14.666666666666666px; font-style: normal; font-variant: normal;
font-weight: 400; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> component)
</span><a href="https://phabricator.freedesktop.org/diffusion/GITPHAB/"; style="text-decoration: none;"><span
style="background-color: transparent; color: #1155cc; font-size: 14.666666666666666px; font-style: normal;
font-variant: normal; font-weight: 400; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">works great</span></a><span style="background-color: transparent; color: black; font-size:
14.666666666666666px; font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none;
vertical-align: baseline; white-space: pre-wrap;">.</span></span>
</div><div style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt; text-align: left;"><span
style="background-color: transparent; color: black; font-family: inherit; font-size: 14.666666666666666px;
font-style: normal; font-variant: normal; font-weight: 400; text-decoration: none; vertical-align: baseline;
white-space: pre-wrap;"><br /></span></div><div style="text-align: left;"><span
id="docs-internal-guid-a56034b1-85da-e5ca-b5cc-0f96b7e878a7" style="font-family: inherit;"><span
style="color: black; font-size: 14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">We
decided to make the switch official, so we updated the documentation on the </span><a
href="http://wiki.pitivi.org/"; style="text-decoration: none;"><span style="color: #1155cc; font-size:
14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">wiki</span></a><span style="font-size: 14.6666666666667px; vertical-align: baseline; white-space:
pre-wrap;"> and
</span><a href="https://www.pitivi.org/"; style="text-decoration: none;"><span style="color: #1155cc;
font-size: 14.6666666666667px; text-decoration: underline; vertical-align: baseline; white-space:
pre-wrap;">website</span></a><span style="font-size: 14.6666666666667px; vertical-align: baseline;
white-space: pre-wrap;"> to link to </span><a href="https://phabricator.freedesktop.org/tag/pitivi/";
style="text-decoration: none;"><span style="color: #1155cc; font-size: 14.6666666666667px; text-decoration:
underline; vertical-align: baseline; white-space: pre-wrap;">Phabricator</span></a><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">, closed the Pitivi Bugzilla “product”
and closed the remaining bugs in Bugzilla with a custom made script. The script also linked each bug to the
proper task in Phabricator.</span></span><br /><span style="font-family: inherit;"><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-spa
ce: pre-wrap;"><br /></span></span><span style="font-family: inherit;"><span style="font-size:
14.6666666666667px; vertical-align: baseline; white-space: pre-wrap;">For those new to Phabricator, remember
that instead of creating a “bug” you create a “task”.</span></span></div></div>
</div> <!-- /post-contents -->
<div class="post-footer">
<p><a
href="http://blog.aleb.ro/2015/10/pitivi-moves-from-bugzilla-to.html";>April 12, 2018 02:51 PM</a></p>
@@ -2214,7 +2214,7 @@ place Important buttons like “New Project”, “Open Project”, etc. in th
<h3 class="post-title"><a href="http://blog.aleb.ro/2016/01/polishing-pitivis-ruler.html";>Polishing Pitivi's
ruler</a></h3> </div> <!-- /post-header -->
<div class="post-contents ">
-<div dir="ltr" style="text-align: left;"><br /><br />In Pitivi, the ruler is displayed above the timeline to
show the times corresponding with the current view. A series of H:MM:SS.XXX timestamps on a ruler might leave
the impression that only trained professionals are supposed to use it. I had trouble reading the timestamps
and looked for ways to make the ruler more useful. Read below for the story.<br /><br /><div
style="text-align: center;"><div class="separator" style="clear: both; text-align: center;"><a
href="http://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png";
/></a></div>Pitivi ruler, Dec 2013</div><br /><h2 style="text-align: left;">Relevant parts</h2>Around the New
Year 2013-2014 I thought about highlighting the relevant parts in the timestamp. For example, if you have
0:00:05
.000 and then 0:00:10.000, you have to look quite a bit until you notice what changes from one to the other.
In this case the "10" should be highlighted because that's different than the previous timestamp. This way
it's easier to see what an interval represents. Jeff liked the idea and the commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=a7cb639b8ac8750edd44125a7ea0a3fd0601a5bf";>went
in</a>.<br /><div><br />The ruler being more useful, I started to look more at it while using Pitivi. One
week later, after 6 code cleanup commits, the millis were being displayed with a smaller font, so they can be
ignored more easily. One hour later though, the hours and millis were being displayed only when useful:<br
/><ul style="text-align: left;"><li>The hour is displayed only if greater than 0. </li><li>The millis are
displayed only when the zoom level is high enough that millis other than “.000” start to show up in the
timestamps. This got improved lat
er!</li></ul>The shorter timestamps looked good so the changes <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=7a301c8787ce264efcb766e050ed7500ac5599f3";>went</a>
<a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3f78e856c4566712d3a5ccb161e40748ab08d3b6";>in</a>.<br
/><br />Guessing most projects are less than one hour long and most of the time users don't use zoom levels
where milliseconds matter—this was already a big improvement, it’s much easier to see “MM:SS” than
“0:MM:SS.000”.<br /><br /><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png";><img
border="0" src="https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png";
/></a></div><div style="text-align: center;">Pitivi ruler zoomed out, Jan 2014</div><br /></div><h2
style="text-align: left;">Dividing an interval</h2>An “interval” on the rule
r is the interval at which the timestamps are shown. At different zoom levels, the length of the interval is
picked automatically out of a hardcoded list, so you see an optimum number of timestamps. It was awkward that
the displayed intervals were always divided in 10 parts. While it makes sense for a 10 seconds interval to be
divided by 10, it’s not very useful when a 30 minutes interval is divided by 10.<br /><div><br />It was easy
to define the tick frequency for each of the hardcoded intervals, but it looked awkward for most of the zoom
levels. Previously we clearly preferred largish interval sizes (so the interval can be divided in 10 smaller
but still visible units) but it was not so nice anymore when a large interval is divided only in 2 units.
Some fine-tune of the minimum interval length and the minimum division length was required. The smaller
timestamps fit great with the smaller intervals:</div><div><br /></div><div class="separator" style="clear:
both; text-align: cen
ter;"><a href="http://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s1600/interval.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png";
/></a></div><div><div style="text-align: center;">Dividing by 2 is enough for some intervals, Dec
2015</div><br /><h2 style="text-align: left;">Timestamp shape</h2>While fine-tuning the minimum interval and
interval division size, I realized that when displaying millis, it’s useful to display <b>only</b> the
millis, except for the full second timestamps when <b>only</b> [H:]MM:SS is displayed. This way it’s much
easier to see where the full seconds are, because “00:01” looks quite different shape-wise than “<span
style="font-size: x-small;">.500</span>” which is displayed with a smaller font. Luckily, by keeping all the
timestamps short (“<span style="font-size: x-small;">.900</span>” is the shortest a
nd “9:00:00” is the longest), it was possible to have a simple formula for choosing the optimum interval per
zoom level.<br /><br /><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s1600/second.png";><img
border="0" src="https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png";
/></a></div><div style="text-align: center;">Pitivi ruler zoomed in, Jan 2016</div><br />The commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=c5e5d11ae5230d59bd1a356d54961c45460e06cd";>went
in</a>, along with <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3c5859f0b22ae2f4f1daf69a7ffe27ccd025786b";>a
cherry</a>.<br /><br />Some did not like the pear-shaped playhead though, so we later replaced it with an
empty diamond.<br /><br /><div style="text-align: center;"><a
href="http://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6m
V-44UaAYR3XQIUlCzOHI1KquQCK4B/s1600/new_playhead_500.png"><img border="0"
src="https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png";
/></a></div><div style="text-align: center;">Pitivi playhead, Apr 2016</div><br />Start Pitivi and look at
the ruler, zooming in and out, a nice feeling starts bubbling up inside.<br /><div><br />Until we wrap up
0.96, you can already see the ruler in action by downloading the Pitivi <a
href="http://www.pitivi.org/?go=download";>bundle</a>! BTW, the bundle already includes the proxy files
functionality which allows using any video format reliably. Read: no more artifacts when using MTS files.
When compared, the ruler polishing I described above is just me playing in the sand. The proxy files
functionality brings Pitivi much closer to 1.0. Please try it out and tell us how it works for you! :)<br
/><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"></div
<div><br /></div><div>If you are still here, see maybe the entire <a
href="https://git.gnome.org/browse/pitivi/log/pitivi/timeline/ruler.py";>history</a> of Pitivi’s <a
href="https://git.gnome.org/browse/pitivi/tree/pitivi/timeline/ruler.py";>ruler</a>.</div></div></div></div>
</div> <!-- /post-contents -->
+<div dir="ltr" style="text-align: left;"><br /><br />In Pitivi, the ruler is displayed above the timeline to
show the times corresponding with the current view. A series of H:MM:SS.XXX timestamps on a ruler might leave
the impression that only trained professionals are supposed to use it. I had trouble reading the timestamps
and looked for ways to make the ruler more useful. Read below for the story.<br /><br /><div
style="text-align: center;"><div class="separator" style="clear: both; text-align: center;"><a
href="http://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png";
/></a></div>Pitivi ruler, Dec 2013</div><br /><h2 style="text-align: left;">Relevant parts</h2>Around the New
Year 2013-2014 I thought about highlighting the relevant parts in the timestamp. For example, if you have
0:00:05
.000 and then 0:00:10.000, you have to look quite a bit until you notice what changes from one to the other.
In this case the "10" should be highlighted because that's different than the previous timestamp. This way
it's easier to see what an interval represents. Jeff liked the idea and the commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=a7cb639b8ac8750edd44125a7ea0a3fd0601a5bf";>went
in</a>.<br /><div><br />The ruler being more useful, I started to look more at it while using Pitivi. One
week later, after 6 code cleanup commits, the millis were being displayed with a smaller font, so they can be
ignored more easily. One hour later though, the hours and millis were being displayed only when useful:<br
/><ul style="text-align: left;"><li>The hour is displayed only if greater than 0. </li><li>The millis are
displayed only when the zoom level is high enough that millis other than “.000” start to show up in the
timestamps. This got improved lat
er!</li></ul>The shorter timestamps looked good so the changes <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=7a301c8787ce264efcb766e050ed7500ac5599f3";>went</a>
<a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3f78e856c4566712d3a5ccb161e40748ab08d3b6";>in</a>.<br
/><br />Guessing most projects are less than one hour long and most of the time users don't use zoom levels
where milliseconds matter—this was already a big improvement, it’s much easier to see “MM:SS” than
“0:MM:SS.000”.<br /><br /><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png";><img
border="0" src="https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png";
/></a></div><div style="text-align: center;">Pitivi ruler zoomed out, Jan 2014</div><br /></div><h2
style="text-align: left;">Dividing an interval</h2>An “interval” on the rule
r is the interval at which the timestamps are shown. At different zoom levels, the length of the interval is
picked automatically out of a hardcoded list, so you see an optimum number of timestamps. It was awkward that
the displayed intervals were always divided in 10 parts. While it makes sense for a 10 seconds interval to be
divided by 10, it’s not very useful when a 30 minutes interval is divided by 10.<br /><div><br />It was easy
to define the tick frequency for each of the hardcoded intervals, but it looked awkward for most of the zoom
levels. Previously we clearly preferred largish interval sizes (so the interval can be divided in 10 smaller
but still visible units) but it was not so nice anymore when a large interval is divided only in 2 units.
Some fine-tune of the minimum interval length and the minimum division length was required. The smaller
timestamps fit great with the smaller intervals:</div><div><br /></div><div class="separator" style="clear:
both; text-align: cen
ter;"><a href="http://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s1600/interval.png";
style="margin-left: 1em; margin-right: 1em;"><img border="0"
src="https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png";
/></a></div><div><div style="text-align: center;">Dividing by 2 is enough for some intervals, Dec
2015</div><br /><h2 style="text-align: left;">Timestamp shape</h2>While fine-tuning the minimum interval and
interval division size, I realized that when displaying millis, it’s useful to display <b>only</b> the
millis, except for the full second timestamps when <b>only</b> [H:]MM:SS is displayed. This way it’s much
easier to see where the full seconds are, because “00:01” looks quite different shape-wise than “<span
style="font-size: x-small;">.500</span>” which is displayed with a smaller font. Luckily, by keeping all the
timestamps short (“<span style="font-size: x-small;">.900</span>” is the shortest a
nd “9:00:00” is the longest), it was possible to have a simple formula for choosing the optimum interval per
zoom level.<br /><br /><div style="text-align: center;"><a
href="http://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s1600/second.png";><img
border="0" src="https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png";
/></a></div><div style="text-align: center;">Pitivi ruler zoomed in, Jan 2016</div><br />The commit <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=c5e5d11ae5230d59bd1a356d54961c45460e06cd";>went
in</a>, along with <a
href="https://git.gnome.org/browse/pitivi/commit/pitivi/timeline/ruler.py?id=3c5859f0b22ae2f4f1daf69a7ffe27ccd025786b";>a
cherry</a>.<br /><br />Some did not like the pear-shaped playhead though, so we later replaced it with an
empty diamond.<br /><br /><div style="text-align: center;"><a
href="http://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6m
V-44UaAYR3XQIUlCzOHI1KquQCK4B/s1600/new_playhead_500.png"><img border="0"
src="https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png";
/></a></div><div style="text-align: center;">Pitivi playhead, Apr 2016</div><br />Start Pitivi and look at
the ruler, zooming in and out, a nice feeling starts bubbling up inside.<br /><div><br />Until we wrap up
0.96, you can already see the ruler in action by downloading the Pitivi <a
href="https://www.pitivi.org/download/";>bundle</a>! BTW, the bundle already includes the proxy files
functionality which allows using any video format reliably. Read: no more artifacts when using MTS files.
When compared, the ruler polishing I described above is just me playing in the sand. The proxy files
functionality brings Pitivi much closer to 1.0. Please try it out and tell us how it works for you! :)<br
/><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;"></div><
div><br /></div><div>If you are still here, see maybe the entire <a
href="https://git.gnome.org/browse/pitivi/log/pitivi/timeline/ruler.py";>history</a> of Pitivi’s <a
href="https://git.gnome.org/browse/pitivi/tree/pitivi/timeline/ruler.py";>ruler</a>.</div></div></div></div>
</div> <!-- /post-contents -->
<div class="post-footer">
<p><a
href="http://blog.aleb.ro/2016/01/polishing-pitivis-ruler.html";>April 12, 2018 02:45 PM</a></p>
@@ -2267,7 +2267,7 @@ place Important buttons like “New Project”, “Open Project”, etc. in th
<p>This summer we had three GSoC Pitivi projects. The GSoC work has been merged on the “master” branch and
we made a separate “1.0” branch where we implement or backport the relevant fixes. A special thank you to
Suhas Nayak and Ștefan-Adrian Popa, two of our GSoC students who contributed a large number of bugfixes and
made possible this release.</p>
<h3>1.0</h3>
<p>As you might know, we’re focused on bug fixing until Pitivi 1.0. See what’s left to do for 1.0 in <a
href="https://phabricator.freedesktop.org/project/view/125/";>Phabricator</a>.</p>
-<p>We need people to test Pitivi (the Flatpak “stable” branch) and report back any crash or stability issue
they notice, so we fix it. — If you want to <a href="http://www.pitivi.org/?go=contributing";>help</a> in any
way, come to our <a href="http://www.pitivi.org/?go=contact";>IRC channel</a>.</p>
</div> <!-- /post-contents -->
+<p>We need people to test Pitivi (the Flatpak “stable” branch) and report back any crash or stability issue
they notice, so we fix it. — If you want to <a href="https://www.pitivi.org/contribute/";>help</a> in any way,
come to our <a href="https://www.pitivi.org/contact/";>IRC channel</a>.</p> </div>
<!-- /post-contents -->
<div class="post-footer">
<p><a
href="https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/";>September 22, 2017 11:40
AM</a></p>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
![https://yatinmaan.github.io/assets/images/gsoc_pitivi.png"](https://yatinmaan.github.io/assets/images/gsoc_pitivi.png"){kind=link}
![https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s1600/Peek%2B2019-02-15%2B00-34.gif"](https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s1600/Peek%2B2019-02-15%2B00-34.gif"){kind=link}
![https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s400/Peek%2B2019-02-15%2B00-34.gif"](https://3.bp.blogspot.com/-f3jh6wlahRw/XGX7SY4pX_I/AAAAAAAA9qI/3zTueql370o7DWlChOfKPCqkQWUC__3AACLcBGAs/s400/Peek%2B2019-02-15%2B00-34.gif"){kind=link}
![https://yatinmaan.github.io/assets/images/pitivi_logo_circle.png"](https://yatinmaan.github.io/assets/images/pitivi_logo_circle.png"){kind=link}
![https://yatinmaan.github.io/assets/images/gsoc_gnome.png"](https://yatinmaan.github.io/assets/images/gsoc_gnome.png"){kind=link}
![http://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"](http://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"){kind=link}
![https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"/](https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"/){kind=link}
![http://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"](http://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"){kind=link}
![https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"/](https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"/){kind=link}
![http://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s1600/interval.png"](http://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s1600/interval.png"){kind=link}
![https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png"/](https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png"/){kind=link}
![http://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s1600/second.png"](http://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s1600/second.png"){kind=link}
![https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png"/](https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png"/){kind=link}
![https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png"/](https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png"/){kind=link}
![http://planet.gnome.org/img/feed-icon-10x10.png"](http://planet.gnome.org/img/feed-icon-10x10.png"){kind=link}
![https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"](https://1.bp.blogspot.com/-RMFqWp3HE9I/VqNryliNTfI/AAAAAAAAW2k/qyZzH_wMpLA/s1600/2012.11.png"){kind=link}
![https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"](https://1.bp.blogspot.com/-34MfDMyLVgw/VqLY5_tlJnI/AAAAAAAAW18/uzdK__c9yes/s1600/hour.png"){kind=link}
![https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png"](https://1.bp.blogspot.com/-XvfCvEzY3bw/VqLhFeObJbI/AAAAAAAAW2Y/DY58Sb757lA/s400/interval.png"){kind=link}
![https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png"](https://1.bp.blogspot.com/-ujr3bmkYPVY/VqLZLclz6-I/AAAAAAAAW2I/cdZOf2rN0l0/s320/second.png"){kind=link}
![https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png"](https://3.bp.blogspot.com/-yVjIJ-YOLEk/VxVh5WKmg2I/AAAAAAAAXuA/6PjQ0B6mV-44UaAYR3XQIUlCzOHI1KquQCK4B/s400/new_playhead_500.png"){kind=link}