Jump to content

paristo

Members
  • Content count

    77
  • Joined

  • Last visited

About paristo

  • Rank
    Member

Recent Profile Visitors

427 profile views
  1. There are four assumptions here: That files itself that contains all the data are modified. The image data that is being processed in memory (files opened in editor) are lost. The process to change the image data values (contrat, brightness, saturation etc) are losing data. The specific process to change the image data value (curves vs levels vs exposure slide) are losing data while some not. As everyone knows, the first one is lossless. No data is modified unless you rewrite the raw file (some editors can do that). The second is question about how the application does the process. In the current way (1.6.x) the AP will convert the raw file to own form in RAM to process it, and that conversion is lossy for that session. So unless you reload the raw file and perform new conversion, you have lost the data. I am not sure about AP new 1.7 version does it allow return to raw conversion and adjust settings without reopening the file (lossless performance). The third is just wrong if the adjustments are in own layers, like default in AP, and in Photoshop called "Smart layers". Meaning the adjustment only stores metadata that how the image is to be shown to the user, no image data is modified. The fourth is then per application based, like there are plugins that requires that image editor will export the file first (it combines all the layers etc) and then outputs it as input to the plugin. And then plugin does perform its own edit to the image and outputs it back, either replacing the layer or getting added as new layer or even opening a new image. Like example in Affinity Photo using a DXO plugins, it is better to first stack all visible layers in AP and make copy of it, and then open that new layer in the plugin. You don't modify the existing layers than the new stacked layer. And it is lossy task as you can't go back later in the DXO plugin to readjust it, but you need to rerun the plugin from scratch to the copy layer you made and delete the previous one. Now, does the Exposure adjustment in AP perform a lossy adjustment to layer, instead being a adjustment layer modifying the view and being only applied on the export? If it is not in the layer adjustment list, and become as adjustment layer among other layers, then it is destructive adjustment to the layer you apply it, but not the the original file but to that layer. But as you can see in Affinity Photo, Exposure adjustment in layers is non-destructive (lossless), so you can go back later and readjust it. But other question is, is it destructive (non-readjustable) when you convert raw file (open raw file) in to Affinity Photo? Likely once you hit "Develop", it is what it is. In some other applications, you might be able to just click the original layer and get the conversion settings again to modify it and then all your previous layers etc are applied normally again.
  2. Just to throw a thanks. As I was having this challenge all the time when on computers without digiKam. And I was forced to use a some third party apps etc to get around the problem. Now I can just use the AP as I didn't never open the "New Batch" function....
  3. paristo

    Nik Plugins

    Yeah, it is 4K limitation as you don't have any scaling set for it via Windows. Want to override it? Set screen resolution to Full HD from 4K.
  4. Would be nice if the Affinity Photo would allow to produce the wanted print marginals to wanted print size. What is required is first user selects New Document that is set to the final print size. Then user can choose to add margins of three bleed trim safe And all those are not going to come over the chosen final print size in New Document, but would enlarge the created document size with additional empty space and with correct marginal lines as chosen to overlay. So if user selects a final print size to be A3 in "New Document" then the document size is exactly the A3. If user selects then to add a margins, the document is enlarged by the amount of chosen bleed margin size like +6mm on each side. If the user then choose to add trim margin visible, then that margin gets overlaid the document as that is the final print size (the chosen A3). And then if user choose to add safe margin, it will be the only margin that is inside the final print just showing the final safe side. This would allow super much easier producing the print out to offset printing when one doesn't need to care at all about anything else than just slap the file inside the document and check it is fitted just outside of the trim (final) and then get out the file that has correct bleed and trim markings overlaid outside without creating those by user himself. The other additional nice additions would be to allow to resize the layer in pixels as in any other way as the document is possible to be just by going Layer > Resize Layer. So if a photographer needs to prepare files for off-set printing, it would be super easy to just produce the files from photographs. Open image file Select the final print size (document size) Input bleed margins and safe margins Resize image to overlap the trim margin as wanted. Set the layer (image) wanted rasterization (enlargement etc) Export as PDF / TIFF
  5. paristo

    Focus Merge Halos

    When I was considering Affinity Photo purchase, I put it against focus stacking etc things as those were main reasons to get it. I used all kind macro photos as well landscape etc and Affinity Photo came almost always superior to Helicon Focus. The halos you are seeing is from applying the data from images (layers) that has the detail out of focus. And in some situations it can be very challenging try to get it fixed as some lenses nodal point changes when focus is changed, so perspective changes as well and that means objects position in space moves and they ain't anymore where they should be. But Affinity Photo always could offer more controls to do stacking...
  6. Couldn't get the quote box right and reply anymore so write here second. Adobe products does break many of the HIG rules, but so does Microsoft as well. They actually did a very few very good implementations, but it is actually accident as these things has been researched already at 70's how graphical user interfaces should be done. Like Microsoft got the Windows Phone correct by placing the actions to bottom of screen, not to top. The top part worked when screens were 2.8-3.5" but not since going to 4" or above. What I would like to see in Affinity Photo is option to spawn the dialogs under the mouse cursor or to specific position so I can predict and move the mouse there. But Affinity has many lot better than many Adobe implementations. But some are just requiring too many routes to do. Like how to fill a selected area with a color? With GIMP it is simply that you drag and drop the color from your color palette/wheel on the selection. To get in affinity photo "Selected color as transparent" really requires to google it how it is done, while with GIMP it is "Color > Color to Transparency". But when GIMP requires to know the workflow how to do a given effect by knowing the order and filters etc, with Affinity and Photoshop it is often predone process by click-be-done, but if you want to have the control, you need to do how GIMP does it. Oh, and I would take commandline for many many tasks anyday.
  7. That former is impossible to really do. Reason is why the Shift+Click is used is because you will define the direction from starting point and so on get correct angle. With Shift+Draw your hand is not so accurate to draw a line to exactly correct position after few pixels when starting to draw, so automatic angle detection would throw you always off many degrees, most often even 5-15 degree so you would end up drawing a line again and again and again to get it right. That leads instant frustration. The answer for that would be the virtual ruler, what the shift+click really is (or could be) First click couple times to end / start of the points and then draw the line with your tool to control the pressure etc.
  8. Three different things here discussed. 1) Image manipulation application = Affinity Photo 2) Digital Assets Management = Wanted / use third party applications like digiKam. 3) Digital photograph raw conversion application = Wanted / Affinity Photo having basic functions If Affinity/Serif would do something great, they would make a own standalone raw converter that can be used as plugin with their applications. So you could insert a memory card, open the converter, drag'n'drop files from card to it as listed and point a new directory where to convert them as wanted other format, by applying the lens corrections etc. Make it small and tiny application, like example what a Rapid Image Downloader is for Linux https://www.damonlynch.net/rapid/ that can do you everything alone by just inserting memory card, doing the backups to multiple destinations and organize the files based wanted exif data etc. For majority of the people, they come home after week or two trip and their camera has maybe a 200-500 photos. They don't need complex things to manage files, just get them "Event > Days" directory tree. And then they browse files via file manager and use image editor to process picked ones. Then when more complex things are we going, more demanding situations and setups come around. Like running a studio you have 4-5 photographers working there, each one having a 2-3 cameras and produce weekly thousands of frames that each need to get to centralized local server and then to their wanted services or storage mediums and workstations. Some shoot with JPEG and some shoot raw, card management is done correctly so everyone is using multiple cards in the shoot/task and they get rotated etc. Some prefer Adobe tools, some needs some other ones... So if Affinity comes with a applications for one task, does it very well, it is great for many. So separate converter (standalone and plugin for Affinity) as DAM and all should come better.
  9. I think that the history panel should be more of the "mother panel" for all. So you can work around it. Like if you open a adjustment and it has own window to delete it, reset it all and do adjustments, then it should be possible to do reverse in that window itself since opening it, adding it or last adjustment you just did, without going to main history panel that is whole workflow history.
  10. Totally need this. After year still double clicking individual sliders to reset to default. I think there should be two modes. 1) Double click to reset previous setting after opening the adjustment 2) Shift+Double click to reset default regardless what was last adjustment. This is like if I add a layer filter and set some adjustments and then close it. Open up for re-adjustment after some other filters and do something but notice I don't like it. I want to get easily it back to previous state when adding the filter. But sometimes I want to set very specific one to defaults as creating a new one.
  11. DAM doesn't need to convert raw at all! That is the whole point of the DNG as well. The DNG file is "like a ZIP file", just like every other raw file is just a container. Most raw files inside holds a sidecar file with metadata, a low resolution preview JPEG file and then three TIFF files, one for each bayer filter color. The raw converter job is to import the TIFF files (and if manufacturer has done, decrypt the encryption) and then read the metadata and then proceed to do the demosaicing by combining three TIFF files to one by the commands that there are given. The DNG does the same thing, except that the TIFF files are never encrypted, there comes a sidecar file for metadata and all the modifications done to the image, there are two preview JPEG (large and small) and you can even embed the original raw file inside, to be used in future with a raw converter that can read the original file instead converted clear images DNG offers. So when ever you have a DAM, all it needs to know is to read the raw file container JPEG file for preview, read the metadata sidecar file and that's it. No need to what so ever to do conversion. So everytime you save your "non-destructive" file, its preview JPEG is updated and DAM reads that. It is all already solved long long time ago, the only difference is that you really get a new window to do your image editing, instead swapping to "Develop module" or such "tab" otherwise. And that is as well better in multi-screen environments, with low memory systems etc as you have more flexibility to choose what you use and when. That is one of the great things with the Affinity Photo that you can just double click raw file in memory card to open it, make the adjustments, save the Affinity file to memory card. Take the card out and move to other computer and do the DAM import there and you get that Affinity file correcly with the original raw file and then you can just double click the Affinity file in DAM on any computer and get it opened in Affinity Photo in those computers. The raw file stays intact without any problems.
  12. I am still having the problem. Done re-install, run manually regedit to delete every single key pointing to Affinity, and still can't launch any version of Affinity that installers I have. There comes nothing, a process starts for a second and then disappears.
  13. The luminar problem is that it is designed to work with a very few files. It is as well designed mainly to be "Wow" for your already edited files. A DAM point to exist is very simple: 1) Digital collection of all your hundreds of thousands/millions of digital files 2) Manage the metadata by tagging and applying identifications, rating etc. 3) Search/Filter/Browse files by metadata (time, location, gear, setting, people, tag) by combining them to narrow down what you are looking for, even by drawing a sketch about photo you are searching. 4) To backup, copy, move files, print them, order prints, have multiple variations, upload to remote service etc. 5) To view them, slideshows, individually etc. A DAM is not there to edit files, to convert raw files or do anything to those. That is the job of the image editing and image manipulation applications. As DAM is exactly where you manage your photos so that you example can insert a memory card to computer, copy the files from card to computer, backup copied ones, tag them, insert other metadata like people. And then rate them. Then you easily find the successful ones, import them to image editing application, do the edit and finish by tagging edited ones as "Finished". And in time you are handling a same DAM, but you use multiple other editing tools to do your work for the images editing. Luminar etc are designed more like for smartphone user, who goes to holiday and takes a 50 photos in a week trip and then all are so fancy and great that they need more "pop" so it is just couple sliders and "it is better". Instead DAM is for professionals who come day after day with thousands of the frames. Every frame needs to be backed up, marked, tagged and ranked so you are not wasting time for the photos that isn't going to be sold or used. But you don't delete the others as you can need to use them any time later in future. Then you will send the files to someone else who edits them and sends them back to you. If Affinity is going to do a DAM, it needs to be very well focused just for the management of image files of all sorts. And get them opened with Affinity Designer, Affinity Photo and finally in Affinity Publisher. The DAM even should support to use a any third party raw converter to process raw files.
  14. If you didn't read, I did. "Clean Boot" means that you disable every service from Windows boot stack. Nothing special really. One of the first things you should try if you often install all kind software. This problem became only after updating Affinity Photo.
×