![]() Besides, FFmpeg.wasm has its own set of limitations (or rather WASM itself). It is certainly not an easy and quick project to hack around. There are lots of caveats, tricks and not properly documented APIs. Besides, it was a great opportunity to learn more about WebAssembly.Ĭreating extensions, however, can always be tricky. It is not as fast as a “bare-metal” FFmpeg (no hardware acceleration) but is way more convenient. For now, I can’t publish in Chrome Web Store (more details on sections ahead), but you can still load it manually (instructions on the repository). It allows users to either convert and replace the image component or download the converted result straight (QuickTime can’t open it though). FFmpeg.wasm + Browser Extension: GIFSaneįun fact: the demo above is in WebP, so GIF wouldn’t be able to convert □Īfter a couple of weeks of hacking things, I managed to put together GIFSane. With my “ fresh” knowledge about WASM, I thought: wait a second, what if I created a browser extension that converted GIFs into videos using FFMPEG!? Guess what: I did it again. I was expecting something like HTML playback control. I tried some extensions, but the UI and UX were never that friendly. I realised it opens many interesting possibilities and, during my search for other projects, I came across FFmpeg.wasm.Īt some point last year, my annoyance with GIFs came about again. I already knew about the existence of WASM, but this post was eye-opening. In this case, it allows JavaScript to interoperate with libraries and programs written in other languages, such as SQLite. Well, dear friend, there is this magical thing called WebAssembly. “SQLite, in the browser!? How!?” you may ask. Then, last year, James Long published A future for SQL on the web, where he describes how to use SQLite in the browser. This was 2019, and I still use it nowadays. But these documents had to be exported to Markdown.Īt some point, I got annoyed by the lack of this feature, and I decided to create a browser extension to solve that: Grammarly to Markdown ( GitHub). As a non-native English speaker, it helps me a lot when writing technical documents or blog posts. Some time ago, I was a bit annoyed with Grammarly. ![]() This day never arrived, and I decided to take matters into my own hands. I always secretly hoped that one day browsers would support this. Not having this feature always annoyed me a bit. ![]() Video playback features basically… which GIFs don’t have. But, depending on their length and what has been recorded, you might want to pause, go back, jump sections etc. GIFs are ominous nowadays, being more popular than even newer and more efficient formats, such as WEBP or APNG. Embedding a GIF into your Github page, static blog or NPM package, which tend to use Markdown, is the easiest way to embed a “video-like” component: !(./img.gif) and all good. The software engineering world adopted them for a particular use case: recording tutorials and demos. They are everywhere: from memes to artsy GIFs, they come in all shapes and formats. It was not until Netscape 2.0 that the GIF format was incorporated and conquered the world ( really). Yep, your maths are correct: they came even before browsers. They were first released in 1987 by CompuServe. Animated images in GIF format are around for a long time. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |