Jump to content

Wumpus

Members
  • Content count

    68
  • Joined

  • Last visited

About Wumpus

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks so much, @DWright The cameras with the problem all have "Merrill" in the title, plus their predecessor model, just called the "SD1": they all use the identical sensor, and have the same output, but slightly different firmware. That comprises around 5 or 6 cameras. I personally tested it with my "SD1 Merrill" (a re-issue of the original SD1), as well as my "SD14", and some different Merrill user's provided images. My SD14's images behave very nicely in AP, but all the Merrill-type sensor images exhibit the same problem. HTH
  2. 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).
  3. +1 That would be convenient. Additional +1 if the docs could be expanded to explain what a "Clipped Tone" is, in the context of Affinity Photo.
  4. Thanks so much for testing this, @Mark Ingram How can I support getting the issue posted to the LibRAW 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 integrator (Affinity) verifying that it's not some lone user that hasn't done any due diligence, and also, the LibRAW folks might not otherwise appreciate that this affects all Merrill sensor Foveons (not all Sigma cameras, but a large percentage of them). Happy to assist. DC RAW engine doesn't have the same issue.
  5. 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.
  6. 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.
  7. Just a <1% chance thing to point out when I was burned by mysterious behaviour with Tiff's. It turned out that Microsoft changed the compression format that the tiff was using with something Microsoft preferred. It did this while it was carrying out its thumbnailing service (updating the Windows OS thumbnails for the concerned folder: nothing to do with the tiff format, except that the Tiffs were all recompressed). Because some files were fine for a while, then suddenly seemed 'broken' to other apps (yet behaved 'better' in Windows), I discovered what was happening and confirmed it with Microsoft. Probably unlikely, but just want to suggest that it could also be something unrelated that you don't even expect, messing with your files. Some apps will take liberties with your files. There's a few utilities that let you look at the full file structure, including EXIF and other metadata, and identify what each set of data signifies.
  8. 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.
  9. Celebrating six months of trying to obtain support for this issue!
  10. I found the drivers much more linear by setting them to a positive # for the curve, as shown in the screenshot. The responsiveness was really nice, actually. Notice I actually have Windows Ink enabled (I had thought it was disabled).
  11. Offsite so can't check until later, but found a prior post where I mentioned my model ( Huion 610 Pro v2 ). March 2019 Designer Beta forum It seems my model is different from yours, but i think the 1060 Plus was around the same timeframe as mine, so there's bound to be overlaps or similarities. I think our models both had 8192 levels of pressure, higher per second flow rate, and batteryless (if I recall: I'm pretty sure I had been looking at both models before I made my purchase). If I understand correctly, your question is about pressure 'transition' (curve?): it sounds to me like its' not exactly linear, but more like a formula one gas throttle? I will check mine out, but I don't recall any kind of concern once I got mine settled, but I think that might have been an issue for me when I started out using the wrong driver, and it was always jumping from zero to max pressure, and also my flow rate had been really slow and laggy. Make sure you have got the correct driver, and you might need to play with Windows Ink or Pen & Ink settings. I will try to verify but might not have a chance for a day or two.
  12. Still no change for current 1.7.2.414 beta. In fact, BW images still missing all quality benefits, and still an outstanding issue for all versions since January 2019. Nudges, bumps or escalations all appreciated.
  13. @Bobi and @Gnobelix I'm using this too, and have had great support from Huion, and it works well (except I haven't found out yet how to apply the tilt to any functions, but that's not important for photo editing, IMHO). The build quality was superb, the feature list is mind-blowing, and while Wacoms tend to be more broadly tested from developers (I have had 3 in the past, all bought as new) and after a while they just stop fully working. I wasn't feeling the love, and didn't enjoy repeatedly paying a premium price for something that always works very well until the day it doesn't (with no warning). I took a gamble on Huion, and it's only been about 8-9 months, but the construction and materials are quite high, with far greater functionality than anything in the price niche from Wacom. The drivers are definitely not as intuitive or have as clean or elegant or modern a user experience as Wacom, but they work, and you can master them if you invest a bit of time and checking other tutorials (lots on these models). They are gathering momentum in the marketplace, and again, the support is almost a white glove experience (other vendors take note). The second downside is that (this is from memory, so this might be off a little): there was a Huion 1060 II model, and a 1060 PLUS NEW model, and a 1060 II Plus model, and I had carelessly grabbed the wrong driver from their site and only had about 10% functionality. The different (but similarly named) models hardly have any overlapping support, so you need to be super careful about getting the exactly-named drivers (flip over the tablet to read the tiny model name). Maybe it's due to a right-left language or something in the translation, but it seemed to me, to be terribly easy to make that mistake, but once pointed out and having installed the correct driver, all was good. My prediction is that they are going to eat a lot of Wacom's marketshare, who have (IMHO) been sitting on their hands counting revenues for too long. All the power to Huion, even if the result is just to get Wacom to properly respond to their user base. I receive no direct or indirect benefit from this commentary, from either Wacom or Huion.
  14. In addition to manifestations of severe transmogrification levels, it appears that photos of transparent faeries riding on blue unicorns in close proximity to the camera may also create images that trip the yellow "Clipped Tones" warning. Also, when there are so many mid-tones that they even spill out the top of the histogram, that's "Clipped Tones" too. If anyone knows of any additional purpose of this switch, and how to correct for this warning, that would *really* be much appreciated. I already have loads of speculation across the fora for the last half year: I had been hoping to find an authoritative alternative. Thx!
×