laurentia
-
Posts
161 -
Joined
-
Last visited
Posts posted by laurentia
-
-
1 hour ago, Mark Ingram said:
Hi all. Thanks for your patience over the weekend when our offices were closed.
We've had a meeting this morning and decided to ALSO offer MSI installers, to those people who would like them. I can't tell you when this will happen, as there is engineering work that will be required to allow this to happen, but we hope it won't be long.
Thanks for your feedback!
Hi and thanks a lot!
I am looking forward to this!
-
2 hours ago, Nox said:
I agree, delivering the suite as "Windows Apps" and not normal ".exe"-applications is extremely customer and user unfriendly. Not even Adobe dared to take this tainted path.
It rips off all the control the user have about their PC and the programs and makes things unnecessarily complicated.I'm very disappointed.
Hi,
I totally agree!
Windows users are not like Apple users, they need to see under the hood and the "WindowsApps" folder is not accessible even as an admin. My few useful programs are accessible by shortcuts and there, it's impossible.
I also ask for the return of ".exe" files -
Hi,
just for information this is my current driver updated by Windows.
Hope your PC works fine.
-
On 5/19/2021 at 10:08 AM, qwz said:
So, is there a fix i.e. some way to enable OpenCL with Intel HD 620?
HI,
OpenCL works well on my W10 laptop wih HD 620.
Photo 1.9.4.1065.
-
28 minutes ago, Rolbrecht said:
I don’t know what color management Microsoft is using so that un-profiled pictures appear the same with all kinds of programs, like AF, PS, Xnview, Browsers. Would it be possible to provide some kind of LUT that could be enabled or disabled when an un-profiled picture is introduced into AF? Or the LUT could be automatically added as a separate layer?
Hi,
By default, Windows uses sRGB.
For the solution, it's sufficient that the user has the choice of the profile to be assigned exactly as in PS when the right box is checked. -
1 hour ago, Gabe said:
It's both. It does't warn, and it assigns sRGB instead of the selected profile in Preferences.
Hi,
That's the basic problem! Why assume that the original space is sRGB?!
Ok, we have to start from something, but it is better to leave this choice to the user! A drop-down box is not so difficult to code, it has been done elsewhere without difficulty. -
In fact, Photo seems to first make a presumably sRGB assignment and depending on the choice made in the preferences, displays it as is or converts it in the workspace.
In the case of an image defined in ProPhoto RGB for example, you can easily imagine the damage!
The cleanest solution would be to let the user make the assignment of his choice instead of making an arbitrary one that has little chance of being the right one. -
2 hours ago, walt.farrell said:
-
Often users can provide an answer quicker than you'd get by waiting for someone from the Serif staff to respond. There are many of us, and relatively few of them
No one has said otherwise and that is not the question. The user can see what is happening and the developer knows what he has written.
___________________________________________________________________________________________________________________________________________________
You don't seem to understand the problem. Converting an image from one color space to another is done by matrix translation of the RGB values of each pixel. Without the knowledge of the source color space, you can't calculate the correct values in the target space. It's as simple as that.
AF Photo can only assume that the image is defined in an arbitrary space, a priori the sRGB, and then performs its calculation which can only generate errors and a degraded image if the starting color space is different and more wide than sRGB.
It would be better if Photo offered the user a wider choice, one of which would be to assign the space of his choice before opening the image (like Photoshop).
Usually this choice does not have to be the workspace but the space in which the image was originally created. This is where the result of the conversion will be good. -
Often users can provide an answer quicker than you'd get by waiting for someone from the Serif staff to respond. There are many of us, and relatively few of them
-
My questions are primarily addressed to developers ...
-
Hi,
the problem address images without an embedded profile opened in Photo.
- By default, the image is displayed in Photo as being in sRGB. But is this an assignment or a conversion? If it's a conversion, what is it based on, since we don't know what colorspace it was created in?
- If the "Convert open files into workspace" box is checked, Photo displays the image as being in the workspace defined in the preferences and displays the warning message. But again, is this a real conversion or a profile assignment? If it's a conversion, the problem is the same: what is it based on, since we still don't know which colorspace the image was created in?
It would be good if in this case of an image without a profile, Photo asked the user what to do and left the choice of the space to be applied to avoid conversion mistakes.Photo 1.9.2.1035
-
hello everyone,
my wishlist is short:
be able to pass the image in Lab mode as in PS with the possibility to hide layers a and b. -
Hi Walt,
I have already played with converters of this kind and the result is quite bad. Might as well do it yourself with good tools like lumariver for example.
XRite Camera Calibration generates ICC profiles for C1 that are a bit specific. -
Hi everyone,
First of all, thank you very much for your work with DxO Nik Collection! 👍
I haven't seen anything about it so far. I'd like to be able to pass the image in Lab mode so that I can work on the L layer and mask layers a and b as we can do in PS.
I've seen that we can switch to Lab mode in the curve tool (for example) but we can also work automatically on the two layers a and b which is not the goal.
This would allow we to create luma curves without touching the colors.If that's already possible, I must have missed something...😔
😷
-
Hello, Ian,
on my windows AF 1.8 version, there is no choice for the input profile - neither ICC nor DCP - only a choice for the output profile.
I agree, an input profile choice would be a good thing! -
On 10/31/2019 at 4:15 PM, Chris B said:
It would be preferable to wait for this. There are some brilliant improvements coming to this area of the app. I'd be interested to hear your feedback once it is available.
Hi Chris,
with the new beta 514, juliep's example works in manual lens selection without adding a lensfun file, but does not work in automatic selection.
-
Hi,
great news if you use the Nik collection by DxO 2.3 : Viveza 2 works fine : https://forum.affinity.serif.com/index.php?/topic/79748-color-problem-with-nik-collection-plugins/&page=4&tab=comments#comment-553503
- Mark Ingram and Patrick Connor
-
1
-
1
-
Hi.
I had not looked for lack of time yet, but I confirm that since the update of the suite Nik by DxO 2.3, the call of Viveza 2 since Affinity Photo beta 486 works perfectly with a zoom factor of 20% and 100% at home.
I specify that I use a color workspace 4 times larger than the sRGB. -
-
30 minutes ago, Gabe said:
As far as I can tell, there's nothing we need to fix, as the issue is with the plugin
Are you sure ?
The DxO PhotoLab workspace is limited to Adobe RGB and I don't use it for this reason. Your profile has exactly the same gamut as the Adobe RGB, I use significantly larger workspaces.
The plugin works very well with PS, I don't think the problem comes from him ... -
1 hour ago, Gabe said:
@Jowday can you attach a screen recording of what's going on? They work fine for me
Hi Gabe,
you can see here for example : https://forum.affinity.serif.com/index.php?/topic/99436-colour-profile-conversion-for-dxo-plugins-beta-180486/&tab=comments#comment-532673
-
On 11/1/2019 at 4:14 PM, Tom Lachecki said:
Just wanted to add, we actually compensate for this when the two crop factors differ.
Hi Tom,
it's true when the distortion is linear all over the field, but some lenses are known for their distortion in mustache (especially wide angle) and in this case it does not work very well.
-
And me too ... with great impatience!
-
1 hour ago, Chris B said:
Hey Julie,
It looks like the slr-sigma.xml file doesn't contain the exact lens you're using.
The xml file contains:
Sigma DT 18-300mm f/3.5-6.3 DC Macro but not Sigma DT 18-300mm f/3.5-6.3 DC Macro OS HS so you could fudge the XML and add the OS HS at the end and it should work.Hi Chris B,
unfortunately, it does not work. I tried this including with the exact syntax that appears in the exifs ie the original HSM termination and several other combinaisons. In any case it did not work and it seems that there is a problem with the procedure under Windows.
This is good news if the next beta improves this.
-
Quote
Unfortunately I still have the problem.
Hi Julie, I'm well aware ...
Usually developers read the topics, but if you have a direct way to let them know, don't hesitate.
Photo develop persona : input profile
in Feedback for the Affinity V2 Suite of Products
Posted
Hello,
In the develop persona, only the output profile can be positioned.
An input profile is desirable to improve the quality of the development depending on the camera used.
This would be to display the icc (and icm) profiles in a drop-down box. To avoid a list that is too long, it's possible to display only profiles whose device class is "scnr", which will eliminate display profiles, spaces and printing profiles.