April 9, 2012
Hot on the heels of Xuggler 5.3, comes Xuggler 5.4. Another bug-fix release, and only one bug fix at that:
- “No-install” Jar now works on Ubuntu 11.10 and CentOS 6.2. If you’re on older version of Ubuntu or CentOS, you’ll need to compile your own version (sorry).
Also, for grins, I’ve written an example for how to use Xuggle within a PlayFramework application. It’s available from GitHub here. And to demonstrate the power of no-install, I also deployed it on Heroku earlier today:
Xuggle-Xuggler-Play Demo (Will Be Turned Off By May 2012).
April 5, 2012
Xuggler 5.3 was released to our ivy repository last night and is a bug fix release. Only one new feature — and technically it’s a separate project to aid in testing. Still, some big bugs with “no-install” for Windows were fixed, and some of the RTSP users out there in the wild will be happier. Enjoy.
To see how to download it, go to our downloads page.
- New xuggle-xuggler-test project demonstrating maven usage of xuggler and doing VERY intensive tests of Xuggler (takes a long time to run and will eat lots of cpu).
- Windows no-install builds should work correctly
- RTPS file reading fixed
- StdioURLProtocolHandler should work on Windows
- Remove any latest.revision ivy dependencies in xuggler
- libvpx should link into ffmpeg when cross-compiling on platforms that require PIC
- pixel formats updated in com.xuggle.xuggler.IPixelFormat for latest ffmpeg version
- spandsp build no longer uses automake if available on building platform
p.s. I included the happy dog for no reason at all 🙂
April 3, 2012
One of the things that has bugged me about Xuggler from day-zero was the need to separately build and install the native code BEFORE you can do anything useful. With Xuggler 5.2, for the most common operating systems, this is no longer necessary. Happy day.
Native code is what gives Xuggler its power, but native code to Java users is strange. We invested a lot into Xuggler to make it POSSIBLE to build it on many operating systems, but time and time again we’ve found that is still too high of a bar for most users. Who wants to worry about installing C++, C and assembly compilers? Answer: almost no one (myself included).
What was worse than building though is the need to install Xuggler BEFORE it could run. This mean setting some obscure operating-system specific environment variables and hoping for the best. Ugh.
So now, with Xuggler 5.2, the default Xuggler installation INCLUDES all the pre-compiled native code for the 6 most commonly requested operating systems, and can find that code WITHOUT setting environment variables. That means for Windows users, Xuggler now looks like any other Jar file. It includes support for both 32 bit AND 64-bit operating systems. Neat.
There are a few more bug-fixes coming in Xuggler 5.3, but otherwise, we’re narrowing down on the final release of Xuggler for the 5 series. Enjoy.