Jump to content

Search the Community

Showing results for tags 'Sigma'.



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
  • 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 15 results

  1. BW Images still open as colour, and when manually converted to BW, they lose all their Foveon benefits. There's two methods to obtain BWs from Foveon RAWs, and neither of them work in AP. Images taken with the Merrill series cameras are normally able to deliver BW images without the mushiness of a CFA (colour filter array, such as Bayer), or the heavy resolution loss from an antialias filter, like with the a Leica Monokrom, yet are not prone to strong aliasing artifacts like many other cameras. All test images were captured in BW, latest camera firmware, and open properly in some other applications as BW (however, some LibRaw demosaic engine apps open them as colour, suggesting LibRaw as a possible element for the problem. Note however, that digiKam which uses LibRaw 1.19 builds these image thumbnails correctly in BW, and it is configured not to extract the embedded jpeg - it is building a downsampled version of the raw). Forcing BW RAWs to convert from colour to BW in Affinity Photo for the nearly 9 months of production and beta AP versions results in severely downgraded noise and detail and tonal range. How can I support Affinity support getting the issue posted to LibRAW's devs, so that it gets added into their mix of stuff 'in the queue' to be prioritized? I'd really prefer if it had the gravity of a respected LibRaw integrator (Affinity) verifying that it's not some lone user that hasn't done any due diligence. As well, the LibRAW folks might not otherwise appreciate that this affects all Merrill sensor Foveons (not all Sigma cameras, but a large percentage of the current user base).
  2. BW Images still open as colour, and even if manually converted to BW, they lose all the Foveon benefits. There's two methods to obtain BWs from Foveon RAWs, and neither of them work. Images taken with 1:1:1 Foveons (such as those with the Merrill series sensors) are normally able to deliver BW images without the mushiness of a CFA (colour filter array, such as Bayer), or the heavy resolution loss from an antialias filter, like a Leica Monokrom, yet are not prone to strong aliasing artifacts like other cameras. All test images were captured in BW, latest firmware, and open properly in many other applications as BW (however, some LibRaw demosaic engine apps open as colour, suggesting a possible source for the problem, for someone within Appian to register this bug to the LibRaw community). Forcing BW RAWs to convert from colour to BW in Affinity Photo for the last 8 months (all production and beta versions) results in severely downgraded noise and detail and tonal range. Thx.
  3. BW Images still open as colour, and even if converted to BW, lose all the Foveon benefits. There's two ways to obtain BWs from Foveon RAWs, and neither of them work. Images taken with 1:1:1 Foveons (such as those with the Merrill series sensors) are able to deliver BW images without the mushiness of a colour filter array, or the heavy resolution loss from an antialias filter, like a Leica Monokrom, yet are not prone to strong aliasing artifacts like other cameras. All test images were all captured in BW, latest firmware, and open in many other applications as BW (some open in colour, and two of those use LibRaw). Manually forcing them to convert to BW in Affinity Photo for the last nearly 8 months (all production and beta versions) results in severely downgraded noise and detail and tonal range.
  4. Members 12 59 posts BW Images still open as colour, and even if converted to BW in AP, it loses all the Foveon benefits (not very usable). There's two ways to obtain BWs from Foveon RAWs, and neither works. This has been occurring for six months of production and beta releases, and is not a newly reported issue.
  5. BW Images still open as colour, and even if converted to BW, lose all the Foveon benefits. There's two ways to obtain BWs from Foveon RAWs, and neither works. Similar crops below from the same image, all at 200% zoom (slight variations in cropping). Most recent of multiple posts (prior beta) Above: AP 1.7.2.414 choosing BW Above: AP 1.7.2.414 choosing BW and only using blue channel Above: IrfanView 4.5.2 as opened (uses DCRaw) Above: Sigma Photo 6.6.1 Export using Blue Channel only
  6. Resolved: Can confirm 1.7.1.404RC2 has full control over noise removal, especially chroma noise (working since recent betas: thank you so much), and is fully usable now on Sigma Merrill cameras. Also, only as of 404RC2 is EXIF and focus reliably consistent. Outstanding: BW images still open as colour: no benefits from in-camera BW captured images. Additionally, some BW images shot at higher than base ISO open like linear exposure (super dark). Quick test images (apologies for quality): 6745, ISO100, BW: in 1.7.1.367 and .404RC2 has EXIF and focus info, but recent prior betas were partially missing EXIF & focus metadata. In all versions, these open as colour (should be BW). 6742, ISO800, BW: Very difficult trying to extract a workable image from these RAWs (shot higher than base ISO). Opens fine in other RAW editors. Why Not Use Normal Colour to BW (Post-processing Conversion): The key issue behind this is that the Foveon Merrill can capture the full spectrum at every single 'pixel' (photosite), and output it in BW (like a Leica M Monochrom). No demosaicing is required (or ever wanted). When these are shot as BW in the camera, Affinity Photo opens them as normal colour images, and loses all their benefits. For instance, Foveons also normally capture full spectrum at every 'pixel', and when all treated as BW, you can get 3 times as much sampling per pixel as the monochrome Leica, for improved noise. See earlier post (Issue #1): https://forum.affinity.serif.com/index.php?/topic/80333-med-resolution-images-auto-upsampled-to-high-bw-images-import-as-colour/ SDIM6745.X3F SDIM6742.X3F
  7. Just an update after doing some testing last night with 1.7.1.385, and the ongoing denoising/demosaicing issues (not sure which was causing the problem) which made Merrill (SD and DP Merrill series cameras) barely usable, now appears significantly improved. Before, there was so much noise evident (mostly chroma, but also some luminance) even with reasonably well exposed images, that to get rid of sufficient noise resulted in also removing so much detail that the output almost looked like a stylized cellphone oilpainting filter. NOTE: this problem only occurred with the Sigma Merrill cameras, and did not affect earlier Sigma cameras, which performed normally. Now, it is possible (for well lit areas within an image) to adjust the denoising so that you can just apply enough to get rid of widespread noise, but through the currently available controls, selectively adjust the extent applied such that a balanced amount of detail can be retained (meaningful noise:detail tradeoffs). It still needs a fairly bright exposure, but it is no longer prohibitive. I don't know if this was due to the hard work of Affinity or LibRaw, but thank you very much. I ran out of time, but images captured as pure BW may still be opening in AP as colour. I will test with .390 this weekend. But this is a huge quality improvement for all Merrill users.
  8. Buon giorno, scrivo questo post per riprendere due post precedenti che sono comunque interconnessi, chiedo agli amministratori di chiudere i miei due post precedenti. Uso un altro software con licenza GNU / GPL, o "darktable", e lo uso per una semplice ragione, sfruttando la libreria lensfun che è presente anche in affinità ma che è in grado di applicarla anche su file jpeg e usando un software gnu / gpl adattato allo scopo "ShitfN" per correggere le distorsioni prospettiche attraverso il rilevamento in gruppi di linee di fuga, sia che si tratti di linee verticali o verticali oblique, riesce a farmi guadagnare tempo prezioso nel correggere distorsioni e prospettiva, dato che Affinity ora applica il profilo dell'obiettivo solo ai file raw e non direttamente ma dopo il salvataggio, il che è scomodo, ma per me ancora poco pratico poiché utilizzo una fotocamera "Sigma".Inoltre Affinity per ora non ha una funzione di correzione della prospettiva automatizzata o almeno non di quella che funziona così bene, il risultato è che ogni volta che devi procedere a mano e in termini di tempo, diventa insostenibile ogni volta che devi cambiare un numero pieno di immagini. Chiedo quindi che, dal momento che questi due software, la libreria lensfun e ShitfN siano open source, fare uno sforzo e adattarli il prima possibile in quanto ciò fa la differenza tra un programma comodo e quindi utile e un programma bello ma non completo. Metti un video come richiesto, in modo che tu capisca di cosa sto parlando. Grazie Lorenzo correzione dell'obiettivo prespective correction.mp4
  9. This issue pertains to the Sigma dp0 Quattro which I own, and almost certainly also pertains to these other Sigma cameras on the Supported list: dp1 Quattro, dp2 Quattro, dp3 Quattro, sd Quattro. The problem is the same in Affinity Photo 1.4.3 and 1.5 Beta 6, installed on my Apple MacBook Pro Retina 2012 with Sierra OS. I want to thank the Dev team for tackling Sigma cameras at all. I know other Sigma camera owners are also grateful, as hardly anyone is tackling the Sigma X3F raw files in their raw processors, and the Sigma software is slow, ungainly and has very limited features. I also encourage the Dev team to tackle the current-model Quattro cameras I listed above, before tacking older Sigma cameras. THE PROBLEM: the rendered output has a very poor appearance when zoomed in. Even though the files are the full resolution, they look as if a 'coarse effect' or a 'low-resolution overlay effect' has been applied. The effect is so severe that the files really are unusable for Sigma camera owners. I have posted sample images including comparison with the straight-out-of-camera JPEG images, here: https://www.dpreview.com/forums/post/58608616 Please compare the camera JPEG with the Affinity file at 100% to see the magnitude of the issue. I am calling this a bug because, even though Affinity Photo 'works', it produces something unusable due to image quality issues. thanks
  10. Wetterhoun

    Black screen DNG

    I get a black photo when opening a DNG file of a RAW photo, shot with my Canon 80D and the Sigma 18-35mm f/1.8 lens, in Affinity Photo for iPad. See enclosure. Is DNG not supported?
  11. Since the recent update I can import RAW files. Thanks for that! :) The Canon 80D RAW photos I tested with Affinity Photo for iPad that I shot with the 55-250mm STM are of high quality. The Canon 80D RAW photos taken with the Sigma 18-35mm f/1.8 lens are of very poor quality when opened in Affinity Photo on my iPad Pro 12.9". See enclosed example. The colors are wrong, there is a lot of yellow in the highlights. Is this a bug?
  12. Good morning I noticed an obvious difference of tone by opening the same X3F raw file with Sigma Photo Pro and Affinity, which may be the problem? Trying to change settings in the sRGB color profile to ProPhoto RGB course the situation improves but is not solved. Lorenzo
  13. Hi Affinity Photo Team, When I open X3F files from my Sigma DP2 Merrill, I am met with green tint all over some photos or at outer circular areas around the center. Am I doing it wrong? Is there anything I can do for work around at the moment? If this could be fixed, it would be really awesome. n
  14. Hello, I'm HalbLeiter. Today, I experienced strange problem in the EXIF of the image I've taken. I'm using Nikon Df and SIGMA Art 24-35mm f/2.0, and the images were taken with the RAW(.NEF) format. When I opened these images with the Affinity Photo, the lens data were shown (ex. focal length, aperture) but the lens maker and model were not shown. I also made questions to the lens maker(SIGMA) and camera maker(NIKON). Answer from SIGMA: This problem is related with the camera maker. Maybe the camera maker have no information about the newly released lens on the look-up table. However, we don't have permission to tweak the firmware on the camera. Please ask to the camera maker. Answer from NIKON: In original, we(NIKON) are not supporting 3rd party accessories such as lenses, batteries and speedlights. In other case, when the camera body cannot recognizes the lens, the lens maker is updating their firmware to make recognizable. Please ask to the camera maker. How do you think about this? _DSC7569.zip
  15. I'd like to to know if Affinity accepts the raw files- X3F- from a Sigma Quattro dp2. I'm especially interested in local adjustments. If not, do you have plans to include it in your list of raw files anytime in the near or not so distant future ? Thanks
×