Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

279
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#jpeg

2 posts2 participants1 post today
Public
His Holiness-Adjacent Gregly

I ran into a weird Unicode issue with EXIF tags in a JPEG recently: the “user comment” field was in Unicode, but it was an encoding I couldn’t identify. It started with the bytes “UNICODE\0”, followed by what looked like UTF-16 (\x00 bytes interspersed with 8-bit ASCII) but no byte-order identifier (\uFEFF or \uFFFE). The thing is, Windows and various tools decode it just fine, but my code attempts to do so have all met with failure. Ideas? #photography #programming #jpeg #exif

Public
R. L. Dane
For today's #DailyDoodle, I traced and sketched the cover art for the #PhilipGlass album #GlassWorks while listening to the first track on repeat.

It's always been a favorite of mine, and I love how ordered his music is. I think you either love his stuff or utterly hate it, either completely enjoy listening to it, or NOPE right out of it after about a minute.

Here is the track, via invidious: https://inv.nadeko.net/watch?v=_2vRbNehGB0

I traced the basic outline of the image via the line tool (rather, the line mode of the pen tool) in #Xournal++, and then freestyled the shading with the album art to the side, rather than traced.

For tracing, I just put the Xournal++ window above the swayimg window, and made it mostly transparent.

I think I will start using this account for my daily doodles, as it'd be nice to have them gathered together in a separate space from my usual account (@(@rl_dane@polymaths.social), and I don't take that many photos, anyway.

It's very interesting how much #entropy there is in hand-drawn sketches. Even when I was trying to save space by converting the image to monochrome (which I didn't do with this one), the file sizes for the sketches were still pretty large, and even attempting to convert to #JPEG or #WebP didn't save much space over the monochrome PNG unless I really cranked down the compression factor and turned it into a blurry mess.

It's also fascinating that the compressed XML source for the image is about the same size as the PNG. ^__^ (204KiB vs 158KiB)
The album art for the Glassworks (1981) album, featuring a complex crystalline structure with the large text PHILLIP GLASS superimposed over the top in an Art Deco style
My sketch of the album art. There's no PHILLIP GLASS text in my version, but I traced the major outlines and then tried to freehand the overall impression of the piece using line thickness variation, but no color.
Public
Norobiik @Norobiik@noc.social

Google's open-source #Jpegli promises 35% better #ImageCompression than other methods, improving quality while saving bandwidth.

The #CodingLibrary is compatible with existing #JPEGEncoders, making it easy as a drop-in replacement.

#Google thinks it just solved #JPEG's biggest problems
androidpolice.com/google-solve

Android Police · Google thinks it just solved JPEG's biggest problemsBy Manuel Vonau
Public *
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸

#Google reckons that it can improve #JPEG with #Jpegli, a new #encoder and #decoder #library that promises to be highly compatible with JPEG.

Jpegli uses heuristics developed for #JPEGXL, making it more of a JPEG XL successor (or improvement). Compared to JPEG it offers a higher #compression ratio, 10+-bit support which should reduce issues like banding. Jpegli #images are said to be compatible with existing JPEG decoders, much like #JPEGXT and XL

hackaday.com/2024/04/07/jpegli

Hackaday · Jpegli: Google’s Better JPEG And Possible Death Knell For WebPAlong with the rise of the modern World Wide Web came the introduction of the JPEG image compression standard in 1992, allowing for high-quality images to be shared without requiring the download o…
#webDev#webp#avif
Public
Jonathan Kamens

I didn't really understand the motivation behind using #webp instead of #jpeg until my wife gave me a 3MB image she wanted me to put onto her web site for her, and I said, "Woah, wait a minute, that's rude to the viewer, let's see if we can shrink it down a bit," and converted it to webp and it shrank to 109KB without any visible loss in fidelity in the browser.
#WebDev

Continued thread
Public
Oblomov

One of the ways in which I would like to minimize disk usage is using #JpegXL instead of #PNG (or even #JPEG, but I'm not hosting JPEG images), which I cannot do as long as #Firefox doesn't enable JPEG‌ XL‌ support in the mainline edition of its browser (no, I don't care that #Google has decided to boycott it in #Chrome, just like I haven't cared about their lack of #MathML support and proper #SVG animation support for years).

4/n

ExploreLive feeds
About