| [Top] | [Contents] | [Index] | [ ? ] |
This manual describes the GNU VCDImager(1) package. It provides a front end, `vcdimager', to generate CD-ROM images suitable for being burnt on to CD recordables. It takes MPEG movie files as its input and generates an image file and a cue-sheet file. These can then be fed to a CD-recording program which recognizes the BIN/CUE-format, such as cdrdao(2), for instance.
Features of the backend library(3), on which all frontends rely, include:
This package also includes `vcdrip', a tool for dumping information about (Super) Video CD image files(5) and extracting the MPEG streams from them.
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
one line to give the program's name and a brief idea of what it does. Copyright (C) yyyy name of author This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. |
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. |
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice |
This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This chapter gives some background information regarding the underlying Video CD technology.
Warning: All information this chapter is presented without any warranty of accuracy or correctness. You are encouraged to send corrections and improvements for this manual to bug-vcdimager@gnu.org.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Video Compact Disc (Video CD or VCD) is a standardized digital video storage format. It is based on the commonly available Compact Disc technology, which allows for low cost video authoring. Video CDs can be played in most DVD standalone player, dedicated VCD players and finally, modern Personal Computers with multimedia support.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In general, the layout of a Video CD is as follows:
00:02:00 consisting of 16 empty sectors,
primary volume descriptor (PVD) and directory records with file
pointers to information area structures (described below) and external
pointers to MPEG/CD-DA tracks following the
ISO9660 data track.
00:03:00.
00:04:00.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are different Video CD flavours commonly used. The following sections tries to explain the differences amongst them.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is the most basic Video CD specification dating back to 1993(6), which has the following characteristics:
The Video CD specification requires the multiplexed MPEG-1 stream to have a CBR of about 174300 bytes per second(7) in order to accommodate single speed CD-ROM drives. This allows one of the following two resolutions:
The CBR MPEG-1, layer II audio stream is fixed at 224kbps with 1 stereo or 2 mono channels.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
About two years after the Video CD 1.1 specification came out, an improved Video CD 2.0 standard was published. This one added the following items to the features already available in the 1.1 specification:
By adding PAL support to the Video CD 1.1 specification, the following resolutions became available:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Also known as XVCD, this is not an official standard. It's actually just a name for VCDs which do not conform with the official standards in order to use the additional performance of the DVD decoders and thus achieve better image quality. Such an XVCD may be unsupported by many available standalone playing devices.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
With the upcoming of the DVD media, a new VCD standard had to be published in order to be able to keep up with technology, so the Super Video CD specification was called into life. Most notably a switch from MPEG-1 CBR to MPEG-2 VBR encoding for the video stream was performed. The following new features are based upon the Video CD specification.
For the Super Video CD, only the following two resolutions are supported for motion pictures:
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Just like the XVCD, and thus also known as XSVCD, this is not an official standard and may not work with all playing devices supporting SVCDs.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are a few command-line options for `vcdimager' at the moment:
$ vcdimager --help
Usage: vcdimager [OPTION...]
-t, --type=TYPE select VideoCD type ('vcd11',
'vcd2' or 'svcd') (default: 'vcd2')
-c, --cue-file=FILE specify cue file for output
(default: 'videocd.cue')
-b, --bin-file=FILE specify bin file for output
(default: 'videocd.bin')
-l, --iso-volume-label=LABEL specify ISO volume label for video
cd (default: 'VideoCD')
--iso-application-id=LABEL specify ISO application id for
video cd (default: '')
--info-album-id=LABEL specify album id for video cd set
(default: '')
--volume-count=NUMBER specify number of volumes in
album set
--volume-number=NUMBER specify album set sequence number
(< volume-count)
--broken-svcd-mode enable non-compliant compatibility
mode for broken devices
--sector-2336 use 2336 byte sectors for output
--add-dir=DIR add directory contents recursively
to ISO fs root
--add-file=FILE,ISO_FILENAME add single file to ISO fs
--add-file-2336=FILE,ISO_FILENAME add file containing full 2336 byte
sectors to ISO fs
-p, --progress show progress
-v, --verbose be verbose
-q, --quiet show only critical messages
-V, --version display version and copyright
information and exit
Help options:
-?, --help Show this help message
--usage Display brief usage message
$
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNU VCDImager expects MPEG streams in a format suitable for (Super) Video CD production.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Video CD specification requires the multiplexed MPEG-1 stream to have a bit rate of about 174300 bytes per second. The video stream is required to have one of the following resolutions:
The audio stream must be MPEG-1 layer II, fixed to a 224 kbits/sec CBR with 1 stereo or 2 mono audio channels.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When creating Super Video CD images MPEG-2 VBR streams are expected with a maximum allowed bit-rate of approximately 2.6 mbits/sec. The following video resolutions are (officially) supported(8):
There are a few other requirements imposed by the specification, like the need to encode scan information as user data in the picture layer of all intra pictures, and the requirement to precede every I picture by a GOP header which shall be preceded by a sequence header in its turn and possibly begin all in the same packet, thus forming a so called access point sector.
The audio stream must be MPEG-1 layer II, with a bit-rate ranging from 32 to 384 kbps kbits/sec bit-rate with up to 2 stereo or 4 mono channels, or 1 extended MPEG-1/2 multichannel (5+1) surround sound stream.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Furthermore the MPEG files should be aligned to 2324 byte MPEG packet boundaries. If they aren't GNU VCDImager will try to align them on the fly while issuing a warning that padding was needed.
%If on-the-fly padding should fail, you can try fixing those files with VCDpad %(9) or any other %program capable of aligning or fixing MPEG packets.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Files can be added to the ISO file-system, that is the first track of the Video CD, by making use of the command-line options `--add-file=FILE,ISO_FILENAME' and `--add-file-2336=FILE,ISO_FILENAME'. The latter option allows you to include files containing the complete user data of mode 2 CD-ROM sectors (10).
The path name given as ISO_FILENAME determines where to link the file in the file-system of the Video CD. The given path name must be a valid ISO9660 file name with the following restrictions:
If the parent directory for a file entry does not exist it will be created automatically on demand.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you happen to have a CD-i application consisting of the files `cdi_imag.rtf', `cdi_text.fnt', `cdi_vcd.app' and `cdi_vcd.cfg', with `cdi_vcd.app' being the main application executable, you could add the following lines to your `~/.popt' popt(12) aliasing file(13)
vcdimager alias --cdi \ --iso-application-id "CDI/CDI_VCD.APP;1" \ --add-file-2336 /usr/share/cdi/cdi_imag.rtf,CDI/CDI_IMAG.RTF \ --add-file /usr/share/cdi/cdi_text.fnt,CDI/CDI_TEXT.FNT \ --add-file /usr/share/cdi/cdi_vcd.app,CDI/CDI_VCD.APP \ --add-file /usr/share/cdi/cdi_vcd.cfg,CDI/CDI_VCD.CFG |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The `vcdrip' utility offers just a few command line options:
$ vcdrip --help
Usage: vcdrip [OPTION...]
-b, --bin-file=FILE set image file as source
--sector-2336 use 2336 byte sector mode for image file
--cdrom-device=DEVICE set CDROM device as source (Linux only)
-d, --dump dump information about VideoCD
--rip rip mpeg tracks
--rip-spi rip segment play items
-v, --verbose be verbose
-q, --quiet show only critical messages
-V, --version display version and copyright information
and exit
Help options:
-?, --help Show this help message
--usage Display brief usage message
$
|
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In the following example session, the files `track1.mpg', `track2.mpg' and `track3.mpg' are mastered into the default output files `videocd.cue' and `videocd.bin'. The volume label is set to `My Test VCD'.
$ vcdimager --iso-volume-label="My Test VCD" track1.mpg track2 track3.mpg finished ok, image created with 13421 sectors (31566192 bytes) $ |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The next example show how to extract the MPEG streams contained in the image file `test.bin' (the resulting streams are stored in files named `track_##.mpg' with `##' being the track number, starting with 0).
$ vcdrip-devel -v --rip --bin-file=test.bin --DEBUG: found ENTRIES.VCD/SVD INFO: track_00.mpg: 1262 -> 2555 --DEBUG: stream leadin at 1292 --DEBUG: stream leadout at 2360 INFO: track_01.mpg: 2555 -> 101705 --DEBUG: stream leadin at 2585 --DEBUG: stream leadout at 101510 INFO: track_02.mpg: 101705 -> 200994 --DEBUG: stream leadin at 101735 --DEBUG: stream leadout at 200799 INFO: track_03.mpg: 200994 -> 300041 --DEBUG: stream leadin at 201024 --DEBUG: stream leadout at 299996 $ |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
see http://www.gnu.org/software/vcdimager/
see http://www.ping.de/sites/daneb/cdrdao.html
the core of the GNU VCDImager
package consists of a library named libvcd, the frontends are
just user interfaces to the exported C-API
...though most devices will have problems with such out of specification media. You may want use the `--sector-2336' option for images longer than 80 minutes
on Linux it is supported to operate directly on CD-ROM devices
actually this flavour was based on the Karaoke-CD, which was the first MPEG based CD-ROM format.
2324 bytes of payload per sector * 75 sectors per second = 174300 bytes per second
actually you can try other resoulutions as well, but then you are leaving the SVCD specification behind you...
see http://www.nocrew.org/?part=vcdpad
8 bytes for subheader, 2324 bytes payload and finally 4 bytes for EDC
if no file name extension is supposed to exist the dot must be placed as a trailing dot.
see documentation for popt for more information about option aliasing
add it to `/etc/popt' if the setting should be available system-wide
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
Introduction
GNU GENERAL PUBLIC LICENSE
1. Video CD Concepts
2. Reference
3. Examples
A. Acronym Expansions
| [Top] | [Contents] | [Index] | [ ? ] |
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ < ] | Back | previous section in reading order | 1.2.2 |
| [ > ] | Forward | next section in reading order | 1.2.4 |
| [ << ] | FastBack | previous or up-and-previous section | 1.1 |
| [ Up ] | Up | up section | 1.2 |
| [ >> ] | FastForward | next or up-and-next section | 1.3 |
| [Top] | Top | cover (top) of document | |
| [Contents] | Contents | table of contents | |
| [Index] | Index | concept index | |
| [ ? ] | About | this page |