Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by paristo

  1. I found that Affinity is offering all their applications for -50%, and decided to purchase the Publisher so I would get rid of another software that doesn't work so great on Windows, and made purchase via my phone. And I didn't see that it was for OS X version instead Windows as I have completely forgotten that those serial keys are different, and it is easy thing as when I pressed the "-50% off" link on main page after coming to site with google using "Affinity Publisher Windows" link, I saw only this: And as you can see, there was nothing on the screen about Windows or OS X but just "Buy now €27.99" and didn't notice any other point question for that for which one it was as I went straight to the payment method. And after I went to my account, I noticed it was for OS X and not for Windows. I haven't downloaded or activated the serial, so is there a change to get that changed to Windows version, or do I need to withdraw it through my credit card company and buy a Windows version instead? IMHO, the Software version should be drop-down list in each application and it should default to "Choose" and not allow to purchase anything until all software in the basket are selected for a wanted platform version.
  2. 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.
  3. 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....
  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. 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.
  15. I am assuming no one else has come up with this problem? As I can't make a Windows refresh just to check does it help or not. Now my main workstation in studio is incapable run Affinity and I need to use a laptop to do the work as well there... Not a nice situation :-(
  16. No help. I even created a new account for test and nothing starts. Command line start doesn't reveal anything. Everything is just totally silent.
  17. Just a odd thing happened. I haven't used Affinity Photo for few weeks on workstation but only on laptop and now I tried to launch it (1.6.0 version) it doesn't start. No splashscreen or anything. Mouse cursor just states background process but no Affinity Photo process appear to process manager or anything other. I have renamed the Affinity AppData profile directory without success. I have upgraded it to 1.6.1 without success. I have uninstalled Affinity, rebooted and then reinstalled without success. I have tried to launch Affinity by holding Ctrl down while double clicking icon. I just can't get any information WHY it doesn't launch. Only security system is the Microsoft's Defender.
  18. Yes, more options for the directories (defaults, as common defaults) are needed. - Save Affinity file to same location as the opened file by default, unless otherwise pointed elsewhere. - Export file to same location as the opened file, unless pointed elsewhere. - Remember different Export and Save As -directories per file opened (file from C: doesn't get offered being saved where file from D: got opened) It would be nice to be able just unpack package full of image files, open to Affinity Photo and save file and get it saved to "Affinity" directory after pointing in first save time. Then get export as well saved to "Export" directory after pointing the first time there. It would speed up the processing multiple files in same directory (detect the directory path is it same as "Session" or is it as "Project".
  19. Yes, that is a problem when having more than two files open and you lose track of the order where you are processing files. A slight lighter/darker color or even a single pixel thick line above the tab is good.
  20. Challenge with the progress bars is that you need to be accurate with them, and you need to know the ending time. Everyone should be familiar with the infamous Windows progress bars where it hangs at 5%, 6%, 7% and then suddenly jumps to 98%, 99% and sits there half of the time until gets to 100% and still rolls? How to calculate the process then? Okay, you have 45 frames focus stacking, should we split the 100% to a 90 frames so first you show progress when a frame is processed for alignment so then when all 45 frames are aligned, you end up 50% part and then is focus stacking started. So after every frame is processed and added for the stack, you progress the bar? Sounds easy right? But it aint'... How to calculate process when loading an image? By the amount of data read from disk, or by the processed the data in memory or what? Then when it comes to simple "processing" informations like a circling balls in Windows now, or a circle going around like Google etc, it is as well not so good. As the animation is a own thread running, but doesn't tell that thread doing process hasn't hanged! So you can be in infinite loop in data processing, but the animation "I am working!" is as well in infinite loop. And ain't better from "Loading 1 Document" One of the easiest really is the data input/output about reading and writing data to disk. But that too is very far from reality as there can be many complex background operations waiting to be processed. Like if you save a file to a memory stick, it can take anywhere from 180 to 720 seconds that the data is actually flushed from the RAM to the actual memory stick so it is there when you pull it out! Even when the application doing the writing says "100% completed"! That is why the correct drives ejection is required as you tell the OS that specific storage device is about to be removed and it needs to flush the data from RAM to it so it is there correctly. I worked with a few dozen Affinity Photo files last week in one day over a network drive. The Affinity told that the file was saved and then I went to make a phone call that lasted about 4 min and came back and shut the laptop and went away. Later on I opened the files on a another computer from the network drive, only to find out that the layers with TIFF files were corrupted by few pixels rows. Every single one that I had saved in a batch, had the similar effects, from few rows to tens of rows. The fault was mine, as I didn't follow my standard procedure, save first locally and only then copy the files over network drive and check the disconnection. I knew better, I just wanted to trust that things would go right as I didn't have time. And now, by trying to save the couple minutes, I wasted days! (Okay, I didn't as I had backups from the process elsewhere). Even when a simple "Save Dialog" gets closed as "Save is Completed", it doesn't mean it is! So how you make a progress bar for that?
  21. Yes, in a way. But you said not to do a DAM while I recommend Affinity to go a head and do a DAM, but really get it right. Affinity should do a DAM that is purely focused for managing images. Then they have their Affinity Photo and Affinity Designer for working. And what they need to do is a "raw persona" that is own separate product for raw conversion that is used with all two (DAM and Affinity Photo) as integrated unit, instead both having something. Bring the updates to the raw converter quickly and even backport for older versions if possible.
  22. But the look (user interface) is very important to the user as it makes tool nice to use so you like to use it. Features are important so you can use the tool for the purpose (don't try to hammer nailes on wood with a saw...) but if you can use a little more inefficient tool that is just pleasure to use, it is better. No matter how powerful the tool is, if it is not nice to use (usability based to user interface) then it is frustrating to use such and reason to pick it over something else is lower. If it is only tool you can use to do the work, then you will use it, and hate it same time.
  23. There is always a room for a good DAM. The best on the industry at the moment is digiKam when it comes to manage your digital images. Search tools second to none and allows flexibility to run on all systems. If Affinity would provide even half of the features that digiKam does, then Affinity would have a true jewel in their hands on Windows and iPad markets.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.