Jump to content

Contributions:Extensions: Difference between revisions

From BCI2000 Wiki
Kgoering (talk | contribs)
No edit summary
Kgoering (talk | contribs)
No edit summary
Line 12: Line 12:
*[[Contributions:AudioExtension]]: An all purpose audio toolkit which allows for realtime multichannel audio I/O.
*[[Contributions:AudioExtension]]: An all purpose audio toolkit which allows for realtime multichannel audio I/O.
*[[Contributions:StimBoxFilter]]: A logger and controller for the gtec g.STIMbox.
*[[Contributions:StimBoxFilter]]: A logger and controller for the gtec g.STIMbox.
*[[Contributions:ParallelPortFilter]]: A logger and controller for communication through parallel ports.


==See also==
==See also==

Revision as of 17:22, 30 June 2015

A framework Extension is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific input-device loggers are provided in the src/contrib/Extensions folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices. Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler: see the Programming Howto:Quickstart Guide for a walkthrough that shows you how to recompile BCI2000 modules.

The following user extensions are available in the Contributions section of BCI2000:

See also

Programming Reference:EnvironmentExtension Class

Programming Tutorial:Implementing an Input Logger