Getting Started with PiTiVi
All editing in PiTiVi takes place in the timeline. Fortunately, editing in PiTiVi is incredibly simple, and you really need to know how to use only one main tool: the cutter.
Video editing is all about cutting video into different pieces and putting them next to each other to tell a story. To perform a cut in PiTiVi, place the playhead where you want the cut to happen (by clicking on the ruler), and click the scissors icon on the toolbar. The clip splits in half, and you can click on each clip to move it around. Now, if you move your mouse to the edge of one of the clips, the cursor changes, and you can shorten and lengthen the clip to taste. To get your cut at just the right place, you may want to use the ruler to zoom in and out of the timeline and resize until the clip is just right. If you get tired of constantly toggling the play button in the previewer to start and stop playback, use the spacebar as a shortcut for toggling playback.
One of the wonderful aspects of video editing is that it is so simple to perform, but the impact that is delivered lies in how you organize the clips, the timing between cuts, how those cuts line up with music and more. Each of these skills fundamentally boils down to cutting, trimming, moving and viewing the results in the previewer.
While editing, you may want to get rid of some of the audio and replace it with other audio, such as if you want a series of fast cuts to music. You do this by splitting the audio from the video in a given clip and deleting the audio part. By default, your two clips are two different units and when you drag them, the video and audio are stuck together in each clip. To split the audio from the video in a given clip, first click on the clip on the timeline (it will turn a little darker to indicate that you selected it), and then click the far-right button on the toolbar (the button has an icon with two blocks and an up-and-down arrow). Clicking this icon unsticks the video and audio from the selected clip. Now, click the audio clip and only that will be selected. Delete this by clicking the red circle icon on the toolbar and only the audio clip will vanish, leaving the video present. If you now play back the video at that point in the timeline, you will hear no audio but see the video.
Now, import an audio file into the source list, and drag that to the timeline where the audio you just deleted was. You now have video over an entirely different audio track. Play with cutting the video into lots of different pieces, resizing them and placing them next to each other over the audio. Before you know it, you will have lots of fast-changing clips with your new audio soundtrack.
When you add any clip to the timeline, a horizontal red line is drawn over the duration of the clip. This is the fade line. With it, you can control where audio fades (on the audio track) or video fades (on the video track). An audio fade is where you smoothly adjust the volume of the clip from one level to another. As an example, at the end of a video you may want to fade your audio to silence. On the video track, the fade line lets you control how you fade from video to black. In the same example, at the end of a project, you could use this line to fade the video to black slowly.
Using the fade line is simple. Double-click at the point you want a fade to happen, and a small handle appears on the fade line. Now, click the handle and move it to adjust the fade. On the volume track, the higher the red line the louder the volume, and on the video track, the higher the red line the more video is visible instead of black. Next, click another part of a fade line and the red line connects the dots. This is how you do fades: add two points on a line and adjust their settings, and PiTiVi performs the fade for you. As an example, add a fade handle a little bit before the end of a video and one right at the end. Move the far-right handle to the bottom and the far-left one to the top, and the clip will fade out at the end.
One final note about fades is that they are tied to a clip and not part of the wider timeline. As such, if you add a fade to a clip and then move the clip around, the fade moves too. This makes it really simple to perform fades and then reorganize the clips in your project later.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- RSS Feeds
- Non-Linux FOSS: libnotify, OS X Style
- UX Designer
- So when they found it hard to
57 min 59 sec ago
1 hour 20 min ago
- Reply to comment | Linux Journal
1 hour 42 min ago
- Android has been dominating
1 hour 47 min ago
- It is quiet helping
4 hours 32 min ago
4 hours 49 min ago
- Reachli - Amplifying your
6 hours 6 min ago
6 hours 55 min ago
- good point!
6 hours 57 min ago
- Varnish works!
7 hours 6 min ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?