Kino Tips: Installing from Scratch and Exporting MPEG Videos
Although a digital camcorder can be used to show the exported movie on a TV screen, we do not recommend wasting the limited camcorder resources. Keep the full-quality version of the movie on a DV tape so you can work with it later.
Because the human eye barely can detect the difference between an MPEG 2 compressed movie and the original DV format when shown on a TV screen, making a DVD for general viewing is more useful.
The structure of a DVD is not simple. In general, it is possible to make a DVD that contains a movie, additional photos and so on, but this is a topic for another article. With Kino, you can build a simple DVD structure to use with a standalone DVD player.
Begin at the Export tab. Select DV Pipe and than choose the tool FFMPEG DVD-Video Export. In Profile, select Output Standard DVD-Video directory (All only); in cases of widescreen sources, use widescreen output. Next, type the output file name without any file extension. This name becomes the top name on the DVD directory tree. Press Export.
Exporting may take hours. We like to start the process before going to bed. When exporting is complete, you have the resulting DVD directory tree (VIDEO_TS and AUDIO_TS), named according to your input. You then can check the results with mplayer or xine.
Before burning the final DVD, you should make the image. We prefer to use the following command, assuming the name movie_dvd :
mkisofs -dvd-video -o movie dvd.iso movie dvd
You have to burn this image; we usually use growisofs for this task:
growisofs -dvd-compat -Z /dev/dvd=movie dvd.iso
The option -dvd-compat is used to provide maximum media compatibility.
You then can design your own image for the DVD label, print it out and put this new DVD into a real DVD box.
If you have the movie saved as a .dv file, you easily can turn it into an MPEG 4 video and burn it to a CD. Because not all of our friends are Linux users yet, we prefer to export to an .avi MPEG 4 file.
To increase the quality of the video, we suggest using a two-step encoding process. For the first pass, use:
ffmpeg -i foo.dv -f dv -pass 1 -passlogfile foo -vcodec mpeg4 -g 250 -qscale 2 -bf 2 -acodec mp3 foo.avi
For the second pass, use:
ffmpeg -f dv -i foo.dv -s 640x480 -4mv -part -strict strictness -pass 2 -passlogfile foo -vcodec mpeg4 -g 250 -hq -bf 2 -b 1500 -acodec mp3 -ab 128 foo.avi
The input file, the output file and the log file in both of these steps must be the same. Also, you have to specify your desired bit-rate during the second pass. The larger the bit-rate you set, the better quality movie you will have. We cannot suggest a value, however; it usually is based on the size of the requested file. You can repeat the encoding a few times, though. Start with a high bit-rate, and if you are not satisfied with the size, decrease the rate and repeat. Do not forget check the quality as you go.
Processing the file takes some time. Depending on the size of the movie, it can take more than five hours for one step. In the example above, we used PAL sources. If you have NTCS instead of PAL, use -g 300 rather than -g 250. Play with the options and have fun!
Olexiy Tykhomyrov (firstname.lastname@example.org) has been using Linux since 1994. He works for the Department of Experimental Physics at Dnepropetrovsk National University and teaches physics and communications. He loves his son Misha, who calls him Tiger because some of his students are afraid him. Tiger likes swimming and traveling.
Denis Tonkonog, a former student of Tiger, also works at Dnepropetrovsk National University and likes traveling and fishing with a gun. Friends call him Black Cat but nobody explains why. He can be reached by e-mail at email@example.com.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Hacking a Safe with Bash
- Django Models and Migrations
- Secure Server Deployments in Hostile Territory, Part II
- Huge Package Overhaul for Debian and Ubuntu
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Home Automation with Raspberry Pi
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development