![]() ![]() ![]() Unlike with Apple Photos, you can open more than one photo in Affinity Photo for the purpose of editing them. You just right click on a photo and then choose Open with Affinity Photo. It's come a long way in its latest versions from a few years ago. So far I like it except for the poorly written Help files. I bought Pixave today after playing with the trial version. I'm dreaming of something with the features of lightroom and the file compatibility of Pixave (Sans library) Kyno is an interesting alternative to bridge, I'd wager it is faster (Chokes a wee bit on raw files, but it is about 5 minutes old) but again it's going to be a bit insubstantial for a full on photography guy. The import is a little painful but once over and done with it's actually pretty damned fast, though my use case is more general DAM/organisation/file viewing rather than specifically photography. The tagging though drag´n drop looks nice, I´d like to see that in an Affinity DAM as well.Īs a file viewer it is actually pretty good, but lacking in some areas, you can't update real metadata or IPTC/XMP data, which is a little bit of a bummer. ![]() I highly doubt that it can be any faster than bridge (which again, is totally free), if anyone can prove this in video I´d like to know. Pixie 5mb download size also really makes me suspicious about the feature richness/ how their´re implemented. In the future you´ll get layered TIFF with embedded afphoto stream so every DAM or viewer like C1 or bridge will display full res afphoto files. (Maybe it´s great for afdesigner files though). I also don´t see what´s the big deal in browsing afphoto files, they´re huge and RAW development of many photos in a row is unusable so you won´t have many afphoto files per project anyway. (This happens frequently if you have to transfer photos from MB to iMac e.g., in C1 you can use Sessions and in bridge you can just copy the files) This double process makes it really hard to use as a fast image browser like bridge but it´s lack of pro features makes it also unusable as a DAM for a photographer (missing RAW development for anyone shooting more than a dozen fotos is the first no-go). However, even after I've pulled down the image from Docker Hub (as in this case) it will still take several minutes re-pulling the same image.As I´ve read in the MAS, Pixave does not recognize the pictures when you just put them into the folder in the finder, you have to import them so that pixaves data base recognizes them. Especially once the image from Docker Hub was already downloaded onto my local machine. => => writing image sha256:25a9f036db87ec77ef64e2dfae9cffe2973a947887face86d989cdaa60169216 0.0sīefore I upgraded to Windows 11, I'm sure this part of the build would take several seconds. => RUN pip install -r requirements.txt 40.7s => CACHED RUN pip install -upgrade pip 0.0s => CACHED COPY requirements.txt /code 0.0s *=> load metadata for docker.io/library/python:3.8 81.5s Is this normal? => load build definition from Dockerfile 0.1s The steps " load metadata for docker.io." and " load build context" take soooooo long every time that I build my docker image that it's painful.īelow is an output of a recent build, and the above two steps mentioned (*) have taken almost 4 minutes combined. ![]()
0 Comments
Leave a Reply. |