Making Movies with Kino
Every camcorder owner would like to turn raw video into something real through editing. It does not matter how much the camcorder box brags of special effects and so forth, you still need proper editing tools. Fortunately, with today's powerful PCs, Linux and an application called Kino, you can put together your own little Hollywood studio.
Kino is nonlinear editor software. It can capture raw video, edit and re-organise it, and export the final results. With additional free, extra-cool plugins, Kino gives you all the necessary tools to make good movies.
Producing a movie usually includes making a recording with a camcorder. We don't cover this, but start with explaining how to copy a recorded raw video onto a PC with Kino. Modern camcorders communicate with PCs through the IEEE1394 interface that Apple calls FireWire; Sony prefers the name i.Link. After capturing, you can edit your raw video, adding titles and creating effects. You also may want to improve your movie by adding, mixing and replacing sounds. Kino supports all of these functions. When your movie is finished, you may want to make a DVD, so you can play it on a standalone DVD player, or even make an MPEG4. The quality of compressed movies is lower than the original raw files, so if you really want high quality and to use all the advantages of your digital camcorder, you also can copy the movie back to the DV tape with Kino and your camcorder.
To send the video stream from a camcorder to a PC and back, you need an IEEE1394 interface on both sides, the PC and camcorder. Check your PC; many modern computers, including laptops, have this interface already built-in. If not, you can buy an IEEE1394 card separately from many vendors. You certainly need a digital video camcorder. Your camcorder probably is either Digital 8 (D8 for short) or MiniDV.
To connect the camcorder to the PC, you need a cable. Camcorders usually have four-pin female connectors, and PCs have six-pin connectors. Take a look at your computer (or IEEE1394 card) and buy a 4-4 or 4-6 cable if you do not have the correct cable.
Obviously, you need a PC equipped with a large capacity hard disk. You must have a lot of free space. For instance, to copy a 60-minute MiniDV tape to your computer, about 12Gb is necessary. Further work might need about 15Gb for edited frames and sounds, so 27Gb of free space is the absolute minimum for making a movie from one hour of raw video. Depending on what you want to do, you may need an extra 14Gb to export your results to a new .dv file. While capturing, the computer has to record about 3.5MB per second, so the hard disk should work as quickly as possible. Any modern Ultra-DMA drive works if configured properly.
A 1GHz processor and 128MB of memory is the absolute minimum suitable configuration for working with video. To work comfortably, you could use more memory and possibly a more powerful CPU.
As far as software, you need Kino and the libraries it uses, but this is not everything. Kino provides only basic tools for editing and has few effects. Tim Shead and Dan Dennedy have been developing timfx, a set of Kino plugins that adds extra effects. Another plugin, called dvtitle, by Alejandro Sierra is needed for adding titles.
Because Kino requires additional programs and libraries, installing from source is not a simple task (see the on-line Resources section for Kino's home page). Kino is available as a package for several distributions, including Debian, SuSE and Fedora. Installing a package is much easier than building from source.
Kino development is progressing quickly. While writing this article, the latest version was 0.7.3. In Debian 3.0 (stable), the Kino version is 0.5.0, and Debian 3.1 (the developing branch) suggests the latest version is 0.7.3. SuSE 9.1 suggests using Kino 0.7.0. To help you keep the programs up to date we created all necessary packages. See Resources for links.
Once the software is installed, connect your camcorder to the PC by IEEE1394, and run the command kino from any X terminal or, under KDE or GNOME, from the Alt-F2 dialog. The Kino opening window is similar to the one shown in Figure 1.
The GUI is easy to understand. To capture video, choose the Capture tab on the right. Before starting to capture, however, it is best to check your preferences. Click on Edit→Preferences to see the default settings. Set Normalisation, Audio and Aspect Ratio according to your camcorder. Parameters depend on the camcorder you are using and the country where you bought it. The NTSC standard is used in the USA, Canada and Japan, and the PAL standard is used everywhere else. Camcorders usually have two audio modes, 16 bits and 14 bits, and the latter often is set by default. Change this to 16 bits before recording for better quality.
Captured frames can be stored in three formats, .dv and two kinds of .avi files. Generally, it does not matter which kind of format you use; we prefer to use raw DV.
After setting your preferences, press Capture, and enter a filename for the captured video without using an extension. You also can choose the Auto Split Files option so Kino saves each automatically recognised change of scene in a separate file, adding a number to the core filename. You can accept the default settings for all the rest.
Now, set your camcorder so it understands control signals. Usually this is in the Play mode, but check the manual if you are uncertain. Try controlling the camcorder with Kino by moving the tape back and forward. Try pressing the Play button in Kino. The video should start playing, and its output should be displayed in the main Kino window as well as on the camcorder screen. Notice the dropped frames field. Theoretically, this should be zero, but in practice, it's not bad if the first one or two frames are lost. If, however, the number of dropped frames keeps increasing, your hardware is too slow or misconfigured. If you cannot control the camcorder with Kino, try loading the raw1394 driver manually. As root, type modprobe raw1394.
If you have slow hardware, you also can try using dvgrab, a command-line tool for grabbing DV. This program is available from the Kino home page (see Resources). Before using it, exit your X session. Follow the directions from its man page. After grabbing the raw video, you can start Kino and load the captured files for editing as described below.
If the Play option operates correctly, you can start capturing. Go to 1–2 seconds before the position where you want to start, and click Capture. Kino starts the camcorder and captures. Pressing Stop at any time stops the capturing. Video transferred in this way appears in the scene list on the left part of the Kino screen. AutoSplit sometimes works incorrectly, but you can correct that later. Kino's window right after capture is shown in Figure 2.
As soon as you finish capturing, select Save from the File menu, and save the project as a Synchronized Multimedia Integration Language (SMIL) file. An SMIL example is shown in Listing 1. Between the <seq> and </seq> tags, clip descriptions appear. Each one defines a simple or a complex scene. A simple scene is described by a <video...> command that points to the first and the last frames of the clip file that will be used in the movie; a complex scene is a set of simple scenes. The first frame of each scene is shown in the left panel of the Kino Storyboard.
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
- Google's SwiftShader Released
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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