View allAll Photos Tagged processing
Homage to a print that Jared Tarbell sent me a while ago. Thanks for the inspiration JT (though yours is much more elegant... nice trick with the black orb with multiple specular highlights... sublime!). Rendered out at 5000x5000. Check the fullsize to see the detail.
Smaller, more and differently shaped. Loses the subtlety of the gradient though. Plus the stars are a bit shonky.
photoshopped* version of www.flickr.com/photos/razornl/4357622243
What I did: I took the original drawing, resized it to 10%, blurred a bit, then resized it back to 100%. This is the result. Pretty/scary.
actually this looks more like what I see while I'm drawing. I work at rather dimmed lighting, so that my perception is somewhat like what you see here instead of the actual scribblings I have to make to produce it.
I never expected that stripping all the detail from the original would produce something like this. Surprising for me it shows quite well what was there for me to work with.
best viewed large and from varied distances.
* gimped actually.
Doesn't look like a lot stacked up like that, but printing each layer took 2-3 hours...seemed like the damn things never ended! Never screenprinted 200 copies of anything before, esp. without the benefit of a drying rack.
I love this photo so much. It was taken with a 35mm, scanned, and edited. Please let me know which one you like better! :)
Picture of Assam from probably ten years ago or so when we lived in California, processed by my camera program.
Staying very still until we walk away. Then he'll go under the deck, very slowly. How opossums survive I'll never know.
Processed with Flare
This is an example of the Dual Processing option on WavelengthPro.
As you can see the original UV image is in the background for reference, the active window is the dual processing. The balance of UVred channel and UVblue channel is changed by dragging the slider from side to side.
Three possible splits are shown HERE.
Step 3: Stack your photos
I followed this tutorial -
www.lonelyspeck.com/milky-way-exposure-stacking-with-manu...
Previous step - www.flickr.com/photos/trismi/30935548464/in/album-7215767...
Full write-up: trisha-smith.photography/post/154750049274/milky-way-phot...
Comment faire du vieux avec du neuf...
Comment imaginer que l'on a changé le monde...
Rassurez moi, c'est pas le résultat que je vois ? Ce n'est que le processus...
Vatileaks 2, indagati i due autori dei libri-inchiesta Nuzzi e Fittipaldi. L’accusa: “Divulgazione di notizie”
Flocking algorithm + processing
----------------------------------------------------------
We can’t deny the beauty of these patterns but one can’t help but question the static nature of them. Algorithms are as much about variables as they are about output. Freezing them in time, giving them static shape questions how viable is one objects to the next. If they exist in the range, does only personal aesthetic preference decide importance of one over another and where the process plays such an important part how can we ignore their pre and post decessors. Can their physical manifestation exist not just as a single frame and how does this affect their validity. Are these just decoration and if so, does it then matter if they were created using generative tools or just simply drawn as they are?
Just a thought..
----------------------------------------------------------
Every now and again, I revisit code from many months ago and end up finding GLARING ERRORS and POOR CODING STYLE and after fixing these problems, the code runs exponentially faster than it used to. The ripple code was one of those projects.
Originally, I rendered the ripple array directly to the screen, and I was able to get away with about 60x40 squares. After playing with it a bit recently, i realized that I could simply define a color array and use arraycopy to copy it over onto a PImage that i then use to render out the ripple information.
Whereas I could do 1 plane of 60x40 elements before, now I could do 500 planes with alpha intormation at the same FPS as I was getting previously.
Just goes to show, revisit old code!