Jump to content

DeepDesertPhoto

Members
  • Content Count

    142
  • Joined

  • Last visited

Posts posted by DeepDesertPhoto

  1. A while back I asked if the 96 PPI resolution for panoramas, stacks, focus merge, and HDR merging would be fixed so that the final rendering would reflect the original 300 PPI of the source images.
    I noticed that it has been fixed when rendering panoramas using the TIFF format for the source images.
    However, I just tried to render a panorama with the source images being in the Radiance (HDR) format and the finished resolution of the pano was 96 PPI even though the source images were 300 PPI.

    Is this just an oversight by the development department or is it a bug?
    Just wonder, because even though I don't use Radiance or EXR formats often it is annoying to have to manually reset the final resolution to 300 PPI before doing my final editing.

    I mostly use Radiance and EXR for stacks and focus merging. I did a test and found that when using Stack or Focus merge I get the same 96 PPI resolution on the final rendering.

    Although this is not a priority fix I was wondering if this would be remedied in the next release so that when I use EXR or Radiance formats the final rendering will be the same as the source images.

  2. Just downloaded and installed the new update for AP 1.9.1.

    The export problem for TIFF Lab color seems to be repaired.

    It no longer crashes when trying to open Lab color files or when exporting LUT.

    But there is still one problem; it will not allow me to add, delete, or rename custom Export Presets.

    I have a custom TIFF export preset I wanted to rename to better distinguish it from the default preset but when I go to manage presets the buttons for "add" "delete" and "rename" will not work.

    Is there a workaround I don't know about or is this another bug that needs fixing?

  3. 4 hours ago, MEB said:

    Hi @DeepDesertPhoto,
    This issue was already fixed in the Beta. The fix will be included in the next retail update soon (v1.9.1).

    Hi @Paul Coddington,
    Welcome to Affinity Forums :)
    The issue exporting TIFF LAB 16-bit files was also fixed in the Betas and will be included in the next update (v1.9.1).

    If you still find any issues, please let us know. Thanks for your reports/support.

    Yes, MEB, I already know about the Beta version.
    I have been using it to work with my LAB color files.
    But it is an extra step in my development process since all of my custom presets are on the main program.
    Hopefully you will have the new update out soon.

  4. 5 hours ago, Paul Coddington said:

    Yes, I will wait for them to fix it as I have plenty of things to go on with for now. I don't need to export Designer projects to TIFF immediately. I am using LAB color space to create vector images with very precisely specified colors that I want defined by absolute (LAB) values not ICC-relative RGB values.

    I have just seen Affinity Publisher crash attempting to open a LAB Adobe Illustrator file (it defaults to open *.AI files in Explorer, as it turns out, and I am converting some older *.AI files to *.AFDESIGN, so discovered this by accident yesterday). So all three Affinity apps seem afflicted by the same bug for various contexts that invoke an underlying shared LAB module it seems.

    At least with me posting this, support now have confirmation that multiple users are affected, not just one. My system will have uploaded a few crash reports as well.

    LAB does have some advantages over RGB.
    LAB was originally invented to mimic the colors perceived by the human eye. Although I am not creating vectors like you I like to archive my finished images in LAB color for printing purposes.
    When I print with my LAB images I find that the colors of the print are visually identical to what I see on the screen.
    When I used to print in RGB mode certain shades of red and blue would never look come out right in the print.

    As MEB said in his reply there is a Beta version that can handle LAB color.
    I don't have Design or Publisher, but if you are getting the same crash when it tries to export or open a LAB color file then the problem is in the base coding of the program, so make sure to keep sending in those crash reports. They can't fix it if they don't know about it.

  5. 8 hours ago, Paul Coddington said:

    Yes, I expect that is the case (even the export dialogs for both look the same). Photo crashes for me if I use it to try and export the same Designer files to TIFF, so it will likely be a problem in a shared library used by all three applications. I have no trouble exporting them as any other color space I've tried so far.

    I have been exporting my finished images as TIFF 32 Bit HDR files to preserve all the color and details of the Camera RAW image after development.
    I then use the Beta version to create 16 Bit LAB for final archiving.
    The reason I don't use the Beta version to do everything is because all of my custom presets are on the main program.
    Using the Beta version to export a Lab TIFF from the 32 bit HDR TIFF is an extra step, but at least the Beta version enables me to complete the work.

    Hopefully they will have an update soon that corrects these problems in the main program so that I don't have to keep using the Beta for the final export step.

  6. 38 minutes ago, Paul Coddington said:

    I have a similar problem which may be related.

    Except I am attempting to export 16-bit Lab TIFF from Affinity Designer projects rather than open them in Photo.

    Basically, selecting Lab for export as TIFF immediately crashes the program for both Affinity Photo and Designer.

    I don't have Design, but if it uses the same base coding as AP for its export functions then it might be the same problem.
    I downloaded the Beta version of 1.9.1 which is able to open 16 bit LAB TIFF.
    You'll have to contact a moderator to see if there is a Beta version for Design that has this problem fixed.

  7. 14 minutes ago, Patrick Connor said:

     

    It is a bug in 1.9.0 (hidden by the crash) that is also in current 1.9.1 beta

    The beta 1.9.1.219 was built before the fix for this went in, but the next beta will address the inability to export presets. If you happen to have Publisher then the Mac beta includes this fix.

    This is currently a specific beta issue so I will move it to the beta section.

    I don't have Publisher or Design.
    All of my work is in photography and photo-manipulation.
    I also do some digital painting.
    So Affinity Photo is all I am using right now.

    I know it takes time to fix the multitude of bugs but any idea as to when the next update for the main install will be ready?
    Just wondering.

  8. Since the new update to fix all the bugs in AP 1.9.0 is not out yet I have been using the beta version for specific tasks that I cannot do with the main program due to the bugs making it crash.
    But I have noticed that I cannot create any export presets with the beta version.


    For example, when exporting TIFF 16 bit Lab the default preset uses ZIP for the compression, Bilinear for the resampler,  and "whole document" for the ICC profile.
    I normally change the resampler to Lancsos 3.
    I normally change the compression to "None".
    And I normally change the ICC Profile to CIELAB D50.


    In the original program I had these settings saved as a preset so that I would not have to manually make these changes every time I wanted to export to this TIFF format.
    When the 1.9 update was installed that was when the bugs caused the program to crash when using the preset I created or trying to open images created using that preset.

    When I downloaded the Beta version I thought I could create the same preset so that I could continue my work while waiting for the official update with the fixes.
    However, when I tried to create the preset with the alternate settings the "Add Preset" would not highlight when I clicked "Manage Presets".

    Is this due to it being a Beta version, or is this a bug in the Beta version.
    If it is a bug I hope it is fixed when the new update is ready because not all the default export presets work for me and I need the ability to save the settings I create.

  9. I don't know if this has been asked yet, but I downloaded the AP 1.9.2 beta and when I opened it the program asked me to register it.
    I bypassed that message since I wanted to see if the problems I reported in 1.9.0 were truly fixed.
    But I was wondering, if I do decided to register the Beta version will it interfere with the main program already on my Mac?
    I was also wondering if I can keep the Beta version on my Mac to use as a backup in case I have further problems with the original program I bought?

  10. 59 minutes ago, walt.farrell said:

    Yes, it is a zip file. But it is a Mac zip file, not a Windows zip file. (That is, a zip file containing Mac data, not a zip file containing Windows data.)

    It took quite a while to download, about 45 minutes, but it does seem to work on my Mac.

    It did work when I used it to open a LAB color file that was a problem for AP 1.9

    But all of my Camera Raw Development presets and Custom Export presets are on the main program, so I will only use the Beta version for opening problem files until the new update becomes available for the main program.

  11. 20 minutes ago, AGG said:

    A mi me ocurre algo parecido. También me sucedió en la Beta antes de que saliese la actualización de Affinity 1.9  (Utilizo  Macbook Pro 15", última versión de Big Sur)

    Cuando voy a  guardar el documento, me sale un cuadro de diálogo indicando que no puede escribir porque no encuentra la ruta.

    Esto además de otros errores ya comentados. En ocasiones no funcionan las herramientas, bajo rendimiento,.....etc.

     

    I had to run your comment through a translator, but if I understand you correctly AP 1.9 is pretty buggy.
    I just sent tech support a file that causes the program to crash.
    Hopefully they will find the problems and send out another update with corrections as soon as possible.

  12. 2 minutes ago, MEB said:

    Thanks for the file @DeepDesertPhoto. This is a regression from 1.8 and 1.9 Beta (where it was still loading on build 196). Issue logged to be looked at.

    Just in case you might need the info I have included 2 screenshots of the LAB presets.
    One screenshot is of the original builtin TIFF LAB 16-bit preset.
    The other screenshot is a custom preset I made in which is changed the resampler, the ICC Profile, and the compression.

    Since the program crashes when trying to open a file made from the custom LAB preset this info might by relevant.
    Any questions or if you need another file for comparison let me know.

    I do need this problem fixed as soon as possible because if I cannot open the files with AP I cannot print them for my work.

    Custom LAB Preset.jpg

    Original Affinity TIFF LAB 16-bit Preset.jpg

  13. 27 minutes ago, MEB said:

    No, it isn't too big, don't worry. Thank you @DeepDesertPhoto. Here's the upload link.

    I just sent you one of the files in question.
    My internet is kind of slow. Took 20 minutes to upload the file.
    Just to let you know I used a custom TIFF export preset to create my files.
    I made this preset a long time ago with one of your older versions of AP so this problem might be related to that.
    I was going to delete the preset to see if it would have an effect but for some reason when I click the "Manage Presets" in the Export window it will not highlight any options.
    Might be another related problem.

    If you need a TIFF 16 LAB file that does open normally for comparison purposes let me know and I will send it using the same link.

  14. 4 hours ago, MEB said:

    Hi @DeepDesertPhoto,
    Do you mind attaching one of the TIFF crashing Affinity Photo please? I can provide an upload link if you wish to keep the file private - just let me know. Thank you.

    Hello.

    Yes, I would like to keep it private because my images go up for sale to exclusive stock agencies and I cannot have them copied and shared.

    So I will need the private upload link before I send it to you.

    Not all of my older files have this problem, but for some reason some that were created by the prior version of AP simply won't open and the program crashes.

    There is a batch of 14 photos I worked on dated February 5th and 6th. All of them were originally Nikon D810 camera RAWs that I exported to TIFF 16 LAB color after development.

    Out of those 14 TIFFs created by AP 1.8.6 two of them will not open using 1.9.0 and the program crashes yet they are identical to the other 12 in that they are TIFF 16 bit LAB color.

    The file I will send you is 369 megabytes in size. That is not too big, is it?

    If the file size is within your limit please send me the private upload link.

  15. 17 hours ago, Adil _P said:

    Hello I upgraded to Affinity 1.9 for MAC OS X and am running macOS Catalina 10.15.7

    I worked on a file for most of the day yesterday in AP 1.9 and when I came to export the work into a jpeg file I used the File>Export route and got the following dialogue box up (See enclosure) when I hit export button the dialogue box asking where you want to save your work is missing and the dialogue box disappears. I search my MAC to see if the file had been created and stored which was not the case. I also tried the "save" and "save as" features do not appear to work either.

     

    Anyone else have similar problems?

    Screenshot 2021-02-06 at 20.43.25.png

    I have already posted 3 times about bugs I have discovered.
    The program crashes when I click export LUT.
    It crashes when I try to open a TIFF file in the LAB color space that was created by the prior version of AP.
    It also crashes when I tried to export to TIFF 16 bit LAB color.

    It seems this new version has a lot of bugs to squash.

  16. I already posted about AP 1.9 crashing when trying to open files that are in TIF LAB color, but I also found out this bug seems connected to exporting TIF in LAB color.

    I managed to export to TIF 32 bit RGB, and other formats, but for some reason the LAB color space is crashing the program.

    I must have triggered 10 or more crashes while experimenting in an effort to isolate this problem.

    Each crash report was sent to Apple automatically.

    So far the only way I have been able to work on older TIF LAB files that were made with prior versions of AP is to use another utility program to convert those files into PNG 16 bit RGB. I can open PNG files, but I should not have to do this conversion process to work on other files.

    Please fix this as soon as possible.

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.