Getting Started with PiTiVi
Video editing on Linux has had a long and complicated history. Although Linux has long-bathed in image editing, music production and other creativity-enabling applications, the platform traditionally has struggled with video production. In the early days, the problem was pinned on the complexities of supporting different video codecs, but as codec support continued to improve, the spotlight instead was shone on video editors.
Unfortunately, video editors were largely divided into two camps: hugely complex, resource-hungry behemoths, such as Cinelerra, or over-simple, limited offerings such as Kino. Across the world Linux, users craved a middle ground, desperately hoping for a simple, usability-orientated editor that supports a wide variety of media formats fused with the ability to be used on real-world projects.
Three years ago at the GNOME developer conference, Edward Hervey, a French developer living in Barcelona, presented the first cut of his video editor project, PiTiVi. With it, Edward made a series of firm decisions. First, it was based on the GStreamer multimedia framework—arguably the most popular and recommended way to handle low-level multimedia operations and content. Second, he focused his project firmly on usability and ease of use. Edward never set out to produce a super-complex professional editing tool, but rather a tool focused on simple real-world projects, such as editing your honeymoon video and putting it on YouTube. Finally, Edward was willing to delay the development of PiTiVi to “do things right”.
The latter was particularly apt. It took him three years to get PiTiVi in a shape where it could be used for the “real” projects he targeted. Much of the reason for this was that as Edward hacked on PiTiVi, he would find bugs and missing features in GStreamer, so he would step away from the PiTiVi coal-face to fix the GStreamer bug or feature before returning back to PiTiVi. Although it was a frustrating and time-consuming process, Edward's work paid off. GStreamer is an incredibly powerful and stable framework for building applications, so much so that I myself created a music multitracker project with it called Jokosher. Edward's work not only generated a better GStreamer, but also a more powerful and mature PiTiVi.
PiTiVi is available for all major Linux distributions and is now bundled by default with Ubuntu 10.04 Lucid Lynx. You can find packages for these different distributions in most distribution archives, so use apt-get, yum or emerge to grab PiTiVi for your system. When you have installed it, you can click Applications→Sound & Video→PiTiVi to load it. If all else fails, you can download PiTiVi from its Web site at www.pitivi.org.
With PiTiVi ready to roll, you also need to ensure you have the right video codecs installed for the video formats you want to edit. This is as simple as ensuring you have the gstreamer-good package installed. If you want more codecs, but ones that are legally restricted in terms of redistribution, install the gstreamer-ugly package. Finally, there is another package with a set of work-in-progress codecs called gstreamer-bad, which you can try. Personally, I install them all so I have the widest codec coverage.
Start PiTiVi by clicking Applications→Sound & Video→PiTiVi. First, let's take a look at the PiTiVi (Figure 1).
The interface consists of four main areas: the source list, previewer, timeline and toolbar.
The source list is the main white area on the left part of the window. This is where you can import the different video clips, photos and sound files that will be used in your project. You can either drag the files onto this white area or click the Import clips... button to load them. Whichever approach you use, each clip will appear in the source list area ready for use in your project. Test this by either dragging a video onto the source list or importing it with the Import clips... button and selecting a video. If for some reason PiTiVi can't load your file (most likely due to it being an unsupported format), an error appears at the bottom of the source list.
The previewer is to the right of the source list and provides a place to view the video in your project. The black box is where you will see your video, and the buttons underneath are standard transport buttons to control playback. The previewer is used not only for playing back your edited project, but also for previewing clips in the source list. Test this by dragging the video you imported into the source list and dropping it on the black box in the previewer. Now, use the transport controls to play it, and you should see the video play back. Click the different transport buttons to fiddle with the playback.
The timeline is the long area underneath the source view and previewer. This area is where you perform the editing on your project. The concept is simple: the timeline provides a literal timeline of your project with the far left being the very beginning of your video project and time increasing to the right. In the timeline, you can drop clips, cut them into pieces and arrange them in your desired order. The timeline also can be used to adjust volume, add pictures and overlay music over different parts. Test the timeline by dragging the video from the source list and dropping it on the timeline; the clip appears in the timeline, similar to Figure 2.
When a clip is loaded, there are two bars: the Video and Audio tracks. If you see only the second bar, you may need to click the clip in the timeline and drag it up to the video track to see both. Each bar represents exactly what it says—the different video frames and the audio content. This content is displayed separately, so you can remove one and not the other if you like. This is common for removing audio and replacing it with something else, such as a soundtrack.
Before moving on, the timeline has two additional special features: the ruler and the zoom. The ruler is the gray part with the numbers at the top of the timeline. If you click any part of the ruler, you can skip to a different part of the timeline, and that part of the project is shown in the previewer. When you click on the ruler, you can see the current position in the video by the red line that is drawn vertically on the timeline (this is called the playhead). To the left of the ruler is the zoom. This little slider can be used to adjust the scale of the timeline. This is useful for zooming out on the project to see it as a whole or zooming in closely to specific parts of a clip to cut a specific scene at just the right point.
The final area to look at is the toolbar, which is below the timeline. This line of buttons provides a simple palette of tools that you can use to edit content on the timeline. Let's explore some of these tools now.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide