Alright, it seems I should have checked that that Github thread more closely.
I managed to get it to load and work properly!
Copy all the dll files from here: C:\Program Files (x86)\ZED SDK\bin
And paste them here: C:\Program Files\Python39\Lib\site-packages\pyzed (for python 3.9)
It loads and work fine with my application so far.
Sorry to hear that you had trouble installing the Python API. There are indeed some issues for Windows users with Python versions greater than 3.8, but versions before that should work fine.
If ever you still have problems, you can also build the API from source. Here is the repository and the instructions to do so : zed-python-api
I’m encouraged to hear that you figured out the issue. I’m still trying to get there. Can you take a look at the screen shot and confirm whether or not your pyzed directory looked similar to mine. Unfortunately I am still getting the Dll load failed error
Hi gpark.
Could you try putting the files in C:\Program Files\Python39\Lib\site-packages\pyzed instead of \AppData\Local\Programs\Python\Python39\Lib\site-packages\pyzed ?
My AppData site-packages does not contain the files.
I am using the same configuration as you. Did you install Python from the Windows store or from an installer?
I did not make any change to my environment variables to make it work.
Python 3.9, cuda11.1, zed sdk 3.5 works perfectly for me. Also try doing this in the virtual environment. In some cases you might have to manually copy all the dlls in the bin folder to the pyzed folder in site-packages.
To make it short, it means that you lacked some “dependencies” for the libraries you wanted to use. This is a common problem when installing python packages, mainly in windows. Before trying to use any kind of library, first it is suggested to look up whether it needs another library in python “family”.
The solution is to provide the python interpreter with the path-to-your-module/library. The simplest solution is to append that python path to your sys.path list. In your notebook, first try:
This isn’t a permanent change in sys.path, because when you log out, your environment is reset, so any variables you may have set are lost.
The better (and more permanent) way to solve this is to set your PYTHONPATH, which provides the interpreter with additional directories look in for python packages/modules.
from BASH type: export PYTHONPATH=/path/to/new/folder:/another/path/...../ #each path must be separated by a colon
I recently purchased a ZED 2i and am experiencing issues. I have tried multiple versions of the ZED SDK along with different Python versions, including within a virtual environment. Additionally, I copied the DLL files from zed-sdk/bin to site-packages/pyzed.
Can someone please help me with a solution? I would greatly appreciate any assistance.