Jump to content

Search the Community

Showing results for tags 'tiff'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity 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 92 results

  1. Hello When I export an image with spot colours as TIFF or EPS, the spot colours don't appear in the exported image. It looks like they are converted to CMYK. They do appear in an exported PDF but I haven't checked any other format. Thanks! Bauke
  2. When I open a raw file in affinity it is shown as a .tiff even in develop persona. Is it actually opened as a raw or is it converted to a .tiff when it is brought into affinity?
  3. Hi Team, I noticed the following issues while opening TIFF files. I could only get the top Layer but I cannot get all the layers. I noticed this issue for the files which were created from Photoshop. I switch from photoshop to Affinity Photo and I wanted to rework these files, but I could not open them now. Below some screenshots. If I opened them in Photoshop elements I see all the layers. I used to have full version of photoshop I no longer have the same. They used to open in Photoshop just fine. When I was switching to Affinity from Photoshop, I thought that I can use all the existing files. This is a big issue for me as I cannot use existing processed files. Is this a know issue ? Thanks Krishna Affinity Issue01.tiff Affinity Issue02.tiff
  4. There are 4 groups in this .afdesign file, made to fill a 4K cinema screen (4096 x 2160) with alternating black lines, color space 2020. The two horizontal groups and two vertical groups are identical (I think), except that one is shifted point 5 pixels on the x or y axis. The horizontal files export with identical file sizes. But the vertical centered file exports to a similar size (all less than a megabyte). But the 'offset' file is over 3 megabytes large. When the tiff files are opened in Designer they look identical (with all the layers intact.) But in Preview they look dissimilar. (The horizontal files look different as well.) I have tried all sorts of variations with similar results. (I also erased the final un-needed line recently in an attempt to change the result.) Does this Export happen similar for others? Does the Tiff file look identical on your screen? Many thanks. I am using iMac 5K, 27, 4.2 OSX 10.13.6 horizontal_vertical_lines_4k_.afdesign OffCenteredTest.tiff CenteredTest.tiff
  5. Making the transition from PS to AP, but running into an issue of tiffs that have a saved channel we use for selection. We typically mask out parts of our images that need color correction. We make our mask and save the selection to a channel that can later be recalled to be tweaked later. In this example we have a channel called "wall" in photoshop. Opening this image up in AP gets me an unexpected result. I would expect to see the added channel in AP that I could turn into a selection as we do in photoshop. These images are placed inside a InDesign document saved as a PDF for print. Why am I getting this result and how can I avoid this without reworking thousands of high res Images that I have already have saved selection channels saved into them? If my final image has to in tiff format, I want to avoid the tiff hack of saving layers or native app formats. Is AP mishandling the channels coming from photoshop? I can however, take an image and make a selection in AP save the selection as a spare channel, save it as a tiff and reopen it in AP without any issue. Coming from photoshop, it seem not to work the same. Here is what I am seeing: I expect to see this: Attached in the Tiff file that contains the "wall" channel. https://www.dropbox.com/s/kich7uu71cmi96v/FlowerCanvas.tif?dl=0
  6. This is a very basic request that should in theory be very easy to implement, but I would like the ability to export a completely uncompressed tiff file from Affinity Photo. I am aware that the data compression used in tiff files in Photo mathematically lossless, however, there are scenarios in which even this lossless reduction in redundancy can be undesirable, in cpu processing demands of doing this compression for when the file is intermediary or storage constraints are neglidgeable, preserving backwards compatibility with very old programs, or in my specific case, using images as a source for wavetable synthesis, or general image data sonification effects. Yes, there are workarounds, like file converter utilities, but giving user control on whether or not lossless tiff compression is used would be so much simpler, something I've encountered in pretty much all raw / raster image editors I've used.
  7. I want to deliver uncompressed 16-bit TIFF files to a client (unfortunately, I don't know the specifics on how they will be printed, like size, paper stock, etc..,) so I would like to give them the best image I can, then they can do what they need to on their end to meet their print needs. So I'm trying to work out the best workflow. There are 12 images I need to deliver, so I was going to batch process them into 16-bit TIFF files (from the RAW files), then open them in Affinity Photo to edit. Keeping in mind that AP can't export uncompressed TIFFs, what's the best workflow from this point? Open in AP, edit, save as TIFF with layers, then flatten, and deliver as is? Assuming that the TIFF I'm working with is uncompressed. Or , edit, save as TIFF with layers, then open in Preview and save as an uncompressed TIFF? Is there anyway to work with the photo in AP's file format, then get it back to an uncompressed TIFF? Not sure if I'm over complicating things, but all I really want to do is Take my RAW file, edit in Affinity Photo, and deliver an uncompressed TIFF. (The client actually requested a EPS file, because they will use Illustrator at some point, but that's not my problem lol.) Thanks for the help.
  8. I had a issue when exporting TIFF file with multiple layers in Affinity Photo. After exporting, the tiff file has multiple layers in Affinity Photo, but only one layer in photoshop at the same one (attached photos). My customer complained me about issue because they edited tiff file with photoshop. There were somethings wrong from me?
  9. Hello. I was looking for photoshop alternatives since Adobe refuses to sell lifetime license stuff until I found this. unfortunately, my camera AKA Canon 200D is not supported. My only available OS is windows so I can't rely on Apple core to take care of my RAW files. So I want to know when will my camera be added to the supported list and if I can use TIFF (8-bit, 16-bit or 32-bit float) format instead of RAW until my camera is added. Thanks in advance YAR Oracool
  10. Jdphotopdx

    File type?

    How do I simply see what file type I’m working with? I import a raw image from Lightroom mobile. I want to make sure it’s not importing a jpeg copy but the original raw file. Should be very easy in the metadata but it’s not there.
  11. My customer demands an uncompressed TIFF file. What do I do? It's not for me to discuss with the customer if uncompressed TIFF files makes sense or not - if the customer wants it I'll have to deliver it! What do I do? Does AP force me to load the compressed TIFF to PS and save it as uncompressed TIFF file from there? Cheers, Timo
  12. 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.
  13. I'm using Affinity Photo 1.6.4 on a Windows 7-64 bit Home Premium machine. I have some TIFFs that Affinity Photo does not open correctly--even though Windows Photo Viewer, DxO PhotoLab, and GIMP open them fine. For whatever it may matter, these TIFFs are grayscale instead of RGB, and are 16 bits per pixel. Opening the file brought up the Develop persona instead of the Photo persona. The file displayed completely wrong--grossly over-exposed, high contrast, like somebody had grabbed the top right of the tone curve and dragged it almost all the way to the left edge (while leaving it at the top). The first attachment is a screen capture from immediately after opening the file. The second attachment is a screen capture of the same file opened in Windows Photo Viewer, which displayed it correctly. Back to the Affinity screen capture. Note the histogram at top right, which seems to correspond to what I see. Maybe more significantly, note the "RGBA/32 (HDR) - RAW" text toward the top left, which seems to be wrong. In other words, Affinity appears to be misconstruing what it's opening. Just as an experiment, I clicked Develop, but the image did not get fixed or even change appreciably. Also: this is a big file, over 150 MB and 80 MP (it's a scan of an old 8x10 negative). In case you want to experiment, the file's page at the U.S. Library of Congress is: http://www.loc.gov/pictures/collection/det/item/2016796043/ and the direct location of the full-resolution TIFF is: http://cdn.loc.gov/master/pnp/det/4a20000/4a23000/4a23600/4a23684a.tif Thanks!
  14. After processing JPEG and TIFF files in Affinity Photo for Windows, I can no longer open the files in Nikon Capture NX-D. However, the same files will open in other programs such as Picture Window Pro, Windows Photo Viewer, & On One. Any suggestions? Thank you.
  15. Hello everybody! Greetings from Athens! I recently received some very large tiff images (product photography) with clipping paths. Subject images created in photoshop. As I am trying to work on them on my affinity photo, I cannot figure out the selections that made with photoshop. I cannot find any similar "path tab" as in photoshop. Affinity photo opens the image plain, no any further info, details, nothing! Do i miss something? if someone can assist me on this, it will be highly appreciated. The scope of editing such images is to change the background color. Thank you
  16. Hi there! Affected version: Affinity Design 1.6.4.104 (Windows) and confirmed on 1.6.2 (macOS) OS: Windows 10 Pro x64 1709 / macOS High Sierra We have a project file that includes two artboards, where one is always exported with a broken color profile on TIFF (CYMK). This results in three outcomes, depending on the software used with that file: - Windows image viewer and thumbnails: partly read color profile resulting in a color tint - Affinity Designer, Photo and Adobe Photoshop read the file without error and display correctly (probably more tolerant error handling) - Paint.NET aborts loading with a stream read error on the color profile section So the TIFF file is clearly damaged or only partly saved. The project file was started from a copy of a previous project, which exports its slices without issues at same settings. The new project file with the problem has the same export bug on Affinity Designer for macOS (using latest 1.6.2), so I suspect the file itself is somehow damaged. I prefer not to share the project file publicly but can provide it to support for debugging purpose of course. Here is the preview, the the labels are exported slices from the same AD file (two artboards). The left one is correct, the right one has a red tint. Paint.NET error: Thanks!
  17. Hello. I am suddenly having issues with exporting any files that I have in affinity designer. No file formats will export to the desktop, my flash drive, or any folders.
  18. I have just updated to version 1.6.4.104 and am experiencing a problem I never had with the previous version. This defines the problem. I import a DNG file. and then crop it. No other adjustments, I then export the file as a PSD file, a JPG file and a TIFF file. When i open the PSD file in either Adobe elements or Lightroom I see the whole cropped image. ie the image I had cropped in Affinity When I attempt to open either the TIFF or JPG file in Elemets or Lightroom I only see a portion of my cropped image. It is as though It has been cropped again. Attached are Original DNG.DNG Exported PSD.psd Exported TIFF.tiff Saved_Affinity_File.afphoto
  19. Hi, Can really do with some help here. Just got a Sony A7R3 not too long back. I use Mac Photos for my photo management. From Photos, I tried to edit my .ARW raw files using Affinity. However, when the file's opened in Affinity, it is converted to TIFF. When I export the RAW file out and open it directly with Affinity, it opens as RAW. Not sure if it's a bug, or I have some settings done wrongly. I had no problems with my previous camera, OMD-EM1. Thanks!
  20. einhugur

    I think TIFF export is broken

    I think TIFF export is broken If opening PNG with transparency and then exporting it as TIFF with affinity the result is very very bad most of the time. When using other Applications on same PNG the result is good, the TIFF looks same as the original PNG (at least with the naked eye) calendar96.tiff
  21. I'd appreciate some feedback on the process I'm using to convert image files for print (book). I've recently come over from Photoshop and am sure that Affinity Photo/QuarkXPress2017 are the right combination to produce the result I want, but I need reassurance - or suggestion of a better way ... This is what I do: Open the file (usually a .jpg) in Affinity Photo Change colour format to CMYK (8 bit) Using Resize document, change DPI to 300, uncheck Resample and click resize Then using Resize document again, change units to Millimetres (is there a way to make this the default unit) and then change the width to slightly over the finished size of the image in the book, choosing Resample at this stage. Then save as ... Then Export as TIFF CMYK (making no other changes on that dialogue box) However, I then always seem to have to resize the image (sometimes to less than 10%) once I've imported it into QuarkXPress2017 ... and the image file produced is rather large. Can anyone suggest what I'm doing wrong? Help would be much appreciated!
  22. Since this subject comes up often I am writing a definitive statement. Fireworks (layered) PNG files There is no such thing as "layered PNG". The PNG standard does not define a way to store layers, and only deals with flattened images. Fireworks saves out additional layer data to PNG files in a proprietary format using a private tag. A definition for this proprietary data has never been made public. A PNG saved by Fireworks can still be used as a flattened image by any application that can handle PNG files. These applications will handle the standard data and ignore the proprietary Fireworks data. Affinity handles standard PNG files. But, it cannot import or export the layer data using the Fireworks method. There is no expectation that we will ever be able to handle Fireworks layer data in PNG files. We acknowledge that being able to support Fireworks PNG files would be of great benefit to users of Affinity. If a public definition of the data format becomes available, we will be able to address the issue. Layered TIFF files There is no such thing as "layered TIFF". The TIFF standard only handles flattened images as part of the publicly described tags. TIFF does allow for companies to register additional tags for their own use. Adobe registered two private TIFF tags that enable them to embed layer data in a TIFF. These tags are an extension and are not part of the central TIFF standard. These tags are used to embed PSD layer data into a TIFF, in addition to the standard flattened image. Since Affinity has a PSD importer, we are able to import the layer data from a TIFF if it has these tags. However, since this is handled by our PSD importer it is subject to the same limitations as importing a standard PSD into Affinity. We make clear that while we aim to provide the best third party support for PSD, we can never replicate 100% the way Photoshop handles and displays a PSD file. Photoshop has its own approach to applying alpha/transparency, vector masks and vector strokes, layer effects and gradients. This means that while we can offer importing of editable elements of a PSD file, the result will not be a one-to-one pixel reproduction of what you see in Photoshop. We have registered our own TIFF tags for embedding Affinity layer data in a TIFF, in similar fashion to PSD layer data. This is intended for use with DAMs that use TIFF as their interchange format. When saving a TIFF file, if your document has multiple layers you will be given the option of including Affinity layer data. This will preserve the editable elements of a multi-layer document. This obviously comes at a cost of increased file size. Our TIFF tags will use our proprietary data format and as such can only be used by Affinity applications. At this time we have no plans to save TIFF files with the PSD format layer data. PSD layer data held in a TIFF file will be imported and converted to the Affinity format.
  23. 3drealism

    Tiff file and Alpha Channel

    Hi, when I render an image in 3ds Max and save as a tiff file with the alpha channel included, then when I load into Affinity the alpha channel is automatically enabled - when I disable alpha channel my image disappears. Does not behave correctly. Ideally the alpha channel should not be active when image is first loaded but can be made visible in the channels list.
  24. I'm kind of new to Affinity Designer, really any graphic design software, and have a question. When I have drawn/created an image in Affinity Designer in the CMYK color and I'm saving it as a TIFF CMYK, what resampling option should I use when I'm going to be printing it? Thanks in advance for any feedback.
  25. Just bought Affinity Photo. Love it so far, but was a little disappointed to learn that HEIC files aren't directly supported, so I had to figure out a workaround. In Apple Photos, I exported an HEIC file to 16 bit TIFF, but when I open it in Affinity Photos, it displays like the attached file. It opens fine in other programs, so I'm not sure if it's "glitching" just in Affinity Photos or is something with the way Apple Photos is exporting it and the other programs can "work around" it. This happens with all HEIC files using any color profile for the export. Photos originally captured as JPG export fine. Thoughts? Editing to add that I just read that while the iPhone can capture 10 bit color depth, it can only encode (write) to 8 bits, so exporting to a 16 bit file isn't likely going to gain anything and will just make the file bigger. Are there any plans to directly support HEIC in the future? I saw some forum posts about it but didn't see a definitive answer.
×