Terminal emoji not appearing on macOS
First of all, thanks for making this tool! I'm really glad to see a modern replacement to asciicast2gif, and using it has been incredibly easy!
This is a partial dupe of #2, except on macOS instead of Linux.
When I try to render this asciicast with a build of the latest main and the font workaround in #2:
./target/release/agg 524144.cast abi3audit.gif --font-dir=~/Downloads/Noto_Emoji/static/
I get frames that are still missing emoji:
whereas my expected output is something like that on the asciinema website, but with B&W emoji instead:
I downloaded the Noto Emoji fonts from the same Google Fonts source as in #2, and I can confirm that they're actually present at that directory:
$ ls ~/Downloads/Noto_Emoji/static/
NotoEmoji-Bold.ttf NotoEmoji-Regular.ttf
NotoEmoji-Light.ttf NotoEmoji-SemiBold.ttf
NotoEmoji-Medium.ttf
Please let me know if there's any additional information I can provide, and thank you in advance!
I'm having this issue as well, but not with emoji, but rather SF Symbols.
https://developer.apple.com/sf-symbols/
I have the same problem on Linux with emojis and tried with Noto Emojis and Noto Color Emojis and other fonts that i use.
Produced with asciinema online :
Produced with agg :

I'm having the same issue. My terminal uses the powerlevel10k fonts: https://github.com/romkatv/dotfiles-public/tree/master/.local/share/fonts/NerdFonts, but the show up as empty squares in the GIF. Would appreciate some help.
The tool takes --font-family "MesloLGS NF" argument and doesn't complain about the missing font. Thanks
I've just released 1.4.0 with much improved font loading and rendering behaviour. Please give it a try.
The emojis should now be rendered in monochrome as long as you install Noto Emoji font - see new Fonts section in README.

There's still issue of double-column characters (like most emojis) not being aligned properly, but that's a deeper issue which we'll tackle separately.
Thanks @sickill, that's fantastic! I'll have a chance to give it a spin soon 🙂
(And thanks again a ton for creating and maintaining Asciinema!)
Assuming v1.4 solved the issue. Ping me if otherwise, I'll re-open in that case.