Jump to content

Search the Community

Showing results for tags 'tif'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests, Suggestions & Discussions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 25 results

  1. When processing a 114 mb 16 bit tif file, in Affinity Photo, after various adjustment layers are made and then flattened, the file is exported as an 8 bit tif file with the size of 57 mb as you would expect. However when the crop tool is used to reposition the image to cut the bottom part of the image and leave a blank area at the top of the image for later filling in using the clone tool, the size of the exported 8 bit tif is 76.2 mb. The dimensions of the image is correct, just the file size is 'wrong'. The crop parameters are exactly the same dimensions as the original. Before exporting I have added other adjustment layers and then flattened the image, but whether I do this or not, the output size is still 76.2 mb. If I open this exported 8 bit file in Photoshop it shows as 'Layer 0' and if I then flatten it in Photoshop it then saves as a 57 mb file. The only conclusion I can draw from this is that Affinity Photo is creating an invisible layer when the crop tool is used in this way and this layer cannot be flattened within Affinity itself. I have used this technique now on a few images, each with different amounts of crop used and the output file is always the same - 76.2 mb.
  2. System: iMac late 2015 running 10.14.5 (18F132), Affinity Photo 1.7.1. Hello, I am editing .tif files (16-bit Mac Photoshop format tiff files) in Affinity Photo 1.7.1. I've noticed that after opening the files in Affinity Photo 1.7.1 and saving changes (no layers), that the size of the file on disk is reduced by approximately 50%. The number of pixels in the files and the file bit depth doesn't appear to change, just the size of the file on disk. For example, I had a 16-bit .tif file that was 102.8 MB on disk, I opened it Affinity Photo 1.7.1, I made a levels adjustment, merged/flattened the levels layer, did a command-s to save changes, and now the file size is 43.4 MB on disk. The number of pixels is the same, and according to the info window in the Preview app, the file is still 16-bit. This is happening with every file I edit and save today, and it never occurred previously. The issue does not occur when I save edits to the same files using Adobe Photoshop CS6 on the same iMac. Is this correct behavior due to a change in Affinity Photo 1.7.1? Or is it a bug? As I mentioned above, this did not previously occur (I've been using Affinity Photo this way for months now, perhaps over a year). I attached before and after screen shots of the Info Panel for one of my files. Thank you, Michael System: iMac late 2015 running 10.14.5 (18F132), Affinity Photo 1.7.1.
  3. Uncompressed tiff (16 bit grayscale), is the first really compatible format by Affinity. Please do not change it in the future. (Other tiff versions are less compatible.) Thanks, for effort to Affinity improve. Good job! (It would be great to add the default file extension settings TIF / TIFF)
  4. I'm trying to open a 3.88gb tif generated by PIX4D but it states that it is an unrecognised file format, any ideas?
  5. Hi, so, I am reporting a rather obscure error. It may be difficult to reproduce unless duplicating fairly exact conditions, so I will be specific. System / Software Operating System: Windows 10 Pro 64-Bit 1709 Build 16299.371 Hardware: Gigabyte 15X - i7-7700HQ / 16GB Ram / 1.5TB NVMe SSD / Nvidia GeForce GTX 1070 Max-Q GPU Affinity Photo: v 1.6.4.104 Capture One Pro: v 11.1.0.140 Issue Description Using Capture One (C1) 'Edit with' to edit an existing NEF raw file, a 16-Bit uncompressed TIF file is generated and saved in C1 and then sent to Affinity Photo (AP). Once this file is updated and saved within AP, the TIF file is successfully returned to C1. However, on trying to edit the filename in C1 immediately afterwards, C1 says that the file is locked by another process. This happens on all successive similar edits of NEF files. If one exits C1, and goes back to those files, they are no longer locked and can be renamed. To Duplicate 1. In C1, select a file such as a raw NEF file named IMG-1234567.NEF.2. In C1, right click the image thumbnail, and use 'Edit with' to edit in an external app, selecting Affinity Photo.3. In C1, this creates a TIF file in the same directory, in this case naming the file IMG-1234567.TIF.4. In AP, this TIF file is opened up. The image is simply adjusted (such as brightness or curves) and the image is flattened.5. In AP, use 'Save' in the File menu (or Ctrl-S) and then Exit (you can alternatively just exit AP using the close window button and confirm saving changes to the file on exit).6. In C1, after being returned from AP, the image thumbnail looks okay, updated and all looks fine. 7. In C1, however, it is not possible to RENAME the file, as C1 says the 'item is being used by another process'. Essentially the file is locked from file-based operations, unable to be renamed or deleted. Investigation 1. This occurs when a raw file is converted to a 16-bit TIF files that are uncompressed, using any ICC profile, 300 px/in. fixed 100% scaling, before being sent to AP. This problem does not occur when converting to and sending 8-bit TIF files, jpegs, PSD files or any other from C1 to AP. 2. It only seems to occur when raw files are converted to 16-bit TIF prior to sending. Editing an original jpeg or TIF file, where a 16-bit TIF is made and sent to AP does not produce any issue. 3. I have tried out this problem on a similar hardware system, with the same operating system (Windows 10) freshly installed, and the same issue occurs. However, on a Windows 7 system, this issue does not occur. 4. Using SysInternals diagnostic software, I have ascertained that when the TIF file is returned from AP to C1, the process that has locked the image file is in fact C1 itself, as though it has stalled on some operation on the file once returned from AP, thus locking the file until the software is restarted. 5. Sometimes, when I have tried this, 10% of the time there is no issue, but I cannot determine the reason for this variation. 6. Using 'Edit with' in C1 to call other editing software, such as Photoshop or OneOne PhotoRaw, using a 16-bit TIF is not an issue. Using software, such as Lightroom, to call AP is also not a problem. It is specifically when pairing C1 with AP, using a 16-bit TIF as the round-trip file format. 7. I have had one other user say that they were unable to duplicate the issue, although I cannot be sure that the exact operating system, software and GPU setup were the same. While I do not expect much of an outcome on this issue, I place it here for reference should the issue ever hit another user with similar hardware, operating system and software versions. In many cases, when people try to duplicate such an issue, one of the common reasons that the issue is not duplicated is due to some variable, environmental condition or procedural steps not being mirrored. However, should anyone with this setup like to report back their own findings, I would certainly welcome the information. Thank you, Cass.
  6. artphotopro

    tif file crash

    Hello Affinity, I have managed to crash AFP with a tif file, I have included the file and the screen grab of the error. Regards Chris _DSC0544_artphoto_007569.tif
  7. Hello, I'm testing the 10 days trial of Affinity Photo and have an issue with multi-layer TIFF images generated by Adobe Photoshop: when I import such images into Affinity Photo, all layers are gone, flattened into a single layer. Is there a way to make Photo recognize the Photoshop's multi-layer TIFFs? Thank you for your help!
  8. I have been doing some processing of astrophotography data. These files usually originate as FITS files which are the raw data files from the telescopes. I process the files using Liberator 3 which then saves the FITS files as TIF files (8, 16, or 32 bit). When I open the saved TIF files in Photo they have large rows switched around or have data that is off the page and missing. When I open the same TIF file in Photoshop the files appear normal. I can then re-save the TIF files out of Photoshop and then Photo opens them correctly. This is on Photo running on Windows 10. Here is a sample TIF file that was saved out of Liberator. When I open this specific file in Photo the image is moved up off the document area and the top part is missing. I can post screen grabs of the errors if other people are not getting the same thing when opening this file. Thanks for any assistance! http://www.spacetelescope.org/projects/fits_liberator/ The file is an image of the Eagle Nebulae if anyone was wondering. 502nmos.zip
  9. I always could export tif files from Dropbox into the affinity app, but affinity turns the file into a flat one layer file. Please fix that, so I can use my layers in the tif files again.
  10. 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.
  11. File passed to Photo 1.6.1.93 from Lightroom in Windows 7 64 bit. Carry out various edits - layers - masks - filters. Attempt to export tif, overwriting file created in Lightroom. Photo crashes during 'file save'. This has now happened on around 5 out of 6 times with different photos and changes. Can no longer justify wasting time doing edits!
  12. Normally i export to both TIFF and JPG when I have finished editing in Photo. JPG is easy, it always remember my prefered settings. But TIFF: The Preset setting changes every time. It is empty or shows "TIFF RGB 8-bit". I always select "TIFF RGB 16-bit" and it should remember that. Windows, Photo 1.5.2.69
  13. Tif error? The picture (mask) in the .tif format, is opened as empty, in AP and AD. In ACDSee and Photoshop, it opens correctly. (.tif file attached: mask.tif) Thanks!
  14. Affinity photo 1.5.1 crashes when loading the attached 16-bit tiff (gzip compressed to upload it) which is generated by Nikon Scan 4.0.3 using . It seems to be related to the multi-layer tiff that NikonScan is producing (high-res 16-bit RGB image as layer 0 and low-res 8-bit RGB preview as layer 1). When extracting layer 0 from the tiff with Image Magick convert, then AP reads the image fine. I guess it has to do with the unexpected "difference" in bit-depth for the different layers... Thanks, Martin test.tif.gz
  15. All my other photo software uses TIF as the file extension for Tagged Image File Format image files. I am curious why TIFF was used by Affinity. It makes my file lists look ragged and will probably interfere with sorting lists. Can we have the option to export as TIF not TIFF please?
  16. Hi, can we have consistency with extensions? When I batch save I get "fileName.tif" When I export I get "fileName.tiff" I would prefer all tif files to be saved with the extension .tif however, the main point is that they are always saved with the same extension. Thanks.
  17. Just starting out with AP and very impressed so far. I'm wondering why saved .tif files (generated from CaptureOne) increase by over 20% when saved in AP? I only have apply one small clone edit for this to happen.
  18. At the beginning I just want to say that it seems that everyone want to have photoshop but under the name Affinity Photo :) So... In Photoshop we can choose if we want TIFF with lossy jpeg compression or lossless ZIP or LZW. In Affinity Photo dialogue window there is no such thing. There resampler that suggest that AP compression algorithm is lossy. Can you tell me if it is lossy or lossless? Does it matter which resampler option I choose? What are the differences between them? p.s. Sorry for my English
  19. Hi, Is the issue with black tiff files in preview on macs fixed in 1.5? Cheers Peter
  20. Exporting a Tif file adds the file type .tiff not .tif I know both are acceptable but .tif is done by everyone else so AFFINITY should conform. cheers Ian
  21. When I save as TIF, lanczos 3 (non separable), the resulting file is blank, or black, or filled with static. This is the file compression recommended in your tutorials (excellent, btw). Other filetypes, jpg, png are viewable with that compression algorithm. The resulting file is the same size as that calculated in the export pane. No Mac app I have can open, including graphic converter. Is this issue repeatable by members of this forum, or is it some anomaly related to my system?
  22. Hey, i created a panorama with Hugin(2014). I exported it as PNG and it opened in Photo just fine. But the dynamic range was poor. So i exported a TIF. HDR or not, LZW compressed or not, everytime i open the file in Photo, it crashes. Filesize is around 400MB and opens just fine in Photoshop. I attached a download to said file, maybe you can figure something out? https://db.tt/R6gpzTuQ Thank you for your consideration :)
  23. would like to see export as tiff with an extension of "tif". Some programs don't like tiff.
  24. hi folks! just downloaded the beta of affinity photo -- looks sleek and awesome, opens files pretty quickly too! but i work mostly on layered tif files and saw that when i open tif files on affinity photo, the layers are gone... i did try to see if it's the same with psd, but with psd files, all the layers show up. anyway, i've been trying to search this forum for someone who noticed the same thing but haven't had any luck yet! hope to hear from someone soon! thanks!
×