Simon Naarmann

Please try: Add `-DBUILD_ALLEGRO4=OFF` when you `cmake` DUMB. Also build and install DUMB first, and only then CMake/build/install Allegro 5. Reason: Allegro 4 (what you aren't using; you're using Allegro...

If kode54 considers this correct behavior of DUMB, maybe file the issue against Foobar? Subsongs of 0 seconds, or even shorter than 10 seconds, look like technical artifacts rather than...

I don't think Allegro 4 had a standard variable for its binaries. They're generally expected to be in the path, thereore I would add your local A4 directory to your...

> check if that variable is set and if not to run `allegro-config` This is a good idea.

What should we pass as `restrict_` when we have no idea what specific `.mod` file we are going to get? I've experimented with a handful of `.mod` files, and passing...

Thanks! Allegro 5 has always dispatched by filename extension even before calling DUMB. That's because Allegro 5 must decide which library to call in the first place. I've keep this...

Okay, I'll use 0 then for both `.mod` and `.nst`. Interesting that the naming didn't standardize. Then yeah, you have to offer this choice to guarantee optimal playback, because not...

Yes, this `restrict_` needs public documentation: Explain exactly why we should choose 0 as a default. Also we need a minimal example of DUMB-using code. The example programs are nice,...

I don't have a Mac to debug this, but here are ideas: * Look at [`macosx/qzmouse.m`, function `osx_set_mouse_xy()`](https://github.com/liballeg/allegro5/blob/master/src/macosx/qzmouse.m#L319), it does some coordinate mathematics. Are they semantically correct? * Which of...

@Dominator101: Does our bug still manifest with Allegro 5.2.8.0? [Allegro 5.2.8.0](https://github.com/liballeg/allegro5/releases/tag/5.2.8.0) merged #1286, the fix for OSX coordinates. That fixes #923 and, as pedro-w suggests, has a chance to also...