See the readme for installing Pd.

unzip GEM so that it is at

pd\gem

If you run GEM.INSTALL.bat, then all of the example files and documentation should be put in the correct locations.
(Note that you eventually have to edit GEM.INSTALL.bat to match your local directory layout.)

There is also an installer for windows.

For Windows 8 and 10 there is a missing dll that is needed for GEM to run. If your system doesn't have msvcr71.dll already then find it on the Web and install it in the pd\bin folder.

You probably don't have hardware acceleration.

You can use software rendering, but it basically useless except for extremely basic patches.

You can get a good graphics accelerator for really cheap these days. I recommend a card based on nVidia's chipsets, such as the TNT2 or GeForce, but there are other companies such as 3dfx and Matrox.

Make sure that you are running the latest drivers for your card. The basic drivers that come with the cards are usually very bad.

Also, PCs don't deal with lots of texture maps very well (they are bus limited, at least until AGP), so if you are trying to use lots of constantly changing texture maps (especially with [pix_multiimage], [pix_video] or [pix_film]), that will cause problems.

Set the environment variable GEM_NO_TABLET = 1

I haven't completely figured out how to get access to the video stream in WinNT.

I'm using Video for Windows with a Connectix QuickCam, as well as an Intel Video Capture Card, and it seems to assume that you are only writing to a file or previewing into a window.

Windows tries to take over the system and doesn't really provide any stable hooks (unlike IRIX). If anyone knows how to deal with this, please let me know.

Download the Gem-installer and run it.

You should install it into the "extra/Gem" directory of your local Pd-installation.

By default this is: %PROGRAMFILES%\Pd\extra\Gem, which should be fine if you have accepted the defaults when installing Pd.

That's it.

Building on W32 is a pain.

I happen to have a buildsystem running and try not to touch it, in case it breaks and i cannot create one again...

Visual Studio 2003

setup for building Gem-0.92

• AMD64 laptop running XP (sp3 i think)
• GemLibs: later check which version / incarnation
• compiled using the project for Visual Studio 2003 (see build/win-vs2003)
• installer is compiled using NSIS (build/win-nsis)

autoconf

in theory it should be possible to build Gem using autoconf on W32 using msys/cygwin

problems probably occur, due to the use of DirectShow for grabbing/decoding