Jump to content
You must now use your email address to sign in [click for more info] ×

awhite

Members
  • Posts

    29
  • Joined

  • Last visited

Reputation Activity

  1. Like
    awhite reacted to mapline in Remember Last Crop Mode   
    99% of the time I use the same crop mode but each time I have to choose it from the drop down choices of pre-sets. How about it remembering last choice. Small change but will improve usability please.
    Many thanks for a great programme.
  2. Like
    awhite got a reaction from rafikiphoto in Add .tif file mask to export dalog   
    I understand that it's not an option to change the default TIF extension from .TIFF to .TIF (because .TIFF is a standard?). In my case all other applications I use save as .tif. It would be helpful to at least add a .tif filter to the AP export dialog so that files with both extensions are visible in the window, currently the window is always empty :) (See attached screenshot).
    Thanks for consideration.

  3. Like
    awhite reacted to Kobold in Sticky Settings .... pain in the ...   
    Hello, 
    why there is no way of making easy default or sticky settings in Affinity Photo? Choosing the same options over and over again is so boring and time eating and unnecessary, for example crop ratio ........  each photo choosing again, or image size, bicubic .......  again and again. Sorry guys, but there is so often the comparison to Photoshop, and how professional Affinity Photo is working, but I am not satisfied with these points, and there is more of such important options, that are stealing time. Getting more gimmicks on new updates, funny things, yes, but why not fixing these important things first, that make an app work proper and fast. These settings, as the ratio and the image size rendering (just as examples that got used very often, permanently  by most users) , they don´t even stay while working on the same photo. That is really disappointing, cause this is basics for a good working app! And the app is not brandnew anymore!
  4. Like
    awhite reacted to LilleG in Digital Asset Management   
    Personally, as a user/owner of both Photo and Designer, I'm a lot more interested in the developers concentrating their time and attention on perfecting (or as close as any developer comes) the apps they already have out than in having them possibly spreading themselves too thin trying to introduce too many things at once.  Photo and Designer are both young and while showing great potential, both need further development in order to be the Adobe killers that many of us are hoping for.  In the meantime, there are other options for DAMs, some free, some not.
  5. Like
    awhite reacted to Opera in New resizing dialog / scale to new size / A-Photo   
    please enhance the resizing dialog to this regular standard:

  6. Like
    awhite got a reaction from Hofnaar in Save As... to save in the same folder as the current file   
    AP does the same. I suggested the change to the "standard" behavior two times already and I'm quite sure someone did before me. I hope they change it in some future release, because it is really annoying.
  7. Like
    awhite reacted to DarkClown in Still no real love for Affinity ...   
    From the first day AP was released for Windows (even the beta) I was desperately trying to make AP work for me .... I wanted AP to be the THE (first real) alternative for PS (considering I couldn't find enough swear words for Adobe and their cloud policy). I was accepting and reporting all bugs you obviously had to expect from a sw that complex. I was trying to make the product better as quick as possible by generating test cases, videos to show bugs and even offering Serif my support in development and localisation. And seeing the sw that had great features, good customer support, a big crowd of (active) fans and users - what could go wrong to make AP the new PS in a long term? As you can see I'd do everything to make this baby mine. One can hardly approach a product more positively than I did with AP ...
     
    After all that time I see myself closing PS6 tonight working on a customer project and I'm asking myself: why do I still not(!) use AP? AP actually hast most (>95%) of the functions I frequently use in my daily work as a photographer. Even the plugins work in AP. Some functions are even more powerful than in PS6. Still I don't even think of AP when it comes to productive work for customers. And it's not because I'm used to PS ... not because it's a habit - there are very real reasons for it. Some of them I often mentioned before but serif keeps ignoring them up to the stage of not even bother to make any kind of comment. So I though I'd open this topic and bring my issues (again) to the attention of serif staff and other users ... maybe I'm not the only one.
     
    To find some good examples for my problems I decided to take a current project that requires stacking (where I feel AP is a lot easier with than PS). 7 RAW pictures that require alignment and focus stacking to adapt different areas of the picture. And what I'm describing now is not an exception ... things I describe are not necessarily reproduceable ... but it does not happen with ANY OTHER PROGRAM I use on my machine (just for those who already start blaming the state of my system as a scapegoat!). And whenever I start AP known and new things like that happen. I'm using lots of memory and disk space ... a still reasonably quick graphics card and processor on Win 7!
    After taking some time for reading the 7 big RAW files, aligning them and doing the focus stacking I get the processed picture. As well as a source list including all of my stacked single pics and the resulting pic. I add a levels filter and a curve filter to the file. Already after adding the curve filter the histogram is not displayed any more. I know this bug. It has been reported quite a while ago by me (and maybe other people) - apparently wasn't looked after. This does not always happen ... and is not clearly reproduceable, but since levels and curve setting are pretty useless unless you can see the histogram (except for those who do not know what they are doing) it is a bit of a bummer. Certainly knowing that it can only be solved by saving the picture and restarting AP. So I skipped this step and clicked on the first single stacked picture in the displayed list. First of all not even the focus did change to the newly selected picture I clicked on. 5 Seconds later AP completely disappeared and Lightroom was the active application (first I thought AP did crash, but it did not ... it just completely lost it's focus) ... so by clicking the task list I could get it back ... the behaviour interestingly was reproduceable. Now going to the develop persona and coming back to the photo persona the "source list" was reduced to one file called "untitled". Where did all the 8 files disappear to? OK, better don't ask. Now I want to compare the newly stacked picture with another similar picture I took. So I decide to undock the current window. Really a bad idea ... the new window does not resize but moves somewhere mostly outside the current working area. (Just as ONE example: when I do this in PS the new window resize to the layer size and displays with a certain distance at the top left corner of the workspace. PS comes with ready made presets for windows alignment. PS allowns a window to adapt to the picture size all the time. With AP it takes me ages to adjust this new window to the working area I'd like to have. And believe me I really tried hard to get it working or to adapt to this ridiculous user-hostile attitude - no chance. For those who did not get it yet: There is a good reason why the PS Window Menu has more than 25 additional commands for window adjustments - it's not because they had nothing else to do!)
     
    But many other things really set me up .... it's this lack of responsiveness of the UI (sometimes) ... you sometimes can drag sliders and they will not move ... or maybe with significant delay (seconds later). Sudden changes of focussed windows for reasons I don't understand (so you have to click in the window again you want to work in). Trying to confirm an action e.g. in a Windows UI manner (pressing Enter if you want to confirm a setting) and nothing will happen. Lacking "OK" and "Cancel" buttons so dialogs will remain open unless you find this tiny cross at the top. Settings I can't save (standard values in dialogs), paths AP will not remember (saving a picture where I loaded the original from). The export persona tries successfully to hide my user setting for standardised output format (bi-cubic,sRGB, JPG) as the last(!) entry in an extensive long list of useless "Standard" setting ... and it makes me search my standard setting for EACH picture I do export ... it seems to me like Serif is challenging my stamina and endurance in so many ways.
     
    I could go on and on on theses topics... my conclusion and answer to the question "why there's still no love" would be the following:
    Serif build an high performance Aston Martin Sports car ... but when you want to open the door you break your finger nails, the steering wheel is covered with nettles and the safety belt will come loose while driving. The gas pump nozzle is mounted in the middle of the roof, the bonnet occasionally opens while driving and it takes 15 switches 3 hooks and an armoured metal plate to get to the opener for the boot as well as many other obstructions. In a race against the Adobe Maserati it can easily keep up, is quicker in some curves sometimes even drives offroad ... But what car do you like to drive and will you choose to drive to work? Sadly Serif does not realise, understand nor care for these essentials at all! They can't stop celebrating AP won races (now on an iPad) ... and seem to forget that there a people around need to use the car on a daily base ...

    I'm not waiting for Affinity Publisher ... I'm waiting for AP to get a daily working horse!
    Cheers, Timo

    All descriptions refer to the latest final Version 1.5.2.69
  8. Like
    awhite reacted to - S - in Add .tif file mask to export dalog   
    I agree.  I have tens of thousands of TIFF images dating back almost a hundred years.  The originals and post-processed master files are all in *.tif format and therefore I will continue to use *.tif for consistency reasons.  Having a mixture of *.tif and *.tiff would be an error waiting to happen especially when carrying out searches/filtering, or carrying out operations in bulk using command line tools.  In addition the Affinity Photo 'save as' dialogue box doesn't see any *.tif files at all, which is a PITA. 
    In all honesty I don't understand why Serif don't just standardise on *.tif anyway.  I don't see any advantages of defaulting to *.tiff when everyone else uses *.tif and have done for a long time.  In my eyes it adds unnecessary complications with no benefit.
  9. Like
    awhite reacted to JustGeorge in AP Windows Exporting to Current Directory   
    I think this is a feature request, and not a bug report.  (I'm posting a pointer to here in the "Bugs on Windows" forum.
     
    Apparently by default, AP Windows exports to the last used directory, not the current working directory.  This can get very frustrating trying to find and move the errant file, as this is one of the two programs I use frequently that does this, so I forget in between sessions.  (ViewNX 2 is the other, but I'm using it less-and-less as I use AP more.)
     
    I don't work from one single directory.  I ingest from my cameras into date-based directories, based on file format (NEF, NRW and ORF).  Scanned images are filed totally separately, based on subject matter.  I'm using both Zoner Photo Studio 18 and FastStone as DAM programs.
     
    As an example:  if yesterday I worked in /2015-11/NEF, and today work in /2016-08/ORF, saving the latter TIFF ends up in the 2015-11/NEF directory, if I forget to change it.  (And that extra step can be a mild nuisance when I get really going  :)   .)

    Nikon ViewNX2 works like Photo; I have to remember to select the directory I want to save to.  However:  Zoner Photo Studio 18, FastStone, PaintShopPro x8, Paint.net, and Olympus Viewer 3 all save edits to the current directory.  Even the new Topaz Studio does this.  Qimage Ultimage saves files to a single default working directory, which is ok, since I know where to look.
     
    Saving to a default export directory would be an acceptable alternative, but obviously not my first choice.
     
    Hopefully this is something that can be implemented soon.
     
    --JustGeorge
     
  10. Like
    awhite reacted to fotojindra in AP Win - TIFF compresion   
    Hi,
     
     I would like to know deeper about Export possibilities of TIFF format. In the Export settings I do not see the possibility to choose between ZIP, LZW, RLE or other compression possibilities. When I am exporting to TIFF it makes some file that seems smaller then compressionless file however I do not see what happened to it. I do not even know whether the file was exported losslesly or there was an information loss :(
     
    Thanks
     Jindra
     
  11. Like
    awhite reacted to JustGeorge in AP Windows Exporting to Current Directory   
    AP Windows exports to the last used directory, not the current working directory.  This can get very frustrating trying to find and move the errant file.  Is there a setting I've not found?  Or should this be a Bug Report or a Feature Request?

    --JustGeorge
     
  12. Like
    awhite reacted to Gunny in "Remembering" last used parameters   
    While testing Affinity Photo for Windows I noticed several minor but rather annoying things. This is the most obvious:
     
    I'm used to creating rather wild selections and then feathering them. I usually use the same settings repeatedly (it basically depends on the size of the image) but every time I open the Feather dialog the slider is set to 0 and I have to move it again to the previously used value.
     
    I noticed similar thing in Liquify persona (the brush size is always preset to the same value) too and I'm sure there are many other places and settings like this...
     
    It would be really useful if the app could "remember" the last used settings because it's very likely the user will use it again. Presetting it automatically would save the user some unnecessary clicking.
  13. Like
    awhite reacted to BatteriesInc in Accept both comma and full stop for decimals   
    Hi,
     
    Would it be possible to accept both "," and "." as acceptable decimal separator, or give users a choice in the matter?
     
    You typically end up in this situation if your base operating language is English, but your keyboard is not - it then becomes a bit of a guess as to what will happen when you press the "." button on the numeric keypad (yes, some of us like larger keyboards :) ).  Some software will follow system language, some will follow the keyboard language, and typically you have precious little influence in the matter (only  LibreOffice and its NeoOffice derivative have a setting for it in their "Languages" preference).
      AD and AP both want a value of 4½ entered as "4.5" (system language), whereas "4,5" is what I end up with using the numerical keypad.  Rather than enter this as a bug and fire off a debate, how about being a bit smarter and develop an input routine that will accept either for numerical values?  I have yet to come across anyone who enters triad separators when keying in a number for data entry.
     
    In case that gets too complicated, could a choice be added to the setup?
     
    Cheers!
  14. Like
    awhite got a reaction from Alfred in How can I open files in a new window (Affinity Photo)   
    Thanks Alfred, that's what I needed.
  15. Like
    awhite reacted to Alfred in How can I open files in a new window (Affinity Photo)   
    'Separated mode' is a Mac thing. If you're on Windows (as I am) you just need to drag on the document window's title bar to make it float so that you can reposition and resize it: there are currently no 'Tile' or 'Cascade' options in the Affinity apps.
  16. Like
    awhite got a reaction from Dave Quail in Affinity Photo Customer Beta - 1.5.2.62   
    A few issues I have:
     
    1. This is not fixed: https://forum.affinity.serif.com/index.php?/topic/35335-saving-file-removes-all-exif-data/
    2. Still uses LZW for 16bit TIF, no options.
    3. The Save/export dialog doesn't reflect original file location.
    4. TIF extension is *.TIFF, no option for *.TIF
  17. Like
    awhite got a reaction from Leigh in TIFF file size   
    It's the LZW compression, it's good for 8bit images, but if you use it on 16bit image, the file usually gets larger than uncompressed file.
  18. Like
    awhite got a reaction from Petar Petrenko in [APh] TIF compression   
    I noticed Photo uses LZW compression for TIF files and there is no option to choose a compression type. That's fine for 8bit images, but for 16bit images a LZW compressed file is larger than the same file with no compression, so it would be better to use ZIP or no compression for 16bit images.
     
    And one more detail, It would be great if I could select to use *.TIF extension instead of *.TIFF in the save/export dialog, all other programs I use produce TIF and it's a little annoying for me to delete the "f" from the file extension every time.
×
×
  • Create New...

Important Information

Terms of Use | 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.