Dominick Accattato, CTO Infrared5

The other day I was creating a distribution of Red5 and was getting “unresolved compilation problems”. At the time I was pretty impatient so I immediately contacted Paul Gregoire. Turns out I should have just took a small break and got some fresh air. The solution was to clean the build and re-create the distribution. Here is how I solved the issue with Paul’s suggestion:

ant -Ddist.dir=./dist/test clean ivyclear dist

Caused by: java.lang.Error: Unresolved compilation problems:

The import org.red5.server.net.rtmp.message.StreamAction cannot be resolved

StreamAction cannot be resolved

StreamAction cannot be resolved to a type

StreamAction cannot be resolved

DISCONNECT cannot be resolved

CREATE_STREAM cannot be resolved

DELETE_STREAM cannot be resolved

RELEASE_STREAM cannot be resolved

PUBLISH cannot be resolved

PLAY cannot be resolved

SEEK cannot be resolved

PAUSE cannot be resolved

PAUSE_RAW cannot be resolved

CLOSE_STREAM cannot be resolved

RECEIVE_VIDEO cannot be resolved

RECEIVE_AUDIO cannot be resolved

I just released the fifth video in the series which demonstrates how to remotely debug the Red5 server. The video includes:

-edit the red5-debug.sh shell script
-remotely debugging Red5 from within eclipse

Please feel free to comment and or suggest additional topics! Thanks

Video Link

Here’s an interesting video on the evolution of security!

If you’re just getting into Red5, and you are wondering what it’s capabilities are and how you could approach saving audio/video streams with Red5, then please read on.

Recently on the mailing list, a question on how to save streams to the server came up via a new Red5 user. The user was kind enough to explain that they hadn’t much knowledge on the subject and that they did their due diligence by searching the web for answers.  Unfortunately, there is a lot of information on saving streams, but most of it is geared towards long winded examples and less on teaching the user what they need to do to get from A to B.  Keeping this in mind, I gave the following answer which instead of providing an entire example, just gave him the tools and knowledge to get to their next step in the red5 evolutionary process.  Soon, this user may be spreading the knowledge back by providing these same answers to other users or contributing to our wiki.  My suggestion is as follows:

I would suggest that you take the following approach:

• download and install red5
• open up the home page screen (http://localhost:5080/)
• install some examples
• look for an example that does something you’re looking for.. probably oflaDemo in your case or the publisher application.

once you have this 50,000 foot view, you will can check out the example code and look at what API you will need.

In your case, you’re going to want to look into the following Clientside API:

• NetConnection
• NetStream

example:

// create the connection
var nc:NetConnection = new NetConnection();
nc.connect("rtmp://localhost/myApp");

// create the stream
var ns:NetStream = new NetStream(nc);
ns. publish("myStreamName", "record");

The result will be an FLV file named “myStreamName.flv” located in your webapp’s streams directory.  This happens automagically on the server.  Of course there are ways to monitor and prevent this automagical functionality, but it’s a good start.

Also, keep in mind that the code above just publishes… there are equivalent api calls to play a stream: e.g.:

ns.play(”myStreamName”);

Hope this helps…

For those of you who have held back on working with Xuggle due to their restricting AGPL licence you can now breathe a sigh of relief and head on over to the xuggle site.  The Xuggle team has released a new version named “Eliza” and ain’t she pretty! In addition to the release, they have slapped the good old LGPL license back on the packaging.  What this means is that you can now use Xuggle 3.3 with your products without:

Instead, you can now freely use Xuggle 3.3 as you please.  The only restriction that LGPL places on your project is that you must contribute back any code modifications to the source code of Xuggle.  You should all be pretty familiar with this licensing model since it’s used with some of your most prized open source technologies such as Tomcat and your’s truly Red5! Many of you might remember that Xuggle 1.x was also licenced under LGPL, however starting with 2.x, the licence had been changed to AGPL. The news of LGPL is a big win for the Red5 community.  Good to hear and I thank the Xuggle team for their contribution.  So what are you waiting for, go get Xuggle 3.3 Eliza!

Head on over to Chris Allen’s site and get another inside look into the development of Trench Run on the iphone.