However, where does one go from here? Does it become old hat? I hear some Avant-garde types are beginning to explore post-blue ideas. #333333 has a romantic bleakness to it that I would love to see explored.
Oh my. One should not so blithely confess that they can't see The Emperor's New Blue. Such a shame.
It can, actually, you just need to hold done ⌥ while clicking on the file format picker. (Perhaps Apple thinks demonstrating the true capabilities of Core Image would blow the brains of Preview’s users.)
[images_files] 0 $ md5sum * | sort
4a93faba1d6abc2f3c0fa4a925a23a4c viii.gif
672b8ee4b7e2893f209dd66eeb368744 ix.gif
7005d06133499ca4d1e6d1b265adea83 ii.gif
784f2d5bc7cb0cdce826fb656896c034 v.gif
8e39d526b119fabfacb259d53eb89140 vi.gif
9d2e88d7588d5e22c9d51d6b005034fb vii.gif
9f55b70b1564ab62faafbf37f311c5c0 iv.png
b67f99e04dc8720d5846b818e86ecd39 style.css
eb42e0f64ece46753a7aeba4fe3149a6 i.png
f346c6fbe6fa659b6020c75c579084de iii.gif
So I'd say no, they're different for some reason. Sizes vary a lot, too. Unfortunately I don't even know where to begin telling why.But:
% as --version
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
...
and gnuplot (famously) isn't part of the GNU project.I know, missing the point, but those jarred - was that deliberate by the artist, or a mistake? In either case, it seems to distract from the overall artistic intent.
If you have to ask this, you don't know the art world. Artists don't make mistakes.
The proper way to ask is "was this an attempt to communicate X, or simply an acceptance of Y?". If the latter, or if the answer contains "I was fascinated by the results" or "I found the result even more enlightening", you have your answer.
without LZW, it should be trivial to append a frame to an image. its so hard... instead of downvoting me, does anyone know of a good/simple example of this in C/python or anything? array2gif[1] is pretty close.
(Yet dimmer, possibly false, memories: by taking advantage of LZW literals, I think it's possible to unencodedly write supposedly encoded blocks?)
[1] 10-50 lines of python, depending upon fanciness, IIRC
I chuckled.
/* XPM */
static char * treachery_xpm[] = {
"10 10 1 1",
" c #0000FF",
" ",
" ",
" ",
" ",
" ",
" ",
" ",
" ",
" ",
" "};
X Pixmap format. Save as treachery.xpm.
(Made using Gimp, because it was faster than writing by hand. Sorry. But I have generated large pixel files programmatically in the X Bitmap format, which is similar but only one bit color information. Easier than writing a GIF.) db 'II*',0 ; header
dd ifd ; offset to IFD
xres: dd 72,1 ; XResolution value
yres: dd 72,1 ; YResolution value
bps: dw 8,8,8 ; BitsPerSample value
data: times 100 db 0,0,255 ; image data
ifd: dw (next-ifd)/12 ; IFD entry count
dw 256,4 ; ImageWidth tag, type
dd 1 ; ImageWidth count
dd 10 ; ImageWidth value
dw 257,4 ; ImageLength tag, type
dd 1 ; ImageLength count
dd 10 ; ImageLength value
dw 258,3 ; BitsPerSample tag, type
dd 3 ; BitsPerSample count
dd bps ; BitsPerSample offset
dw 259,3 ; Compression tag, type
dd 1 ; Compression count
dw 1,0 ; Compression value, padding
dw 262,4 ; PhotometricInterpretation tag, type
dd 1 ; PhotometricInterpretation count
dd 2 ; PhotometricInterpretation value
dw 273,4 ; StripOffsets tag, type
dd 1 ; StripOffsets count
dd data ; StripOffsets value
dw 277,3 ; SamplesPerPixel tag, type
dd 1 ; SamplesPerPixel count
dw 3,0 ; SamplesPerPixel value, padding
dw 278,4 ; RowsPerStrip tag, type
dd 1 ; RowsPerStrip count
dd 10 ; RowsPerStrip value
dw 279,4 ; StripByteCounts tag, type
dd 1 ; StripByteCounts count
dd ifd-data ; StripByteCounts value
dw 282,5 ; XResolution tag, type
dd 1 ; XResolution count
dd xres ; XResolution offset
dw 283,5 ; YResolution tag, type
dd 1 ; YResolution count
dd yres ; YResolution offset
dw 296,3 ; ResolutionUnit tag, type
dd 1 ; ResolutionUnit count
dw 1,0 ; ResolutionUnit value, padding
next: dd 0 ; next IFD offset
[1] Source: page 24 of https://www.adobe.io/content/dam/udp/en/open/standards/tiff/...