{"name":"605120","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/7\/b7aef74c52c1cc43cb23bc7a5aa445b7.png","w":640,"h":351,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/7\/b7aef74c52c1cc43cb23bc7a5aa445b7"}

http://sourceforge.net/projects/alleg/files/allegro-unstable/5.1.0/

MD5SUMS:
5c4dc39e6f64e4ccc33acc58615399f1  allegro-5.1.0.7z
908776157b355acaa9b6bcf112692a87  allegro-5.1.0.tar.gz
c5d97f63d794150867cab7a47c53c85f  allegro-5.1.0.zip

P.S. if you like, please send doodles to accompany future releases to me.

To quote from the Allegro website:

Beautiful stuff...

favorites include:

• ALLEGRO_SRC_COLOR, ALLEGRO_DST_COLOR

• ALLEGRO_INVERSE_SRC_COLOR and ALLEGRO_INVERSE_DST_COLOR

• Added API for registering callbacks to intercept window messages on Windows

• polygon triangulator

• Added a shader addon

and ALLEGRO_VIDEO. That's tight.

Did you draw the WIP logo? I love it.

My favorites are:

• al_convert_bitmap

• API related to touch input

• video player addon

I didn't know you can release an unstable version, though, I mean, wasn't already there?

May be a 3D doodle? and should make reference to W.I.P API isn't?

We release unstable snapshots at semi-regular intervals to keep things moving along, and to get more testing.

Thanks. Downloading.

I'm looking forward to test the video addon.

Sure, anything you like. I can't promise when the next release will be, it depends how much activity there is.

Do we have names for the releases?

No code names!

Allegro 5.1.0 "Weeping Alligator"

Crocodile tears?

Will there be Windows binaries available for those without the (ever growing) list of dependencies and CMAKE as 4.9.x had? I'm sure it would encourage more people to try and test it.

I think the only new dependencies are for the video addon - which probably should be left out of the Windows binaries anyway. Building the non-GPL version of ffmpeg can be quite an undertaking after all.

The ffmpeg backend didn't work that well when I tested it, at least on higher resolution files. I didn't put any effort into fixing it because I'm hoping we can replace it with a Theora backend, with much simpler code.

Amen.
------
FFmpeg it's cool too, but I think is too big, obviously you can compile it with the formats that you want (Theora included). I think it has it disadvantages and advantages, if someone wants to create a video editing tool, supporting only theora is not a good idea (working with just Ogg files?) , but I think if someone would like to create a video editing tool would have to go deeper than just ffmpeg anyway (I think ).

At the other hand, Theora is really cool for: streaming or HD, I have test it and it's really awesome, very competitive, and if you use it right, you can have a lot of video in a few Mb's. Allegro 5 is already using the ogg container for audio, so I think there would be a cleaner code (and lighter binaries).

Well... At leas that is what I think...

Just about covers every permutation I can think of, and who needs the decorator pattern when you have C

Yes, but then they'll see things like this:

And all the effort will be for nothing.

{"name":"605129","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/c\/dcf1ef3cbe7d88b2dcb0223345dc984e.png","w":302,"h":240,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/d\/c\/dcf1ef3cbe7d88b2dcb0223345dc984e"}

It will take roughly twice as many bits. For a game it probably doesn't matter, but I wouldn't call it competitive in any way - it's about at the level of mpeg2 (which is ancient). However there's also webm which seems to be rather competitive, except supposedly it's just a massive patent infringing copy&paste job from H264

Still, personally, I'd use theora for all video right now since as I said for a game it shouldn't matter all that much.

Well, when I said competitive, I meant that it's free, and it's almost like a patented video codec. It's not better than other non-free codecs like h.264, but I think comparing it with h.263 is too cruel(depends), besides if I try to sell a game with the h.264 codec I may get into trouble. So for that reson I said it was competitive, I guess I should have used other words, though. HoHoHo!!

But I don't know... As far as I can use Theora, I don't care whatever you use guys.

Thanks for all the work anyway!.

Mark Oates, I demand you clean all the Pepsi(TM) off my keyboard. I'm waiting!

There will be binaries for Windows once I figure out how to weak link some new dependencies (Cg.dll and D3DX mostly).

Hey there, just in case you have the time... What do you mean with "weak link"?, I have never heard that term.

In this very case I mean dynamic linking.

I'm trying to build 5.1.0 right now. I'm getting this:

WARNING: allegro_video wanted but no supported backend found

I had built some earlier 5.1.0 revision but never got into building the video addon. Now I want to try it and I've already downloaded the FFmpeg dev binaries including the lib and header files. I was expecting for cmake to allow me to define something like FFMPEG_INCLUDE_DIR as for other build options but looks like I have to put the libs directly on my MinGW path. Is there a plan to change this?.

[EDIT:] I placed the FFmpeg files in the MinGW folder but I'm still getting the same warning. So, how do you build the video addon?.

There is no way... I have also tried and I get the same warning. Elias has just pulled our leg with the video addon .

Looks like the video addon is currently only enabled for Linux through cmake. I'm guessing the file cmake/AllegroFindFFMPEG.cmake is where the corresponding cmake changes must be done.

Unfortunately, I know only the very basics of cmake so I can't figure it out yet.

Yeah, I believe the cmake build needs to be adjusted. Anyway, I'm putting off getting it to build outside linux until the theora backend is done (or until i need it myself ).

After doing some ugly changes to the cmake files, I managed to build the video addon. However, when I run ex_video I get audio but no video at all, al_get_video_frame() returns NULL. I wouldn't go as far as to tell that it's broken on Windows, though. Chances are I did something wrong. It could also be due to my too old machine/graphics card.

Finally, what's with this line in ex_video?:

fprintf(stderr, "SDL: could not set video mode - exiting\n");

Ups... Coping and pasting?

Ken can you post the modifications here?, I would like to test it too. I just don't have the time to learn more about cmake. Thanks

This is what I did (yes, it's ugly).

Edit the file cmake/AllegroFindFFMPEG.cmake and add the following:

if (WIN32)
    set(FFMPEG_FOUND 1)
    set(FFMPEG_LIBRARIES avcodec avdevice avfilter avformat swscale swresample avutil postproc h:/libs/allegro-5.1.0/build/lib/liballegro_audio.dll.a)
endif()

For the allegro_audio lib I had to write the full path. Change the path accordingly.

Hope you can get it to work.

Let me see. I'll try it when I get the time.