Display

Native Display

Your native display normally accessed via HDMI

By default opendsp boots with this display on. But you can tweek the config to turn it off by default if you dont need it - it helps to avoid cpu consumption waste.

Virtual Display

This is a network accessible display, used as a way to free up the Native display in case will needed it for projections or presentations.

If you need help to find your OpenDSP on the network please check Network page.

You can also access the GUI interface from different devices, you mobile phone, a tablet, smart tv, laptop or a PC.

The access is made via VNC protocol, you can download any client compatible with that protocol to start work with virtual display.

By default opendsp boots with this virtual display on. But you can tweek the config to turn it off by default if you dont need it - it helps to avoid cpu consumption waste.

Web Virtual Display

In case you dont have a VNC client, or dont what to download and install to use it, you can access via web using noVNC integrated into OpenDSP by default. Just open you web browser and follow the your OpenDSP ip address or network name:

http://opendsp

Raspberry PI2/PI3 Video Drivers

3 video drivers to pickup for your raspberry GPU:

Legacy
Fake Kms
Full Kms

By default opendsp boots with legacy driver for more compatibility, but you are free to change it for your own needs.

Drivers Review

Processing: Legacy you got nice and smooth speed for almost all P2D and P3D, for Texture/Shaders you need the Full Kms driver to support(but makes other P2D/P3D slower). It runs crappy on Fake Kms.

Puredata GEM: not tested yet...

Lebiniou: You get real smooth textures and nice FPS from it by running with OpenGL output module with Fake Kms driver. It buggys on Full Kms driver and you get no accelleration at all by using legacy driver.

Omxplayer: Runs perfect!(better than my laptop by the way) on Legacy and Fake Kms drivers. Gives no image on Full Kms driver