There’s a local lab development branch which can already do that. It may not be perfect yet but it works great. See here:
This would actually be a good idea and I was about to ask for the same.
I’m not part of the project, but this request has been rejected in the past. If you feel there is a market for this, you can code it or pay someone to code it and do support. Its Free Software so the code is as much yours as it is anyone else’s.
It will already open an image in GIMP, I believe.
hi,
this is the first time I hear about this… sounds like a bug. can you describe more precisely what you do?
this is normal. some tools are only applied when viewing the image at full size. see rawpedia for more info.
this also sounds very strange. can you give more details?
would be nice but I’m afraid won’t happen anytime soon… we have too many other things to do and too little manpower already 
as others have already pointed out, there’s an “experimental” branch that does this. the plan is to integrate it in the official version “soon”, but we can’t give an estimate of what this means exactly yet.
I understand I can cut and paste a profile.
What I was referring to with the way photoshop handles their history panel was that it shows a bunch of steps, but when you click on that step, you have no idea what parameters were used for that step, so you cant recreate it.
And also PS doesn’t save the parameters of a selection. If you want a selection saved, you have to specify and then save it as it’s own separate file.
The ideal image editor would have a history panel that functioned like this:
Record each Event. ( adjust contrast for example) also record the parameters the user entered on that step. (Contrast: amount, sharpness: radius, and amount, hue change: changed color values, etc.)
Create a visual list where each event is represented ( PS history panel does this part already)
Give the user the ability to select any step along the way, and at least VIEW the values of the parameters that were employed during that step, but also delete that step, or alter the parameters. (Application would then need to re-process image to update the results to the newly modified changes)
Allow the user to Copy and paste steps to other images, and copy/import ENTIRE history lists to other images.
Applications:
Several photos of same model. Apply all kinds of changes to various parts of the first image, using multiple selections until image looks perfect.
Now you want all other images to look the same. So you load second image, and import the entire history panel. Image is processed identical to first image. But the selections are off, because it is a different photo.
Simply click on the first selection, choose option to enter brand new values in for that step, draw in the appropriate selection. the click “done” or whatever. Then also redraw the other selections that dont match the first image and click done.
Then click a button that says “process new steps in history list” and the application sequentially goes through each step, making the new changes and now that image has it’s own history list, and the image is identical to the first, but with appropriate new selections.
Who needs PS “actions”? Photoshop already had a history panel, if they had simply included the ability to re-apply the steps, and alter the steps at any time and resave the history list, then they would have already had an "action.
The history list for an image would be the “action”. Want to run the action on a different file? just import the history list from the file that has the desired processing.
Another application:
You learn a new sharpening routine that looks way more natural, and want to go back and apply it many images without trying to reconstruct every single step that was done to every single file, simply to resharpen them with new parameters.
Open image, delete sharpening step in history panel, sharpen with new values, or new method, plugin, etc.
With PS i always had to write down all my settings, or screen shot them, just to recreate them on other images. Ridiculous.
They did have a save history log in the Metadata. But the first option didnt record the information one needs to recreate a file.
And the second option for recording history in Metadata literally records every single thing that happens. the log will show every time the file was opened. It will show if you switch from one window another file is in, to the window of the file recording the history and vice versa.
Parsing through that information to try and go back and recreate steps that were done to an image was too brutal, and I wound up just writing down the parameters for all my steps instead.
I think you should spend some time reading https://rawpedia.rawtherapee.com as a bunch of the things you describe are already there or don’t really apply to a raw processor (they’re pixel editor features).
Try to explain more. When I load a new image, the image opens up, but remains pixelated. I have to do something to the image so that the preview looks normal. I am in the habit of zooming out one click then back in one click so that the image is rendered “un-pixelated”
I did try Therapee 5.2 on a laptop and did not encounter this problem.
Should I try reverting to 5.2 to see if that fixes the problem? I would be happy to do anything I can to help you guys debug things.
Also, can I install 5.2 without uninstalling 5.3? and run it seperately? I will uninstall though and try 5.2 if that is helpful.
I assume the sidecar files in the directory with the images would be unharmed if I uninstall Therapee?
Yes when I open the tone curve panel within the Exposure panel, it defaults to the settings that I used in the last image I was processing. Its not super big deal, I just click the “reset” arrow and it zeroes out all the parameters. Effects my perception of the image briefly, but hasn’t caused a problem to the final image.
Let me know any more specific questions, or ideas I can do to help debug those problems.
: )
Agriggio:
I forgot to mention the laptop I tried Therapee on with 5.2 and didnt notice pixelation issue when loading an image was windows 10.
Aggrigio:
THIS IS SIGNIFICANT.
I just realized that issue is only happening when I open JPEGS to view them in Therapee.
When I open a RAW file, the image opens just fine, and renders “un-pixelated” immediately without me having to click on the zoom function.
So perhaps there actually is no issue, considering that Therapee is a RAW editor after all. Not a JPEG editor.
: )
This was a common bug in the past, but it rarely happens now. Simply clicking the main preview was enough to trigger the event which renders the preview in higher quality. Does simply clicking the main preview work for you?
Dont know what you mean by “main preview”
I click on a thumbnail to open an image, and it opens in the editor. is there a different window I should use?
Also I discovered it is only happening when opening JPEGS.
hi Alberto. It would be interesting to see what fixes and enhancements are planned for the next release; or in the next 6 months, say. Is it possible for you to say? Or is there a summary in github you could point me to please?
thanks!
I must admit, I never really cared about that oddity, but I had a RT session the other day and nearly every second image started pixelated. No big deal, but it’s still as present as in the first GTK3 release.
I actually have this problem as well, I didn’t think about mentioning it as I was so focused on the actual processing.
Same here, I think I also had it in between processing steps. Will have to check again…
In RT you can save partial profiles…
What does that mean?
You have worked on your model image until it’s perfect. Now you load another image and want it to look apply the same changes except for one or two. So you save the parts of profile of the perfect image you want to apply to the other images according to the instructions here:
http://rawpedia.rawtherapee.com/Creating_processing_profiles_for_general_use
1 Like
First to note, I was referring to what I thought was pointless about PhotoShop history log.
In particular that they dont log any of the parameters of each step/event. And more importantly that any area selections made do not get saved in the history log, so selections have to be saved as their own file.
In PhotoShop if you edit an image with many steps/processes, it’s pretty much impossible to go back to that image, and decide to apply the exact same sequence of events to another file.
With the exception of “actions” which is a convoluted way of accomplishing the task, considering that PS already has a history log.
But pertaining to Therapee, another user pointed out that a lot of my concerns were referring to the needs in a “pixel editor”, and Raw Therapee is intended to function more like Adobe Raw, rather than pixel editing.
Him/her brought this to my attention, and I agree. Not nearly the same need in a raw adjustment application.
But in any work flow for image editing, pixel editing, or raw adjustment I still think that a sequence of events is more effective, or at least and additional way to look at/quantify the process and components of complex image editing.
Having the ability to look back through the history log, and choose a specific processing event to toggle on and off, or delete said process, is helpful to establish what exactly one did to achieve a certain look, and what the cause and effect of the different processes are. And which ones were superfluous/detrimental and which ones were integral to the outcome the user was striving for.
Eventually certain patterns would emerge, as to how to achieve certain image styles, and viewing ones’ workflow as a series of steps, and specifically what series of steps, in my opinion is much quicker, and vastly more clarifying method of advancing ones editing abilities, and artistic vision, and also inventing/breaking new ground on previously unknown ( to the user or others ) methods of achieving certain visual objectives.
Essentially linear editing is a different way of looking at/solving the same problem, which of course can also be solved not looking at things in a linear way.
It would be nice to always be able to look at a history of processing events, toggle on and off different ones, and see what the effect was. And if looking at an image from a batch of images, one realizes there was a particular step they decide they should omit from the sequence of steps to achieve the image style they want, they could just delete/toggle off that step. And and achieving continuity with the other images in the batch would be as simple as opening them, and deleting/toggling that step off in those images as well, and all the images would be recreated with the exact image to image continuity as before, but each minus the particular step that was deleted, or changed to make the image better.
Creatively this also allows one to really experiment, compare, contrast, alter, the different processing steps, and UNDERSTAND the cause and effect of different processes more effectively and resolutely.
Certain collections of of processing steps would become like “Actions” and one could load a favorite sequence of steps ( history log ) and the “action” would be loaded in to a new file, but also still editable for each step in case that particular image needed slight tweaking because of of specifc needs for that image.
Photoshop could have implemented linear/editable History based processing in their history log EONS ago, but instead they chose to not even make the parameters that were used in a particular processing step in the history panel even available/view-able so that one could identify, and reconstruct the process he/she used on other files, let alone actually have independent/editable access to each of the steps in the History Panel.
So they eventually tried to address those needs with two clunky replacements, “adjustment layers” and “actions”.
Neither of which is as effective, or elegant as a linear and editable history event list. Adjustment layers are very prohibitive because of resource consumption, and also can not be applied to many of the pixel editing features, or filters etc available in Photoshop. And actions are just like hitting record on a tape player, and recording the entire series of events as one big performance then pressing stop. Both are clunky and bloated, and in the end, both systems are riddled with plenty of mystery as to exactly what occurred, and how one arrived at their final destination.
Sad, but true.
1 Like
Chapeau!!
That is the very reason I keep using Nikon software each and every time I experiment creative processing.
(and unfortunately that software is now out of production…)
@Ansel_Adams_Family I’ve the impression that what you want is more viewing the edited parameters in a single place instead of an editing log, where you could find several occurrence of the same parameter. For the later, it would be useless to update a parameter to a new value at one point in the history if it’s updated later on to another value. The change would then not have any effect.
For educational purpose, I can agree that summing up what have been tried so far would be useful, but that’s not what the History does. Actually, if you select an entry in the history and modify something in the right panel, the rest of the History is truncated and the said parameters is added to the new tail. What you see in History is a list of parameters that have been changed, however it technically is a snapshot of all the parameters, for each line.
You can see it with inactive values : sometime (because of heterogeneity of behavior), some tools that you act on does not create a new history entry, because the tool itself is not enabled. But it will still be memorized in the next history entry, once you’ll e.g. enable that tool. You’ll end up with one entry in the history, but which will include 2 changes in the parameters set. Think of it as a list of complete parameters snapshot, not a list of single parameter change.
We could enhance RT to let the user visually know if a parameter is not at its default state, however we can’t place them all in a single place.