I bought Panasonic SD-9 2 years ago and since then I was filming all my vacations, parties, etc. Usually when I film I end up with at least a 50 MTS files that are mostly unrelated, so I wanted to have some nice fade out and fade ins between the joined slices. Those fades are the only thing that was some kind hard to do in linux, but half a year ago I found a nice patch to ffmpeg that does exactly this. So here we go.

Requirements:
1. ffmpeg source code (if you use the latest trunk then you need libx264 version >= 0.99):
svn co svn://svn.ffmpeg.org/ffmpeg/trunk
2. patch file (mail list post, or patch authors site or the file hosted on my blog)
3. mencoder (it is used to count the total frames of the movie)
4. avimerge (to put all the converted files back together)

Steps:
1. Go to the directory for ffmpeg
2. Apply patch (patch -p 0 < patch_file)
Application of patch may fail, as ffmpeg is changing, but all you really need is vf_fade.c file placed in libavfilter directory, and add line:
OBJS-$(CONFIG_FADE_FILTER) += vf_fade.o
to libavfilter/Makefile, as well a line:
REGISTER_FILTER (FADE, fade, vf);
to libavfilter/allfilters.c

3. Build ffmpeg: ./configure with appropriate options, mine are:
--prefix=$HOME/ffmpeg --enable-libx264 --enable-libxvid --enable-libvorbis --enable-libtheora --enable-libmp3lame --enable-libfaac --enable-avfilter --enable-nonfree --enable-postproc --enable-runtime-cpudetect --enable-hardcoded-tables --enable-hwaccel=h263_vaapi --enable-hwaccel=h264_vaapi --enable-hwaccel=mpeg2_vaapi --enable-hwaccel=mpeg4_vaapi --enable-hwaccel=vc1_vaapi --enable-hwaccel=wmv3_vaapi --enable-filter=fade --enable-encoder=libx264 --enable-encoder=libxvid --enable-encoder=libmp3lame --enable-encoder=libfaac --enable-encoder=wmv2 --enable-encoder=wmv1 --enable-encoder=vorbis --enable-encoder=mpeg4 --enable-encoder=ac3 --enable-decoder=h264_vdpau --enable-gpl
And make, followed by make install.

Now you should have working ffmpeg with fade in/outs.

Here’s a make_avi.sh script that I’ve written for this:

