[heckflosse]

that puts 'brand name' RAW converters to shame

That may be a side-effect of our work, but clearly not our intention ;-) The intention is to make pixelshift processing more easy. It's a fascinating technology which unfortunately wasn't handled well in past.That led to statements pixelshift would be usable only for motionless studio shots (without using flash) and so on....
I also want to mention again: I don't own a pixelshift camera. I still use my very old Nikon D700 because I have a lot of good old Nikon lenses which prevent me from switching brand. Without owning all the Nikon lenses I would immediately buy a K-1!

[teiki arii]

I still use my very old Nikon D700 because I have a lot of good old Nikon lenses which prevent me from switching brand. Without owning all the Nikon lenses I would immediately buy a K-1!

I actually understand your dilemma. I'm "lucky", I have Leica-R lenses for which Leitz Company scrapped DSLR camera project until Leica SL. I had to switch to Pentax K-1 mount thanks to Leitax after I switched from Canon DSLR cameras. Canon EOS 5D MKIV and Leica SL are too expensive for what they are and the Pentax K-1 is the best OVF SR DSLR camera for my needs..
Incidentally, is it so difficult to transpose Windows Pixel Shift module to MacOs RT?



out of order, Collioure. MacOs RawTherapee 5.0 Process.
Leica Apo-Extender-1.4x and Leica Elmarit-R 180/2.8 (II) non-Apo to make a non-Apo Combo 250/4. Pentax K-1.

[heckflosse]

Incidentally, is it so difficult to transpose Windows Pixel Shift module to MacOs RT?

I asked for a build which works on macOS versions from 10.8 upwards.

[teiki arii]

Ok, thank you very much, cross fingers..

[heckflosse]

Incidentally, is it so difficult to transpose Windows Pixel Shift module to MacOs RT?

A MacOS RT pixelshift build is available here

[heckflosse]

As a side note: pixelshift version of RT also allows to extract the three individual frames of Pentax 3-in-1 HDR files. Currently it can not combine them (I will take a look at that when pixelshift is mature) but at least you can extract the frames to combine them with other software atm.

[teiki arii]

A MacOS RT pixelshift build is available here

Let me kiss you! 😘
I'll try it tomorrow on MacOs Sierra....

[heckflosse]

Let me kiss you! ��

Nono, it was partha on pixls.us who made the MacOS build. He deserves your credits ;-)

[teiki arii]

RTps 5.0 doesn't work..

[heckflosse]

RTps 5.0 doesn't work..

As partha wrote here `Please let me know if there are issues.` can you please report the Issue there?
As I'm not a Mac user it does not make sense if I tell him that it does not work, because he will ask for more details.

[teiki arii]

Done, thank you! ��

[Homo_erectus]

I love that RT has such an active group of users here.

I've experimented with RT over the years and, while I find it's output to be quite good, one thing or another has always pushed me away from it. Version 5 seems quite nice but on both the Mac and Windows 10 platforms I'm getting various issues, mostly crashes, that make it unusable.

On Windows 10, RT (version RT 5.0-r1-gtk3 for Windows Vista/7/8/10 64-bit - fast) will not save processed files onto the desktop (this bug goes back to version 4 in my experience). It processes the file and then nothing happens. It never actually puts the final jpg on the desktop. The first time I tried to select a different location via the batch processing window, RT crashed. Weirdly, having RT save the files into a folder on the desktop works fine.

On the Mac (I've tested it on two different Macs, one iMac running 10.11.6 and one MacBook Pro running 10.12.3 both using RT version RT 5.0-r1-gtk3 for macOS 10.8/9/10/11/12 64-bit - fast) when I try to point RT to the install location of Photoshop in RTs preferences, the program crashes to desktop. Also, when I try to change the location where processed files are saved, the program crashes.

Given that my experience has been that RT is more or less unusable, I'm fascinated that other people seem to have no problems, or at least, I haven't seen any one complaining about the issues that I keep encountering. So, am I just particularly unlucky? Are other people seeing the same issues and just working around them? What's going on?

[heckflosse]

I love that RT has such an active group of users here.

I've experimented with RT over the years and, while I find it's output to be quite good, one thing or another has always pushed me away from it. Version 5 seems quite nice but on both the Mac and Windows 10 platforms I'm getting various issues, mostly crashes, that make it unusable.

On Windows 10, RT (version RT 5.0-r1-gtk3 for Windows Vista/7/8/10 64-bit - fast) will not save processed files onto the desktop (this bug goes back to version 4 in my experience). It processes the file and then nothing happens. It never actually puts the final jpg on the desktop. The first time I tried to select a different location via the batch processing window, RT crashed. Weirdly, having RT save the files into a folder on the desktop works fine.

On the Mac (I've tested it on two different Macs, one iMac running 10.11.6 and one MacBook Pro running 10.12.3 both using RT version RT 5.0-r1-gtk3 for macOS 10.8/9/10/11/12 64-bit - fast) when I try to point RT to the install location of Photoshop in RTs preferences, the program crashes to desktop. Also, when I try to change the location where processed files are saved, the program crashes.

Given that my experience has been that RT is more or less unusable, I'm fascinated that other people seem to have no problems, or at least, I haven't seen any one complaining about the issues that I keep encountering. So, am I just particularly unlucky? Are other people seeing the same issues and just working around them? What's going on?

The key to get issues with rt fixed is to report them either here or here

[heckflosse]

when I try to point RT to the install location of Photoshop in RTs preferences, the program crashes to desktop. Also, when I try to change the location where processed files are saved, the program crashes.

There's already an Issue for that on github. I guess it will be fixed soon.

[Homo_erectus]

Ok, great. Thanks.