Skip to main content

How to make VCD with K3B using Linux

If you have a video file ie .avi, or .mp3 and you would like to burn to CD in VCD format so that you can play it with your vcd player. This is how I did it.

avi file

Let's say you have a .avi video file named myvideo.avi. You have to convert it
to mpg.

ffmpeg -i myvideo.avi -target pal-vcd myvideo.mpg

(Note: the -target command requires at least version 0.4.9 of ffmpeg)

Burn it!
Using k3b, a KDE burning software, you can burn it to cd in vcd format by selecting File -> New -> New Project -> New Video CD Project menu. Please make sure the file size does not exceed the storage size of the CD. If there is an error indicating vcdxbuild binary not found, you need to install vcdimager package.

Problem: There is no vcdimager package for Slackware as I know of. After searching high and low (even using slapt-get was no help), I opted to download sources: vcdimager, libpopt and libcdio source packages.

For all this source,

./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var

and as usual,

make; make install

After compiling and installing all of these packages, k3b should be able to find vcdxbuild binary and successfully burn the file to cd in vcd format.

vcdimager :
popt library :
libcdio :


DA5H said…
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var

doesn't work, i have to change usr 4 my user name???. I show you my terminal
zamri said…
can u translate the error message for me?

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src
http_access allow our_networks
http_port transparent
always_direct allow all

where is your proxy server IP address.

If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.

Moving your mysql database to another hard disk

Recently, my server's only hard disk was almost full. I bought a new hard disk with bigger size and I decided to just add it as a second hard disk. Since I need to move it to the 2nd hard disk, I need to find a proper way to move the db with minimum downtime. So I googled around and found a solution.
First, I needed to format the 2nd hard disk and I chose xfs as the filesystem. I created 2 partitions using Linux's fdisk for this task. First partition is 10 GB and 2nd one is around 900 GB. That's approximately added up to 1 TB. Then I mounted the 2nd partition in current partition eg /media/hd2 as follows:
mount -t xfs /dev/sdb5 /media/hd2
where /dev/sdb5 is the partition and /media/hd2 is the mounting dir.
Stop mysql db before doing anything:
service mysql stop
Afterthat, I copied the entire db to newly mounted hard disk:
cp -rv /var/lib/mysql /media/hd2
It will take a while if you have huge databases.
Then, change the ownership of the dir to user and group of mysql:
chown -R mysql:…