The main Spektrafilm thread is becoming a bit messy. Let’s talk about installation issues in this thread instead.
Spicy take perhaps, but IMO pip is a mess, or at least it’s easy to end up with a mess. Try managing your installation with uv.
The main Spektrafilm thread is becoming a bit messy. Let’s talk about installation issues in this thread instead.
Spicy take perhaps, but IMO pip is a mess, or at least it’s easy to end up with a mess. Try managing your installation with uv.
Thanks for your support, but unfortunately I get similar issues with uv, namely:
× No solution found when resolving dependencies:
╰─▶ Because rawpy==0.26.1 has no wheels with a matching platform tag (e.g., `macosx_15_0_x86_64`) and only the following versions of rawpy are available:
rawpy<=0.26.1
rawpy>0.27.dev0
we can conclude that rawpy>=0.26.1,<0.27.dev0 cannot be used.
And because spektrafilm==0.3.1 depends on rawpy>=0.26.1,<0.27.dev0, we can conclude that spektrafilm==0.3.1 cannot be used.
And because only spektrafilm==0.3.1 is available and you require spektrafilm, we can conclude that your requirements are unsatisfiable.
hint: Wheels are available for `rawpy` (v0.26.1) on the following platforms: `manylinux_2_27_aarch64`, `manylinux_2_27_x86_64`, `manylinux_2_28_aarch64`,
`manylinux_2_28_x86_64`, `macosx_11_0_arm64`, `win_amd64`
I’m on MacOS x86_64 …
Has this dependency been introduced recently? Asking because I have agx-emulsion up and running just fine.
Could be that older Intel Macs sometimes don’t get new wheels, especially for packages with compiled extensions. rawpy==0.26.1 only has wheels for macosx_11_0_arm64.
So, I interpret this message as: It’s time to install Linux on your Mac.
Someone correct me if I’m wrong.
EDIT: And, yes. I believe rawpy came with the Spektrafilm release (as it brought support for raw files).
I tried to install from a local clone of spektrafilm now, changing the version requirement from 0.26.1 to 0.27.0 in pyproject.toml, and installed rawpy 0.27.0 separately. (Hoping the version bump would still work with spektrafilm).
Now the install continues, but breaks later at llvmlite (required by numba required by spektrafilm) - sigh …
Linux is not an option (actually I even have it in a separate partition) because I still use Photoshop and other commercial SW.
Dang. Resistance may be futile…
Then I’d install Linux in UTM.
Thanks for the hint, I will try UTM when I have more time. I have successfully built and run darktable, ART, Filmulator, vkdt, … on MacOS, so for the moment UTM/Linux seems overkill just to be able to directly run spektrafilm.
I will stick to the implementation within vkdt, even though it does not yet contain the latest and greatest film simulations like fuji velvia.
Thanks for your help anyway!
Update: using conda instead of plain python pip, the installation worked. I had to separately install numba and llvmlite, though - but contrary to the official documentation at llvmlite - anaconda | Anaconda.org it did provide a package with version 0.47 for macos-64. Maybe I just misunderstand their site …
Thanks again!
I’m on Open Suse TW. I had to manually set the ‘include-system-site-packages’
from false to true to make it work. Found in ~/.local/share/uv/tools/spektrafilm/pyvenev.cfg.
Otherwise I got :‘QTBindings are not found’.
I installed with uv. Is it uv, the program, my OS, or me? Where’s the fault?
I thought, the idea of installing via venv is that it is selfcontained?
Now I’m dependend on my OS’es qtbindings, but as long, as it works, I’m fine with that.