The key here is the frame_rate value. Assuming your original video file is X and you want your video to play N times faster, you should sent your new frame rate to be (X*N):1 For example, if your video has a frame rate of 25 fps and you want to increase playback by 4 times, you should use 100:1 for your frame_rate value. You can use the same command to create a slow motion movie. If you wanted to slow the video down to about half speed, you would use 12fps or 13fps for a 25 fps movie. You can find the current fps of your video by running
What I did to turn a 50 min movie to a ~12 min video:
AddThis just launched a new Labs project, AddThis Follow. Super simple to get setup. You can see I already added it to the side bar of my blog. Allows users to easily follow me and AddThis will provide the analytics on those of you stalking me from my blog. Good stuff.
I’ve been really happy with my recent move over to http://www.linode.com. I was checking out their API and noticed there wasn’t any Java client. I wanted a do a small pet project so I took a couple hours this weekend and wrote a Java client for the API.
Open-source with a business model company, Terracotta, acquired Ehcache, the very popular caching library.
The creator and maintainer of Ehcache, Greg Luck, had these things to say about the acquisition:
What this means for Ehcache Users
Ehcache remains under the Apache 2 license
New feature development is accelerated with the addition of a team of engineers working full-time on Ehcache
I am full-time on Ehcache. I have not had the time I would have liked to devote to Ehcache (I have been doing a miserly 10-15 hours per week for the past 6 years) but now I do. Look out!
Ehcache extends its standards support. There are multiple emerging standards in this area and I plan to work with the community to lead further standardisation efforts. A lack of time has been my biggest obstacle in doing more on this to date.
Ehcache gets new hosting at ehcache.org with state-of-the-art forums, source control and bug reporting. The changes will happen slowly and carefully.
File release at sourceforge.net is retained
Maven deployment to oss.sonatype.org and Maven Central is retained.
Distributed caching via Terracotta is seamless. Ehcache users can have full confidence that they can start single node and scale as high as they need to with Enterprise features.
Enterprise support, training and professional services for Ehcache. I have provided these for a few years now, but now we will have the full Terracotta organisation behind them with the usual SLAs.
What this means for Terracotta Users
Ehcache APIs will replace Terracotta distributed cache APIs as a single caching interface / standard for Terracotta distributed caching
a single-node version of Terracotta ala Ehcache will be available for the first time
Full freedom to run on the latest version of Ehcache at all times, knowing it will work with Terracotta
Single vendor support structure for caching interfaces / libraries as well as their scalability / reliability runtime.
the investment protection of standards
It’s pretty cool to see open source companies like SpringSource (recently acquired by VMWare) and Terracotta making big moves. I look forward to seeing what’s next for these guys.
Last night Google announced Java support on Google App Engine.
After a bit of toying around, here are my findings.
The Eclipse plugin is pretty slick. Deploying and build is simple.
The dev server that you spin up locally looks to be jetty under the hood.
Objects intended for storage are JDO annotated and after compiling, you run the .class files through the DataNucleus Enhancer which adds additional metadata so Google can map it to BigTable. The Eclipse plugin automatically performs this step for you after compiling. The examples provide a bunch of ant macros to help facilitate building/deploying.
One issue that I had was that the project was building with Java 1.6 and I would get an error after compiling:
Caused by:java.lang.UnsupportedClassVersionError:Bad version number in.classfile
Even though they say they support Java 1.5 and 1.6, I guess this doesn’t work on the Java 1.6 for the Mac. Switching the build to 1.5 allows the DataNucleus Enhancer to run successfully.