I have never touched the registry. It looked straight forward enough but I had a couple of concerns. Firstly, the path in the example didn’t correspond to the directory structure on my computer. My path includes a version number, i.e. \Program Files\RawTherapee\5.6\rawtherapee.exe. Secondly that location on my computer already contained some garbage referring to RT version 5.1 which has been uninstalled. So given that combined with the fact that I didn’t believe it would work anyway – based on your comments and my inability to get what I wanted from the command line – I decided the safest thing was to leave it alone.
What I am looking for when I call RT from another program is to open the file for editing in an already running instance of RT so that the response is relatively quick and I want o be able to make use of the template defined on the “Que tab”. I have auto-start checked so that when I am finished with my edits, I just hit “put-to-que”, leave RT and return to my other program (Photo Mechanic in my case). And as I said, I get that on the Mac. I’m just not set up for serious editing on the Mac.
Well, it is now almost a year later and the issue still exists. However, now I am running RT5.8 under Windows 10. My registry is consistent with the entry shown several posts above – that is, the -R flag is set. If I right click on an image file, I am presented with the option to open with RawTherapee. If I choose that option, RawTherapee opens in a full-fledged instance as advertised. So far, so good. However, if I now right click a second file and choose open with RawTherapee I get a second full-fledged instance instance. And also for a third file, etc. I do not believe that this behaviour is consistent with that described in rawpedia. It is certainly not the behaviour I want or need.
Is there any way to ensure that “open with RawTherapee” will make use of the currently open instance? Or is this a bug?
AFAIK there is no way to change this behavior. On the other side, right now, the history of changes is not yet saved. So if you are in middle of an edit and the window would be reused the history (not the current result) of the edit would be lost. I would not like this.
Thank you for your response. The potential loss of edits would not be an issue for my workflow, but for others, it could be. My issue with the current behaviour is the time it takes to spawn a new process. But I can live with the current behaviour as I have been.
However, the fact remains that, at least for Windows 10, the statement in rawpedia:
Using -R also allows you to open an image in an already-running instance of RawTherapee, if that instance was also started using -R .
is incorrect. (And I have verified this by using the command line directly rather than just indirectly via “open with”.)
Just as an aside: @bobm I think the reason this issue has gotten little to zero attention, is that for most (?) users opening files from Windows Explorer is not the common workflow. RawTherapee has an internal thumbnail browser that can / should be used for this purpose. It allows you to open multiple images in multiple tabs, just as you want.
So despite the unexpected behavior, the question could also be: why do you want to open from Explorer, instead of browsing from RT?
I second @Thanatomanic view about opening files in windows explorer. You can also open a folder by right clicking, That is more handy if you want to process a series of photo from that folder.
could you test if the -R option works if you add gdbus.exe in the rawtherapee folder (alongside rawtherapee.exe) gdbus.zip (20.2 KB)
Actually, I don’t want to open a file from windows explorer; that is just the easiest of confirming what is going on. What I really want to do is open a file in RawTherapee from Photo Mechanic
I use Photo Mechanic as my file browser and metadata editor. My commitment to Photo Mechanic is perhaps even stronger with the current beta release of Photo Mechanic Plus with all of its powerful database features.
Anyway, after developing my raw files with RawTherapee, I browse the resultant jpegs with Photo Mechanic. If I wish to make a small adjustment, I want to be able to call RawTherapee from within Photo Mechanic. I need a full fledged instance of RawTherapee so that I can export a jpeg directly and I wish to avoid the delay inherent in opening a separate instance of RawTherapee each time I call it.
My issue is somewhat similar to the recent discussion about Opening RT from IMatch. It was this discussion that triggered me to revisit this issue after it lay dormant for almost a year.
OK, so I added gdbus.exe alongside rawtherapee.exe and then the -R flag seems to work as described in rawpedia. That is, I can edit multiple files sequentially using “open with” in Windows explorer or called from within Photo Mechanic without generating multiple instances of RawTherapee.
So, I’m happy. Thank you. But should I still open an issue in github as suggested by @ChasingShadows?
Thank you for testing
If you don’t mind I will open the issue to warn the windows builders to add this exe in windows builds.
Alongside I will correct the windows build page in rawpedia.
I’ve been curious about this behavior in Linux, and in Linux Mint 19.3 (Ubuntu 18.04) opening a raw file from the file manager (not the RT file browser) opens a “no-File-Browser” window, and opening another image without closing RT first, launches another instance of RT.
Is there any linux «gdbus.exe» alternative, so we can do the same as @bobm?
I have already installed dbus 1.12.2. Is it a problem of not up to date packages? If so, there will be a new Linux Mint version next month, and I’m not even using this feature (it was just curiosity), so I think I can wait.
Is this gdbus something I should have as well ?
If I am understanding, it resides within the RawTherapee installation and fixes a “bug”
Is install as simple as navigating to the folder containing RawTherapee.exe and copying it there ?
Please pardon my ignorance about all this.
Thanks for reading and all help is appreciated.
Well, most probably it will be a matter of the dbus version: Linux Mint 19.3 is based on Ubuntu 18.04, and perhaps 2 years is a bit too much for certain package dependencies.
And as Linux Mint 20 seems to be around the corner, it’s just a matter of waiting a bit and see what happens…
Well I’ll open from Windows Experorer more often than not. Or I’ll sometimes open a selected raw (nef) file from another program. I suspect that always using RT’s internal browser is the workflow of the 'leet “expert” users, while us duffers will often open files from Windows Explorer or some other program instead.
As to why I want to open from Explorer, it’s because I’ve already identified the file I want to edit in Explorer (or whatever other program) and don’t want to waste time hunting it up again in the RT thumbnail browser.
