Spike2 Scripts


Export covers converting data to a different format; for merging or otherwise altering data files, see the Editing section.


Print instantaneous frequency values to the Log (07/10)

Print instantaneous frequency values to the Log


This script calculates the instantaneous frequency values from a nominated event, marker or WaveMark channel and writes them to the Log window. You can also display all of these data types as an instantaneous frequency plot using the Channel Draw Mode functions.

This script requires Spike2 v4.24 or higher.

Export raster data as text (04/10)

Export raster data as text


This script exports raster data from result files into a new text document. When the script is run, the user is prompted to open a result file that includes a raster type channel and select the raster channel to export.

This script requires Spike2 v4.24 or higher.

Save result files as images (04/10)

Save result files as images


This script is an example of exporting multiple result files in either bitmap or metafile format. The user selects a directory containing result files and the script then exports them one by one. You can set the window size of the first result file to be exported and this is then used to set the size of the image for all subsequent files. The image files are saved in the same directory and with the same file names as the result files.

This script requires Spike2 v5.21 or higher.

Export as text based on a trigger channel (04/10)

Export as text based on a trigger channel


This script will export data in sections of spreadsheet-format text based on a nominated trigger channel, with each section separated by new column headers. All visible channels are exported based on user defined settings such as output sample rate and section length.

This script requires Spike2 v5.21 or higher.

Convert Spike2 data files to WAV format (06/09)

Convert Spike2 data files to WAV format


This script converts waveforms in a data file to 8 bit or 16 bit WAV format. Waveform channels may then be played with many standard tools.

Process event channels to a text file (12/10)

Process event channels to a text file


This script dumps event channels as text from a Spike2 data file. The script will dump the data as mean frequency, instantaneous frequency, rate, event intervals, or as event times.

Some of these scripts have come from users rather than the CED team. If you have a script that you would like to offer to fellow users via this page, please tell Simon Gray. We provide some scripts for Signal too.

These scripts are stored as WinZip files, myscript.zip, except where they are shown as spike\scripts\myscript.s2s. Those latter files were installed with Spike2 and spike stands for the directory in which you installed Spike2. See the summaries by clicking on the description in the side menu. Then you can down-load them by clicking on the filename.


Mains ‘hum’ is often complex and composed of odd harmonics of the mains frequency, making it very difficult to remove or suppress using simple high pass or notch filters. HumRemoveExpress.s2s is a Spike2 version 7 script that you can use offline to strip out much of this residual mains interference, making your data much more presentable and easier to analyse. This video tutorial shows how to use the script to remove mains hum.

  • Alpha MED Sciences
  • Alpha Omega Engineering
  • Axon Instruments
  • Binary data
  • Bionic/Cyberkinetics
  • Biopac
  • CED SON (Macintosh)
  • CONSAM (D. Colquhuon)
  • DATAQ Instruments (Codas)
  • DataWave
  • Data Sciences International
  • Delsys Files
  • European Data Format(+)
  • Grass-Telefactor (PolyView)
  • HLR Data Format
  • Heka Data Format
  • Multi Channel System (Mc_Rack)
  • MindSet (16/24) data Files
  • MindWare data files
  • Motion Labs Systems Files .c3d
  • NeuroScan
  • Neuralynx
  • Plexon
  • RC Electronics
  • Text files
  • TMS International
  • Tucker-Davis Technologies
  • WAV (Microsoft)
  • WaveMetrics Igor Pro (PC/Mac)
  • Xltek Neuroworks
Cambridge Electronic Design Limited

Registered in England: 972132

Registered office:

  • Cambridge Electronic Design Limited,
  • Technical Centre,
  • 139 Cambridge Road,
  • Milton,
  • Cambridge CB24 6AZ

VAT: GB 214 2617 96

Producer Registration number: WEE/BD0050TZ

Terms and Conditions of Sale

For our US customers, we can provide tax form W-8BEN, that identifies us as a UK company.

DUNS: 219151016
NAICS: 423490
Commodity codes
Hardware: 84716070
Software: 85234945

By email:


By post:
  • Cambridge Electronic Design Limited,
  • Technical Centre,
  • 139 Cambridge Road,
  • Milton,
  • Cambridge CB24 6AZ
By telephone:

(Int.+44) (0)1223 420186

From North America (Toll Free):

1 800 345 7794


Privacy policy

CED, through this site, does two things that relate to privacy. We would like to explain them.

Emails from down-loads

We offer free down-loads of many files on our site, from test programs to complete install files for updated versions of major packages like Spike2 and Signal.

When customers wish to take a down-load of a major package, we ask a few questions, including their name, email address, the serial number of the software for which they seek an upgrade and whether they would like an automatic email whenever we update the product. This information is emailed back to CED when they access the final down-load screen. Within this email, your browser transmits the type and version of browser you are using, and the screen resolution you are running.

The reasons why we take and keep this information are that it is useful for our software development team to know who has taken the latest versions, and it is useful for our web site development team to know which browsers people are using to view our site, and what resolution they have their screens set to.


When people down-load a major package, we try to write a cookie, a small file in your computer, that records your name, serial number of the software package, and the version you are down-loading. These files have a lifetime of one year.

The reasons for storing this information are firstly that if you ask for another down-load some other time, your details are read from the cookie and are pre-written into the form, to save you looking them up again. The other reason is that next time you access our site, your browser looks through your CED cookies and compares the versions down-loaded with the latest version numbers read from our site. If there is a later version of a product you have already down-loaded, we tell you on the home page screen, so you know that it is worth going to the down-load page again.

None of this information is ever given to anyone outside CED. ×