I keep files in progress on local SSD storage. Once a day I synchronize it with network storage via samba. FreeNAS/zfs. Mirror of two disks… There I also take zfs snapshots for the dataset, where I’m saving photos, once a day. The lifetime of the last snap is 2 weeks. If this information is important.
Local SSD is fine. I was asking as we had a lot of issues when RT had to read directly from network devices.
Network resources are used only for storing files + torrent client. Well, unless I count viewing images, videos, or documents.
The program may also crash if I click on the title of the program window. It happened once, but it happened.
I don’t remember a single case where it fell while I was working with it. Once I worked for about 12 hours without switching. I took a break - that happened, but I didn’t switch to other windows.
It crashes when switching to other applications. For any application. Notepad, browser - whatever. 50/50, but falling.
To be honest, it doesn’t bother me much. The moment of scrolling through images is much more annoying. It does not know how to create previews - generating images based on the default profile. Even if it takes a long time, I could go away to rest. But sitting and waiting for development while flipping through is not very convenient. Time. It is not entirely clear why it cannot do this in her free time - the developers did not provide for this.
I could scroll through the pictures, of course, in Adobe Bridge, or in any other browser, but what is important to me is that the program generates preview images for the profile that I created for it. It’s easier for me to visually understand what rating to give to images. Because in Adobe Bridge, or anywhere else, I can give an erroneous rating due to an incorrectly developed image. The program develops images very competently, albeit in a flat form (I dropped the curve) - it makes it clearer to me what’s wrong with the picture and what it is like.
Well creating preview images is exactly the developing process …
Well, it’s clear that someday they will do a lot of things. I’m talking about workarounds )
It doesn’t matter. You can use xnview/bridge etc and to hell with it.
Now the program began to crash during operation.
I tried to assemble it using the manual https://rawpedia.rawtherapee.com/Windows, but it looks like reading it is like taking public transport without having your own car)) The manual is either outdated, or the author assumes that the reader knows how to improvise well, encountering errors during assembly))
I haven’t even started the rawtherapee configuration stage before building.
It’s very disappointing to go back to work in Adobe Camera Raw and there’s nothing you can do - it “works” for everyone.
The program began to crash every fifth photo. I looked, thinking that maybe something had happened to my computer, but neither Adobe programs, nor stable diffusion, nor davinci resolve, nor any other program even aroused suspicion.
No. In dev version there is some kind of huge color shift, although in the color management settings I also indicated the system profile and had already decided to manually indicate my own profile, which I created in displaycal.
Export settings - srgb. No variants.
There was no such problem in the regular version.
lucky, as a drowned man.
I had this problem in some version, older than 5.10, a few months ago. In short, I encountered the problem before. Then it disappeared somewhere when I downloaded rawtherapee again.
It seems that you specify the srgb workspace for the program, but it continues to “sit” somewhere in the prophoto color space.
Because if I switch the workspace to prophoto and back, I won’t see any difference in color at all.
With all this, if I specify the output profile as prohoto, open such a file in photoshop, then I will not see the difference, and only if I convert it in photoshop to srgb, will I see the difference. What I mean is that the srgb workspace either does not work in my program (rt), or one of two things. I’m stumped, to be honest.
And, by the way, it turns out that the same picture exists in the regular version of rt. Does the workspace module even work in rt? There I can select any workspace, and the image will not change, no matter how will be not “decorated” or “decorated” (colors) it is.
Example: In Adobe Camera Raw I switch the workspace (settings) from prophoto/etc to srgb and I see a difference in the color of the picture. In rawtherapee I don’t see a difference when switching workspace profiles.
Downloaded art 1.22. There, if I switch the color workspace, then I can see the difference in color.
Accordingly, when exporting, I do not observe any differences - the color in art and in other programs is the same. I struggled with this issue all day, but didn’t solve anything.
An upset customer, and I’m completely shocked.
I have RT 5.10 …some version I will update with that but you can see here I see the change in color when a different working profile is used for the pipeline calculations… (at least if using the default auto-matched tone curve)
The output profile has an impact as well, esp the BPC setting and how other software interprets that…
Using the default profile in RT it will show at least on my setup the change in the red jacket and the blues as well are quite visible. It will also render the BPC changes provided the profile supports that… by default appears that it does not… If on the other hand you use a profile that does say the one of the profiles from color.org it will indeed render with bpc applied. The one last nuance is that ART will actually show BPC in the preview when you toggle it on and off with a supporting profile whereas RT will only export a version of that image…
Just so there are no artifacts for screenshots I exported these combinations…
The RT exports made with the default output profile should show the color differences introduced by altering the working color profile but will not be impacted by changing the BPC setting.
Then use the color.org profile and you will see both…
Likely this is also what contributes to differences noted in photoshop as I read but cannot test that Photoshop uses by default BPC when it renders to screen and so the washed out colors that some people report in photoshop when transferring in from RT might be due to photo shop presenting a version that resembles the export below generated with BPC and the color.org profile…
Color.org profile no BPC so similar to above
Not sure if this will show up in browser previews but it shows up in my color managed viewer xnview.
Here you can see the difference with ART as it can preview BPC
Caveat here though might be also if you are using the default of auto-matched curve…if instead you set that to linear/disabled and or use a DCP file with its tone curve then the changes you see from changing the working profile appear to be different depending on the image.
Honestly. I’m exhausted. Even if the stars from the sky suddenly make this program ideal, I’m done. Work ahead with photographs - a train. I no longer adequately perceive reality - I’m very tired today.
Thanks, but I’m still with rt. I apologize if you tried to answer me, but I did not take advantage of your advice and help. No hard feelings on my part.
1 Like
What are you trying to tell us with this from one of your videos?
You see, that this tool is switched off?
I can turn this moment on. Usually it is turned on for me. It will not play a special role. With this option enabled, history repeats itself.
I switched to art. Everything works perfectly there and, by the way, the program does not crash, although in theory the gtk libraries are the same as those used for the build.