I've checked my notes and checked the actual binaries.
Attachments
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Camera raw updates for Leopard?
- Thread starter fluidhd
- Start date
- Sort by reaction score
oj that is a lot of good resources and cool to see you are using a G4 in 2023. I have a 1.5Ghz and it crawls with conversion etc.
I have typed "sudo port install libopenraw-legacy" into the terminal and hit "y" when it asks to proceed. I can report back exactly what I get after it's done in, I'm sure, 24+ hours.
I tried this version first but it crashes without opening.
I have typed "sudo port install libopenraw-legacy" into the terminal and hit "y" when it asks to proceed. I can report back exactly what I get after it's done in, I'm sure, 24+ hours.
I tried this version first but it crashes without opening.
I have fixed gimp2 build for ppc (so far confirmed on 10.6).
Not yet merged, but available here: https://github.com/macports/macports-ports/pull/19103
With this, ufraw https://ports.macports.org/port/ufraw should also build (gimp2 was the only stopper, apparently)
Not yet merged, but available here: https://github.com/macports/macports-ports/pull/19103
With this, ufraw https://ports.macports.org/port/ufraw should also build (gimp2 was the only stopper, apparently)
I am only using it to test stuff on a "real" PPC machine. Running RPP on PB G4 is pure masochism. I use fastest Intel that I have for that.
Re. 9.6.47 - I only checked the main binary with MachOView. It's quite possible that some of the libs or frameworks have higher system requirements. And, btw, it is Intel only.
@barracuda156
I cleaned MacPorts "clean-all" and did "self update" then did the command as I said "port install libopenraw-legacy" and got this fail message:
"failed to build clang-3.7: command execution failed"
Is there a way to submit the whole log so that the community in general has access?
@ojfd do you mind sharing your version of RPP somewhere to ensure that PPC users have access?
I cleaned MacPorts "clean-all" and did "self update" then did the command as I said "port install libopenraw-legacy" and got this fail message:
"failed to build clang-3.7: command execution failed"
Is there a way to submit the whole log so that the community in general has access?
@ojfd do you mind sharing your version of RPP somewhere to ensure that PPC users have access?
Last edited:
If the author of the RPP wanted the PPC users to have access, he would have provided a PPC version on his server
I can provide you with a copy, if you really need it, but I would also ask you to refrain from uploading it on any public server without obtaining the written permission from the author first. He is still around.
---------------
[rant mode on]
Two words that I hate most these days are "sharing" and "community". For me it is nothing but a modern day packaging for "warez" and "we don't give a rat's potatoe about other people's intellectual property". Also, when I read or hear "community" on today's media, all I can associate the word with is "commune", "kolkhoz" and "communists". And I can't do anything about it. 😅
[/rant mode off]
Sorry for the vent. It is not addressed at you personally, btw.
Last edited:
Well if you can DM I’d like a chance to get a copy.
I agree creators should be paid for their effort. I paid for both VueScan and RPP. I also despise the modern expectation that every piece of software or service should be free. Free trials are definitely a good thing. Without a trial I would not have purchased either software. The demand for “cheap” and “free” has definitely gouged the quality of almost every product and service. On the other hand, there is the gross exploitation of subscriptions like Creative Cloud by Adobe which is why I just said F Adobe and went to Aperture and Leopard. If it was good enough for professionals in 2008, it’s good enough for me.
Thanks to this moochy frenzy, it’s sometimes impossible if not nearly impossibly to get anything of quality today. I don’t mean that it’s hard to discern from crap, I mean it’s all crap. If you want to get a sewing machine, record player, or almost any kinds of tools, you’re better off finding an antique. Modern offerings are dirt-cheep Chinese chaff that satisfies your impulse RIGHT NOW but don’t complain when it disintegrates in a week. I bought some tools from trusted brands online and they have snapped and revealed their composition to be of the same crushed powder as Apple’s VESA mount screws. They weren’t cheap. I’ve ended up buying a 1980’s industrial sewing machine that obviously will last generations. I have a 1980’s Record player that is among the best and, gasp, it is serviceable. I have resorted to purchasing all of my tools directly from Japan and they are supremely superb. The new Japanese tools come with quite a premium but that’s the cost of peace of mind. The other stuff is just like all the other “antiques” I buy. They’re not “new and hip” so most people generally just pass them on. It’s a blessing to have access to old stuff until the hipsters discover it. I’ve seen my car, my TV, my motorcycles etc. become trendy and the prices climb like a fever. Look up the going price for a 34” Sony WEGA HD CRT today. Easily $300 in most cases. An old man let me have his for $20 on the condition I remove it for him. I paid good money for a Nikon Super Coolscan film scanner. It’s more than 20-years old but it is sort of the de-facto standard for enthusiasts. You’d be hard pressed to find an equal-quality scanner for less than the cost of a used Coolscan now. I looked.
That said, RPP is free to use and I’m sure it wouldn’t take much to get the author’s blessing. He’s very responsive but I bet he would explicitly mention that he offers no support for such old versions. Oh, and any purchased key should work with any version, so NO version has been abandoned and should be purchased to unlock.
I agree creators should be paid for their effort. I paid for both VueScan and RPP. I also despise the modern expectation that every piece of software or service should be free. Free trials are definitely a good thing. Without a trial I would not have purchased either software. The demand for “cheap” and “free” has definitely gouged the quality of almost every product and service. On the other hand, there is the gross exploitation of subscriptions like Creative Cloud by Adobe which is why I just said F Adobe and went to Aperture and Leopard. If it was good enough for professionals in 2008, it’s good enough for me.
Thanks to this moochy frenzy, it’s sometimes impossible if not nearly impossibly to get anything of quality today. I don’t mean that it’s hard to discern from crap, I mean it’s all crap. If you want to get a sewing machine, record player, or almost any kinds of tools, you’re better off finding an antique. Modern offerings are dirt-cheep Chinese chaff that satisfies your impulse RIGHT NOW but don’t complain when it disintegrates in a week. I bought some tools from trusted brands online and they have snapped and revealed their composition to be of the same crushed powder as Apple’s VESA mount screws. They weren’t cheap. I’ve ended up buying a 1980’s industrial sewing machine that obviously will last generations. I have a 1980’s Record player that is among the best and, gasp, it is serviceable. I have resorted to purchasing all of my tools directly from Japan and they are supremely superb. The new Japanese tools come with quite a premium but that’s the cost of peace of mind. The other stuff is just like all the other “antiques” I buy. They’re not “new and hip” so most people generally just pass them on. It’s a blessing to have access to old stuff until the hipsters discover it. I’ve seen my car, my TV, my motorcycles etc. become trendy and the prices climb like a fever. Look up the going price for a 34” Sony WEGA HD CRT today. Easily $300 in most cases. An old man let me have his for $20 on the condition I remove it for him. I paid good money for a Nikon Super Coolscan film scanner. It’s more than 20-years old but it is sort of the de-facto standard for enthusiasts. You’d be hard pressed to find an equal-quality scanner for less than the cost of a used Coolscan now. I looked.
That said, RPP is free to use and I’m sure it wouldn’t take much to get the author’s blessing. He’s very responsive but I bet he would explicitly mention that he offers no support for such old versions. Oh, and any purchased key should work with any version, so NO version has been abandoned and should be purchased to unlock.
Yes, please. clang should not come into picture at all on PowerPC (and for sure on supported officially 10.5).
(You do have the latest ports, right? Just in case.)
In fact, if you do the following first, it will help me fix the problem:
1. sudo port sync
2. port rdeps libopenraw-legacy
Post the output of rdeps here.
This is what I get on Rosetta, for example:
Code:
macmini:~ svacchanda$ port rdeps libopenraw-legacy
The following ports are dependencies of libopenraw-legacy @0.3.4_0+gnome:
xz
lbzip2
gettext
libiconv
gperf
libtextstyle
ncurses
gettext-runtime
gettext-tools-libs
pkgconfig
autoconf-archive
cctools
libunwind-headers
llvm-3.4
python27
bzip2
db48
expat
libedit
libffi
expect
automake
autoconf
m4
tcl
dejagnu
sqlite3
zlib
openssl11
python_select
python2_select
perl5
perl5.34
gdbm
readline
llvm_select
grep
pcre2
gsed
texinfo
help2man
p5.34-locale-gettext
gawk
legacy-support
libtool
gcc12
gmp
isl
ld64
ld64-97
libmacho-headers
libmpc
mpfr
zstd
lz4
gcc10-bootstrap
libgcc
libgcc12
gcc_select
libxml2
icu
curl
brotli
cmake-bootstrap
libidn2
libunistring
libpsl
python310
openssl
openssl3
python3_select
curl-ca-bundle
unzip
libjpeg-turbo
cmake
libarchive
lzo2
libb2
libuv
glib2
meson
py311-build
py-bootstrap-modules
py311-installer
python311
py311-packaging
py311-pretend
py311-setuptools
py311-wheel
py311-flit_core
py311-pytest
py311-setuptools_scm
py311-typing_extensions
py311-attrs
py311-hatchling
py311-editables
py311-pathspec
py311-pluggy
py311-py
py311-trove-classifiers
py311-calver
hatchling_select
py311-hatch-fancy-pypi-readme
py311-hatch-vcs
py311-hypothesis
py311-sortedcontainers
py311-zopeinterface
py311-coverage
py311-zope-event
py311-iniconfig
pytest_select
py311-pyproject_hooks
py311-testpath
ninja
re2c
bison
bison-runtime
gdk-pixbuf2
gi-docgen
py311-jinja2
py311-markupsafe
py311-markdown
py311-pygments
pygments_select
py311-toml
py311-typogrify
py311-smartypants
gtk-doc
docbook-xml
xmlcatmgr
docbook-xml-4.1.2
docbook-xml-4.2
docbook-xml-4.3
docbook-xml-4.4
docbook-xml-4.5
docbook-xml-5.0
docbook-xsl-nons
itstool
py311-libxml2
libxslt
py311-anytree
py311-six
py311-nose
nosetests_select
py311-lxml
py311-mock
py311-docutils
docutils_select
py311-roman
gobject-introspection
py311-cython
cython_select
cairo
libpixman
fontconfig
freetype
libpng
ossp-uuid
xrender
xorg-libX11
xorg-xtrans
xorg-xorgproto
xorg-util-macros
xorg-libXdmcp
xorg-libXau
xorg-libxcb
xorg-xcb-proto
xorg-libpthread-stubs
xorg-libXext
xorg-xcb-util
py311-mako
shared-mime-info
xmlto
util-linux
fop
libpaper
w3m
boehmgc
libatomic_ops
tiff
lerc
boost176
lzma
p7zipOn default 10.5 there will be no gcc10-bootstrap dependency and gcc7 will be in place of gcc12. There should be no clang anywhere. If there is, it must be fixed in Macports.
Exactly as you said, I did "sync" and this is what the dep list looks like:
Importantly, be aware that I am running 10.5 on Intel. The OP started the thread because he was using a G5. Sadly, that is no longer working and OP has disappeared. I'm still determined to contribute something to this generally so I hope whatever I find does indeed work on PPC but I am on a Mac Pro.
Code:
The following ports are dependencies of libopenraw-legacy @0.3.4_0+gnome:
xz
gettext
libiconv
gperf
libtextstyle
ncurses
gettext-runtime
gettext-tools-libs
pkgconfig
autoconf-archive
cctools
libunwind-headers
grep
pcre2
clang-7.0
cmake-bootstrap
clang-3.7
clang-3.4
llvm-3.4
python27
bzip2
db48
expat
libedit
libffi
expect
automake
autoconf
m4
tcl
dejagnu
sqlite3
zlib
openssl11
perl5
perl5.34
gdbm
readline
python_select
python2_select
llvm_select
clang_select
ld64
ld64-127
libmacho-headers
llvm-3.3
llvm-3.7
libcxx
xz-bootstrap
clang-11-bootstrap
python27-bootstrap
gcc10-bootstrap
libstdcxx_clang_fix
libomp
cmake
curl
brotli
libidn2
libunistring
libtool
libpsl
python310
openssl
openssl3
python3_select
zstd
lz4
curl-ca-bundle
unzip
libarchive
libxml2
icu
gcc7
gmp
isl
libmpc
mpfr
gcc_select
libgcc
libgcc7
lzo2
libb2
libuv
legacy-support
llvm-7.0
xar
gsed
texinfo
help2man
p5.34-locale-gettext
gawk
libjpeg-turbo
nasm
glib2
meson
py311-build
py-bootstrap-modules
py311-installer
python311
py311-packaging
py311-pretend
py311-setuptools
py311-wheel
py311-flit_core
py311-pytest
py311-setuptools_scm
py311-typing_extensions
py311-attrs
py311-hatchling
py311-editables
py311-pathspec
py311-pluggy
py311-py
py311-trove-classifiers
py311-calver
hatchling_select
py311-hatch-fancy-pypi-readme
py311-hatch-vcs
py311-hypothesis
py311-sortedcontainers
py311-zopeinterface
py311-coverage
py311-zope-event
py311-iniconfig
pytest_select
py311-pyproject_hooks
py311-testpath
ninja
re2c
bison
bison-runtime
gdk-pixbuf2
gi-docgen
py311-jinja2
py311-markupsafe
py311-markdown
py311-pygments
pygments_select
py311-toml
py311-typogrify
py311-smartypants
gtk-doc
docbook-xml
xmlcatmgr
docbook-xml-4.1.2
docbook-xml-4.2
docbook-xml-4.3
docbook-xml-4.4
docbook-xml-4.5
docbook-xml-5.0
docbook-xsl-nons
itstool
py311-libxml2
libxslt
py311-anytree
py311-six
py311-nose
nosetests_select
py311-lxml
py311-mock
py311-docutils
docutils_select
py311-roman
gobject-introspection
py311-cython
cython_select
cairo
libpixman
fontconfig
freetype
libpng
ossp-uuid
xrender
xorg-libX11
xorg-xtrans
xorg-xorgproto
xorg-util-macros
xorg-libXdmcp
xorg-libXau
xorg-libxcb
xorg-xcb-proto
xorg-libpthread-stubs
xorg-libXext
xorg-xcb-util
py311-mako
shared-mime-info
xmlto
util-linux
fop
libpaper
w3m
boehmgc
libatomic_ops
tiff
lerc
boost171
lzma
p7zipImportantly, be aware that I am running 10.5 on Intel. The OP started the thread because he was using a G5. Sadly, that is no longer working and OP has disappeared. I'm still determined to contribute something to this generally so I hope whatever I find does indeed work on PPC but I am on a Mac Pro.
Thank you for clarification. Please report the issue on Trac: https://trac.macports.org/newticket
(I cannot handle Intel issues personally.)
AFAIK, on Intel clang-3.7 should build fine. You do not try to build for ppc on Intel, do you? That is possible, but needs manual settings.
On 10.6.8 clang-3.7 certainly builds and works (both i386 and x86_64):
Code:
10:~ svacchanda$ sw_vers
ProductName: Mac OS X Server
ProductVersion: 10.6.8
BuildVersion: 10K549
10:~ svacchanda$ port -v installed | grep clang
clang-3.4 @3.4.2_17+arm_runtime+universal (active) requested_variants='+universal' platform='darwin 10' archs='i386 x86_64' date='2022-11-06T03:24:11+0800'
clang-3.7 @3.7.1_9+universal (active) requested_variants='+universal' platform='darwin 10' archs='i386 x86_64' date='2022-11-06T03:33:19+0800'
clang-9.0 @9.0.1_7+defaultlibcxx+emulated_tls+universal (active) requested_variants='+universal' platform='darwin 10' archs='i386 x86_64' date='2023-04-12T23:48:51+0800'
clang-11 @11.1.0_7+defaultlibcxx+emulated_tls+universal (active) requested_variants='+universal' platform='darwin 10' archs='i386 x86_64' date='2023-04-13T06:04:41+0800'
clang-11-bootstrap @11.1.0_4+emulated_tls+universal (active) requested_variants='' platform='darwin 10' archs='i386 x86_64' date='2023-04-13T06:33:38+0800'P. S. BTW, all Intel systems have pre-built ports (EDIT: not too sure about 10.5 though), so you should not need to build anything, more or less. Provided you install in default prefix /opt/local and do not build as +universal (and obviously not using Rosetta to build for ppc).
P. P. S. Please report the issue as a clang-3.7 issue on whatever system you use (this is not libopenraw-legacy issue).
To get a clean log with error, do:
Code:
sudo port clean clang-3.7
sudo port -v install clang-3.7
Last edited:
Still at it with a new question.
How can I extract a camera profile from libraw or libopenraw?
As I understand, all RAW converters have built in camera profiles so that the color comes out vibrant and appear mostly accurate. Even Apple’s built-in RAW support does a good job of replicating the actual colors of the image.
Seemingly, libraw or libopenraw include profiles for certain cameras that do just this. Yes?
Finally, VueScan for Mac has limited RAW conversion or “developing” capability. When I open a RAW image in VueScan, it looks very good and just how I expect.
So far as I know, VueScan uses either libraw or libopenraw for this function. VueScan opening camera RAW files isn’t officially supported but it’s included incidentally.
Given that VueScan gives great image quality, then either Libraw or Libopenraw have a decent camera profile built in, right?
So if I could extract that profile, perhaps I could apply it to other RAW converters that are supported on Mac?
How can I extract a camera profile from libraw or libopenraw?
As I understand, all RAW converters have built in camera profiles so that the color comes out vibrant and appear mostly accurate. Even Apple’s built-in RAW support does a good job of replicating the actual colors of the image.
Seemingly, libraw or libopenraw include profiles for certain cameras that do just this. Yes?
Finally, VueScan for Mac has limited RAW conversion or “developing” capability. When I open a RAW image in VueScan, it looks very good and just how I expect.
So far as I know, VueScan uses either libraw or libopenraw for this function. VueScan opening camera RAW files isn’t officially supported but it’s included incidentally.
Given that VueScan gives great image quality, then either Libraw or Libopenraw have a decent camera profile built in, right?
So if I could extract that profile, perhaps I could apply it to other RAW converters that are supported on Mac?
As far as I know, a color profile can only be used with color data. But a RAW file is not yet colorized.
This is a very brief (and very old) document about how RAW converters create colors from RAW data. Not sure if it's useful or not for you.
Thank you this is a good resource.
So the “demosaicing” is what the RAW converter does to a RAW file. It interprets the file using whatever algorithm is built into the converter.
Am I assuming correctly that:
A converter has support (decoding look up tables) for individual cameras, but the decoded image is “colorized” using a blanket profile that the converter itself applies to ANY image from ANY camera. It does not use individual color profiles per camera.
So the “demosaicing” is what the RAW converter does to a RAW file. It interprets the file using whatever algorithm is built into the converter.
Am I assuming correctly that:
A converter has support (decoding look up tables) for individual cameras, but the decoded image is “colorized” using a blanket profile that the converter itself applies to ANY image from ANY camera. It does not use individual color profiles per camera.
In my understanding, the data is first colorized into a CIE color space. Once it is in CIE, it can be converted into any RGB space. The color you see on the monitor while you're editing a RAW image is the result of CIE to your (RGB) monitor profile conversion. After you're done editing it, if you choose to output it to, say, sRGB, those CIE colors will be converted to sRGB.
Color conversion matrices in digital cameras: a tutorial
Color conversion matrices and chromatic adaptation transforms (CATs) are of central importance when converting a scene captured by a digital camera in the camera raw space into a color image suitable for display using an output-referred color space. In this article, the nature of a typical...
Ok I see so the RAW’s don’t normally correspond to any given color space or profile.
So back to trying to get the support on old Macs. It may be that Libopenraw is the best bet for Leopard except that it’s: 1. An awful pain to install 2. Isn’t currently working in Leopard
I’m really curious where RPP keeps its camera compatibility library, or whatever, and if it can be “expanded” by dropping in more recent support files.
So back to trying to get the support on old Macs. It may be that Libopenraw is the best bet for Leopard except that it’s: 1. An awful pain to install 2. Isn’t currently working in Leopard
I’m really curious where RPP keeps its camera compatibility library, or whatever, and if it can be “expanded” by dropping in more recent support files.
It is compiled into the main binary. There are no parts to swap. Even if there were, they would be Intel or ARM or both architectures. No PPC.
But why are you so concerned about the camera compatibility? Are you using the 'latest and greatest' cameras, but still sticking to old computers? Just curious..
I’m not. I’m just curious to see how we can stretch the usefulness of old machines. I have a Quadra 610 and Trinitron I regularly use for Photoshop and drafting and it’s fun and relaxing to use old simple stuff.
I believe the OP was wanting to use his PowerMac for converting RAW’s for editing without the need for any newer machine.
It’s just a hobby. I resort to my 2019 iMac and M1 Max machines for the real work.
It is rewarding to scan film in Leopard and develop it and prepare to print all within the old OS.
I believe the OP was wanting to use his PowerMac for converting RAW’s for editing without the need for any newer machine.
It’s just a hobby. I resort to my 2019 iMac and M1 Max machines for the real work.
It is rewarding to scan film in Leopard and develop it and prepare to print all within the old OS.
It will be helpful to know what exactly does not work. (I am not claiming it is working, but it should work; if you tell us what does not, maybe we can fix it for you – and for everyone else.)
P. S. It is practically unfeasible to test functionality of every random app, so it is not that “no one cares”, it is just always a trade-off – spending more time on one thing means less time left for fixing something else. So it is actually important to let developers and maintainers know what works and what does not.
It really boils down to: if you want to use an app, try using it and report whatever is broken. This is the only way to have functionality maintained.
RawTherapee should be buildable by the way for PowerPC. The source code forces some silly defaults, but those are trivially removable.
Did not take long, I have it built and somewhat working. (Yeah, I know.)
Specifically, GUI segfaults, but command-line converter works. At least I threw a random PEF at it and got a neat jpeg.
Even at this level it will solve a problem with modern cameras. Assuming you got something else to do the rest of editing.
But let’s see if we can fix the GUI. (It actually segfaults on Sonoma as well, so either a general bug or I messed up some settings or patches.)
Command-line for visual material? Kinda defeats the purpose
But please, keep us posted.
I always wanted to try it on Snow Leopard, but all builds were half way broken.
What did they use for GUI, btw? Qt, wxwidgets or something else?
Command-line for visual material? Kinda defeats the purpose
But please, keep us posted.
I always wanted to try it on Snow Leopard, but all builds were half way broken.
What did they use for GUI, btw? Qt, wxwidgets or something else?
Well, the topic was about Camera Raw updates or functional substitutes, AFAIU, not about a full-blown replacement of Photoshop. To convert RAW files from the camera into TIFF or what’s not, GUI is not necessary. Yes, if you do DTP, converter on its own is insufficient, but Photoshop CS4 still works.
The source code uses GTK3 for GUI, so that is what I am trying to use. GTK3 on its own works. The problem is either with the RT code or with something I do on my end. (Since I have no desire to try building GTK3 +quartz instead of +x11, I need to tweak the code to allow a normal Unix-like build.)
wxWidgets are a nightmare btw, but thankfully unneeded here.
Yeah, right. How do you determine the correct white balance, contrast, saturation, over or under exposure and so on without seeing the preview first?