[Bf-committers] pixel get & image processing

Domino Marama domino at dominodesigns.info
Tue Mar 15 10:47:17 CET 2011

On Thu, 2011-01-27 at 04:33 +0000, Campbell Barton wrote:
> But, I get the impression python devs work on specific projects where
> image access is useful (research & custom scripts)  so I wrote a
> ctypes (pure python) direct memory access to pixel data for people who
> like to experiment with this.
> Download:
> http://www.graphicall.org/ftp/ideasman42/image_buffer_raw_access.py

All was going well with this until I started passing out scripts for my
users to test. Windows users seem to have a problem

found bundled python: C:\BLENDE~1\install\win32-vc\2.56\python
Traceback (most recent call last):
"C:\BLENDE~1\install\win32-vc\2.56\scripts\modules\bpy\utils.py",  line 
51, in _test_import  mod = __import__(module_name)
   File "C:\BlenderSVN\primstar\image_buffer_raw_access.py", line 339, 
in <module> main, _struct_dict = _api()
   File "C:\BlenderSVN\primstar\image_buffer_raw_access.py", line 75,  
in _api blend_cdll = ctypes.CDLL("")
"C:\BLENDE~1\install\win32-vc\2.56\python\lib\ctypes\__init__.py", line 
340,  in __init__ self._handle = _dlopen(self._name, mode)
WindowsError: [Error 126] module not found

It's been tested on an official build, a self compile and a build from
graphical, all have this problem which I'm guessing is a missing

Has anyone successfully tried this on Windows or know a way to fix it?


More information about the Bf-committers mailing list