#!/bin/sh
BIT_RATE=2700k
SIZE=720x576
fade_dur=15
FFMPEG=ffmpeg
for FILE_IN in $*; do
echo -n "$FILE_IN...."
#last_frame=`$FRAME_COUNTER $FILE_IN`
last_frame=` mencoder -nosound -ovc frameno -vc null -o /dev/null $FILE_IN 2>/dev/null | egrep " [0-9]+ frames\$" | gawk '{print \$12}'`
echo $last_frame
filters="-vfilters fade=in:0:$fade_dur,fade=out:$[last_frame/2 - $fade_dur-5]:$fade_dur"
${FFMPEG} -i $FILE_IN -deinterlace -vcodec libxvid -aspect 4:3 -r 25 -s $SIZE -b $BIT_RATE $filters -acodec libmp3lame -ac 2 -ab 128k -y -pass 1 -passlogfile temp.log -f avi /dev/null && \
${FFMPEG} -i $FILE_IN -deinterlace -vcodec libxvid -aspect 4:3 -r 25 -s $SIZE -b $BIT_RATE $filters -acodec libmp3lame -ac 2 -ab 128k -y -pass 2 -passlogfile temp.log -f avi ${FILE_IN/MTS/avi}
done
in_file_list="$*"
out_file_list=${in_file_list//MTS/avi}
avimerge -o merge.avi -i $out_file_list


Just save it, change FFMPEG variable to your location of ffmpeg and run it passing a list of MTS files, it will create a merge.avi file in the current directory.
You can also tweak the “fade_dur” to make the fade longer/shorter.

I know it’s not much of a how to, but maybe someone will find it useful.

If so, than we have something in common, for years I have been asking myself those questions, while not having enough time to dig into the subject and learn more about Java. This language had always seemed to me to slow and having an ugly GUI (remember all that applets floating around the web in the late 90-ties ?).

As I have finally found some time to study a part of J2EE consisting of Servlets and JSP (using the excellent Head First Servlets and JSP: Passing the Sun Certified Web Component Developer Exam (SCWCD) by Kathy Sierra et al.), I will present you with what I have learned. I really hope that you will benefit from the information presented below. If you have bought some kind of Tomcat hosting or some other J2EE web hosting than you can skip the first point, and go straight to the second one.

1. Getting a web container - Tomcat

First of all, you should know that most J2EE technologies (OK, maybe not most, but few crucial ones: EJB, servlets & JSP) cannot be run like normal Java applications just by invoking java executable in the command line.

Servlets, JSP and EJB need a... lets call it a framework and this kind of framework implementation specifically for servlets/JSP (called a Web Container) is Apache Tomcat, and it will be the basis for this tutorial. If you would like to use some other container than have a look at e.g. Jetty.

Now, lets start with the tutorial.

Garmin nüvi 660 wide screen GPS review

First you need to have JDK installed, which can be downloaded from http://java.sun.com/javase/downloads/index.jsp (choose JDK 5.0 Update x), and then install the JDK (if there are any problems than let me know I'll try to clarify this).

Secondly we will download tomcat from here and for this tutorial I use Tomcat 5.5.17. For the lazy ones, here is a direct link to 5.5.17 version.

Before running Tomcat, there should be a JAVA_HOME variable defined in environment, how to do it:

in Windows: Go to Control Panel, double click System, select Advanced tab, and click "Environment Variables" button. Check if there is no JAVA_HOME defined in user and system variables pointing to JDK directory, if there is then double check that it points correctly to a JDK (not JRE), if there is no such variable then click New button in system, give a JAVA_HOME name, and paste in the directory where your JDK is sitting (on my system it is "C:\Program Files\Java\jdk1.5.0_06").

in Unix: Find where you have JDK, usually "where java" or "whereis java" should give you the path to the java executable (not a symlink!), on my system it is "/opt/sun-jdk-1.5.0.07". Depending on the shell you have, setting variable will be "export JAVA_HOME=..." or "setenv JAVA_HOME ..." (replace the dots with the path to the JDK). BTW, please feel free to ask be questions if you have any problem.

Unzip the archive in a directory you want and start the file startup.bat. Unix users should first do "chmod u+x *.sh", and then run startup.sh. If everything works fine then you should see something like this:

Now go to the address http://localhost:8080/ and see if it really works, you should see a page about Apache Tomcat.

If it is correct then....

Congratulations! You have just made the first step into the J2EE world ;).

2. Writing the first servlet

Now it's time to get our hands dirty and write some code, but first we need to make some essential directories.

