Jump to content

MGBJAY

Members
  • Content count

    16
  • Joined

  • Last visited

About MGBJAY

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I will convert a few of my CR2 images and will share my experience as soon as I do that. Not certain that I would convert all of them at this point. You are gutsy to do that all at once. MGBJAY
  2. Good Morning IanSG ... Thanks for the answer. I will be using ADOBE DNG. I thought I would give it a try and see what all the scuttlebut was all about. I am currently using mostly with my CANON EOS 5D. Yes, the original from back in 2007 I believe. It has been a versatile tool, and I hope to get a good number of years out of it still. I prefer the native CR2 file format that it produces, and am simply curious about the DNG format, and want to see how it functions. Again, Thanks. MGBJAY
  3. Hmmm. Now that may be the most informative bit of information this entire thread has produced to date. I will try that right now. Thanks
  4. Is it possible to EXPORT before I hit the DEVELOP button? I am not wanting to try this before I try to get an answer because of the time that I have spent getting this image right where I want it ... and it is right now. Just trying to discover an option ... if one is available. And I am trying to avoid "just trying it" and screw all this work up.
  5. OK ... I've tried to find this answer to no specific avail ... If I choose to convert a few of my CR2 RAW images to the DNG format, will I then be able to open them into APHOTO and edit to my hearts content? I have been unable to find a straight answer to that question? The longer that I use APHOTO, the more I find questions that I have had answers for using PS and LR ... but not so much here. MGBJAY
  6. ... well saving all those presets absent the ability to actually "name" each one of them goes back to another query I posted earlier regarding "overlay brush" adjustments and not being able to name any of those. Besides that - there then follows the need to actually catalogue all of those presets which becomes another job and useless for using on another image because each image is rather different in the way each may employ a preset created for another image. And if I understand what I have read heretofore ... choosing to go back into the DEVELOP PERSONA once committing develop ... the image that opens is "stuck" with the adjustments made in the previous version before making it an *.afphoto image - which then is the image frozen with those adjustments and unable to take them back to their original neutral choices, In other words ... one must use the newly DEVELOPed image as the baseline from which to start a new version of the same image ,,, which by definition is not the same image, but the adjusted one - leaving as I said - beginning all over with the original CR2 RAW image absent the favour of having the adjustment choices applied to the image previously DEVELOPed. I am NOT trying to make this any more complicated than it needs to be ... but it does take a few words to be clear when trying to exactly explain what I am after. Appreciative of (your) patience. MGBJAY
  7. If I have an image that I have processed in the Develop Persona and want to save the way that it is without hitting the DEVELOP button, is it possible to do that? The reason behind my asking this is because I want the image the way that it is right now, and then I want to make a few more tweaks to it ... and save it that way as well without having to start all over again from the beginning ... and without losing all the adjustments that I have in the current image. Any thoughts or workarounds available to do this , or am I stuch with hitting DEVELOP and then EXPORTING to a file type and saving and then re-opening the *.afphoto image and starting all over with that version of the image ... or instead going back the the original CR2 RAW image and re-creating the entire process from DEVELOP all over again? I hope this is a clear question ... and thanks for whatever input might follow. MGBJAY
  8. I am sure that this may have been mentioned to date, though I've not seen it. As has been mentioned regarding other "it would be nice if ..." issues, I thought it would be helpful and quite useful if users had the ability to name each BRUSH OVERLAY applied to an image during the DEVELOP PERSONA process. In a recent image, I ran into this disadvantage full force with the experience of having four such overlays, yet was unable to identify which on I was looking to delete. Sure ... it can be done with some difficulty and clunky "hit and miss" efforts, but why not make the process a bit more streamlined with the advantage of being able to identify such "layers" by giving each its own name. Given the effort it takes to get the exact appearance one is striving for already consumes focus ... alleviating the "clunkiness" of such a task would be welcome. Of course, if this naming solution could be applied to every layer one might incorporate in the editing or creation of any image during any process and under each "Persona" would be equally as helpful. MGBJAY
  9. PSD format, as well as others, are available to be opened and utilized by many different software's. A few individual elements may in fact be unavailable, but the overall format can be easily read by other programs. And while I appreciate your responding ... making the format available is what gives "creators" the ability to freely access their information across platforms. Simply because one chooses to spend "their" money on a software, oughtn't harness one into such forever ... and the work performed in that software should remain portable. The software is only a tool, not the creative force employing the tool. The results should be available irrespective of the tool used to create it. A baker can put the ingredients for a devil's food cake all together and mix it all up, according to that baker's recipe ... and then place that mixture into any oven and produce the result. The oven has no say so over the recipe. Only the amount of heat. And "every oven" ... irrespective of the manufacturer can produce the necessary heat to get the job done. The software is merely producing the heat ... not the content. The baker can, at his whim, take that recipe and produce the result in any properly functioning oven. Perhaps, however, I am in possession of a ruggedly stubborn mindset. MGBJAY
  10. Good Morning ... ... while this is not exactly "the" issue being discussed in this thread, it is something that I have been considering as a new AFFINITY user. Considering the speed with which technology gives rise to change in our time, something that I have begun to wonder about is the "long-term" stability of the SERIF platform with regard to future access to our images that have been saved in the "*.afphoto" proprietary format. This file format cannot be read by any other reader other than itself, and to the degree that I have been able to validate what I am about to say, SERIF is not making their information available to any developers so that they can incorporate the ability to open images in "*.afphoto" format by any other software than that which SERIF creates. This is the reason that the "*.dng" file format was designed, and which may or not be one solution to address this concern. I find it somewhat unsettling that SERIF chooses to keep this information to themselves, thereby disallowing users any options to access their files by other image editing software. I just ran into this issue AFTER choosing to use AF when I imported a number of images into both ADOBE BRIDGE and photools.com DAM software IMATCH. Neither of these programs can open the afphoto formatted images. In that situation all that is available is the APHOTO LOGO image. It has the undesirable side effect of making one feel as though having chosen to use AF PHOTO, corrals one into the SERIF sphere, and from that point forward one must either use them or lose the ability to access to those images and the information contained therein. I cannot imagine that I am the only one that has thought about this issue. While "operating systems" may understandably have specific reasons for proprietary code formats, extending that to include image editors is, in my opinion not a great incentive. Just a thought from a new user. Any response is welcome. Especially if I am dead-wrong in my thinking on this issue. MGBJAY
  11. WALT & ALFRED ... ... Thank you both for your responses. Now I get it. Makes sense. MGBJAY
  12. Is there any follow-up on this question?
  13. Firstly, Thanks for the answer, and my apologies for sounding a bit thick here, but ... ... I am still not understanding the results of either choice here. As far as I am concerned, I've already made the changes to the image that I wanted to. I then saved that image as BOTH an *.afphoto image AND a HQ *.jpeg image ... with my understanding that the ORIGINAL image remains as it was before ANY editing applied to it, and remains unchanged as the RAW image it began as ... and that is what I thought was the way this worked. Why am I yet again asked whether or not I want to save it yet again, and if I choose to save it again ... which image is then changed?
  14. ... "the document is about to change, do you want to save your changes?" What I am not understanding is this - Once that I have completed editing an image and have saved it as an *.afphoto image after leaving the DEVELOP persona ... and then EXPORT the aforementioned edited image, and saved that as a HQ ".jpeg" image ... when I then try to "CLOSE" or "X" out of the image, I get the dialogue box asking me whether I want to save the image or not (see attached clip) - I find this very confusing as I thought that I have already saved it twice, as stated. If I choose either YES or NO ... what are the results of those BOTH of those choices upon closing that image?
×