Jump to content

craigleeus

Members
  • Content Count

    22
  • Joined

  • Last visited

About craigleeus

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    US
  1. We're pretty much on the same page. I wouldn't characterize Photoshop as necessarily a simpler way to edit digital images, but Photoshop does make some things easier to use -- like what we're discussing, or like re-centering the image when zooming back in, more and easier to use presets, easier to create, import and use Actions, more options in Refine Mask, and much better handling of crop ratios, to name a few that frustrate me. But AP has good features too. I'm getting off track.... Of all those differences, the Export As control is my top request right now.
  2. dcdancm: Thanks! You're correct, this should be a relatively simple implementation, and it addresses an issue that touches nearly every, if not every, AP user. I've found a number of nice-to-haves, some 'very' nice to have, but this is definitely at the top of my list of desired enhancements. As for 'what happened?' I think a great deal of their work has been technical refinement and bug fixes. Plus, given Publisher was rolled out last year, no doubt the last few years have been largely devoted to that platform. And of course, now there's 3 apps in the family, not to mention the other stuff in their store, to support. I have faith that one of the forthcoming releases will make me a happier camper. Photoshop is my benchmark. Hope springs eternal!
  3. Default Export-as folder followup: I've come up with an idea that if it, or some variation of it, is implemented, it might be very helpful to a lot of people. I mocked up a screen shot (in Affinity Photo of course) of the Export-as dialog window (attached) with a new drop-down menu that has 2 choices: Use source folder (which means the folder either the background image file is in or the folder the .afphoto file is in if re-opening it) Use previous folder (which means use whichever folder was last exported to (for those who want to export repeatedly to this folder regardless of where source is located) An alternative would be for one of those to be the default Export-as location, and there be a radio button or check box to override that to the other option.
  4. Export-As topic. I previously mentioned my preference of defaulting export-as to the source folder. Today, I played around with Photoshop's approach (for Export As, not Quick Export). PS defaults export-as to the image's source folder. If I choose a different folder when exporting a file, PS remembers the new location for that file (and others I choose a different folder for), but otherwise continues to default to the source folder. AP's approach of defaulting to the last used folder might be useful if I'm working with a large number of documents and want them all exported to a different folder, or where I open images from multiple folders but want all output files to export to a same different folder. So I guess there's a place for both approaches. Perhaps, as a suggestion, AP's export-as default could be the source folder, but if I change that folder for an export, maybe open a dialog box asking if I want to continue to export-as to the new folder (which would continue to apply until changed again, or give the option to revert to the source folder for other files.
  5. Hmmm, I might be starting to catch up. Are you referring to the DAM as being a tool like Lightroom, which just links to original images and saves only metadata of changes made to the image? That would maintain high quality originals (RAW or TIF files perhaps) without the hugs afphoto (and likewise huge PSD) files. There are time when Photoshop is needed, but other times when Lightroom alone is sufficient. And Lightroom (and other similar tools), and I presume the DAM, also function as a photo organizer. Am I on track with this reference to DAM?
  6. Yeah, zipping is not going to reduce file size much, but it will restore files to their original content when unzipped. Question all, what are DAW and DAM? (I think of DAW as digital audio workstation, but I don't see that as relevant to afphoto files so it must be something else)
  7. A_B_C, perhaps you can compress it further outside the app (like in WinRAR, or with backup software). That won't significantly compress it, but could help. I would be comfortable with WinRAR, but Serif would have the tools to determine what data can be safely removed (for compression) and later completely recovered if needed. (Not an easy design task) More than likely, though, if they added some compression option, it would be at least partially destructive.
  8. This has been an interesting discussion (for a newbie). Last couple days I played around with different scenarios to understand it all a little better. I am now fairly convinced that faster file saving is the primary driver for saving incremental changes in AP, much like doing incremental backup for you computer speeds that process. And I can attest that saving Photoshop PSD files is quite a bit slower than saving afphoto files. I have a feeling that the reason 'save-as' new files are smaller is that the process uses just the incremental changes needed to create the new file and discards the rest. A layer is added then later deleted. It created incremental increases in file size, but for the new file, it's not needed. If there's enough of those, it could amount to a pretty big decrease in file size. There was a comment on snapshots being a possible factor, so I dug into that, learning what they are and all. I found adding snapshots adds very little to the file size. If I save the file to a new name, all the snapshots came over just fine. (I'm glad i learned about those -- that's a nice feature!) I don't see snapshots as a factor in file size. There were some comments about maintaining a full resolution image being a contributor to added file size. This is probably valid. Unlike AP, keeping a full resolution image in Photoshop is optional. By default the image layer is destructive. To maintain the original resolution image content, one must convert the image layer to a 'Smart Object'. When that is done, the PSD file size increases significantly. I dropped my 141MB TIF file in PS- (1) just saved as a PSD (no smart object): 141 MB; (2) converted background layer to smart object and saved: 379MB; then (3) put TIF in AP and saved to afphoto file: 181MB. Advantage: AP.
  9. You guys have an impressive understanding of the weeds of AP. Question: What's the difference between the 'snapshot' and the background (original) layer? Does AP place a second copy of the original image into memory and then pass that to the file when saving? Correction: in a previous post, I mistakenly said that for the image in question, I opened a RAW file in Develop Persona. In fact, I edited it in Lightroom, exported to TIF and then imported that to AP. [I just placed the TIF file in Dropbox (same link). 140,658 kb.] Clarification: In AP when I originally worked on this image, I reduced the TIF/RAW dimension from 6000x4000, and along with some cropping ended up with 2606x1629. I did increase the DPI from 240 to 300 in case want to print. Overall, though, this is a significant decrease in total pixels. Unlike Photoshop, this doesn't seem to have much effect on file size. More testing today: Today, our of curiosity and considering what I've learned from your posts, I put that TIF file in AP again (like I'm starting over). This time I immediately 'saved-as', without any adjustments. AP file size on first save: 332,333kb (for an unadjusted 140,658 TIF file). Wow! Did it get so much larger because of what I asked previously in this post--AP stores the actual working file and a copy (snapshot) in memory? Continuing my test today, I then, without any adjustments or even closing the file in AP, 'saved-as' again, this time to a new name. AP file size now dropped from 332,333 to 181,259! This is all very confusing. We should not have to dig through a mass of forum posts and trial-and-error to understand this and how best to handle it.
  10. That's what it comes down to for me, and what got me looking closer at this. (Note, I have only been using Affinity Photo for about 4 months -- I still have an Adobe CC subscriptions for Photoshop/Lightroom.) I noticed that my hard drive was filling up quickly. I sorted my afphoto files by size (Windows) and was surprised at the file sizes. Then I started to notice that every time I saved, even when I had deleted layers or reduced the image size, the file size continued to increase. And, the larger the file size, the more Kbytes were added with each save. To me this is a really negative issue for AP. I should add, then even though I have a Photoshop subscription, I would love to drop it, but Serif's Affinity Photo, as good as it is, and it is good, still doesn't have the meat to stack up to Photoshop. (Then again, I readily admit that for the price, my expectations shouldn't be too high and I applaud the work Serif has done.) :-)
  11. I had already overwritten the file in question, but I did the same with another large file. On dropbox is the "original" afphoto file (332,333 kb) and a new one created using the procedures I described (89,083 kb). Also attached is the original RAW file brought into the Develop Persona (24,416 kb) for this project. Link: https://www.dropbox.com/sh/b25mbzmaerehuxc/AAAILWwqa0whMGormQ1KEiPGa?dl=0 Really appreciate your interest in looking at it. Craig
  12. carl123: 'Save-As' to a new name did not have any effect on file size. R C-R: Thanks for the explanation. It makes sense in terms of describing why the file size increases, but makes no sense to me as a developmental approach to saving these files. Why would anyone want to have continually increasing file sizes? Your explanation gave me an idea for a work-around, and it did work. But it's manually intensive, especially when a lot of files are involved. 1. Opened an AP file. Size was 253,636 Kb (which is pretty darn big, but I have some even larger). 2. Then opened a new blank document with same size, dpi and ICC profile as doc opened in step 1. (both docs are now open) 3. Then copied all layers from original doc, pasted to new doc. Saved the new doc and the size was greatly reduced to 73,552 Kb. I played around with Photoshop files and it does behave the way one would want. Deleted a few layers and the file size got smaller (in AP, it got larger). Not hyping PS, AP is a good app, but there is some room for improvement and this, to me, is definitely one area. (PS- if I have save history enabled, then I would expect the file size to increase even if net-net nothing changed except added history (like making changes then making more changes to revert the previous changes back)). I appreciate the comments.
  13. I have a similar question. I am seeing the .afphoto file size increase with every save. (Don't have save with history enabled.) Reducing the image size increases the .afphoto file size. Deleting layers increases the .afphoto file size. Even if I make a change and then undo it, the the .afphoto file size increases when I save (ie- no real change was made). Granted, there was no reason to save it, but still, by undoing the change and putting the document back to the state it was in when I opened the file, I would expect no change in file size, but, no, it did increase. What gives here? This doesn't make sense!
  14. Question -- after thinking about this issue a bit more... In the Adobe environment, if I can use Adobe Camera RAW to make adjustments to a RAW file, then apply that to Photoshop, it becomes a Photoshop image, no long a RAW image (conversion to sRGB and other changes take place). Once in Photoshop, I can no longer save-as or export out to the fully detailed RAW file. I suspect this is also the case when applying Develop Persona changes. Once in the Photo Persona, some of the original RAW detail is converted and returning to the Develop Persona for further adjustments in that persona is not the same as opening the original RAW file in the Develop Persona. To me, that makes the ability to reopen the RAW file and still have the adjustments made earlier now a higher priority, even though I know I probably will not need it too often. But without it, the only way to make further adjustments at the RAW file level is to start over. As I'm sure Affinity's development team knows that Adobe uses a small metadata .xmp file to retain the changes made in Camera RAW. Maybe something like that is the solution. Just some thoughts :-)
  15. I can think of other improvements I would prioritize higher, but it is good to know this is on the drawing board.
×
×
  • 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.