Create a directory where your project will be kept (I'll name it FirstApplication), under that directory
create following dirs:

If you use some java IDE (e.g. Eclipse or NetBeans) for developing code, then mark the "src" directory as the one containing the source, and the "classes" as the one with binaries. For the rest of us lets make directory for com.coderookie, that is under "src" mkdir "com" and "com/coderookie".

Go into the WEB-INF/src/com/coderookie dir, and create a file called FirstServlet.java with the following code:

And now for explanations:
#1 - servlet is really just a class that extends HttpServlet and implements certain methods

#2 - here is one of those mentioned methods doGet is responsible for handling the GET method (pretty obvious) of HTTP protocol (see this wiki page for more information on HTTP methods)

#3 - HttpServletResponse has a method that allows us to get a PrintWriter for the web page output

#4 - using PrintWriter methods we can write anything (using a web page) to the user that entered our servlet

Besides writing the code, we need to write a web descriptor for our application. Descriptor is used to inform web container about the applications ingredients. You must put there such information as: what are the names your servlets, how URLs should map to a certain servlet and much more (I'll cover more in other posts).

Create a web.xml file in WEB-INF directory:

Don't worry about the long tag, you will copy it between different applications, you do not have to memorize it.

Go to the WEB-INF directory and run following command (you MUST replace TOMCAT with the exact location of your tomcat installation e.g. "/home/krzyk/apache-tomcat-5.5.17" or "d:\tomcat")

For Windows users (note "\" and ";"):

For Unix ones (here we have "/" and ":"):

It is time to test your servlet, copy your projects directory to TOMCAT/webapps (again change TOMCAT to the directory where you have unzipped Tomcat). Change directory to TOMCAT/bin and do shutdown.bat (or shutdown.sh) and then startup.bat (or startup.sh).

If there is no error then type in a browser http://localhost:8080/PROJECT_NAME/first (where PROJECT_NAME is a name of your projects directory in webapps directory). Notice that "/first" is the url-pattern from web.xml file.

You should see a "Hello world!" displayed on this page, if it is than we have another success!

3. Combining servlet and JSP

What if you would like to print a HTML page using the servlet above ?

Using println for the whole page would be a horror, just have a look at the example presented below:

To much out.println, don't you think ? But have no fear, JSP to the rescue.

Create a file named hi.jsp (or whatever you like) and place is either in WEB-INF or in the directory of the project (the one that is higher then WEB-INF):

This page contains an EL (Expression Language) structure ${title}, which can be set from the servlet, we will use this page as a view for our servlet.

Change the code of FirstServlet to this one:

Explanations:
#1 - for now, just assume, that everything dynamic that you wan to display on the JSP page, should be previously set by the setAttribute of the HttpServletRequest, first parameter is the name which you will use to display the second argument in JSP (here "title", so in JSP it will be ${title} and will be replaced by Tomcat with "My first super page")

#2 - we must get a ServletContext (this object keeps global configuration for the application), and from it, the RequestDispatcher for the JSP page, in the parameter you need to provide the path to the JSP, relative to the application folder (that is, one step higher than WEB-INF), OK this might be confusing, so look at the ASCII drawing below. And finally, we forward the control to the JSP page by calling forward method of the RequestDispatcher.

Now make your favorite drink ready, and go to the http://localhost:8080/PROJECT_NAME/first

Probably you should see a page with title "My first super page", and "Hi World!" text on it. If it works, then once again, you rule (and I haven't made any mistakes ;).

This is it for now, stay tuned for the following parts, introducing more advanced topics, you can now review material from this tutorial, play around with the JSP and servlet, have some fun. If you develop an interesting application using the very basic information above, please send me an info, a link to the application or the source code. The next part of this tutorial will be about Model-View-Controler design pattern and how to apply it to servlets and JSP.

Add to del.icio.us

PPP is a way of developing routines by writing pseudocode for them in the first place (not a new topic) and after that, making the pseudocode a comment in the routine (functions, procedure, method or whatever your language calls them). After comments are in the empty routine, the last thing to do is write the code below appropriate comment lines.

I know it isn't the clearest explanation, here look below at the example that I prepared.

We'll work on a routine responsible for query searching in a search engine (based on my very simple & ugly search engine.)

Magellan Maestro 3100 a best value GPS for vehicles, review

First, let's write the header comment for the routine:

Pretty simple, but should state what the routine will do. Next I will use a simple English statements as pseudocode and write the body of the routine:

It is not the most complicated routine in the word but will do.

Here's the code added for this routine:

The code above is in PHP but the same could be done for any other language, that's the beauty of pseudocode :) . You could give the pseudocode to some other programmer for a review and he doesn't have to know the lang in which it is written.

Some useful notes (once again taken from Code Complete, Second Edition) on how to write the pseudocode:

1. use English-like words to describe the code
2. do not use syntactic elements of the programming language
3. the pseudocode should be written at the level of intent ("whats" not "hows")
4. it should be enough low level to enable developer to write code based on it

That's it for this post, give me a hint if you liked the code, or better, try to write some more examples of the pseudocode.