Page 2 of 5
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Mon Jul 11, 2016 8:35 am
by Someguynamedpie
Whoops, mixed up LZW with another algo, it'll be pretty easy to implement in Lua so I'll just go this route.
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Mon Jul 11, 2016 9:28 am
by zorg
Since Löve uses LuaJIT, you could go the FFI route too, if you're certain the given bitops libs are that slow on the lua side as well; write an unLZW lib in C, and then load and use it on the lua side.
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Mon Jul 11, 2016 9:37 am
by Someguynamedpie
The FFI route isn't acceptable here due to the desire to maintain cross platform capabilities.
The bitops are very fast, its just that there's no actual operators making it a pain to use.
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Tue Jul 12, 2016 4:08 pm
by josefnpat
@zorg Hello Frank. (Erm ... Dick ...)
@someguynamedpie @bartbes @slime As with many features discussed, I am happy to see JPEG and GIF go. The less features we have in the framework, the more we can concentrate on making the core of the framework better.
But with many features (e.g. IDEs, animation libraries, networking libraries, serial communication, encryption, etc) love "easily" allows through JIT for love to go above and beyond the call of duty - and just like Lua, that's kind of the design philosphy. "Do one thing, and do it well". At this point though, while you won't have the entire love community to help you, there are still plenty of folks who are interested in doing "wacky" things for the sake of "science".
With my implementation of the pure lua LoveVideo module, the community forks and refactors really showed that this was something people wanted. Enough interest came abount, and the love developers added the awesome love.video module using libtheora!
@someguynamedpie My advice to you is: prove to us we need it. Show us what advantages we would have by adding these features by implementing them:
* Fully by hosting binaries / hosting repos (See
LuaSec,
LuaSQLite3 for some bins I host) and showing people how to use them
* By writing utterly crap modules showing how experimental usage could improve the framework (
See my hilariously bad and horrible original video implementation)
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Fri Jul 15, 2016 12:54 am
by Someguynamedpie
One of my test projects got video working in Love2D using libvlc, if you want to talk about oversized libraries.
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Fri Jul 15, 2016 2:49 am
by zorg
Someguynamedpie wrote:One of my test projects got video working in Love2D using libvlc, if you want to talk about oversized libraries.
[wiki]love.video[/wiki] circa 0.10
![Awww :3](./images/smilies/ms-three.png)
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Fri Jul 15, 2016 6:14 am
by Someguynamedpie
Psh, love.video only supports theora, libvlc supports literally everything (cough including DVDs)
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Fri Jul 15, 2016 6:42 am
by bartbes
Someguynamedpie wrote:One of my test projects got video working in Love2D using libvlc, if you want to talk about oversized libraries.
Interestingly enough I did write a prototype with libvlc, which was all kinds of awkward, but mostly because it had its own lua interpreter, which was conflicting with love's. In particular, my libvlc is built against lua 5.3, and love against luajit, that caused instant crashes. I have since written an implementation using ffmpeg though, which we're unlikely to ever ship with love, because of the way it's licensed, but you could use as an addon library.
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Fri Jul 15, 2016 7:40 am
by Someguynamedpie
On the subject of licenses, yall are aware that most openal implementations use LGPL right
Re: Why was JPEG encoding/GIF decoding removed?
Posted: Fri Jul 15, 2016 7:41 am
by Someguynamedpie
But yeah I don't have the source anymore due to a harddrive failure but I got around the Lua linking problem somehow that I don't remember