TSG Doc - User contributions [en]

Observation Lab

2026-09-14T15:26:45Z

E.vandenberge: /* Using the Experiment Control Computer */

Observation in Labs

When conducting observational studies in the labs, camera and audio recordings can be set up using the equipment and software described below.

==Equipment==
* [[AVer CAM520 Pro3]]
* [[Hollyland Lark M2]]

==Software==
* [[OBS Studio]]

==Labs==
* Observation lab
* Bar lab

==Using the Experiment Control Computer==
To use cameras and audio recordings in the Bar lab or Observational labs, follow these instructions:
# Turn on all the green switches and the experiment control computer.
# Once logged in, open [[OBS Studio]].
# On the bottom left, you will see a panel called "Scene". In that panel, you can select a configuration that has already been created (e.g., 2 cameras, 3 cameras, ...). You can also create a configuration yourself. If so, you will also need to indicate the source for which specific cameras you would like to record from.
# Once you have selected the configuration, in the "Source" panel (bottom centre) you can double-click on a specific camera if you want to change the angle and zoom. After double-clicking, select "Configure Video" and then "Camera Control". Change zoom, tilt (up/down) and pan (left/right) according to what you need. Note that focus is automatic.
# You can change the recording path (where your data will be saved) to a local folder of your choice. '''Please do not change the recording path to your working group folder''': the uploading is not fast enough for videos.
# You can then press "Start Recording" at the bottom right, whenever you are ready.
# Once done, remember to upload the data to your work group folder, and to delete it from the local folder.

==Adding Audio Recording==
# To record audio, you can use [[Hollyland Lark M2]] microphones.
# Connect the receiver(s) to the experiment control computer via the cable.
# The pairing between the receiver and the lavalier microphones is automatic.
# If you have selected a pre-made scene with audio, the communication with OBS Studio is automatic. If you have created the configuration yourself, you will need to add the Hollyland microphone(s) as audio in source.

Observation Lab

2026-09-14T15:25:13Z

E.vandenberge: /* Adding Audio Recording */

Observation in Labs

When conducting observational studies in the labs, camera and audio recordings can be set up using the equipment and software described below.

==Equipment==
* [[AVer CAM520 Pro3]]
* [[Hollyland Lark M2]]

==Software==
* [[OBS Studio]]

==Labs==
* Observation lab
* Bar lab

==Using the Experiment Control Computer==
To use cameras and audio recordings in the Bar lab or Observational labs, follow these instructions:
# Turn on all the green switches and the experiment control computer.
# Once logged in, open OBS Studio.
# On the bottom left, you will see a panel called "Scene". In that panel, you can select a configuration that has already been created (e.g., 2 cameras, 3 cameras, ...). You can also create a configuration yourself. If so, you will also need to indicate the source for which specific cameras you would like to record from.
# Once you have selected the configuration, in the "Source" panel (bottom centre) you can double-click on a specific camera if you want to change the angle and zoom. After double-clicking, select "Configure Video" and then "Camera Control". Change zoom, tilt (up/down) and pan (left/right) according to what you need. Note that focus is automatic.
# You can change the recording path (where your data will be saved) to a local folder of your choice. '''Please do not change the recording path to your working group folder''': the uploading is not fast enough for videos.
# You can then press "Start Recording" at the bottom right, whenever you are ready.
# Once done, remember to upload the data to your work group folder, and to delete it from the local folder.

==Adding Audio Recording==
# To record audio, you can use [[Hollyland Lark M2]] microphones.
# Connect the receiver(s) to the experiment control computer via the cable.
# The pairing between the receiver and the lavalier microphones is automatic.
# If you have selected a pre-made scene with audio, the communication with OBS Studio is automatic. If you have created the configuration yourself, you will need to add the Hollyland microphone(s) as audio in source.

Observation Lab

2026-09-14T15:23:56Z

E.vandenberge: /* Equipment */

Observation in Labs

When conducting observational studies in the labs, camera and audio recordings can be set up using the equipment and software described below.

==Equipment==
* [[AVer CAM520 Pro3]]
* [[Hollyland Lark M2]]

==Software==
* [[OBS Studio]]

==Labs==
* Observation lab
* Bar lab

==Using the Experiment Control Computer==
To use cameras and audio recordings in the Bar lab or Observational labs, follow these instructions:
# Turn on all the green switches and the experiment control computer.
# Once logged in, open OBS Studio.
# On the bottom left, you will see a panel called "Scene". In that panel, you can select a configuration that has already been created (e.g., 2 cameras, 3 cameras, ...). You can also create a configuration yourself. If so, you will also need to indicate the source for which specific cameras you would like to record from.
# Once you have selected the configuration, in the "Source" panel (bottom centre) you can double-click on a specific camera if you want to change the angle and zoom. After double-clicking, select "Configure Video" and then "Camera Control". Change zoom, tilt (up/down) and pan (left/right) according to what you need. Note that focus is automatic.
# You can change the recording path (where your data will be saved) to a local folder of your choice. '''Please do not change the recording path to your working group folder''': the uploading is not fast enough for videos.
# You can then press "Start Recording" at the bottom right, whenever you are ready.
# Once done, remember to upload the data to your work group folder, and to delete it from the local folder.

==Adding Audio Recording==
# To record audio, you can use Hollyland.
# Connect the receiver to the experiment control computer via the cable.
# The pairing between the receiver and the mic is automatic.
# If you have selected a pre-made scene with audio, the communication with OBS Studio is automatic. If you have created the configuration yourself, you will need to add the Hollyland as audio in source.

LimeSurvey

2026-09-14T15:22:51Z

E.vandenberge:

{{ambox
| type = notice
| text = '''Migration notice:''' We will soon migrate from LimeSurvey 6 to LimeSurvey 7. Once LimeSurvey 7 is up and running, we will provide more information about the migration.
}}

{{Infobox software
| name = LimeSurvey
| logo = Limesurveyv7 logo.png
| logo size = 200px
| logo alt = Limesurvey
| screenshot = Limesurvey_screenshot01.jpg
| caption = A survey on Limesurvey with the Radboud theme
| developer =
| installed version = 7.0.10+260813
| installed version date = 
| platform = Web
| language count = 84
| website = [https://survey.socsci.ru.nl/admin survey.socsci.ru.nl]
| resources =
{{Infobox tsg
| child = yes
| header2 =
| data2 =
| manuals = {{bulleted list
| [http://manual.limesurvey.org/ Manual]
}}
}}
}}

LimeSurvey is an open-source platform for making and publishing surveys. The Faculty of Social Sciences has its own Limesurvey server which all of its students and staff can use. Log on to [https://survey.socsci.ru.nl/admin survey.socsci.ru.nl/admin] with your university number/email address and password to create a survey.

There is no limit to the number of surveys that you can make, or the number of participants in a survey. There is also no limit to the media content of the survey (e.g. you can include a feature-length movie). Scripting inside the surveys is allowed (with Javascript), enabling you to change the survey behaviour and include complicated stimuli in the survey.

=Usage=
== Login ==
Logging into our LimeSurvey server is done through SURFconext / Single Sign-On (SSO). The first time you log in, you will be asked to authenticate using your Radboud University credentials. After that, you can use your Radboud credentials to log in to LimeSurvey whenever needed.

== Editor version==
Limesurvey v7 offers two editor versions: ''New'' and ''Classic''. You can switch between them by clicking on your name/u-number on the home page and selecting "Editor Version".

*The ''Classic'' version offers a bit more control over the question and answer logic, and will be familiar to those who have used Limesurvey before.
*The ''New'' version has a more WYSIWYG (What you see is what you get) style interface, which makes creating and reordering questions a lot easier.

⚠️Theme options are currently not working correctly in the New Editor. Please DO NOT make changes to the settings here.

== Creating Surveys ==
There is a [https://www.socsci.ru.nl/wilberth/limesurvey/01intro.html Limesurvey beginner tutorial] for use of Limesurvey on the Radboud University Faculty of Social Sciences.

== Publishing ==
Invitations to surveys can be send with a direct link to the survey (e.g. ''[[#Publishing | https://survey.socsci.ru.nl/index.php/123456?lang=en]]'') or by referring to the main survey page ''[http://survey.socsci.ru.nl questions.socsci.ru.nl]''. Note that in the latter case the participant has to find the survey in a list. By default surveys are not listed on the main page. Change this in the ''survey settings'' if you wish. The preferred way is using direct links.

== Collaboration ==
To work with multiple people on the same survey, follow the instructions on our [[Help:LimeSurvey/Collaboration|Collaboration]] page.

== Theme ==
A Radboud-branded theme called ''Radboud Twentythree'' (previously ''radboud'') is applied to all new surveys by default.

If you want to use a different theme, ask the administrator to activate additional themes for you and go to: 
Settings -> General -> Theme -> (Select your theme) -> Save

Additional theme options may be available under Settings -> Theme Options.

⚠️Theme options are currently not working correctly in the New Editor. Please DO NOT make changes to the settings here.

== Sona integration ==
If you want to use Sona to invite people to take your survey, please follow the [http://www.sona-systems.com/help/limesurvey.aspx manual provided bij Sona]. Furthermore, if this participant ID should be stored in LimeSurvey such that it is possible to link a response to a participant ID, then you would also have to follow the instructions in the [https://manual.limesurvey.org/Panel_integration manual provided by LimeSurvery]. Please make sure to test whether it works with a [https://tsgdoc.socsci.ru.nl/index.php/Online_experiment_systems#Pilot_Run pilot run].

Similar integrations are possible with Prolific, Mechanical Turk and other panel systems.

= Previous Version =
If you have made a survey on the old Limesurvey server, you can still access it and your collected data on [https://questions.socsci.ru.nl/admin questions.socsci.ru.nl]. 
Active surveys will continue to work as-is.

If you wish to run a previous survey again, please migrate your survey to the current server.

= Support =
If you are a faculty member at the Faculty of Social Sciences and need help using LimeSurvey, please contact [mailto:limesurvey.fsw@ru.nl limesurvey.fsw@ru.nl]. Users themselves are responsible for the creation and design of their surveys, as well as the data analysis. For technical support, contact our [[LimeSurvey/Administrators|administrator(s)]]. TSG can also offer assistance adding functionality if existing functionality is insufficient for your needs.

= Data Storage =
Surveys and collected data are stored on campus. The server is not to be used for long term data storage. Please us the survey expiration data to indicate when you stop collecting data. Surveys and data may be removed after a year without prior warning.



==External Links==
* [https://survey.socsci.ru.nl/admin survey.socsci.ru.nl] (v7)
* [https://questions.socsci.ru.nl/admin questions.socsci.ru.nl] (v6)
* {{Official website|http://limesurvey.org}}

File:Limesurvey screenshot01.jpg

2026-09-14T15:17:00Z

E.vandenberge: E.vandenberge uploaded a new version of File:Limesurvey screenshot01.jpg

Screenshot of the TSG Customer Survey, powered by Limesurvey.

7-Zip

2026-09-14T14:22:57Z

E.vandenberge:

{{Infobox software
| name = 7-Zip
| logo = 7zip.jpg
| screenshot =
| caption =
| developer = Igor Pavlov
| released = 1999
| discontinued =
| latest release version =
| latest release date = 
| latest preview version =
| latest preview date = 
| installed version =
| installed version date = 
| status = Active
| programming language =
| operating system = Microsoft Windows, Linux, OSX
| platform =
| size =
| language =
| genre =
| license = GNU GPL/LGPL
| website = https://www.7-zip.org/
| resources =
{{Infobox tsg
| child = yes
| downloads = {{bulleted list
| [https://www.7-zip.org/download.html Download Latest Version]
}}
}}
}}

7-Zip is a free and open-source file archiver, a utility used to place groups of files within compressed containers known as "archives". It is developed by Igor Pavlov and was first released in 1999. 7-Zip has its own archive format called 7z introduced in 2001, but can read and write several others.



==Installation==
Download and run the installer for your operating system from the [https://www.7-zip.org/download.html 7-zip website].

==Archive formats==
By default, 7-Zip creates 7z-format archives with a .7z file extension. Each archive can contain multiple directories and files. As a container format, security or size reduction are achieved by looking for similarities throughout the data using a stacked combination of filters. These can consist of pre-processors, compression algorithms, and encryption filters.

The core 7z compression uses a variety of algorithms, the most common of which are bzip2, PPMd, LZMA2, and LZMA. Developed by Pavlov, LZMA is a relatively new system, making its debut as part of the 7z format. LZMA uses an LZ-based sliding dictionary of up to 3840 MB in size, backed by a range coder.

The native 7z file format is open and modular. File names are stored as Unicode.

The 7z file format specification is distributed with the program's source code, in the "doc" sub-directory.

BrainStreamExampleSpellerPart5

2026-08-12T14:32:34Z

E.vandenberge: /* Evaluation */

= Example 2: Visual Speller =
__TOC__
= Part 5 =

[[BrainStreamExampleSpellerPart4|<- Go back to Part 4]] - [[BrainStreamExampleSpellerPart6|Continue with Part 6 ->]]

In the final part of this visual speller example, we will show how to use a [[BrainStreamLoopTick|looptick function]] for stimulus presentation. The advantage of a looptick function over a normal loop function is that BrainStream can modify the loop while it is running. For example, stimulus presentation could be dynamically adapted or stopped early, based on BrainStream's estimates about which stimulus is the target.
== Structure of the looptick function ==

The function for stimulus presentation, runSequence, is now implemented as a looptick function. Below is a schematic overview of this function:

[[File:DocsSectionsExampleSpellerPart5_Flowchart1.png|645px|343x]]

''Figure 1: Flowchart of the runSequence looptick function.'' ''Actions indicated in orange are executed at the BrainStream Matlab session, whereas actions indicated in blue are executed at the client.''

As can be seen from the flowchart, the runSequence function is executed at the client. However, functions from the BrainStream Matlab session can send information to the client to influence the behavior of the loop.

== Looptick function ==

This is the runSequence looptick function (together with explanations in italics):
<pre>function [ev, stoploop, waittime] = runSequence(ev, tick_count, abort_loop)

persistent uservars;
waittime = 0; % init

isi = 0.2; % inter-stimulus-interval
if tick_count == 1 % first tick
init_loop;
end
toc;</pre>

''The first time the runSequence looptick function is called (e.g. if tick_count is 1), the init_loop function (see [.DocsSectionsExampleSpellerPart5#InitLoop below]) will be executed. This function initializes some variables and starts a stopwatch.''
<pre>if abort_loop
disp('New processing pipeline received from [[BrainStream|Brain Stream]]');
exit_loop;
return
end</pre>

''If an error occurs on the BrainStream side or a new job (processing pipeline or event) was sent, BrainStream will set abort_loop to 1 during the next call to the looptick function to finish the current loop. You can use this feature to define some steps to finalize your loop before BrainStream quits. In this case, a message will be displayed on the command screen and the exit_loop function (see [[BrainStreamExampleSpellerPart5#ExitLoop|below]]) will be executed. This function sends a hardware marker to the data source to indicate the end of processing.''
<pre>try
[newvars, success] = bs_recv_user_brainstream(ev, 'stim',0,0); % check for new information from [[BrainStream|Brain Stream]]
if ~isempty(newvars)
uservars = [uservars, newvars];
end

if ~isempty(uservars) && isempty(uservars{1})
disp('Exiting loop by user request')
exit_loop;
return;
end
if success >= 0 || ~isempty(uservars) % get feedback info
for n = 1 : numel(uservars)
disp(uservars{n});
ev.flashStyle = uservars{n};
end
uservars = {};
end</pre>

<blockquote style="margin: 0px 0px 0px 30px; border-style: none; padding: 0px">The function now checks if there is new information sent to the client from the BrainStream side. If there are new variables available, they will be added to the uservars variable. If the variable that was sent is empty, this means that the loop should be ended. Therefore, the [[BrainStreamExampleSpellerPart5#ExitLoop|exit_loop]] function will be executed.</blockquote> <pre> if ~ev.flashed
ev = highlightGrid(ev); % randomly highlight row or column and send stim_## marker
else
ev = showGrid(ev); % dim higlighted row or column
ev = bs_send_hardware_marker(ev,'highlightOff','eeg'); % also mark this moment
end
ev.flashed = ~ev.flashed;</pre>

<blockquote style="margin: 0px 0px 0px 30px; border-style: none; padding: 0px">Every time the looptick function is called, rows and columns on the screen should be highlighted or dimmed alternately. The field of the event structure called 'flashed' keeps track of whether the last stimulus was a flash or the dimmed grid. This is possible because all calls to the looptick function belong to the same event. If the last stimulus was a flash, the grid will be dimmed, and if the last stimulus was the dimmed grid, a row or column will be highlighted. Afterwards, the logical value of the ev.flashed variable is inverted.</blockquote> <pre> if tick_count >= 2*bs_get_blockvalue(ev,'Experiment','nRep',10) % check if at end of sequence (NB: tick_count adds 2 per stimulus cycle)
exit_loop();
else
stoploop = 0;
end
</pre>

<blockquote style="margin: 0px 0px 0px 30px; border-style: none; padding: 0px">The function now checks if the sequence is finished. If all stimuli have been presented, the [.DocsSectionsExampleSpellerPart5#ExitLoop exit_loop] function will be executed. Otherwise, the stoploop variable will remain 0, which ensures the looptick function is called again.</blockquote> <pre> waittime = max(0, tick_count*(isi/2)-toc); % determine time to wait before calling tick function again</pre>

<blockquote style="margin: 0px 0px 0px 30px; border-style: none; padding: 0px">A change in the grid should occur every 100 ms (isi/2). In order to achieve this, we can set the waittime variable. When the loop is initialized, the tic command starts the stopwatch. Each time the loop is called again, the toc command measures the time between the first looptick call and the present time. To determine the value of waittime, we take the time at which the stimulus should occur (tick_count*(isi/2)) and subtract from it the time that has passed already (toc). If the time at which the stimulus was supposed to occur has already passed, waittime is set to 0.</blockquote> <pre>catch
err = lasterror;
exit_loop;
rethrow(err);
end</pre>

''If an error occurs during the execution of the looptick function, the [.DocsSectionsExampleSpellerPart5#ExitLoop exit_loop] function will be executed.''

<div id="InitLoop"></div>

This is the init_loop function:
<pre>function init_loop
[uservars] = bs_recv_user_brainstream(ev, 'stim'); % read user socket, just to flush
uservars = {};
ev.flashed = 0;
tic;
end</pre>

<div id="ExitLoop"></div>

This is the exit_loop function:
<pre>function exit_loop
ev = bs_send_hardware_marker(ev,'endSequence','eeg');
stoploop = 1;
end
end </pre>

== Other changes to the speller ==

If you test this example, you will notice that the speller grid has changed from the previous examples. It now contains 36 elements: all letters of the alphabet and the numbers 0-9. This change has been accomplished by changing the key 'symbols' under topic 'Experiment' in the speller_common blockfile. By changing the blockfile, you can easily change the contents of the speller matrix.
== Evaluation ==

You can find a [[BrainStreamLogFile|log file]] of this experiment [[Media:BrainStreamExampleSpellerPart5_Logfile_spellerpart5.docx|here]]{{Dead link}}. From this log file, we can determine the timing accuracy of the stimuli. Below are log file entries for the first and last five stimuli of one sequence:
<pre>10Jan12|11:09:46.701 INFO > '''***''' ( stim_11) '''*************************************************************'''
10Jan12|11:09:46.702 INFO > 225.95 (eeg:#40127.00) 225.95 226.05 act: modvar (t=EVENT) stim_11

10Jan12|11:09:46.901 INFO > '''***''' ( stim_4) '''*************************************************************'''
10Jan12|11:09:46.901 INFO > 226.15 (eeg:#40178.00) 226.15 226.25 act: modvar (t=EVENT) stim_4

10Jan12|11:09:47.101 INFO > '''***''' ( stim_12) '''*************************************************************'''
10Jan12|11:09:47.101 INFO > 226.34 (eeg:#40229.00) 226.34 226.45 act: modvar (t=EVENT) stim_1

10Jan12|11:09:47.307 INFO > '''***''' ( stim_5) '''*************************************************************'''
10Jan12|11:09:47.308 INFO > 226.55 (eeg:#40281.00) 226.55 226.65 act: modvar (t=EVENT) stim_5

10Jan12|11:09:47.512 INFO > '''***''' ( stim_10) '''*************************************************************'''
10Jan12|11:09:47.512 INFO > 226.75 (eeg:#40332.00) 226.75 226.86 act: modvar (t=EVENT) stim_10
.
.
.
10Jan12|11:10:05.706 INFO > '''***''' ( stim_2) '''*************************************************************'''
10Jan12|11:10:05.706 INFO > 244.95 (eeg:#44991.00) 244.95 245.05 act: modvar (t=EVENT) stim_2

10Jan12|11:10:05.908 INFO > '''***''' ( stim_9) '''*************************************************************'''
10Jan12|11:10:05.908 INFO > 245.15 (eeg:#45042.00) 245.15 245.25 act: modvar (t=EVENT) stim_9

10Jan12|11:10:06.107 INFO > '''***''' ( stim_4) '''*************************************************************'''
10Jan12|11:10:06.108 INFO > 245.34 (eeg:#45093.00) 245.34 245.45 act: modvar (t=EVENT) stim_4

10Jan12|11:10:06.314 INFO > '''***''' ( stim_7) '''*************************************************************'''
10Jan12|11:10:06.315 INFO > 245.55 (eeg:#45145.00) 245.55 245.66 act: modvar (t=EVENT) stim_7

10Jan12|11:10:06.507 INFO > '''***''' ( stim_6) '''*************************************************************'''
10Jan12|11:10:06.508 INFO > 245.75 (eeg:#45196.00) 245.75 245.85 act: modvar (t=EVENT) stim_6
</pre>

The stim_# markers are sent each time a row or column of the matrix is flashed, so every 200 ms one of these markers should arrive. In the log file, the first number in each line (after the date and time stamp) indicates the time at which the marker arrived. This indeed happens every 0.2 seconds. The time between two successive stimuli also remains stable over the sequence.

Nevertheless, the timing accuracy is not perfect, sometimes jitters occur of approximately 10 ms. If you need even more accurate timing, you should use BrainStream in combination with a toolbox that is specifically designed for stimulus presentation, such as [http://psychtoolbox.org Psychtoolbox].

[[BrainStreamExampleSpellerPart4|<- Go back to Part 4]] - [[BrainStreamExampleSpellerPart6|Continue with Part 6 ->]]

Module:Message box/configuration

2026-08-12T14:30:25Z

E.vandenberge: Protected "Module:Message box/configuration" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

--------------------------------------------------------------------------------
-- Message box configuration --
-- --
-- This module contains configuration data for [[Module:Message box]]. --
--------------------------------------------------------------------------------

return {
ambox = {
types = {
speedy = {
class = 'ambox-speedy',
image = 'Ambox warning pn.svg'
},
delete = {
class = 'ambox-delete',
image = 'Ambox warning pn.svg'
},
content = {
class = 'ambox-content',
image = 'Ambox important.svg'
},
style = {
class = 'ambox-style',
image = 'Edit-clear.svg'
},
move = {
class = 'ambox-move',
image = 'Merge-split-transwiki default.svg'
},
protection = {
class = 'ambox-protection',
image = 'Semi-protection-shackle-keyhole.svg'
},
notice = {
class = 'ambox-notice',
image = 'Information icon4.svg'
}
},
default = 'notice',
allowBlankParams = {'talk', 'sect', 'date', 'issue', 'fix', 'subst', 'hidden'},
allowSmall = true,
smallParam = 'left',
smallClass = 'mbox-small-left',
substCheck = true,
classes = {'metadata', 'ambox'},
imageEmptyCell = true,
imageCheckBlank = true,
imageSmallSize = '20x20px',
imageCellDiv = true,
useCollapsibleTextFields = true,
imageRightNone = true,
sectionDefault = 'article',
allowMainspaceCategories = true,
templateCategory = 'Article message templates',
templateCategoryRequireName = true,
templateErrorCategory = 'Article message templates with missing parameters',
templateErrorParamsToCheck = {'issue', 'fix', 'subst'},
removalNotice = '[[Help:Maintenance template removal|Learn how and when to remove this message]]',
templatestyles = 'Module:Message box/ambox.css'
},

cmbox = {
types = {
speedy = {
class = 'cmbox-speedy',
image = 'Ambox warning pn.svg'
},
delete = {
class = 'cmbox-delete',
image = 'Ambox warning pn.svg'
},
content = {
class = 'cmbox-content',
image = 'Ambox important.svg'
},
style = {
class = 'cmbox-style',
image = 'Edit-clear.svg'
},
move = {
class = 'cmbox-move',
image = 'Merge-split-transwiki default.svg'
},
protection = {
class = 'cmbox-protection',
image = 'Semi-protection-shackle-keyhole.svg'
},
notice = {
class = 'cmbox-notice',
image = 'Information icon4.svg'
}
},
default = 'notice',
showInvalidTypeError = true,
classes = {'cmbox'},
imageEmptyCell = true,
templatestyles = 'Module:Message box/cmbox.css',
div_structure = true,
},

fmbox = {
types = {
warning = {
class = 'fmbox-warning',
image = 'Ambox warning pn.svg'
},
editnotice = {
class = 'fmbox-editnotice',
image = 'Information icon4.svg'
},
system = {
class = 'fmbox-system',
image = 'Information icon4.svg'
}
},
default = 'system',
showInvalidTypeError = true,
classes = {'fmbox'},
imageEmptyCell = false,
imageRightNone = false,
templatestyles = 'Module:Message box/fmbox.css',
div_structure = true,
},

imbox = {
types = {
speedy = {
class = 'imbox-speedy',
image = 'Ambox warning pn.svg'
},
delete = {
class = 'imbox-delete',
image = 'Ambox warning pn.svg'
},
content = {
class = 'imbox-content',
image = 'Ambox important.svg'
},
style = {
class = 'imbox-style',
image = 'Edit-clear.svg'
},
move = {
class = 'imbox-move',
image = 'Merge-split-transwiki default.svg'
},
protection = {
class = 'imbox-protection',
image = 'Semi-protection-shackle-keyhole.svg'
},
license = {
class = 'imbox-license licensetpl',
image = 'Imbox-license.svg'
},
["license-related"] = {
class = 'imbox-license',
image = 'Imbox-license.svg'
},
featured = {
class = 'imbox-featured',
image = 'Cscr-featured.svg',
imageNeedsLink = true
},
notice = {
class = 'imbox-notice',
image = 'Information icon4.svg'
}
},
default = 'notice',
showInvalidTypeError = true,
classes = {'imbox'},
imageEmptyCell = true,
below = true,
templateCategory = 'File message boxes',
templatestyles = 'Module:Message box/imbox.css',
div_structure = true,
},

ombox = {
types = {
speedy = {
class = 'ombox-speedy',
image = 'Ambox warning pn.svg'
},
delete = {
class = 'ombox-delete',
image = 'Ambox warning pn.svg'
},
content = {
class = 'ombox-content',
image = 'Ambox important.svg'
},
style = {
class = 'ombox-style',
image = 'Edit-clear.svg'
},
move = {
class = 'ombox-move',
image = 'Merge-split-transwiki default.svg'
},
protection = {
class = 'ombox-protection',
image = 'Semi-protection-shackle-keyhole.svg'
},
notice = {
class = 'ombox-notice',
image = 'Information icon4.svg'
}
},
default = 'notice',
showInvalidTypeError = true,
classes = {'ombox'},
allowSmall = true,
imageEmptyCell = true,
imageRightNone = true,
templatestyles = 'Module:Message box/ombox.css'
},

tmbox = {
types = {
speedy = {
class = 'tmbox-speedy',
image = 'Ambox warning pn.svg'
},
delete = {
class = 'tmbox-delete',
image = 'Ambox warning pn.svg'
},
content = {
class = 'tmbox-content',
image = 'Ambox important.svg'
},
style = {
class = 'tmbox-style',
image = 'Edit-clear.svg'
},
move = {
class = 'tmbox-move',
image = 'Merge-split-transwiki default.svg'
},
protection = {
class = 'tmbox-protection',
image = 'Semi-protection-shackle-keyhole.svg'
},
notice = {
class = 'tmbox-notice',
image = 'Information icon4.svg'
}
},
default = 'notice',
showInvalidTypeError = true,
classes = {'tmbox'},
allowSmall = true,
imageRightNone = true,
imageEmptyCell = true,
templateCategory = 'Talk message boxes',
templatestyles = 'Module:Message box/tmbox.css'
}
}

Module:Message box

2026-08-12T14:30:11Z

E.vandenberge: Protected "Module:Message box" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

-- This is a meta-module for producing message box templates, including
-- {{mbox}}, {{ambox}}, {{imbox}}, {{tmbox}}, {{ombox}}, {{cmbox}} and {{fmbox}}.

-- Load necessary modules.
require('Module:No globals')
local getArgs
local yesno = require('Module:Yesno')

-- Get a language object for formatDate and ucfirst.
local lang = mw.language.getContentLanguage()

-- Define constants
local CONFIG_MODULE = 'Module:Message box/configuration'
local DEMOSPACES = {talk = 'tmbox', image = 'imbox', file = 'imbox', category = 'cmbox', article = 'ambox', main = 'ambox'}

--------------------------------------------------------------------------------
-- Helper functions
--------------------------------------------------------------------------------

local function getTitleObject(...)
-- Get the title object, passing the function through pcall
-- in case we are over the expensive function count limit.
local success, title = pcall(mw.title.new, ...)
if success then
return title
end
end

local function union(t1, t2)
-- Returns the union of two arrays.
local vals = {}
for i, v in ipairs(t1) do
vals[v] = true
end
for i, v in ipairs(t2) do
vals[v] = true
end
local ret = {}
for k in pairs(vals) do
table.insert(ret, k)
end
table.sort(ret)
return ret
end

local function getArgNums(args, prefix)
local nums = {}
for k, v in pairs(args) do
local num = mw.ustring.match(tostring(k), '^' .. prefix .. '([1-9]%d*)$')
if num then
table.insert(nums, tonumber(num))
end
end
table.sort(nums)
return nums
end

--------------------------------------------------------------------------------
-- Box class definition
--------------------------------------------------------------------------------

local MessageBox = {}
MessageBox.__index = MessageBox

function MessageBox.new(boxType, args, cfg)
args = args or {}
local obj = {}

-- Set the title object and the namespace.
obj.title = getTitleObject(args.page) or mw.title.getCurrentTitle()

-- Set the config for our box type.
obj.cfg = cfg[boxType]
if not obj.cfg then
local ns = obj.title.namespace
-- boxType is "mbox" or invalid input
if args.demospace and args.demospace ~= '' then
-- implement demospace parameter of mbox
local demospace = string.lower(args.demospace)
if DEMOSPACES[demospace] then
-- use template from DEMOSPACES
obj.cfg = cfg[DEMOSPACES[demospace]]
elseif string.find( demospace, 'talk' ) then
-- demo as a talk page
obj.cfg = cfg.tmbox
else
-- default to ombox
obj.cfg = cfg.ombox
end
elseif ns == 0 then
obj.cfg = cfg.ambox -- main namespace
elseif ns == 6 then
obj.cfg = cfg.imbox -- file namespace
elseif ns == 14 then
obj.cfg = cfg.cmbox -- category namespace
else
local nsTable = mw.site.namespaces[ns]
if nsTable and nsTable.isTalk then
obj.cfg = cfg.tmbox -- any talk namespace
else
obj.cfg = cfg.ombox -- other namespaces or invalid input
end
end
end

-- Set the arguments, and remove all blank arguments except for the ones
-- listed in cfg.allowBlankParams.
do
local newArgs = {}
for k, v in pairs(args) do
if v ~= '' then
newArgs[k] = v
end
end
for i, param in ipairs(obj.cfg.allowBlankParams or {}) do
newArgs[param] = args[param]
end
obj.args = newArgs
end

-- Define internal data structure.
obj.categories = {}
obj.classes = {}
-- For lazy loading of [[Module:Category handler]].
obj.hasCategories = false

return setmetatable(obj, MessageBox)
end

function MessageBox:addCat(ns, cat, sort)
if not cat then
return nil
end
if sort then
cat = string.format('[[Category:%s|%s]]', cat, sort)
else
cat = string.format('[[Category:%s]]', cat)
end
self.hasCategories = true
self.categories[ns] = self.categories[ns] or {}
table.insert(self.categories[ns], cat)
end

function MessageBox:addClass(class)
if not class then
return nil
end
table.insert(self.classes, class)
end

function MessageBox:setParameters()
local args = self.args
local cfg = self.cfg

-- Get type data.
self.type = args.type
local typeData = cfg.types[self.type]
self.invalidTypeError = cfg.showInvalidTypeError
and self.type
and not typeData
typeData = typeData or cfg.types[cfg.default]
self.typeClass = typeData.class
self.typeImage = typeData.image

-- Find if the box has been wrongly substituted.
self.isSubstituted = cfg.substCheck and args.subst == 'SUBST'

-- Find whether we are using a small message box.
self.isSmall = cfg.allowSmall and (
cfg.smallParam and args.small == cfg.smallParam
or not cfg.smallParam and yesno(args.small)
)

-- Add attributes, classes and styles.
self.id = args.id
self.name = args.name
if self.name then
self:addClass('box-' .. string.gsub(self.name,' ','_'))
end
if yesno(args.plainlinks) ~= false then
self:addClass('plainlinks')
end
for _, class in ipairs(cfg.classes or {}) do
self:addClass(class)
end
if self.isSmall then
self:addClass(cfg.smallClass or 'mbox-small')
end
self:addClass(self.typeClass)
self:addClass(args.class)
self.style = args.style
self.attrs = args.attrs

-- Set text style.
self.textstyle = args.textstyle

-- Find if we are on the template page or not. This functionality is only
-- used if useCollapsibleTextFields is set, or if both cfg.templateCategory
-- and cfg.templateCategoryRequireName are set.
self.useCollapsibleTextFields = cfg.useCollapsibleTextFields
if self.useCollapsibleTextFields
or cfg.templateCategory
and cfg.templateCategoryRequireName
then
if self.name then
local templateName = mw.ustring.match(
self.name,
'^[tT][eE][mM][pP][lL][aA][tT][eE][%s_]*:[%s_]*(.*)$'
) or self.name
templateName = 'Template:' .. templateName
self.templateTitle = getTitleObject(templateName)
end
self.isTemplatePage = self.templateTitle
and mw.title.equals(self.title, self.templateTitle)
end

-- Process data for collapsible text fields. At the moment these are only
-- used in {{ambox}}.
if self.useCollapsibleTextFields then
-- Get the self.issue value.
if self.isSmall and args.smalltext then
self.issue = args.smalltext
else
local sect
if args.sect == '' then
sect = 'This ' .. (cfg.sectionDefault or 'page')
elseif type(args.sect) == 'string' then
sect = 'This ' .. args.sect
end
local issue = args.issue
issue = type(issue) == 'string' and issue ~= '' and issue or nil
local text = args.text
text = type(text) == 'string' and text or nil
local issues = {}
table.insert(issues, sect)
table.insert(issues, issue)
table.insert(issues, text)
self.issue = table.concat(issues, ' ')
end

-- Get the self.talk value.
local talk = args.talk
-- Show talk links on the template page or template subpages if the talk
-- parameter is blank.
if talk == ''
and self.templateTitle
and (
mw.title.equals(self.templateTitle, self.title)
or self.title:isSubpageOf(self.templateTitle)
)
then
talk = '#'
elseif talk == '' then
talk = nil
end
if talk then
-- If the talk value is a talk page, make a link to that page. Else
-- assume that it's a section heading, and make a link to the talk
-- page of the current page with that section heading.
local talkTitle = getTitleObject(talk)
local talkArgIsTalkPage = true
if not talkTitle or not talkTitle.isTalkPage then
talkArgIsTalkPage = false
talkTitle = getTitleObject(
self.title.text,
mw.site.namespaces[self.title.namespace].talk.id
)
end
if talkTitle and talkTitle.exists then
local talkText = 'Relevant discussion may be found on'
if talkArgIsTalkPage then
talkText = string.format(
'%s [[%s|%s]].',
talkText,
talk,
talkTitle.prefixedText
)
else
talkText = string.format(
'%s the [[%s#%s|talk page]].',
talkText,
talkTitle.prefixedText,
talk
)
end
self.talk = talkText
end
end

-- Get other values.
self.fix = args.fix ~= '' and args.fix or nil
local date
if args.date and args.date ~= '' then
date = args.date
elseif args.date == '' and self.isTemplatePage then
date = lang:formatDate('F Y')
end
if date then
self.date = string.format(" ''(%s)''", date)
end
self.info = args.info
if yesno(args.removalnotice) then
self.removalNotice = cfg.removalNotice
end
end

-- Set the non-collapsible text field. At the moment this is used by all box
-- types other than ambox, and also by ambox when small=yes.
if self.isSmall then
self.text = args.smalltext or args.text
else
self.text = args.text
end

-- Set the below row.
self.below = cfg.below and args.below

-- General image settings.
self.imageCellDiv = not self.isSmall and cfg.imageCellDiv
self.imageEmptyCell = cfg.imageEmptyCell
if cfg.imageEmptyCellStyle then
self.imageEmptyCellStyle = 'border:none;padding:0px;width:1px'
end

-- Left image settings.
local imageLeft = self.isSmall and args.smallimage or args.image
if cfg.imageCheckBlank and imageLeft ~= 'blank' and imageLeft ~= 'none'
or not cfg.imageCheckBlank and imageLeft ~= 'none'
then
self.imageLeft = imageLeft
if not imageLeft then
local imageSize = self.isSmall
and (cfg.imageSmallSize or '30x30px')
or '40x40px'
self.imageLeft = string.format('[[File:%s|%s|link=|alt=]]', self.typeImage
or 'Imbox notice.png', imageSize)
end
end

-- Right image settings.
local imageRight = self.isSmall and args.smallimageright or args.imageright
if not (cfg.imageRightNone and imageRight == 'none') then
self.imageRight = imageRight
end
end

function MessageBox:setMainspaceCategories()
local args = self.args
local cfg = self.cfg

if not cfg.allowMainspaceCategories then
return nil
end

local nums = {}
for _, prefix in ipairs{'cat', 'category', 'all'} do
args[prefix .. '1'] = args[prefix]
nums = union(nums, getArgNums(args, prefix))
end

-- The following is roughly equivalent to the old {{Ambox/category}}.
local date = args.date
date = type(date) == 'string' and date
local preposition = 'from'
for _, num in ipairs(nums) do
local mainCat = args['cat' .. tostring(num)]
or args['category' .. tostring(num)]
local allCat = args['all' .. tostring(num)]
mainCat = type(mainCat) == 'string' and mainCat
allCat = type(allCat) == 'string' and allCat
if mainCat and date and date ~= '' then
local catTitle = string.format('%s %s %s', mainCat, preposition, date)
self:addCat(0, catTitle)
catTitle = getTitleObject('Category:' .. catTitle)
if not catTitle or not catTitle.exists then
self:addCat(0, 'Articles with invalid date parameter in template')
end
elseif mainCat and (not date or date == '') then
self:addCat(0, mainCat)
end
if allCat then
self:addCat(0, allCat)
end
end
end

function MessageBox:setTemplateCategories()
local args = self.args
local cfg = self.cfg

-- Add template categories.
if cfg.templateCategory then
if cfg.templateCategoryRequireName then
if self.isTemplatePage then
self:addCat(10, cfg.templateCategory)
end
elseif not self.title.isSubpage then
self:addCat(10, cfg.templateCategory)
end
end

-- Add template error categories.
if cfg.templateErrorCategory then
local templateErrorCategory = cfg.templateErrorCategory
local templateCat, templateSort
if not self.name and not self.title.isSubpage then
templateCat = templateErrorCategory
elseif self.isTemplatePage then
local paramsToCheck = cfg.templateErrorParamsToCheck or {}
local count = 0
for i, param in ipairs(paramsToCheck) do
if not args[param] then
count = count + 1
end
end
if count > 0 then
templateCat = templateErrorCategory
templateSort = tostring(count)
end
if self.categoryNums and #self.categoryNums > 0 then
templateCat = templateErrorCategory
templateSort = 'C'
end
end
self:addCat(10, templateCat, templateSort)
end
end

function MessageBox:setAllNamespaceCategories()
-- Set categories for all namespaces.
if self.invalidTypeError then
local allSort = (self.title.namespace == 0 and 'Main:' or '') .. self.title.prefixedText
self:addCat('all', 'Wikipedia message box parameter needs fixing', allSort)
end
if self.isSubstituted then
self:addCat('all', 'Pages with incorrectly substituted templates')
end
end

function MessageBox:setCategories()
if self.title.namespace == 0 then
self:setMainspaceCategories()
elseif self.title.namespace == 10 then
self:setTemplateCategories()
end
self:setAllNamespaceCategories()
end

function MessageBox:renderCategories()
if not self.hasCategories then
-- No categories added, no need to pass them to Category handler so,
-- if it was invoked, it would return the empty string.
-- So we shortcut and return the empty string.
return ""
end
-- Convert category tables to strings and pass them through
-- [[Module:Category handler]].
return require('Module:Category handler')._main{
main = table.concat(self.categories[0] or {}),
template = table.concat(self.categories[10] or {}),
all = table.concat(self.categories.all or {}),
nocat = self.args.nocat,
page = self.args.page
}
end

function MessageBox:export()
local root = mw.html.create()

-- Add the subst check error.
if self.isSubstituted and self.name then
root:tag('b')
:addClass('error')
:wikitext(string.format(
'Template <code>%s[[Template:%s|%s]]%s</code> has been incorrectly substituted.',
mw.text.nowiki('{{'), self.name, self.name, mw.text.nowiki('}}')
))
end

-- Create the box table.
local boxTable = root:tag('table')
boxTable:attr('id', self.id or nil)
for i, class in ipairs(self.classes or {}) do
boxTable:addClass(class or nil)
end
boxTable
:cssText(self.style or nil)
:attr('role', 'presentation')

if self.attrs then
boxTable:attr(self.attrs)
end

-- Add the left-hand image.
local row = boxTable:tag('tr')
if self.imageLeft then
local imageLeftCell = row:tag('td'):addClass('mbox-image')
if self.imageCellDiv then
-- If we are using a div, redefine imageLeftCell so that the image
-- is inside it. Divs use style="width: 52px;", which limits the
-- image width to 52px. If any images in a div are wider than that,
-- they may overlap with the text or cause other display problems.
imageLeftCell = imageLeftCell:tag('div'):css('width', '52px')
end
imageLeftCell:wikitext(self.imageLeft or nil)
elseif self.imageEmptyCell then
-- Some message boxes define an empty cell if no image is specified, and
-- some don't. The old template code in templates where empty cells are
-- specified gives the following hint: "No image. Cell with some width
-- or padding necessary for text cell to have 100% width."
row:tag('td')
:addClass('mbox-empty-cell')
:cssText(self.imageEmptyCellStyle or nil)
end

-- Add the text.
local textCell = row:tag('td'):addClass('mbox-text')
if self.useCollapsibleTextFields then
-- The message box uses advanced text parameters that allow things to be
-- collapsible. At the moment, only ambox uses this.
textCell:cssText(self.textstyle or nil)
local textCellDiv = textCell:tag('div')
textCellDiv
:addClass('mbox-text-span')
:wikitext(self.issue or nil)
if (self.talk or self.fix) and not self.isSmall then
textCellDiv:tag('span')
:addClass('hide-when-compact')
:wikitext(self.talk and (' ' .. self.talk) or nil)
:wikitext(self.fix and (' ' .. self.fix) or nil)
end
textCellDiv:wikitext(self.date and (' ' .. self.date) or nil)
if self.info and not self.isSmall then
textCellDiv
:tag('span')
:addClass('hide-when-compact')
:wikitext(self.info and (' ' .. self.info) or nil)
end
if self.removalNotice then
textCellDiv:tag('small')
:addClass('hide-when-compact')
:tag('i')
:wikitext(string.format(" (%s)", self.removalNotice))
end
else
-- Default text formatting - anything goes.
textCell
:cssText(self.textstyle or nil)
:wikitext(self.text or nil)
end

-- Add the right-hand image.
if self.imageRight then
local imageRightCell = row:tag('td'):addClass('mbox-imageright')
if self.imageCellDiv then
-- If we are using a div, redefine imageRightCell so that the image
-- is inside it.
imageRightCell = imageRightCell:tag('div'):css('width', '52px')
end
imageRightCell
:wikitext(self.imageRight or nil)
end

-- Add the below row.
if self.below then
boxTable:tag('tr')
:tag('td')
:attr('colspan', self.imageRight and '3' or '2')
:addClass('mbox-text')
:cssText(self.textstyle or nil)
:wikitext(self.below or nil)
end

-- Add error message for invalid type parameters.
if self.invalidTypeError then
root:tag('div')
:css('text-align', 'center')
:wikitext(string.format(
'This message box is using an invalid "type=%s" parameter and needs fixing.',
self.type or ''
))
end

-- Add categories.
root:wikitext(self:renderCategories() or nil)

return tostring(root)
end

--------------------------------------------------------------------------------
-- Exports
--------------------------------------------------------------------------------

local p, mt = {}, {}

function p._exportClasses()
-- For testing.
return {
MessageBox = MessageBox
}
end

function p.main(boxType, args, cfgTables)
local box = MessageBox.new(boxType, args, cfgTables or mw.loadData(CONFIG_MODULE))
box:setParameters()
box:setCategories()
return box:export()
end

function mt.__index(t, k)
return function (frame)
if not getArgs then
getArgs = require('Module:Arguments').getArgs
end
return t.main(k, getArgs(frame, {trim = false, removeBlanks = false}))
end
end

return setmetatable(p, mt)

Template:Mbox

2026-08-12T14:29:37Z

E.vandenberge: Protected "Template:Mbox" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

{{#invoke:Message box|mbox}}<noinclude>
{{documentation}}

</noinclude>

Rode Lavalier GO

2026-08-12T14:20:56Z

E.vandenberge: /* Usage */

{{distinguish|Rode RODELink Filmmaker Kit}}

{{Infobox tsg
| name = RØDE Lavalier GO
| image = Rode_lavalier_go.jpg
| caption = RØDE Lavalier GO
| downloads =
}}

The RØDE Lavalier GO is a basic, wired lavalier microphone.



==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDE Lavalier GO
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS
|-
| Accessories || Foam windshield
|}
<references group="fn" /> 

==Usage==
# Connect the microphone to a camera, recorder, or [[audio interface]] (adapter may be required).
# Clip the microphone in place. Usually, this is somewhere around the speaker's chest or collar.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it.
Attach a wind screen when recording outside in windy conditions.

==See Also== 
*[[Microphones]]


<references />

Headphones

2026-08-12T14:20:35Z

E.vandenberge: /* Usage */

{{Infobox tsg
| name = Headphones
| image = Sony_mdr-7506.jpg
| caption = Sony MDR-7506 headphones
}}

With exception of the [[EEG Lab]]s, headphones are the standard audio delivery system in our labs. In dedicated audio labs, such as the [[Sound Recording Lab]] and the [[VoiceKey Lab]], headphones are part of the standard equipment. In other labs (e.g. [[Cubicles]]), you can borrow one of our recommended headphones (listed below) from your [[Lab Coordinator]].



==Specifications==

{| class="wikitable"
|-
! style="width:200px;"|
! style="width:200px;"| [[File:Shure_se112.jpg ‎|200px|Image: 200 pixels]]
! style="width:200px;"| [[File:Sennheiser_hd201_01.jpg ‎|200px|Image: 200 pixels]]
! style="width:200px;"| [[File:Sony_mdr-7506.jpg ‎|200px|Image: 200 pixels]]
|-
! 
! Shure SE112
! Sennheiser HD201
! Sony MDR-7506
|-
| Type || In-ear || Over-ear, closed back || Over-ear, closed back
|-
| Usage || Instances where the headband of a regular headphone would interfere with other equipment (e.g. EEG) || General purpose || Audio recording, analytic listening
|-
|}

==Usage==
''Participant'' in lab with control room:
#Plug the headphones into the 6.3mm or 3.5mm jack extension cord in the lab.

''Participant'' in lab without control room, or ''Experimenter'' control room monitoring:
#Plug the headphones into the 3.5mm jack port on the front of our [[Lab Computer]].

In labs with an [[audio interface]], the headphones are connected to the interface (main stereo or phone output).

ℹ️Left and right side are usually labelled on the ear-cup or headband. On headphones with a cable on one side (e.g. Sony MDR-7506), the cable is almost always on the left.

⚠️When using the headphones for time-critical audio stimuli, please (ask the TSG to) check your audio settings and scripts before running your experiment.

==See Also==
*[[Audio]]

Audio interface

2026-08-12T14:16:38Z

E.vandenberge: Redirected page to Audio Interface

#REDIRECT [[Audio Interface]]

Microphone

2026-08-12T13:31:19Z

E.vandenberge: /* Varieties */

{{Infobox tsg
| name = Microphones
| image = Obama2010.jpg
| caption = Shure SM57: the microphone of choice for every US president since 1965, and ours since 2015 or so
}}

Microphones turn sound into data. When you want to record sound for your experiment, please contact the TSG to discuss which microphone(s) is/are best suited for your application. Below is an overview of some of the microphones available within our research labs, and/or for use in the field.



==Varieties==
We categorize microphones by their connection type (wired vs wireless), transducer type, polar pattern, and form factor:
*'''Dynamic''' - Typically rugged, versatile, don't require additional phantom power, and can handle loud noises.
*'''Condenser''' - More sensitive than dynamic microphones. Often require phantom power (24-48V).
*'''Shotgun''' - Highly directional, often with an [https://www.dpamicrophones.com/dict/interference-tube/ interference tube] design.
*'''Lavalier''' - Tiny, typically clipped onto a person's collar or shirt to record speech.
*'''Headset''' - Attached to headphones or headband, with a flexible arm for placement directly in front of the speaker's mouth.

==Wired==
===Dynamic===
* [[Shure SM57]]

===Shotgun===
* [[Sennheiser MKE600]]
* [[Rode VideoMic NTG]]

===Headset===
* [[AudioTechnica BPHS1]]

===Lavalier===
* [[Rode Lavalier GO]]

==Wireless==
===Lavalier===
* [[Rode RODELink Filmmaker Kit]]
* [[Hollyland Lark M2]]
* [[DJI Mic]]

==See Also==
*[[Audio]]

Microphone

2026-08-12T13:30:50Z

E.vandenberge: /* Varieties */

{{Infobox tsg
| name = Microphones
| image = Obama2010.jpg
| caption = Shure SM57: the microphone of choice for every US president since 1965, and ours since 2015 or so
}}

Microphones turn sound into data. When you want to record sound for your experiment, please contact the TSG to discuss which microphone(s) is/are best suited for your application. Below is an overview of some of the microphones available within our research labs, and/or for use in the field.



==Varieties==
We categorize microphones by their connection type (wired vs wireless), transducer type, polar pattern, and form factor:
*'''Dynamic''' - Typically rugged, versatile, don't require additional phantom power, and can handle loud noises.
*'''Condenser''' - More sensitive than dynamic microphones. Require phantom power (24-48V).
*'''Shotgun''' - Highly directional, often with an [https://www.dpamicrophones.com/dict/interference-tube/ interference tube] design.
*'''Lavalier''' - Tiny, typically clipped onto a person's collar or shirt to record speech.
*'''Headset''' - Attached to headphones or headband, with a flexible arm for placement directly in front of the speaker's mouth.

==Wired==
===Dynamic===
* [[Shure SM57]]

===Shotgun===
* [[Sennheiser MKE600]]
* [[Rode VideoMic NTG]]

===Headset===
* [[AudioTechnica BPHS1]]

===Lavalier===
* [[Rode Lavalier GO]]

==Wireless==
===Lavalier===
* [[Rode RODELink Filmmaker Kit]]
* [[Hollyland Lark M2]]
* [[DJI Mic]]

==See Also==
*[[Audio]]

Microphone

2026-08-12T13:30:07Z

E.vandenberge:

{{Infobox tsg
| name = Microphones
| image = Obama2010.jpg
| caption = Shure SM57: the microphone of choice for every US president since 1965, and ours since 2015 or so
}}

Microphones turn sound into data. When you want to record sound for your experiment, please contact the TSG to discuss which microphone(s) is/are best suited for your application. Below is an overview of some of the microphones available within our research labs, and/or for use in the field.



==Varieties==
We categorize microphones by their connection type (wired vs wireless), transducer type, polar pattern, and form factor:
*Dynamic - Typically rugged, versatile, don't require additional phantom power, and can handle loud noises.
*Condenser - More sensitive than dynamic microphones. Require phantom power (24-48V).
*Shotgun - Highly directional, often with an [https://www.dpamicrophones.com/dict/interference-tube/ interference tube] design.
*Lavalier - Tiny, typically clipped onto a person's collar or shirt to record speech.
*Headset - Attached to headphones or headband, with a flexible arm for placement directly in front of the speaker's mouth.

==Wired==
===Dynamic===
* [[Shure SM57]]

===Shotgun===
* [[Sennheiser MKE600]]
* [[Rode VideoMic NTG]]

===Headset===
* [[AudioTechnica BPHS1]]

===Lavalier===
* [[Rode Lavalier GO]]

==Wireless==
===Lavalier===
* [[Rode RODELink Filmmaker Kit]]
* [[Hollyland Lark M2]]
* [[DJI Mic]]

==See Also==
*[[Audio]]

Audio

2026-08-12T13:09:37Z

E.vandenberge: /* Recording */

When using audio in your experiment, especially when presenting time-critical stimuli, special care should be taken to optimize the audio settings on multiple levels (hardware, OS, script), as many things can go wrong along the way.

This page outlines some best practices, however we advise to always consult a TSG member if you plan to run an audio experiment in the labs.

==Recording==
When recording audio for stimuli material or as input for your experiment, please:
* Use a high quality [[Microphone|microphone]], with a [https://www.audio-technica.com/en-us/support/a-brief-guide-to-microphones-whats-the-pattern/ polar pattern] and form-factor suitable for your application.
* Use a high quality recorder or audio interface, capable of recording at 24bit and 48kHz or higher.
* Place the microphone at an appropriate distance from your subject. Set the levels so the audio does not clip (exceeding maximum volume).
* Record in a quiet environment.

You can use our [[Sound Recording Lab]]s for high quality voice recording.

==Editing==
We recommend using Audacity for editing and converting audio files. Audacity is open-source and fairly easy to use, available here: https://www.audacityteam.org/

===Export Settings===
We recommend using the following export settings:
* File format: .wav (PCM).
* Sample Frequency: 48kHz.
* Bit depth: 16 bit.

The [[Lab Computer]] audio output is also set to 16 bit, 48kHz. We found that this is good enough for most applications; higher settings will increase file size with limited perceivable quality gains.

When using multiple audio files in your experiment, make sure they all use the same settings for consistent playback in your experiment.

In Audacity, you can set up Macros to automate processing and exporting your audio files: https://manual.audacityteam.org/man/macros.html

==Windows Settings==
Windows has a habit of automatically enabling '''audio enhancements''' when connecting new speakers or headphones. These "enhancements" can distort your audio and cause timing issues. Therefore, please make sure they are turned off:
# Right click sound icon on taskbar (next to clock) -> Sounds
# Goto Playback tab. Select your audio output device and click "Properties"
# Goto Enhancements tab. Make sure "Disable all enhancements" is checked.
# Click Apply.

==Playback==
=== Psychopy ===
This is an example of a Python script that plays a .wav file with high time accuracy.
<syntaxhighlight lang="python" line>
from psychopy import sound, core
from psychopy import prefs
prefs.hardware['audioLib'] = ['PTB']

# Path to audio file
audio_file = "voice.wav"

# Load audio
# preBuffer – integer to control streaming/buffering -1 means store all
audio = sound.Sound(audio_file,preBuffer=-1)

# Play audio
audio.play()

# Wait for audio to finish playing
core.wait(audio.getDuration())

# Close audio
audio.stop()
audio.close()
</syntaxhighlight>

==See Also==
* [[Audio Interfaces]]

Audio

2026-08-12T13:09:10Z

E.vandenberge: /* Recording */

When using audio in your experiment, especially when presenting time-critical stimuli, special care should be taken to optimize the audio settings on multiple levels (hardware, OS, script), as many things can go wrong along the way.

This page outlines some best practices, however we advise to always consult a TSG member if you plan to run an audio experiment in the labs.

==Recording==
When recording audio for stimuli material or as input for your experiment, please:
* Use a high quality [[Microphone|microphone]], with a [https://www.audio-technica.com/en-us/support/a-brief-guide-to-microphones-whats-the-pattern/ polar pattern] suitable for your application.
* Use a high quality recorder or audio interface, capable of recording at 24bit and 48kHz or higher.
* Place the microphone at an appropriate distance from your subject. Set the levels so the audio does not clip (exceeding maximum volume).
* Record in a quiet environment.

You can use our [[Sound Recording Lab]]s for high quality voice recording.

==Editing==
We recommend using Audacity for editing and converting audio files. Audacity is open-source and fairly easy to use, available here: https://www.audacityteam.org/

===Export Settings===
We recommend using the following export settings:
* File format: .wav (PCM).
* Sample Frequency: 48kHz.
* Bit depth: 16 bit.

The [[Lab Computer]] audio output is also set to 16 bit, 48kHz. We found that this is good enough for most applications; higher settings will increase file size with limited perceivable quality gains.

When using multiple audio files in your experiment, make sure they all use the same settings for consistent playback in your experiment.

In Audacity, you can set up Macros to automate processing and exporting your audio files: https://manual.audacityteam.org/man/macros.html

==Windows Settings==
Windows has a habit of automatically enabling '''audio enhancements''' when connecting new speakers or headphones. These "enhancements" can distort your audio and cause timing issues. Therefore, please make sure they are turned off:
# Right click sound icon on taskbar (next to clock) -> Sounds
# Goto Playback tab. Select your audio output device and click "Properties"
# Goto Enhancements tab. Make sure "Disable all enhancements" is checked.
# Click Apply.

==Playback==
=== Psychopy ===
This is an example of a Python script that plays a .wav file with high time accuracy.
<syntaxhighlight lang="python" line>
from psychopy import sound, core
from psychopy import prefs
prefs.hardware['audioLib'] = ['PTB']

# Path to audio file
audio_file = "voice.wav"

# Load audio
# preBuffer – integer to control streaming/buffering -1 means store all
audio = sound.Sound(audio_file,preBuffer=-1)

# Play audio
audio.play()

# Wait for audio to finish playing
core.wait(audio.getDuration())

# Close audio
audio.stop()
audio.close()
</syntaxhighlight>

==See Also==
* [[Audio Interfaces]]

Rode Lavalier GO

2026-08-12T13:05:14Z

E.vandenberge: Created page with "{{distinguish|Rode RODELink Filmmaker Kit}} {{Infobox tsg | name = RØDE Lavalier GO | image = Rode_lavalier_go.jpg | caption = RØDE Lavalier GO |..."

{{distinguish|Rode RODELink Filmmaker Kit}}

{{Infobox tsg
| name = RØDE Lavalier GO
| image = Rode_lavalier_go.jpg
| caption = RØDE Lavalier GO
| downloads =
}}

The RØDE Lavalier GO is a basic, wired lavalier microphone.



==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDE Lavalier GO
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS
|-
| Accessories || Foam windshield
|}
<references group="fn" /> 

==Usage==
# Connect the microphone to a camera, recorder, or [[Audio Interfaces|audio interface]] (adapter may be required).
# Clip the microphone in place. Usually, this is somewhere around the speaker's chest or collar.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it.
Attach a wind screen when recording outside in windy conditions.

==See Also== 
*[[Microphones]]


<references />

File:Rode lavalier go.jpg

2026-08-12T12:56:54Z

E.vandenberge: Photo of the RØDE Lavalier Go microphone, and its included accessories.

== Summary ==
Photo of the RØDE Lavalier Go microphone, and its included accessories.
== Licensing ==
{{Non-free promotional}}

Rode RODELink Filmmaker Kit

2026-08-12T12:53:23Z

E.vandenberge:

{{distinguish|Rode Lavalier GO}}

{{Infobox tsg
| name = RØDE RØDELink Filmmaker Kit
| image = Rodelink.jpg
| caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories.
| manuals =
}}

The RØDE RØDELink Filmmaker Kit is a wireless lavalier microphone system. It has a bodypack-style transmitter with exchangeable lavalier mic (via 3.5mm jack connector). 
The RØDELink kit has been made somewhat obsolescent by more modern, ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], however it still offers some distinct benefits (see [[#Comparison]]).



==Contents==
The RØDE RØDELink Filmmaker Kit contains:
* 1 Wireless transmitter (TX-BELT)
* 1 Wireless receiver (RX-CAM)
* 1 RØDELink Lav microphone
* Foam wind screen
* Microphone pouch
* 3.5mm jack M-M cable

==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDELink Filmmaker Kit
|-
! Microphone
! scope="row" colspan="2"|
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Accessories || Foam windshield
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS Jack
|-
! Transmitter
! scope="row" colspan="2"|
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Belt-clip/cold-shoe
|-
| Range (m) || 100 (LOS)
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
! Receiver
! scope="row" colspan="2"|
|-
| Connector || 3.5mm jack
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Clip/cold shoe
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
|}
<references group="fn" /> 

ℹ️ The RØDELink Lav microphone is not the same as the [[Rode Lavalier GO]], though we suspect most of its internals are. The RØDELink Lav has a locking 3.5mm connector.

==Usage==
The RØDELink kit has no internal storage, so you will always have to connect it to a separate recording device, like a regular microphone. The transmitter was made to connect to a camera, but can also be connected to XLR recorder or [[Audio Interface]], or even to a PC, phone or laptop, using adapters that we have available.

# Insert batteries into the transmitter and receiver units (press button and slide back cover down), or connect them to a USB power source via microUSB.
# Plug the lavalier microphone into the receiver.
# Connect the receiver to your recording device via 3.5mm jack cable.
# Turn on the transmitter and receiver. They should connect and pair automatically.

⚠️When powering the transmitter and/or receiver via USB, we recommend using clean and isolated power sources like a powerbank, NOT a regular wall-charger. The latter can introduce noise.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it. 
Attach a wind screen when recording outside in windy conditions.

When not using the kit, please remove the batteries from the transmitter and receiver.

==Comparison==
Compared to ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], the RØDELink system offers the following pros & cons:

'''Pros'''
:👍 Swappable batteries, or limitless power via USB. Lets you record long days without having to (remember to) charge internal batteries.
:👍 Smaller mic. The mic itself is smaller because it does not have a built-in transmitter, so it's easier to hide/less obtrusive.
:👍 Replaceable mic. The lavalier mic can potentially be swapped out for other microphone styles, or with other polar patterns.
:👍 Large, readable controls. Big buttons and clear OLED displays make the set fool-proof and easy to use.
:👍 "Unlosable"? The mic connection, sturdy clips, and bulky transmitter make the set harder to accidentally drop, lose, or forget.

'''Cons'''
:👎 Swappable batteries. You need to remember to always pack spare batteries, just in case.
:👎 No digital output. The USB port is for power input only.
:👎 Single channel. Each microphone requires its own transmitter and receiver. Most ultra-compacts offer 2 mics/channels per receiver.
:👎 Wired mic. The mic still connects to the transmitter via wire, which could snag, or has to run underneath your speaker's clothes (=more intrusive)
:👎 No noise-cancelling. Most ultra-compacts offer built-in ANC which helps when recording in noisy environments.
:👎 Bulky. The entire set is bulky and less portable.

The TSG will always consider these tradeoffs when advising a wireless microphone for you to use 🙂

==See Also==
*[[Microphones]]

==External Links==
*[https://rode.com/en-us/products/rodelink-filmmaker-kit Official website]

Microphone

2026-08-12T12:45:15Z

E.vandenberge: /* Wired */

Microphone

2026-08-12T12:40:39Z

E.vandenberge:

Rode RODELink Filmmaker Kit

2026-08-12T12:39:33Z

E.vandenberge:

{{Infobox tsg
| name = RØDE RØDELink Filmmaker Kit
| image = Rodelink.jpg
| caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories.
| manuals =
}}

The RØDE RØDELink Filmmaker Kit is a wireless lavalier microphone system. It has a bodypack-style transmitter with exchangeable lavalier mic (via 3.5mm jack connector). 
The RØDELink kit has been made somewhat obsolescent by more modern, ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], however it still offers some distinct benefits (see [[#Comparison]]).



==Contents==
The RØDE RØDELink Filmmaker Kit contains:
* 1 Wireless transmitter (TX-BELT)
* 1 Wireless receiver (RX-CAM)
* 1 RØDELink Lav microphone
* Foam wind screen
* Microphone pouch
* 3.5mm jack M-M cable

==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDELink Filmmaker Kit
|-
! Microphone
! scope="row" colspan="2"|
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Accessories || Foam windshield
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS Jack
|-
! Transmitter
! scope="row" colspan="2"|
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Belt-clip/cold-shoe
|-
| Range (m) || 100 (LOS)
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
! Receiver
! scope="row" colspan="2"|
|-
| Connector || 3.5mm jack
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Clip/cold shoe
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
|}
<references group="fn" /> 

==Usage==
The RØDELink kit has no internal storage, so you will always have to connect it to a separate recording device, like a regular microphone. The transmitter was made to connect to a camera, but can also be connected to XLR recorder or [[Audio Interface]], or even to a PC, phone or laptop, using adapters that we have available.

# Insert batteries into the transmitter and receiver units (press button and slide back cover down), or connect them to a USB power source via microUSB.
# Plug the lavalier microphone into the receiver.
# Connect the receiver to your recording device via 3.5mm jack cable.
# Turn on the transmitter and receiver. They should connect and pair automatically.

⚠️When powering the transmitter and/or receiver via USB, we recommend using clean and isolated power sources like a powerbank, NOT a regular wall-charger. The latter can introduce noise.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it. 
Attach a wind screen when recording outside in windy conditions.

When not using the kit, please remove the batteries from the transmitter and receiver.

==Comparison==
Compared to ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], the RØDELink system offers the following pros & cons:

'''Pros'''
:👍 Swappable batteries, or limitless power via USB. Lets you record long days without having to (remember to) charge internal batteries.
:👍 Smaller mic. The mic itself is smaller because it does not have a built-in transmitter, so it's easier to hide/less obtrusive.
:👍 Replaceable mic. The lavalier mic can potentially be swapped out for other microphone styles, or with other polar patterns.
:👍 Large, readable controls. Big buttons and clear OLED displays make the set fool-proof and easy to use.
:👍 "Unlosable"? The mic connection, sturdy clips, and bulky transmitter make the set harder to accidentally drop, lose, or forget.

'''Cons'''
:👎 Swappable batteries. You need to remember to always pack spare batteries, just in case.
:👎 No digital output. The USB port is for power input only.
:👎 Single channel. Each microphone requires its own transmitter and receiver. Most ultra-compacts offer 2 mics/channels per receiver.
:👎 Wired mic. The mic still connects to the transmitter via wire, which could snag, or has to run underneath your speaker's clothes (=more intrusive)
:👎 No noise-cancelling. Most ultra-compacts offer built-in ANC which helps when recording in noisy environments.
:👎 Bulky. The entire set is bulky and less portable.

The TSG will always consider these tradeoffs when advising a wireless microphone for you to use 🙂

==See Also==
*[[Microphones]]

==External Links==
*[https://rode.com/en-us/products/rodelink-filmmaker-kit Official website]

Rode RODELink Filmmaker Kit

2026-08-12T12:36:41Z

E.vandenberge: /* Comparison */

{{Infobox tsg
| name = RØDE RØDELink Filmmaker Kit
| image = Rodelink.jpg
| caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories.
| manuals =
}}

The RØDE RØDELink Filmmaker Kit is a wireless lavalier microphone system. It has a bodypack-style transmitter with exchangeable lavalier mic (via 3.5mm jack connector). 
The RØDELink kit has been made somewhat obsolescent by more modern, ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], however it still offers some distinct benefits (see [[#Comparison]]).



==Contents==
The RØDE RØDELink Filmmaker Kit contains:
* 1 Wireless transmitter (TX-BELT)
* 1 Wireless receiver (RX-CAM)
* 1 RØDELink Lav microphone
* Foam wind screen
* Microphone pouch
* 3.5mm jack M-M cable

==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDELink Filmmaker Kit
|-
! Microphone
! scope="row" colspan="2"|
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Accessories || Foam windshield
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS Jack
|-
! Transmitter
! scope="row" colspan="2"|
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Belt-clip/cold-shoe
|-
| Range (m) || 100 (LOS)
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
! Receiver
! scope="row" colspan="2"|
|-
| Connector || 3.5mm jack
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Clip/cold shoe
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
|}
<references group="fn" /> 

==Usage==
The RØDELink kit has no internal storage, so you will always have to connect it to a separate recording device, like a regular microphone. The transmitter was made to connect to a camera, but can also be connected to XLR recorder or [[Audio Interface]], or even to a PC, phone or laptop, using adapters that we have available.

# Insert batteries into the transmitter and receiver units (press button and slide back cover down), or connect them to a USB power source via microUSB.<ref>When powering the transmitter and/or receiver via USB, we recommend using clean and isolated power sources like a powerbank, NOT a regular wall-charger. The latter can introduce noise.</ref>
# Plug the lavalier microphone into the receiver.
# Connect the receiver to your recording device via 3.5mm jack cable.
# Turn on the transmitter and receiver. They should connect and pair automatically.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it. 
Attach a wind screen when recording outside in windy conditions.

When not using the kit, please remove the batteries from the transmitter and receiver.

==Comparison==
Compared to ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], the RØDELink system offers the following pros & cons:

'''Pros'''
:👍 Swappable batteries, or limitless power via USB. Lets you record long days without having to (remember to) charge internal batteries.
:👍 Smaller mic. The mic itself is smaller because it does not have a built-in transmitter, so it's easier to hide/less obtrusive.
:👍 Replaceable mic. The lavalier mic can potentially be swapped out for other microphone styles, or with other polar patterns.
:👍 Large, readable controls. Big buttons and clear OLED displays make the set fool-proof and easy to use.
:👍 "Unlosable"? The mic connection, sturdy clips, and bulky transmitter make the set harder to accidentally drop, lose, or forget.

'''Cons'''
:👎 Swappable batteries. You need to remember to always pack spare batteries, just in case.
:👎 No digital output. The USB port is for power input only.
:👎 Single channel. Each microphone requires its own transmitter and receiver. Most ultra-compacts offer 2 mics/channels per receiver.
:👎 Wired mic. The mic still connects to the transmitter via wire, which could snag, or has to run underneath your speaker's clothes (=more intrusive)
:👎 No noise-cancelling. Most ultra-compacts offer built-in ANC which helps when recording in noisy environments.
:👎 Bulky. The entire set is bulky and less portable.

The TSG will always consider these tradeoffs when advising a wireless microphone for you to use 🙂

==See Also==
*[[Microphones]]

==External Links==
*[https://rode.com/en-us/products/rodelink-filmmaker-kit Official website]

==References==
<references />

Main Page

2026-08-12T12:33:44Z

E.vandenberge:

Welcome to the TSG Wiki!

On this wiki you will find documentation for the Hardware, Software and Research Equipment used in the lab environments of the research facilities of the Radboud University's [http://www.ru.nl/socialsciences Faculty of Social Sciences], as well as other useful information. 
To learn more about the Technical Support Group, visit [http://www.ru.nl/socialsciences/technicalsupportgroup/ our website] or the [[TSG info|about]] section.


<div style="width:100%;">
{{Main Page/Frame
| color = be311a
| title = 📄Hardware Documentation
| content = {{Bulleted list
| [[Audio Interface]]s
| [[Balance Board]]
| [[Biopac]]
| [[Brainvision]]
| [[ButtonBox]]es
| [[Camera]]s
| [[Lab Computer|Computers]]
| [[Eyetracker]]s
| [[Head Mounted Display]]s
| [[Headphones]]
| [[Ipod]] (Video & Audio Recording)
| [[JoyStick]]s
| [[Kinect]]
| [[Laptop]]s
| [[Microphone]]s
| [[Monitor]]s
| [[Optotrak]]
| [[Plux biosignals]]
| [[Qualisys]]
| [[Structure sensor]]
| [[TemperatureHumidity|TemperatureHumidity sensor]]
| [[TMSi]]
| [[Vertical Sync sensor]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📃Software Documentation
| content = {{Bulleted list
| [[FFmpeg]] (Video Conversion)
| [[LSL]]
| [[Matlab]]
| [[OBS Studio]] (Screen/Webcam Recording)
| [[Presentation]]
| [[Psychopy]]
| [[Python]]
| [[System Image]]
| [[Unity]]
}} 
;Online Experiments
{{Bulleted list
| [[Online Experiments|Overview of Online Systems]]
| [[jsPsych]]
| [[LimeSurvey]] (Online Questionnaires)
| [[Online Experiments/Toolbox|Toolbox for online experiments]]
| [[Web development]]
}} 
;Data Acquisition
{{Bulleted list
| [[Data Files|Data Formatting]]
| [[Radcloud]]
}} 
;Stimuli
{{Bulleted list
| [[Audio]]
| [[Video Codecs]]
| [[Video Playback]]
}} 
;Miscellaneous
{{Bulleted list

| [[Gitlab Social Sciences]]
| [[IP Distribution Lab Computer]]
| [[Mattermost Social Sciences]]
| [[Virtualization Server]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📄Lab Documentation
| content = {{Bulleted list
| [[BalanceBoard Lab]]

| [[Cubicle]]s (Standard Labs)
| [[EEG Lab]]
| [[Eye Tracker Lab]]
| [[RIVER Lab]] (Virtual Reality)
| [[SensoriMotorLab]]
| [[Social Interaction Lab]]
| [[Sound Recording Lab]]

| [[TMS Lab]]
}} 
;Lab Use Policy and Guidelines
{{Bulleted list
| [[Booking labs]]
| [[Media:EEG_lab_user_guide.pdf|EEG lab user guide]]
| [[Media:Cleaningprocedure_EEG.pdf|EEG cleaning protocol]]
| [[Using labs]]
| [[Informed consent]]
}}
}}

</div>

Main Page

2026-08-12T12:33:26Z

E.vandenberge:

Welcome to the TSG Wiki!

On this wiki you will find documentation for the Hardware, Software and Research Equipment used in the lab environments of the research facilities of the [http://www.ru.nl/socialsciences Radboud University's Faculty of Social Sciences], as well as other useful information. 
To learn more about the Technical Support Group, visit [http://www.ru.nl/socialsciences/technicalsupportgroup/ our website] or the [[TSG info|about]] section.


<div style="width:100%;">
{{Main Page/Frame
| color = be311a
| title = 📄Hardware Documentation
| content = {{Bulleted list
| [[Audio Interface]]s
| [[Balance Board]]
| [[Biopac]]
| [[Brainvision]]
| [[ButtonBox]]es
| [[Camera]]s
| [[Lab Computer|Computers]]
| [[Eyetracker]]s
| [[Head Mounted Display]]s
| [[Headphones]]
| [[Ipod]] (Video & Audio Recording)
| [[JoyStick]]s
| [[Kinect]]
| [[Laptop]]s
| [[Microphone]]s
| [[Monitor]]s
| [[Optotrak]]
| [[Plux biosignals]]
| [[Qualisys]]
| [[Structure sensor]]
| [[TemperatureHumidity|TemperatureHumidity sensor]]
| [[TMSi]]
| [[Vertical Sync sensor]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📃Software Documentation
| content = {{Bulleted list
| [[FFmpeg]] (Video Conversion)
| [[LSL]]
| [[Matlab]]
| [[OBS Studio]] (Screen/Webcam Recording)
| [[Presentation]]
| [[Psychopy]]
| [[Python]]
| [[System Image]]
| [[Unity]]
}} 
;Online Experiments
{{Bulleted list
| [[Online Experiments|Overview of Online Systems]]
| [[jsPsych]]
| [[LimeSurvey]] (Online Questionnaires)
| [[Online Experiments/Toolbox|Toolbox for online experiments]]
| [[Web development]]
}} 
;Data Acquisition
{{Bulleted list
| [[Data Files|Data Formatting]]
| [[Radcloud]]
}} 
;Stimuli
{{Bulleted list
| [[Audio]]
| [[Video Codecs]]
| [[Video Playback]]
}} 
;Miscellaneous
{{Bulleted list

| [[Gitlab Social Sciences]]
| [[IP Distribution Lab Computer]]
| [[Mattermost Social Sciences]]
| [[Virtualization Server]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📄Lab Documentation
| content = {{Bulleted list
| [[BalanceBoard Lab]]

| [[Cubicle]]s (Standard Labs)
| [[EEG Lab]]
| [[Eye Tracker Lab]]
| [[RIVER Lab]] (Virtual Reality)
| [[SensoriMotorLab]]
| [[Social Interaction Lab]]
| [[Sound Recording Lab]]

| [[TMS Lab]]
}} 
;Lab Use Policy and Guidelines
{{Bulleted list
| [[Booking labs]]
| [[Media:EEG_lab_user_guide.pdf|EEG lab user guide]]
| [[Media:Cleaningprocedure_EEG.pdf|EEG cleaning protocol]]
| [[Using labs]]
| [[Informed consent]]
}}
}}

</div>

Main Page

2026-08-12T12:32:57Z

E.vandenberge:

Welcome to the TSG Wiki!

On this wiki you will find documentation for the Hardware, Software and Research Equipment used in the lab environments of the research facilities of the [http://www.ru.nl Radboud University]'s [http://www.ru.nl/socialsciences Faculty of Social Sciences], as well as other useful information. 
To learn more about the Technical Support Group, visit [http://www.ru.nl/socialsciences/technicalsupportgroup/ our website] or the [[TSG info|about]] section.


<div style="width:100%;">
{{Main Page/Frame
| color = be311a
| title = 📄Hardware Documentation
| content = {{Bulleted list
| [[Audio Interface]]s
| [[Balance Board]]
| [[Biopac]]
| [[Brainvision]]
| [[ButtonBox]]es
| [[Camera]]s
| [[Lab Computer|Computers]]
| [[Eyetracker]]s
| [[Head Mounted Display]]s
| [[Headphones]]
| [[Ipod]] (Video & Audio Recording)
| [[JoyStick]]s
| [[Kinect]]
| [[Laptop]]s
| [[Microphone]]s
| [[Monitor]]s
| [[Optotrak]]
| [[Plux biosignals]]
| [[Qualisys]]
| [[Structure sensor]]
| [[TemperatureHumidity|TemperatureHumidity sensor]]
| [[TMSi]]
| [[Vertical Sync sensor]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📃Software Documentation
| content = {{Bulleted list
| [[FFmpeg]] (Video Conversion)
| [[LSL]]
| [[Matlab]]
| [[OBS Studio]] (Screen/Webcam Recording)
| [[Presentation]]
| [[Psychopy]]
| [[Python]]
| [[System Image]]
| [[Unity]]
}} 
;Online Experiments
{{Bulleted list
| [[Online Experiments|Overview of Online Systems]]
| [[jsPsych]]
| [[LimeSurvey]] (Online Questionnaires)
| [[Online Experiments/Toolbox|Toolbox for online experiments]]
| [[Web development]]
}} 
;Data Acquisition
{{Bulleted list
| [[Data Files|Data Formatting]]
| [[Radcloud]]
}} 
;Stimuli
{{Bulleted list
| [[Audio]]
| [[Video Codecs]]
| [[Video Playback]]
}} 
;Miscellaneous
{{Bulleted list

| [[Gitlab Social Sciences]]
| [[IP Distribution Lab Computer]]
| [[Mattermost Social Sciences]]
| [[Virtualization Server]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📄Lab Documentation
| content = {{Bulleted list
| [[BalanceBoard Lab]]

| [[Cubicle]]s (Standard Labs)
| [[EEG Lab]]
| [[Eye Tracker Lab]]
| [[RIVER Lab]] (Virtual Reality)
| [[SensoriMotorLab]]
| [[Social Interaction Lab]]
| [[Sound Recording Lab]]

| [[TMS Lab]]
}} 
;Lab Use Policy and Guidelines
{{Bulleted list
| [[Booking labs]]
| [[Media:EEG_lab_user_guide.pdf|EEG lab user guide]]
| [[Media:Cleaningprocedure_EEG.pdf|EEG cleaning protocol]]
| [[Using labs]]
| [[Informed consent]]
}}
}}

</div>

Main Page

2026-08-12T12:31:12Z

E.vandenberge: Removed Qualtrics link now that the platform is no longer supported by the faculty

Welcome to the TSG Wiki!

On this wiki you will find documentation for the Hardware, Software and Research Equipment used in the lab environments of the research facilities of the Radboud University's Faculty of Social Sciences, as well as other useful information. 
To learn more about the Technical Support Group, visit [http://www.ru.nl/socialsciences/technicalsupportgroup/ our website] or the [[TSG info|about]] section.


<div style="width:100%;">
{{Main Page/Frame
| color = be311a
| title = 📄Hardware Documentation
| content = {{Bulleted list
| [[Audio Interface]]s
| [[Balance Board]]
| [[Biopac]]
| [[Brainvision]]
| [[ButtonBox]]es
| [[Camera]]s
| [[Lab Computer|Computers]]
| [[Eyetracker]]s
| [[Head Mounted Display]]s
| [[Headphones]]
| [[Ipod]] (Video & Audio Recording)
| [[JoyStick]]s
| [[Kinect]]
| [[Laptop]]s
| [[Microphone]]s
| [[Monitor]]s
| [[Optotrak]]
| [[Plux biosignals]]
| [[Qualisys]]
| [[Structure sensor]]
| [[TemperatureHumidity|TemperatureHumidity sensor]]
| [[TMSi]]
| [[Vertical Sync sensor]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📃Software Documentation
| content = {{Bulleted list
| [[FFmpeg]] (Video Conversion)
| [[LSL]]
| [[Matlab]]
| [[OBS Studio]] (Screen/Webcam Recording)
| [[Presentation]]
| [[Psychopy]]
| [[Python]]
| [[System Image]]
| [[Unity]]
}} 
;Online Experiments
{{Bulleted list
| [[Online Experiments|Overview of Online Systems]]
| [[jsPsych]]
| [[LimeSurvey]] (Online Questionnaires)
| [[Online Experiments/Toolbox|Toolbox for online experiments]]
| [[Web development]]
}} 
;Data Acquisition
{{Bulleted list
| [[Data Files|Data Formatting]]
| [[Radcloud]]
}} 
;Stimuli
{{Bulleted list
| [[Audio]]
| [[Video Codecs]]
| [[Video Playback]]
}} 
;Miscellaneous
{{Bulleted list

| [[Gitlab Social Sciences]]
| [[IP Distribution Lab Computer]]
| [[Mattermost Social Sciences]]
| [[Virtualization Server]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📄Lab Documentation
| content = {{Bulleted list
| [[BalanceBoard Lab]]

| [[Cubicle]]s (Standard Labs)
| [[EEG Lab]]
| [[Eye Tracker Lab]]
| [[RIVER Lab]] (Virtual Reality)
| [[SensoriMotorLab]]
| [[Social Interaction Lab]]
| [[Sound Recording Lab]]

| [[TMS Lab]]
}} 
;Lab Use Policy and Guidelines
{{Bulleted list
| [[Booking labs]]
| [[Media:EEG_lab_user_guide.pdf|EEG lab user guide]]
| [[Media:Cleaningprocedure_EEG.pdf|EEG cleaning protocol]]
| [[Using labs]]
| [[Informed consent]]
}}
}}

</div>

Qualtrics

2026-08-12T12:26:53Z

E.vandenberge:

{{Infobox software
| name = Qualtrics
| logo = QualtricsLogo.png
| logo size = 180px
| logo alt = Qualtrics
| caption =
| developer =
| released = 
| discontinued =
| latest release version =
| latest release date = 
| latest preview version =
| latest preview date = 
| installed version =
| installed version date = 
| status =
| programming language =
| operating system =
| platform = Web
| website = [https://www.qualtrics.com/ qualtrics.com]
| resources = {{Infobox tsg
| child = yes
| header1 = FSW User Login
| data1 = *[https://psychru.eu.qualtrics.com/login PsychRU Login Page]
}}
}}

{{Warn|'''The Faculty of Social Sciences has stopped the use of Qualtrics per August 1, 2026 (December 1 for researchers)<ref>https://www.ru.nl/en/staff/news/phasing-out-qualtrics</ref> Employees and students are advised to create their surveys in [[LimeSurvey]] instead.'''}}

Qualtrics calls itself "Experience Management Software". We call it an online survey tool. Use of Qualtrics requires a subscription.

The TSG does not provide support for Qualtrics, as online support by Qualtrics is included in the subscription. However, we can help with custom code if needed (HTML, CSS, Javascript).

== Usage ==
While Qualtrics is a US-based company, using their service is allowed under General Data Protection Regulation (GDPR) since the Faculty and the Supplier have a data processing agreement. Usage is only allowed for those purposes where ''on campus'' storage of data is not considered necessary.

=== Help ===
Please use the Qualtrics ''help > contact support'' function to contact the Support Center.

For help with your account or data management, find contact details to our data officer and Qualtrics administrator on [https://www.radboudnet.nl/bsi/research-facilities-0/online-research/surveys#Qualtrics RadboudNet] (login required).

== Tweaks ==
To add custom JavaScript, click the gear icon (Advanced Question Options) next to a question and click ''Add JavaScript...'' Here are two examples:
=== Check for leaving page ===
<pre>
var leaveDates = []
function handleLeave(event) {
console.log("out")
leaveDates.push(new Date().toISOString())
alert("Please don't leave the window")
}
Qualtrics.SurveyEngine.addOnload(function(){
console.log("load")
document.getElementById("Page").addEventListener("mouseleave", handleLeave, false)
})

Qualtrics.SurveyEngine.addOnUnload(function(){
console.log("unload")
document.getElementById("Page").removeEventListener("mouseleave", handleLeave, false)
Qualtrics.SurveyEngine.setEmbeddedData("date", leaveDates.join(","))
})
</pre>

=== prevent cutting and pasting ===
Use the following code to prevent cutting and pasting from and to text fields, expect people to become angry if you use this.
<pre>
Qualtrics.SurveyEngine.addOnReady(function(){
/* Place your JavaScript here to run when the page is fully displayed */
ee = document.getElementsByClassName("InputText")
for(e of ee){
e.onpaste=function(){ return false }
e.oncut=function(){ return false }
}
})
</pre>

==References==
<references/>

Main Page

2026-08-12T12:25:56Z

E.vandenberge:

Welcome to the TSG Wiki!

On this wiki you will find documentation for the Hardware, Software and Research Equipment used in the lab environments of the research facilities of the Radboud University's Faculty of Social Sciences, as well as other useful information. 
To learn more about the Technical Support Group, visit [http://www.ru.nl/socialsciences/technicalsupportgroup/ our website] or the [[TSG info|about]] section.


<div style="width:100%;">
{{Main Page/Frame
| color = be311a
| title = 📄Hardware Documentation
| content = {{Bulleted list
| [[Audio Interface]]s
| [[Balance Board]]
| [[Biopac]]
| [[Brainvision]]
| [[ButtonBox]]es
| [[Camera]]s
| [[Lab Computer|Computers]]
| [[Eyetracker]]s
| [[Head Mounted Display]]s
| [[Headphones]]
| [[Ipod]] (Video & Audio Recording)
| [[JoyStick]]s
| [[Kinect]]
| [[Laptop]]s
| [[Microphone]]s
| [[Monitor]]s
| [[Optotrak]]
| [[Plux biosignals]]
| [[Qualisys]]
| [[Structure sensor]]
| [[TemperatureHumidity|TemperatureHumidity sensor]]
| [[TMSi]]
| [[Vertical Sync sensor]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📃Software Documentation
| content = {{Bulleted list
| [[FFmpeg]] (Video Conversion)
| [[LSL]]
| [[Matlab]]
| [[OBS Studio]] (Screen/Webcam Recording)
| [[Presentation]]
| [[Psychopy]]
| [[Python]]
| [[System Image]]
| [[Unity]]
}} 
;Online Experiments
{{Bulleted list
| [[Online Experiments|Overview of Online Systems]]
| [[jsPsych]]
| [[LimeSurvey]] (Online Questionnaires)
| [[Qualtrics]]
| [[Online Experiments/Toolbox|Toolbox for online experiments]]
| [[Web development]]
}} 
;Data Acquisition
{{Bulleted list
| [[Data Files|Data Formatting]]
| [[Radcloud]]
}} 
;Stimuli
{{Bulleted list
| [[Audio]]
| [[Video Codecs]]
| [[Video Playback]]
}} 
;Miscellaneous
{{Bulleted list

| [[Gitlab Social Sciences]]
| [[IP Distribution Lab Computer]]
| [[Mattermost Social Sciences]]
| [[Virtualization Server]]
}}
}}

{{Main Page/Frame
| color = be311a
| title = 📄Lab Documentation
| content = {{Bulleted list
| [[BalanceBoard Lab]]

| [[Cubicle]]s (Standard Labs)
| [[EEG Lab]]
| [[Eye Tracker Lab]]
| [[RIVER Lab]] (Virtual Reality)
| [[SensoriMotorLab]]
| [[Social Interaction Lab]]
| [[Sound Recording Lab]]

| [[TMS Lab]]
}} 
;Lab Use Policy and Guidelines
{{Bulleted list
| [[Booking labs]]
| [[Media:EEG_lab_user_guide.pdf|EEG lab user guide]]
| [[Media:Cleaningprocedure_EEG.pdf|EEG cleaning protocol]]
| [[Using labs]]
| [[Informed consent]]
}}
}}

</div>

TemperatureHumidity

2026-08-12T12:25:22Z

E.vandenberge:

{{Infobox tsg
| name = TemperatureHumidity
| image =
| caption = TemperatureHumidity device
| downloads = {{bulleted list
| {{Download link|media=temperaturehumidity.zip|Custom Module|zip}}
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)
}}
}}

The TemperatureHumidity device is a little (15 x 5 x 5 cm) black box with a black sphere on top. As the name suggests, it can measure temperature and humidity.

You can attach the device to a PC via USB. When connected, it will identify itself as a virtual serial port.

== Installation ==
Install the ''rusocsci'' package. On the lab computers it may already be installed for you. Also install ''pytz'', ''python-dateutil'' and ''pyqt4''. Download the {{Download link|media=temperaturehumidity.zip|temperaturehumidity module}} and unzip it in the same directory as your experiment.

== Testing ==
Run the temperaturehumidity module and sensor by running the file 'temperaturehumidity.py'. Double click it in explorer or load in the Psychopy Coder and click 'run'.

== Code example ==
You can read temperature and humidity values with any software that connects to a serial port. Most conveniently you can use the [https://pypi.python.org/pypi/RuSocSci RuSocSci] library in python. Here is a little example how to write a script that reads the temperature and humidity and writes it to the standard output (console):
<syntaxhighlight lang="python">
#!/usr/bin/env python3
import temperaturehumidity
th = temperaturehumidity.TemperatureHumidity()
print(th.waitString())
</syntaxhighlight>

== Potential problems ==
The temperaturehumidity device identifies as a buttonbox. Lab computer are set up in a way that makes the second buttonbox behave different from all other devices. If you are using both the buttonbox and the temperaturehumidity device, please look up the port name of the temperaturehumidity device in the windows device manager and if it is for instance 'COM3' then change the code above into:
<syntaxhighlight lang="python">
#!/usr/bin/env python3
import temperaturehumidity
th = temperaturehumidity.TemperatureHumidity(port='COM3')
print(th.waitString())
</syntaxhighlight>

TemperatureHumidity

2026-08-12T12:23:04Z

E.vandenberge:

{{Infobox tsg
| name = TemperatureHumidity
| image =
| caption = TemperatureHumidity device
| downloads = {{bulleted list
| {{Download link|media=temperaturehumidity.zip|Custom Module|zip}}
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)
}}
}}

The TemperatureHumidity is a little (15 x 5 x 5 cm) black box with a black sphere on top. It is connected to your computer with the attached USB cable. When connected it will identify itself as a Virtual Serial port.

== Installation ==
Install the ''rusocsci'' package. On the lab computers it may already be installed for you. Also install ''pytz'', ''python-dateutil'' and ''pyqt4''. Download the {{Download link|media=temperaturehumidity.zip|temperaturehumidity module}} and unzip it in the same directory as your experiment.

== Testing ==
Run the temperaturehumidity module and sensor by running the file 'temperaturehumidity.py'. Double click it in explorer or load in the Psychopy Coder and click 'run'.

== Code example ==
You can read temperature and humidity values with any software that connects to a serial port. Most conveniently you can use the [https://pypi.python.org/pypi/RuSocSci RuSocSci] library in python. Here is a little example how to write a script that reads the temperature and humidity and writes it to the standard output (console):
<syntaxhighlight lang="python">
#!/usr/bin/env python3
import temperaturehumidity
th = temperaturehumidity.TemperatureHumidity()
print(th.waitString())
</syntaxhighlight>

== Potential problems ==
The temperaturehumidity device identifies as a buttonbox. Lab computer are set up in a way that makes the second buttonbox behave different from all other devices. If you are using both the buttonbox and the temperaturehumidity device, please look up the port name of the temperaturehumidity device in the windows device manager and if it is for instance 'COM3' then change the code above into:
<syntaxhighlight lang="python">
#!/usr/bin/env python3
import temperaturehumidity
th = temperaturehumidity.TemperatureHumidity(port='COM3')
print(th.waitString())
</syntaxhighlight>

Camcorder

2026-08-12T12:21:12Z

E.vandenberge: /* Specifications */

{{Infobox tsg
| name = Camcorder
| image = Canon_legria_hf_g26_videocamera_caleghfg262.jpg
| caption = Canon Legria HF G26 Camcorder
| manuals = {{bulleted list
| {{Download link|media=Fsw-canon_legria_hf_g26-quickstart.pdf|Canon Legria HF G26 Quick Start Guide|pdf}}
| {{Download link|media=Legriahfg26-im2-en.pdf|Canon Legria HF G26 User Manual|pdf}}
| [https://hk.canon/en/support/0303440301 Canon XF405 Manual]
}}
}}

Camcorders are video recording devices used to create stimuli and/or record participant behavior during research experiments. In an effort to standardize video recording formats and control interfaces, the TSG has adopted the Canon Legria and XA/XF ranges of camcorders for use in our research labs (effective 2019). For simple, more user-friendly video recordings, you can use [[Ipod|iPods]]

==Specifications==

{| class="wikitable"
|-
! style="width:200px;"|
! style="width:200px;"| [[File:Canon_legria_hf_g26_videocamera_caleghfg262.jpg ‎|200px|Image: 200 pixels]]
! style="width:200px;"| [[File:Canon-XF405-Side-Front.jpg ‎|200px|Image: 200 pixels]]
|-
! 
! Canon Legria HF G26
! Canon XF405
|-
| Sensor || 1/2.84" CMOS || 1.0" CMOS
|-
| Max. Resolution (pixels) || 1920 x 1080 (Full HD) || 3830 x 2160 (4K)
|-
| Supported frame rates || 25p, 50i || 25p, 50p
|-
| Recording formats || AVCHD, MP4<ref group="sp" name="format">Maximum bit rate, resolution and frame rate may be limited when choosing MP4</ref> || XF-AVC, MP4<ref group="sp" name="format"/>
|-
! I/O
! colspan="2"| 
|-
| Recording Medium || SD card || SD card
|-
| Video Outputs || Mini A/V, HDMI || HDMI, 3G-SDI<ref group="sp">3G-SDI video output limits resolution to 1080p.</ref>
|-
| Headphone Output
| style="background-color:#9F9;" | Yes
| style="background-color:#9F9;" | Yes
|-
| Microphone Inputs || 1x 3.5mm jack || 2x XLR (+phantom)
|-
|}
<references group="sp" /> 

==Usage==
===Observation===
The most common use of our camcorders is to record participant behavior in our labs. Be aware of your recording settings when filming many participants for many hours: the higher the resolution, framerate and bitrate, the larger the file size. Large files may take a long time to transfer and backup, and will cost the faculty a lot of server storage space when archived in Workgroup folders and Data repositories. The TSG advices the following settings for general purpose recordings for an optimal quality to file-size ratio, as well as for easy importing in any video coding software:
{| class="wikitable"
|-
| Format || MP4
|-
| Resolution || 1280 * 720 pixels (720p)
|-
| Framerate || 25 fps (progressive)
|-
| Bitrate || 4 Mbps (for h264 codec)
|-
|}

If you wish to record highly detailed movements, or retain more detail over larger distances, increase the resolution and bitrate. In most cameras these values are linked. Check the user manual or our quick start guide for your camera model to see how to adjust these settings.

===Stimuli Recording===
If you wish to use our camcorders to record video for creating stimuli, please contact [[Erik van den Berge]].

==See Also==
*[[Cameras]]
*[[Video Codecs]]

Social Interaction Lab

2026-08-12T12:08:14Z

E.vandenberge:

{{Under construction}} 

{{Infobox tsg
| name = Social Interaction Lab
| image =
| caption =
| location = MM 00.453
| manuals =
}}

The Social Interaction Lab is designed as a flexible space for observing and recording social interactions between two or more individuals. It can also be used to record AV stimuli.



=Physical Properties=
The lab measures about 4x5m, with a high ceiling of 3.8m. The floor is carpeted, and all 4 walls (incuding the door) can be covered with dark green curtains to minimize reverb and provide a darker, more uniform video background.
The lab does not contain any fixed setup of equipment or furniture, except for a skyrail system to which cameras, microphones, lights, and other gear can be suspended.

=Equipment=
==Video Recording==
The Social Interaction Lab is equipped with Canon XF405 [[Camcorders]]. They are connected to a recording PC via SDI, where up to 4 cameras can be recorded simultaneously using Metus INGEST software.
Note: recording resolution of the XF405 is limited to 1080p over SDI. For 4K recording, you will have to use SD cards.

Camcorders are mounted on motorized pan-tilt heads, which can be operated remotely, so you can adjust the camera angle at any moment. Some camera settings can also be adjusted remotely.

==Lighting==
When recording video, we recommend placing additional lights in the lab to create more even lighting of your subject(s). The regular lab lights, while flicker-free, can create harsh shadows and banding issues.
===Available lighting equipment===
* 2x Amaran F22x LED panel (60*60cm, 200W, Bi-Color)⚠️
* 2x Amaran F21x LED panel (60*30cm, 100W, Bi-Color)
* 1x Amaran F21c LED panel (60x30cm, 100W, RGBWW)
* 2x Amaran COB 60xS (60W, Bi-Color)⚠️

⚠️ ''Indicated lights contain a fan that may that may impact audio recordings. ''

'''Modifiers:'''
* 1x Lantern for Amaran F22x
* 2x Barn doors for Amaran COB.

==Audio Recording==
For recording audio (along with video, or separately), we typically use [[Sennheiser MKE600]] shotgun microphones, boomed overhead. There are typically up to 4 such microphones available in the lab; the exact amount and positioning will depend on your situation.

Microphones can be simultaneously connected to a camera (for recording on video) and an LSL streaming device, e.g. for synchronising audio and video to other measurement devices.

==Motion Capture==
The Social Interaction Lab is home to a [[Qualisys]] system consisting of 10 Miqus Hybrid cameras. These cameras can be used for both marker tracking and markerless tracking.

If you wish to use motion capture in your experiment, or for creating stimuli, please contact the TSG. They will help you with camera placement and settings for optimal recording quality, as well as instruct you on how to use the system <ref>We currently do not provide support for markerless tracking</ref>

=Usage=
Contact the TSG for instructions.

=References=
<references />

Social Interaction Lab

2026-08-12T12:07:36Z

E.vandenberge: /* Available lighting equipment */

{{Under construction}} 

{{Infobox tsg
| name = Social Interaction Lab
| image =
| caption =
| location = MM 00.453
| manuals =
}}

The Social Interaction Lab is designed as a flexible space for observing and recording social interactions between two or more individuals. It can also be used to record AV stimuli.



==Physical Properties==
The lab measures about 4x5m, with a high ceiling of 3.8m. The floor is carpeted, and all 4 walls (incuding the door) can be covered with dark green curtains to minimize reverb and provide a darker, more uniform video background.
The lab does not contain any fixed setup of equipment or furniture, except for a skyrail system to which cameras, microphones, lights, and other gear can be suspended.

==Equipment==
===Video Recording===
The Social Interaction Lab is equipped with Canon XF405 [[Camcorders]]. They are connected to a recording PC via SDI, where up to 4 cameras can be recorded simultaneously using Metus INGEST software.
Note: recording resolution of the XF405 is limited to 1080p over SDI. For 4K recording, you will have to use SD cards.

Camcorders are mounted on motorized pan-tilt heads, which can be operated remotely, so you can adjust the camera angle at any moment. Some camera settings can also be adjusted remotely.

===Lighting===
When recording video, we recommend placing additional lights in the lab to create more even lighting of your subject(s). The regular lab lights, while flicker-free, can create harsh shadows and banding issues.
====Available lighting equipment====
* 2x Amaran F22x LED panel (60*60cm, 200W, Bi-Color)⚠️
* 2x Amaran F21x LED panel (60*30cm, 100W, Bi-Color)
* 1x Amaran F21c LED panel (60x30cm, 100W, RGBWW)
* 2x Amaran COB 60xS (60W, Bi-Color)⚠️

⚠️ ''Indicated lights contain a fan that may that may impact audio recordings. ''

'''Modifiers:'''
* 1x Lantern for Amaran F22x
* 2x Barn doors for Amaran COB.

===Audio Recording===
For recording audio (along with video, or separately), we typically use [[Sennheiser MKE600]] shotgun microphones, boomed overhead. There are typically up to 4 such microphones available in the lab; the exact amount and positioning will depend on your situation.

Microphones can be simultaneously connected to a camera (for recording on video) and an LSL streaming device, e.g. for synchronising audio and video to other measurement devices.

===Motion Capture===
The Social Interaction Lab is home to a [[Qualisys]] system consisting of 10 Miqus Hybrid cameras. These cameras can be used for both marker tracking and markerless tracking.

If you wish to use motion capture in your experiment, or for creating stimuli, please contact the TSG. They will help you with camera placement and settings for optimal recording quality, as well as instruct you on how to use the system <ref>We currently do not provide support for markerless tracking</ref>

==Usage==
Contact the TSG for instructions.

==References==
<references />

Social Interaction Lab

2026-08-12T12:05:14Z

E.vandenberge: /* Available lighting equipment */

{{Under construction}} 

{{Infobox tsg
| name = Social Interaction Lab
| image =
| caption =
| location = MM 00.453
| manuals =
}}

The Social Interaction Lab is designed as a flexible space for observing and recording social interactions between two or more individuals. It can also be used to record AV stimuli.



==Physical Properties==
The lab measures about 4x5m, with a high ceiling of 3.8m. The floor is carpeted, and all 4 walls (incuding the door) can be covered with dark green curtains to minimize reverb and provide a darker, more uniform video background.
The lab does not contain any fixed setup of equipment or furniture, except for a skyrail system to which cameras, microphones, lights, and other gear can be suspended.

==Equipment==
===Video Recording===
The Social Interaction Lab is equipped with Canon XF405 [[Camcorders]]. They are connected to a recording PC via SDI, where up to 4 cameras can be recorded simultaneously using Metus INGEST software.
Note: recording resolution of the XF405 is limited to 1080p over SDI. For 4K recording, you will have to use SD cards.

Camcorders are mounted on motorized pan-tilt heads, which can be operated remotely, so you can adjust the camera angle at any moment. Some camera settings can also be adjusted remotely.

===Lighting===
When recording video, we recommend placing additional lights in the lab to create more even lighting of your subject(s). The regular lab lights, while flicker-free, can create harsh shadows and banding issues.
====Available lighting equipment====
* 2x Amaran F22x LED panel (60*60cm, 200W, Bi-Color)<ref group="fn" name="noisyboy">This light has a fan that may impact audio recordings</ref>
* 2x Amaran F21x LED panel (60*30cm, 100W, Bi-Color)
* 1x Amaran F21c LED panel (60x30cm, 100W, RGBWW)
* 2x Amaran COB 60xS (60W, Bi-Color)<ref group="fn" name="noisyboy" />

Modifiers:
* 1x Lantern for Amaran F22x
* 2x Barn doors for Amaran COB.

'''Notes'''
<references group="fn"/>

===Audio Recording===
For recording audio (along with video, or separately), we typically use [[Sennheiser MKE600]] shotgun microphones, boomed overhead. There are typically up to 4 such microphones available in the lab; the exact amount and positioning will depend on your situation.

Microphones can be simultaneously connected to a camera (for recording on video) and an LSL streaming device, e.g. for synchronising audio and video to other measurement devices.

===Motion Capture===
The Social Interaction Lab is home to a [[Qualisys]] system consisting of 10 Miqus Hybrid cameras. These cameras can be used for both marker tracking and markerless tracking.

If you wish to use motion capture in your experiment, or for creating stimuli, please contact the TSG. They will help you with camera placement and settings for optimal recording quality, as well as instruct you on how to use the system <ref>We currently do not provide support for markerless tracking</ref>

==Usage==
Contact the TSG for instructions.

==References==
<references />

BCI Lab

2026-08-12T11:57:25Z

E.vandenberge:

{{Outdated}}

{{Infobox tsg
| name = EEG BCI Labs
| image =
| caption =
| manuals = {{bulleted list
| {{Download link|media=Connection_diagram_lab1-with_behringer.pdf|Connection Scheme lab 1|pdf}}
| {{Download link|media=Connection_diagram_lab2-with_behringer.pdf|Connection Scheme lab 2|pdf}}
| {{Download link|media=Connection_diagram_lab3-with_behringer.pdf|Connection Scheme lab 3|pdf}}
| {{Download link|media=Connection_diagram_demolab.pdf|Connection Scheme lab 3 portable demo setup|pdf}}
}}
}}



==Equipment==
*Apple iMac (model 2016) running OSX 10.12 El Capitan
*[[Benq XL2420Z]]
*[[Behringer_X-Air_XR18|Behringer audio mixer]] (note: links to information specific for PC lab setup!)
*AudioEngine A2 Speakers
*EEG equipment: 
:Biosemi Active II amplifier with maximum of 8 x 32-channels (lab 1) or 2 x 32-channels (lab2,3) 
:Analog Input Box, 24 channels (lab 1,2) and 8 channels (lab 3)
:USB receiver
*Midi controlled markers to insert triggers (via BioSemi USB receiver)
*Eyelink 1000 eye tracker - lab 1 only! - (camera shared with [[Eyelink1000plussetup#Eyelink1000|remote]] system)

==Usage==
*{{Download link|media=BCILabProtocol.pdf|EEG BCI lab user guide|pdf}}

=== Display Settings ===
Both external Benq displays are hardware-wise cloned (different from main iMac screen).

Monitor: BenQ XL2420Z
Refresh Rate: 120hz
Resolution: 1920*1080 (1080p)
Color depth: 32bit
Display Configuration: external Display 2 cloned with external Display 1

Presentation

2026-08-12T08:32:41Z

E.vandenberge: /* Video */

{{Infobox software
| name = Presentation
| logo = Presentation_name.png
| logo size = 200px
| logo alt = Presentation
| screenshot =
| caption =
| developer = Neuro Behavioral Systems
| installed version = varies <ref>See [[Pre-installed software]]</ref>
| installed version date = 
| platform = Windows
| language count =
| website = [https://www.neurobs.com/ neurobs.com]
| resources =
{{Infobox tsg
| child = yes
| downloads = {{bulleted list
| {{Surfdrive|zDtYMmAvg4NoZXj|Installers & Other Resources}}
| [https://www.neurobs.com/menu_presentation/menu_download/package_player Package player]
}}
| header2 = Templates
| data2 = *{{Surfdrive|https://surfdrive.surf.nl/s/tWYD6jFQpDcgpZL|Template 2017}}
}}
}}

Presentation is a Windows based programming tool that allows experimenters to set up and program all sort of experiments. It is the recommended software for time-accurate experiments and therefore supported by the institutes’ (Social Sciences Faculty, the MPI and the Donders Centre for Cognitive Neuroimaging) technical groups. The technical groups offer (PhD) students a couple of pre-programmed experiments (i.e. templates), which can be adjusted to build up own experiments. In this way, the (PhD) student can efficiently program experiments fitting an technical optimal environment. This is what this course is all about. It aims at teaching programming skills, which are needed to modify the existing templates such that they meet your own demands. Because this can be quite complex, we start with short assignments, which address one basic and simple problem at a time. They will all contribute to the final assignment in which you will work on an existing template.
 

== Course ==

Find the presentation workshop documentation here: {{Download link|media=Programming with Presentation 2013.pdf}}

Find the presentation pre-reader here: {{Download link|media=Presentation pcl pre-read 2013 .pdf}}

== License ==

To run presentation in the labs you need a software dongle. Reserve a dongle when you book a lab. If you need a dongle for research outside the university, discuss this with your [[Lab Coordinator]].

When you want to run in your office use the network license. Boot presentation, choose option '''"activations" -> "Network"'''

Fill in the following within the "'''Network License Settings"''': 

{| class="wikitable"
|-
! Enable Hostname:
| lic-pres.socsci.ru.nl
|-
! Port:
| 1245
|-
! Timeout (ms):
| 5000
|-
|}

[[File:PresentationLicentie.jpg | 700px ]]

== Video ==
Presentation only supports non-proprietary video formats.<ref>https://www.neurobs.com/menu_support/menu_forums/view_thread?id=8785#i6</ref> Neurobs recommends encoding your videos using h264 or XVID, and using the AVI format.<ref>https://neurobs.com/menu_presentation/menu_documentation/video</ref> The TSG discourages the use of XVID and AVI, because these standards have become obsolete in recent years, but since we have had little success getting alternative non-proprietary video formats to work in Presentation,<ref>[[Video_Codecs#Software_support]]</ref> it seems the use of AVI is inevitable. You can find more information on how to export and convert your videos for Neurobs Presentation on our [[Video Codecs#Neurobs Presentation|Video Codecs page]].

== Audio ==
In Neurobs Presentation please use *exclusive mode* to get the best audio performance. This means that no other programs
can use the audio device while the experiment runs.

[[File:SoundSettings.png|Presentation Mixer Settings]]

The maximum audio delay in Presentation on a lab computer at the faculty of social sciences is 24 ms. If better performance
is necessary or more understanding is needed about the components of this delay, please read our page about [[audio delay]].

'''How to present sounds in Presentation'''

in SDL:

<pre>
sound{
wavefile{
filename = "beep.wav"; # The name of the sound file.
preload=true; # Make sure that the sound is loaded before it is actually used.
}myWave;
}mySound;
</pre>

Make sure to use '''preload = true;'''. This ensures that the sound is loaded into memory before the sound is used.

in PCL:

Prepare your stimuli during Inter Trial Interval, when there is enough time to do that. First, unload the previous sound, set the filename property to the new soundfile and load it.

<pre>
sub prepareTrial
begin
myWave.unload();
myWave.set_filename("beep.wav"); # or read the name from a trial list.
myWave.load();
end;
</pre>

During your experiment the sound is presented by:
<pre>
startOfPlaycall = clock.time();
mySound.present();
endOfPlaycall = clock.time();
</pre>

Please note that the moment when the sound can actually be heard from the speakers is later then the moment when the '''mySound.present()''' function is called. In our labs [march 2019], the delay (from '''startOfPlaycall''' until actual sound onset) is about 14 to 24 milliseconds when the Presenation mixer is used in exclusive mode. The function itself takes some (variable) time to execute. That time can, in the example above, be calculated by '''endOfPlaycall - startOfPlaycall'''. Then, some additional time is required before the sound actually is heard from the speakers. In our labs, that additional delay (from '''endOfPlaycall''' until actual sound onset) is about 5 to 8 milliseconds [March 2019]. When your experiment requires an exact knowledge about when the sound actually plays from the speakers, you need additional hardware, for instance a buttonbox with a soundkey.

More information about sound delays is found on our page about [[audio delay]].

== Troubleshooting ==

==== Version History ====

For version history please click here: http://www.neurobs.com/menu_presentation/menu_download/version_history

==== Fixed Bugs ====

For fixed bug / known bugs please click here: http://www.neurobs.com/menu_support/menu_help_resources/known_bugs

==== Forum ====

For various information please click here: http://www.neurobs.com/menu_support/menu_forums/contents_page

==== Documentation ====
For the Documentation click here: https://neurobs.com/presentation/docs/index_html

==== Compatibility Issues ====

*Always check beforehand in which version the script was written.
*New versions do not always maintain backwards compatibility.
*Features can get removed, or changed.

==References==
<references/>

Eyetracker

2026-08-11T15:44:19Z

E.vandenberge:

== SR Research ==

[[image:SR_logo.jpg | right |150px]]
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]

=== EyeLink II ===

The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye.

An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.

'''Specifications'''

{| class="wikitable"
|-
! scope="col" style="width:200px;"|EyeLink II
|-
| 500 Hz binocular eye monitoring
|-
| 0.5º average accuracy
|-
| Access eye position data with 3.0 msec delay
|-
| 0.01º RMS resolution
|-
| High quality computer based or scene camera eye tracking
|-
| Fast and simple participant setup, calibration, and validation
|}

=== EyeLink 1000 ===
[[image:Eyelink1000.jpg | right |150px]]
*[https://www.sr-research.com/eyelink-1000-plus/ EyeLink 1000 (Plus) product page]

The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages

'''Specifications'''

{| class="wikitable"
|-
! Eyelink 1000 and Eyelink 1000 Plus
!
|-
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular
Remote / Head Free: 500 Hz Monocular
|-
| Accuracy || Head Supported: 0.25º -0.5º average accuracy
Remote / Head Free: 0.5º average accuracy
|-
| Real-time Data Access || Head Supported: 1.4 msec (SD < 0.4 msec) @ 2000 Hz
Remote / Head Free: 3 msec (SD < 1.2 msec) @ 500 Hz
|-
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes
|-
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º
Remote / Head Free:0.05º RMS, saccade resolution of 0.25
|}
*[https://www.sr-research.com/eyelink-1000-plus-technical-specifications/ EyeLink 1000 (Plus) Technical Specifications] 
*[[Eyelink_1000_calibration | Matlab calibration example]]
*[[Eyelink1000plussetup|Eyelink 1000 plus setup]]

Here is a '''tutorial video''' on how to '''setup Eyelink with a participant''': [https://www.youtube.com/watch?v=O3z8I5y_l5E&list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&index=7 Eyelink setup and calibration tutorial video.]

From the SR-Research support forum, about '''placement of monitor, camera and participant''':

''Ideally, the Desktop mount should be placed between 50-70 cm from the participant's eyes and be centrally aligned with the Display monitor from the participant's perspective. When using a wide screen monitor it will need to be sufficiently far away from the participant that it fits within the trackable range of the system. As a rule of thumb it will need to be at a distance at least 1.75 times its width (so a 40 cm wide monitor would need to be at least 70 cm away). As widescreen monitors are typically around 50 cm wide, they will need to be placed at least 90 cm away. This means that, in order for the camera to be placed correctly (50-70 cm from the participant's eyes) it will need to be brought forward from the monitor 20-30 cm.''

''The top of the EyeLink camera and illuminator should also be as high as possible in the participant's field of view without obstructing any part of the display.''

{| class="wikitable"
|-
|[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount?<ref>Taken from the [https://www.sr-research.com/support/thread-206.html?highlight=What+is+the+ideal+configuration+EyeLink+1000+%2F+EyeLink+1000+Plus+Desktop+mount sr-support forum] (sign-in required)</ref>]]
|}

== Tobii ==

[[File:tobii_logo.jpg | right]]
[[File:Tobii.jpg|thumb|200px|Tobii T60]]
[[File:TX300.png|thumb|250px|Tobii TX300]]

===Tobii T60/T120===

The Tobii T60 and T120 Eye Trackers are integrated into a 17" TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.

There is a Tobii setup in the babylab, which is in a fixed lab setup.

There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.

'''Specifications'''

{| class="wikitable"
|-
! scope="col" style="width:200px;"|
! scope="col" style="width:200px;"| Tobii T60 Eye Tracker
! scope="col" style="width:200px;"| Tobii T120 Eye Tracker1
|-
| Accuracy (degrees) || 0.5 || 0.5
|-
| Drift (degrees) || < 0.3 || < 0.3
|-
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30
|-
| Data Rate (Hz) || 60 || 120
|-
| Binocular Tracking || style="background-color:#9F9;" | Yes || style="background-color:#9F9;" | Yes
|-
| Display Size (inch) || 17 || 17
|-
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024
|-
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization
|-
| Eye Tracking Server || Embedded || Embedded
|-
| User Camera || Built-in || Built-in
|-
| Audio || Built-in Speakers|| Built-in Speakers
|}

1The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box

Presentation plugin, including documentation on how to install and how to use it:

https://www.fh-joanneum.at/en/projekt/visionspace-wahrnehmungslabor/

'''Downloads'''
*{{Download link|media=Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker|pdf}}

*{{Download link|media=Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide|pdf}}

*{{Download link|media=TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation)|zip}}

*[https://www.fh-joanneum.at/en/projekt/visionspace-wahrnehmungslabor/ Neurobs Presentation plugin & documentation]

'''Lab setup'''

{{See also|Tobii Eye Tracker}}

===Tobii TX300===

'''Specifications'''

{| class="wikitable"
|-
! scope="col" style="width:200px;"|
! scope="col" style="width:200px;"| Tobii TX300 Eye Tracker1
|-
| Precision(degrees) || < 0.1
|-
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)
|-
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)
|-
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz
|-
| Binocular Tracking || style="background-color:#9F9;" | Yes
|-
| Display Size (inch) || 23
|-
| Display Resolution (px) || 1920 * 1080 (max 60Hz)
|-
| Tracking method || Dark Pupil Tracking
|-
| Eye Tracking Server || Embedded
|-
| User Camera || Built-in (640x480@30fps)
|-
| Audio || Built-in Speakers (3W)
|}

== SensoMotoric Instruments (SMI) ==
[[image:SMI_logo.jpg |right]]
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]

=== SMI RED500 ===

[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]

=== iView X ===

'''Downloads'''

*{{Download link|media=IViewX.pdf|iView X Manual|pdf}}

*{{Download link|media=Eye-tracking_Presentation_iview.zip|Presentation Extension|zip}}
*{{Download link|media=SMI-Eyetracker-Example.zip|Example Presentation Script|zip}} - An example script (new since 2018-06-05) that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.
Source code:
*{{Gitlab|h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce|SMI-Eyetracker-Example.sce}}
*{{Gitlab|h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl|SMI-Eyetracker-ExampleINFO.pcl}}
*{{Gitlab|h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl|SMI-Eyetracker-ExamplePCL.pcl}}
*{{Gitlab|h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl|SMI-Eyetracker-ExampleSUBS.pcl}}
*{{Download link|media=Python.zip|Python Script|zip}}

==References==
<references/>

TMS Lab

2026-08-11T15:34:16Z

E.vandenberge:

{{Infobox tsg
| image = labTMS.JPG
| image alt = TMS Lab
| caption = TMS in 2018
| label1 = Location
| data1 =
| downloads = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/msHF8H4qodBYBMF|User Guides and Regulations}}
}}
}}

==MagVenture TMS stimulator==

In the TMS lab, two MagPro X100 TMS stimulators available, one of them has the 'option' included, as described below.

• MagVenture X100 system

The core of the setup is the MagVenture MagPro X100 with option stimulator.
This system is capable of producing 4 types of waveforms, namely:
# Biphasic,
# BiPhasic Burst,
# Half Sine
# MonoPhasic

The MagOption added to the MagPro X100 also gives it the following enhanced stimulation capabilities for Biphasic, Half Sine and Monophasic:
# Dual pulses with up to 20 pulse pairs per second repetition rate
# Advanced power pulse feature adding 40% additional stimulation power

TMS coils (MagVenture):
*[https://magventure.com/products/cool-b65/ Cool-B65], butterfly, Active cooling
*[https://magventure.com/products/mc-b70/ MC-B70], Butterfly, No cooling
*[https://magventure.com/products/c-b60/ C-B60], Butterfly, No cooling

==Localite TMS Navigator System==

Localite TMS Navigator is an image-guided tool to assist in the positioning of a transcranial magnetic stimulator (TMS) coil over a subject's brain. The Localite system includes the software, position sensor and all the related hardware (except the TMS-stimulator) to perform image-guided TMS.

Small objects, called trackers, are attached to the TMS coil, and the subject. These trackers are monitored, or "seen" by an optical position sensor (optical camera). This information is send to a computer which, after a calibration procedure, displays the position and orientation of the coil on the subject's individual MRI.

Thus, Localite TMS Navigator helps to position the coil very precisely in reference to the subjects brain shown in an individual anatomical MR dataset.

Information sheets on how to use the Localite are available in the TMS lab. The complete Localite manual is available at the labmanager (Dennis Schutter).

[[File:TMS.JPG|thumb|left|300px|TMS]] 

==NeuroConn Transcranial Electric Current Stimulation==
# microprocessor controlled constant current source
# 1 channel, anodal and cathodal stimulation possible
# use of external trigger possible, several AC-DC-STIMULATOR devices can be synchronized for multichannel stimulation
# adjustable current up to 5,000 µA (±1%)
# adjustable application time up to 30 min
# please note: currents of more than 1,000 µA and application times of more than 15 min are for research purposes only!
# modes of stimulation:
## single (continuous stimulation, freely adjustable fading in and fading out)
## pulses (cyclic turning on and off of the stimulation, defined pulse width and interstimulus intervall ISI)
## customer specific programs possible (e.g. sine wave, half-sine wave etc.)
# high safety standard through multistage monitoring of output current
# STUDY MODE OPTION
# INTERNAL & EXTERNAL TRIGGER MODULE
Technical data
# 135 mm x 225 mm x 55 mm (W x D x H); weight 0.9 kg
# 12bit D/A conversion
# power consumption approx. 0.4 W
# power supply via built-in rechargeable batteries, incl. external charger
# alphanumeric display with backlight

[[File:NeuroConn.JPG|thumb|left|300px|NeuroConn]] 

==EEG 128Ch brainproducts==

{{See also|Brainvision}}

[[File:BrainKast.jpg|thumb|left|300px|Kijkje achter de schermen]] 

==References==
<references />

Balance Board

2026-08-11T15:29:56Z

E.vandenberge:

{{Infobox tsg
| name = Balance Board
| image = balanceBoard1.jpg
| caption = Balance Board
| manuals = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/Zr7xLFCEKYak8nc|Balance Board Manuals}}
}}
}}

A balance board(force platform) is commonly used in motor control labs and neurologic clinics. They essentially consist of a set of finely calibrated scales, measuring mechanical forces. The pattern of forces can be used to derive body position, at a high spatial and temporal resolution.



== Features ==

There are several boards specified up to 1M2 and 0,5M2 with a sub-millimeter spatial resolution and a 200 hz temporal resolution.

A typical balance board records at a high spatial and temporal resolution. Regarding spatial resolution: a platform can detect changes from a few sub-millimeters (freezing) to at least 500 centimeter (forward or backward steps). The platform records reliably over four vertical forces. Regarding temporal resolution: the signals are typically sampled at 200 Hz. Even though the system allows even higher sampling rates, in practice 100 Hz is sufficient.

The pressure sensors derive directly from the wii balance board. Each sensor has a maximum pressure of 120Kg. In-house electronics is build to get a clean amplification from the sensors. A National instruments card, USB-6221, takes care of the A/D conversion and connects with usb to a pc. The force plate can be integrated into existing systems for stimulus presentation and for recording bodily signals such as EEG, EMG and heart rate. In practice, this means that the systems are time-locked within millisecond accuracy.

==Configuration==

===National Instruments===
[[File:Capture2.JPG|thumb|left|600px|National Instruments settings]] 

==Usage==

===Neurobs Presentation===

<syntaxhighlight lang="text" line>
sub runtrials_national begin

# The dio_device will setup NI-DAQmx device number 1 "Dev1"
dio_device card = new dio_device(ni_dio_device, 1, 0 );
#int id = card.acquire_analog_input( "MyVoltageOutTask" );
int id1 = card.acquire_analog_input( "ForceMeasurement,Voltage_0" );
int id2 = card.acquire_analog_input( "ForceMeasurement,Voltage_1" );
int id3 = card.acquire_analog_input( "ForceMeasurement,Voltage_2" );
int id4 = card.acquire_analog_input( "ForceMeasurement,Voltage_3" );
count_old = response_manager.total_response_count();
loop
until false
begin
if response_manager.total_response_count() > count_old then
count_old = response_manager.total_response_count();
calibrate_board = true;
end;

message_scale[1] = round(round(card.read_analog( id1, 1000.0 ),6) * 1000.0, 0);
message_scale[2] = round(round(card.read_analog( id2, 1000.0 ),6) * 1000.0, 0);
message_scale[3] = round(round(card.read_analog( id3, 1000.0 ),6) * 1000.0, 0);
message_scale[4] = round(round(card.read_analog( id4, 1000.0 ),6) * 1000.0, 0);

if calibrate_board then
zero_scale_left_up = message_scale[left_up];
zero_scale_left_down = message_scale[left_down];
zero_scale_right_up = message_scale[right_up];
zero_scale_right_down = message_scale[right_down];
calibrate_board = false;
end;

message_scale[left_up] = message_scale[left_up] - zero_scale_left_up;
message_scale[left_down] = message_scale[left_down] - zero_scale_left_down;
message_scale[right_up] = message_scale[right_up] - zero_scale_right_up;
message_scale[right_down] = message_scale[right_down] - zero_scale_right_down;
t_scale11.set_caption(string(message_scale[left_up]));
t_scale11.redraw();
t_scale22.set_caption(string(message_scale[left_down]));
t_scale22.redraw();
t_scale33.set_caption(string(message_scale[right_up]));
t_scale33.redraw();
t_scale44.set_caption(string(message_scale[right_down]));
t_scale44.redraw();

pos_dot_x = (message_scale[right_up] + message_scale[right_down]) - message_scale[left_up] + message_scale[left_down]);
pos_dot_y = (message_scale[left_up] + message_scale[right_up]) - message_scale[left_down] + message_scale[right_down]);
p_balance.add_part( balance_pos, (pos_dot_x * 1.0), (pos_dot_y * 1.0));
t_coord.set_caption(string(pos_dot_x)+","+string(pos_dot_y));
t_coord.redraw();

p_balance.present();
p_balance.remove_part( 8 );
end;
card.release_analog_input( id1 );
card.release_analog_input( id2 );
card.release_analog_input( id3 );
card.release_analog_input( id4 );
end;
</syntaxhighlight >

===Python===

<syntaxhighlight lang="python" line>
from PyDAQmx import Task
from PyDAQmx.DAQmxConstants import *
from PyDAQmx.DAQmxTypes import *
import numpy
import msvcrt
import time

times = []
try :
freq = 100.0 # Hz
numinputs = 4

analog_input = Task()
read = int32()
timer= time.clock()
running = True

data = numpy.zeros((numinputs,), dtype=numpy.float64)

#DAQmx Configure Code
analog_input.CreateAIVoltageChan("Dev1/ai0:%i" % (numinputs - 1), None, DAQmx_Val_RSE, -10.0,10.0,DAQmx_Val_Volts,None)
#analog_input.CfgInputBuffer(0)
#analog_input.CfgSampClkTiming("",freq,DAQmx_Val_Rising,DAQmx_Val_ContSamps,1000)

analog_input.StartTask()
datalist = []
while running:
#DAQmx Start Code

timeBeforeRead = time.clock()
analog_input.ReadAnalogF64(-1,10.0,DAQmx_Val_GroupByChannel,data,numinputs*2,byref(read),None)
ser.write('S')
line = ser.readline()

time.sleep((1 / freq) - (time.clock()- timeBeforeRead))

times.append(timeBeforeRead - time.clock())

if msvcrt.kbhit():
running = False

finally :
print "Stop"
t = numpy.array(times)
deviation = numpy.mean(abs(t - numpy.mean(t)))
maxdeviation = max(abs(t-numpy.mean(t)))

print numpy.mean(t), deviation , maxdeviation

analog_input.StopTask();
</syntaxhighlight>

==See Also== 
*[[BalanceBoard Lab]]

Vertical Sync sensor

2026-08-11T15:29:23Z

E.vandenberge:

{{Infobox tsg
| name = Vertical Sync sensor
| image = sensorPic.jpg
| caption = Vertical Sync sensor
}}
{{Infobox tsg
| name = Seeed Studio XIAO SAMD21
| image = Seeeduino_XIAO.JPG
| caption = Seeed Studio XIAO SAMD21
| downloads = {{bulleted list
| [https://wiki.seeedstudio.com/Seeeduino-XIAO/ XIAO SAMD21 product page]
}}
}}
{{Infobox tsg
| name = TEMT6000 Licht Sensor Module
| image = temt6000.jpg
| caption = TEMT6000 Licht Sensor Module
| downloads = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/ZC2axMNWjYaTYFG|TEMT6000 Datasheet}}
}}
}}

The Vertical Sync sensor is used on a computer/laptop monitor for time accurate visual presentation. The sensor measures screen brightness. It generates a BITSI trigger to the com-port("A" = ON/light, "a" = OFF/noLight) when the amount of light is higher than the (customizable) threshold. This means that the onset of visual stimulus on screen can be marked. It can easily be attached with a pincher to the screen. The Vertical Sync sensor is connected to a computer with a usb connection, a serial port is emulated. You may want to read about [[presentation modes]] in order to decide how to use the sync sensor.

== BITSI Protocol ==

BITSI stands for Bits to Serial Interface.
{| class="wikitable"
|-
! scope="row" colspan="3" | Vertical Sync sensor
|-
! scope="row" width="120px" | ASCII (rise/fall)
! scope="row" width="120px" | Code (rise/fall)
! scope="row" width="120px" | Light
|-
| A / a || 65 / 97 || ON / OFF
|-
|}

Meaning when light falls on the sensor, a capital A will be sent to the serial port. A lowercase 'a' will be sent when the signal is deactivated(no light).

===Output===

The treshold for monitor OFF is customizable and can be specified by sending a byte to specify the value for screen OFF. Any byte satisfies, see example code.

== Port Settings ==

===Serial port===

Our hardware design allows to be connected to the computers USB and emulates a serial communication Port.

{| class="wikitable"
|-
| Baudrate || 115200
|-
| Parity || None
|-
| Data bits || 8
|-
| Stop bits || 1
|-
| Flow control || None
|-
|}

=== USB-Com port ===

1.Connect the Vertical Sync sensor to your computer using the USB cable.

2.When you connect the Vertical Sync sensor, Windows should initiate the driver installation process (if you haven't used the computer with an Vertical Sync sensor before).

'''How to Check the Com Port settings(important!)'''

*From the Start menu, open the '''Control Panel'''.

*From the control panel, open the '''System window'''.

*From the system properties window, go to the '''Hardware tab''' and click the '''Device Manager''' button.

*From the Device Manager window, click '''Ports (Com&LPT).''' You should now be able to see which Com Port the USB adapter is assigned to.

*If the Com Port is 10 or higher, you will have to change it to a lower port.

*From the Device Manager window, click on '''USB Serial Port (Com#).''' Click the '''Port Settings tab''' of the USB Serial Port Properties window, and then click the '''Advanced''' button.

*In the Advanced Settings window, use the scroll input to select a '''Com Port''' (select 10 or lower). Change '''Receive (bytes)''' and '''Transmit (bytes)''' to 64. Change the '''Latency Timer''' to 1.

*Click the OK button.

Always connect the usb device to the same port and your settings will be remembered.

== Software Settings ==

=== Python/PsychoPy ===

 '''The basics using the Vertical Sync sensor in PsychoPy:'''

<syntaxhighlight lang="python" line>
# initialize treshold for OFF by sending a code
ser.write(b'1')

visual.Rect(win, .15, .25, pos=(-1, 1),fillColor="white", units="norm").draw()
win.flip()
# wait for a sync square
b = ser.read()
</syntaxhighlight>

 '''Example script using the Vertical Sync sensor in PsychoPy:'''

<syntaxhighlight lang="python" line>
#!/usr/bin/env python

# import psychopy and rusocsci
from psychopy import core, visual
import serial
import time

## Setup Section
win = visual.Window([400,400], fullscr=True, winType = "pyglet", monitor="testMonitor",color=(-1, -1, -1), waitBlanking=True)
# connect to Vertical Sync sensor, find correct com port number
ser = serial.Serial('com3', 115200, timeout=1.0)
# create sync box left corner
rect = visual.Rect(win, .15, .25, pos=(-1, 1),fillColor="white", units="norm")

# wait 5 sec for python to become stabel
core.wait(5)
ser.flushInput()
# define screen OFF by sending a code
ser.write(b'1')

## Experiment Section
# show sync box left corner
rect.draw()
win.flip()
tik = time.perf_counter()
# wait for a sync square
b = ser.read()
tok = time.perf_counter()
# show delay after a flip
print("your timing after a flip: {}s".format(tok-tik))
# as a remark 60Hz/~0.016s 120Hz/~0.008s

## Cleanup Section
core.quit()
</syntaxhighlight>

=== Matlab ===
'''Example using markers with the Buttonbox in Matlab:'''

Download the file Bitsi.m from the DCCN website: https://intranet.donders.ru.nl/index.php?id=bitsim0
 Make sure to have this file in your Matlab path.
<syntaxhighlight lang="matlab" line style="overflow:auto;">
% At the start of your script, create the buttonbox serial object
bb = Bitsi("COM2");
% other code
:
</syntaxhighlight>

BITSI simple mode:
<syntaxhighlight lang="matlab" line style="overflow:auto;">
% This example is for an EEG system sampling at 500Hz samplerate.
% at the start of your script, reset marker
samplerate = 500;
pulseLen = 2000/samplerate;
bb.sendTrigger(0);
% send a marker
val = 1; % val: this is your marker code, range code 1-255
bb.sendTrigger(val);
java.lang.Thread.sleep(pulseLen); % wait long enough for the EEG system to capture the trigger, i.e., 2000/samplerate ms
% reset marker
bb.sendTrigger(0) % Note: if resetting the marker is not possible at this moment in code, you can decide to do this later as long as it has taken place long enough before the next marker has to be sent.
</syntaxhighlight>

Presentation

2026-08-11T15:28:07Z

E.vandenberge:

{{Infobox software
| name = Presentation
| logo = Presentation_name.png
| logo size = 200px
| logo alt = Presentation
| screenshot =
| caption =
| developer = Neuro Behavioral Systems
| installed version = varies <ref>See [[Pre-installed software]]</ref>
| installed version date = 
| platform = Windows
| language count =
| website = [https://www.neurobs.com/ neurobs.com]
| resources =
{{Infobox tsg
| child = yes
| downloads = {{bulleted list
| {{Surfdrive|zDtYMmAvg4NoZXj|Installers & Other Resources}}
| [https://www.neurobs.com/menu_presentation/menu_download/package_player Package player]
}}
| header2 = Templates
| data2 = *{{Surfdrive|https://surfdrive.surf.nl/s/tWYD6jFQpDcgpZL|Template 2017}}
}}
}}

Presentation is a Windows based programming tool that allows experimenters to set up and program all sort of experiments. It is the recommended software for time-accurate experiments and therefore supported by the institutes’ (Social Sciences Faculty, the MPI and the Donders Centre for Cognitive Neuroimaging) technical groups. The technical groups offer (PhD) students a couple of pre-programmed experiments (i.e. templates), which can be adjusted to build up own experiments. In this way, the (PhD) student can efficiently program experiments fitting an technical optimal environment. This is what this course is all about. It aims at teaching programming skills, which are needed to modify the existing templates such that they meet your own demands. Because this can be quite complex, we start with short assignments, which address one basic and simple problem at a time. They will all contribute to the final assignment in which you will work on an existing template.
 

== Course ==

Find the presentation workshop documentation here: {{Download link|media=Programming with Presentation 2013.pdf}}

Find the presentation pre-reader here: {{Download link|media=Presentation pcl pre-read 2013 .pdf}}

== License ==

To run presentation in the labs you need a software dongle. Reserve a dongle when you book a lab. If you need a dongle for research outside the university, discuss this with your [[Lab Coordinator]].

When you want to run in your office use the network license. Boot presentation, choose option '''"activations" -> "Network"'''

Fill in the following within the "'''Network License Settings"''': 

{| class="wikitable"
|-
! Enable Hostname:
| lic-pres.socsci.ru.nl
|-
! Port:
| 1245
|-
! Timeout (ms):
| 5000
|-
|}

[[File:PresentationLicentie.jpg | 700px ]]

== Video ==
Presentation only supports non-proprietary video formats.<ref>https://www.neurobs.com/menu_support/menu_forums/view_thread?id=8785#i6</ref> Neurobs recommends encoding your videos using h264 or XVID, and using the AVI format.<ref>http://www.neurobs.com/wiki/Presentation/Video {{Dead link}}</ref> The TSG discourages the use of XVID and AVI, because these standards have become obsolete in recent years, but since we have had little success getting alternative non-proprietary video formats to work in Presentation,<ref>[[Video_Codecs#Software_support]]</ref> it seems the use of AVI is inevitable. You can find more information on how to export and convert your videos for Neurobs Presentation on our [[Video Codecs#Neurobs Presentation|Video Codecs page]].

== Audio ==
In Neurobs Presentation please use *exclusive mode* to get the best audio performance. This means that no other programs
can use the audio device while the experiment runs.

[[File:SoundSettings.png|Presentation Mixer Settings]]

The maximum audio delay in Presentation on a lab computer at the faculty of social sciences is 24 ms. If better performance
is necessary or more understanding is needed about the components of this delay, please read our page about [[audio delay]].

'''How to present sounds in Presentation'''

in SDL:

<pre>
sound{
wavefile{
filename = "beep.wav"; # The name of the sound file.
preload=true; # Make sure that the sound is loaded before it is actually used.
}myWave;
}mySound;
</pre>

Make sure to use '''preload = true;'''. This ensures that the sound is loaded into memory before the sound is used.

in PCL:

Prepare your stimuli during Inter Trial Interval, when there is enough time to do that. First, unload the previous sound, set the filename property to the new soundfile and load it.

<pre>
sub prepareTrial
begin
myWave.unload();
myWave.set_filename("beep.wav"); # or read the name from a trial list.
myWave.load();
end;
</pre>

During your experiment the sound is presented by:
<pre>
startOfPlaycall = clock.time();
mySound.present();
endOfPlaycall = clock.time();
</pre>

Please note that the moment when the sound can actually be heard from the speakers is later then the moment when the '''mySound.present()''' function is called. In our labs [march 2019], the delay (from '''startOfPlaycall''' until actual sound onset) is about 14 to 24 milliseconds when the Presenation mixer is used in exclusive mode. The function itself takes some (variable) time to execute. That time can, in the example above, be calculated by '''endOfPlaycall - startOfPlaycall'''. Then, some additional time is required before the sound actually is heard from the speakers. In our labs, that additional delay (from '''endOfPlaycall''' until actual sound onset) is about 5 to 8 milliseconds [March 2019]. When your experiment requires an exact knowledge about when the sound actually plays from the speakers, you need additional hardware, for instance a buttonbox with a soundkey.

More information about sound delays is found on our page about [[audio delay]].

== Troubleshooting ==

==== Version History ====

For version history please click here: http://www.neurobs.com/menu_presentation/menu_download/version_history

==== Fixed Bugs ====

For fixed bug / known bugs please click here: http://www.neurobs.com/menu_support/menu_help_resources/known_bugs

==== Forum ====

For various information please click here: http://www.neurobs.com/menu_support/menu_forums/contents_page

==== Wiki ====
For the wiki click here: http://www.neurobs.com/menu_support/nbs_wiki {{Dead link}}

==== Compatibility Issues ====

*Always check beforehand in which version the script was written.
*New versions do not always maintain backwards compatibility.
*Features can get removed, or changed.

==References==
<references/>

ButtonBox

2026-08-11T15:26:15Z

E.vandenberge:

{{Infobox tsg
| name = Buttonbox (2018)
| image = Buttonbox_2018_1.png
| caption = 2018 Buttonbox
| downloads = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/KZzgpmC5oK5JBNr|Buttonbox 2018}}
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)
}}
}}
{{Infobox tsg
| name = Buttonbox
| image = Buttonbox 03s.png
| caption = 2013 Buttonbox
| downloads = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/KZzgpmC5oK5JBNr|Buttonbox 2015}}
| [https://pypi.python.org/pypi/RuSocSci RuSocSci] (Python package)
}}
}}

The buttonbox is used for time accurate(1ms) button press registration. We use it to register buttonpresses, soundkey, voicekey signals and to send tone onset, analog output, triggers with the BITSI protocol. It is suitable for Behavioral, EEG, MEG, and fMRI experiments. The buttonbox is connected to a computer with a usb connection.

The output connector has two binary eight bit ports: input and output. The two ports can be used for responses (input) and stimulus triggers (output). Two 12 bits analog outputs and three 12 bits analog inputs. The output connector has a sound and voicekey which triggers when a amplitude reaches a threshold. By using the serial port, the BITSI can be used platform independently: it works on Windows, Linux and Mac OSX. Most programming environments and stimulus packages support serial communication.

⚠️ There is currently a [[ButtonBox/Microsoft Windows driver issue|Windows driver issue]].

== BITSI Protocol ==

BITSI stands for Bits to Serial Interface. Because the BITSI is designed to interface both in- and output signals, the 'protocol' is asymmetric: the input and output protocols differ.

===Input===

The input port can be used to interface eight buttons maximally. Button presses are translated to serial output characters/bytes according to the following table:

{| class="wikitable"
|-
! scope="row" colspan="3" | BITSI Simple
|-
! scope="row" width="120px" | Signal/Button
! scope="row" width="120px" | ASCII (rise/fall)
! scope="row" width="120px" | Code (rise/fall)
|-
| 1 || A / a || 65 / 97
|-
| 2 || B / b || 66 / 98
|-
| 3 || C / c || 67 / 99
|-
| 4 || D / d || 68 / 100
|-
| 5 || E / e || 69 / 101
|-
| 6 || F / f || 70 / 102
|-
| 7 || G / g || 71 / 103
|-
| 8 || H / h || 72 / 104
|-
|}

This means that when signal 1 gets active(button press), a capital A will be sent to the serial port. A lowercase 'a' will be sent when the signal is deactivated(button release). Mechanical buttons can be connected directly.

===Output===

Output knows two protocols: '''BITSI simple''' or '''BITSI extended'''. To enter a certain protocol two buttons have to be pressed when the BITSIbox is powered or com port opens. '''[2015]Press button H and A for simple mode and H and B for extended mode. [2018]Press button E and A for simple mode and E and B for extended mode.'''

If no button is pressed when powered it boots the last known protocol. In the simple protocol every byte sent to the BITSI over the serial port, is represented at the 8 bit output.

The '''extended''' protocol uses two bytes(or two characters), this combination can access two analog outputs and a tone generator. The first byte selects the output. The second byte determines the value written to this output.

{| class="wikitable"
|-
! scope="row" colspan="3" | BITSI Extended
|-
! scope="row" width="120px" | Function
! scope="row" width="150px" | Byte 1 (ASCII/code)
! scope="row" width="150px" | Byte 2
|-
| Marker Out || M / 77 || Marker Value
|-
| Pulse Out || P / 80 || Marker Value
|-
| Pulse Time || X / 88 || ms before pulse reset
|-
| Analog Out 1 || Y / 89 || Analog Output Value
|-
| Analog Out 2 || Z / 90 || Analog Output Value
|-
| Tone || T / 84 || Start Tone
|-
| Detect Sound || D / || S / 83
|-
| Detect Voice || D / || V / 83
|-
| Calibrate Sound || C / || S
|-
| Calibrate Voice || C / || V
|-
| Analog In 1 || A / || 1
|-
| Analog In 2 || A / || 2
|-
| Analog In 3 || A / || 3
|-
| Analog In 4 || A / || 4
|-
| LEDs Off || L / || X
|-
| LEDs Input || L / || I
|-
| LEDs Output || L / || O
|-
|}

== Port Settings ==

===Trigger port ===

[[File:Connector.png|thumb|300x300px|Schematic view of the 25 pins connector]]

The 25 pins female connector has 8 inputs and 8 outputs, respectively 1-8 are inputs and 9-16 are outputs. Three analog input with an analog to digital convertor of 12 bit, pins 17,18,20 and 21. Two analog outputs with an digital to analog convertor of 12 bits on pins 22 and 23.

The inputs 1-8 will be pulled down from 5V to GND when the buttons are pressed. The outputs 9-16 will be pulled up from GND to 5V when the output is activated.

===Serial port===

Our hardware design allows to be connected to the computers USB and emulates a serial communication Port.

{| class="wikitable"
|-
| Baudrate || 115200
|-
| Parity || None
|-
| Data bits || 8
|-
| Stop bits || 1
|-
| Flow control || None
|-
|}

=== USB-Com port ===

1.Connect the BITSIbox to your computer using the USB cable.

2.When you connect the BITSIbox, Windows should initiate the driver installation process (if you haven't used the computer with an BITSIbox board before).

3.On Windows Vista/7, the driver should be automatically downloaded and installed.

4.On Windows XP, the Add New Hardware wizard will open:

*When asked '''Can Windows connect to Windows Update to search for software?''' select '''No, not this time'''. Click next.
*Select '''Install from a list or specified location (Advanced)''' and click next.
*Make sure that '''Search for the best driver in these locations''' is checked; uncheck '''Search removable media'''; check '''Include this location in the search''' and browse to the '''c:/beheer/arduino/drivers '''directory.
*The wizard will search for the driver and then tell you that a "USB Serial Converter" was found. Click finish.
*The new hardware wizard will appear again. Go through the same steps and select the same options and location to search. This time, a "USB Serial Port" will be found.

'''How to Check the Com Port settings(important!)'''

*From the Start menu, open the '''Control Panel'''.

*From the control panel, open the '''System window'''.

*From the system properties window, go to the '''Hardware tab''' and click the '''Device Manager''' button.

*From the Device Manager window, click '''Ports (Com&LPT).''' You should now be able to see which Com Port the USB adapter is assigned to.

*If the Com Port is 10 or higher, you will have to change it to a lower port.

*From the Device Manager window, click on '''USB Serial Port (Com#).''' Click the '''Port Settings tab''' of the USB Serial Port Properties window, and then click the '''Advanced''' button.

*In the Advanced Settings window, use the scroll input to select a '''Com Port''' (select 10 or lower). Change '''Receive (bytes)''' and '''Transmit (bytes)''' to 64. Change the '''Latency Timer''' to 1.

*Click the OK button.

Always connect the usb device to the same port and your settings will be remembered.

== Software Settings ==

=== Neurobs Presentation ===

The experiment files needs a few settings for the device to work:
* In the settings tab: port -> input port -> 1 must be the device that identifies itself as "Arduino Uno" in the device manager. Note that the port must have a number not higher than 10 (COM1-COM10). Use re-enumerate if it is higher.
* Rate must be set 115200, Parity to None, Data Bits to 8 and Stop Bits to 1, Uncheck FIFO Interrupt.

[[File:Buttonbox2.png]]

'''Testing Buttonbox'''

When pressing on the A button within the input channel tester. You will see the following ASCII code.

[[file:testbuttonbox.png]]

'''Adding Marker'''

[[file:output_buttonbox1.png | 800px]]

'''Testing Markers (output)'''

Send code 1 for Button A

[[file:output_buttonbox2.png]]

Button A will light up.

[[file:buttonboxledA.png | 200px]]

Send code 0 for clearing.

[[file:output_buttonbox3.png]]

'''Example PCL code you can program a handle to send a marker:'''

#handle:
output_port OutputPort = output_port_manager.get_port( 1 );

'''Example to send a marker:'''
OutputPort.send_code(100); #create a marker

for more information see chapter 8 in the presentation course by clicking [http://tsgdoc.socsci.ru.nl/images/9/9e/Programming_with_Presentation_2013.pdf here]

=== Python/PsychoPy ===

Download this site-package to use the buttonbox: [https://pypi.python.org/pypi/RuSocSci rusocsci]

or use in windows command 'pip install --upgrade rusocsci'

'''Example using buttons from the buttonbox in Python:'''

<syntaxhighlight lang="python" line>
#!/usr/bin/env python

# import the rusocsci.buttonbox module
from rusocsci import buttonbox

# make a buttonbox
bb = buttonbox.Buttonbox()

# wait for a single button press
b = bb.waitButtons()

# print the button pressed
print("b: {}".format(b))
</syntaxhighlight>

'''Example using markers with the buttonbox in Python:'''

<syntaxhighlight lang="python" line>
#!/usr/bin/env python

# import the rusocsci.buttonbox module
from rusocsci import buttonbox

# make a buttonbox
bb = buttonbox.Buttonbox()

# send a marker
bb.sendMarker(val=100) #This is your marker code, range code 1-255
</syntaxhighlight>

'''Example using BITSI extended in Python:'''

<syntaxhighlight lang="python" line>
#!/usr/bin/env python

# import the rusocsci.buttonbox module
from rusocsci import buttonbox

# make a buttonbox
bb = buttonbox.Buttonbox()

# select a function
bb.sendMarker(val=(ord('X'))) #select pulse time
bb.sendMarker(val=2) #set time of dureation pulse to 2ms

bb.sendMarker(val=(ord('M'))) #select marker out
bb.sendMarker(val=115) #set marker value 115
</syntaxhighlight>

'''Example using BITSI extended analog read in Python:'''

<syntaxhighlight lang="python" line>
#!/usr/bin/env python

# import the rusocsci.buttonbox module
import serial

# make a buttonbox
ser = serial.Serial("COM2", 115200, timeout = 0.10 )
ser = serial.Serial("/dev/ttyUSB0", 115200, timeout = 0.10 )

while True:
ser.write('A1')
ser.flush()
x = ser.readline()
visual.TextStim(win, text=x).draw()

# black screen for 1000 ms
win.flip()

key = event.getKeys()
try:
if key[0]=='escape':
break
except:
continue
</syntaxhighlight>

 '''Example using the Buttonbox in PsychoPy:'''

<syntaxhighlight lang="python" line>
#!/usr/bin/env python

# import psychopy and rusocsci
from psychopy import core, visual
from rusocsci import buttonbox

## Setup Section
win = visual.Window(monitor="testMonitor")
bb = buttonbox.Buttonbox()
text = visual.TextStim(win, "Press a button on the buttonbox")

## Experiment Section
# show text
text.draw()
win.flip()
# wait for response
b = bb.waitButtons()
# show response
text.setText("you pressed: {}".format(b))
text.draw()
win.flip()
core.wait(5)

## Cleanup Section
core.quit()
</syntaxhighlight>

For more documentation click here: http://pythonhosted.org//RuSocSci/index.html
 
 

=== Matlab ===
'''Example using markers with the Buttonbox in Matlab:'''

Download the file Bitsi.m from the DCCN website: https://intranet.donders.ru.nl/index.php?id=bitsim0
 Make sure to have this file in your Matlab path.
<syntaxhighlight lang="matlab" line style="overflow:auto;">
% At the start of your script, create the buttonbox serial object
bb = Bitsi("COM2");
% other code
:
</syntaxhighlight>

BITSI simple mode:
<syntaxhighlight lang="matlab" line style="overflow:auto;">
% This example is for an EEG system sampling at 500Hz samplerate.
% at the start of your script, reset marker
samplerate = 500;
pulseLen = 2000/samplerate; % get pulse time length for a 2 samples delay
bb.sendTrigger(0);
% send a marker
val = 1; % val: this is your marker code, range code 1-255
bb.sendTrigger(val);
java.lang.Thread.sleep(pulseLen); % wait long enough for the EEG system to capture the trigger, i.e., 2000/samplerate ms
% reset marker
bb.sendTrigger(0) % Note: if resetting the marker is not possible at this moment in code, you can decide to do this later as long as it has taken place long enough before the next marker has to be sent. Another solution using a timer object instead of a simple delay is outlined below.
</syntaxhighlight>

BITSI extended mode:
<syntaxhighlight lang="matlab" line style="overflow:auto;">
samplerate = 500;
pulseLen = 2000/samplerate; % get pulse time length for a 2 samples delay
% select a function
bb.sendTrigger(uint8('X')); % select pulse time
bb.sendTrigger(pulseLen); % set time of duration pulse to (2000/samplerate) ms

val = 1; % val: this is your marker code, range code 1-255
bb.sendTrigger(uint8('M')); % select marker out
bb.sendTrigger(val); % val: this is your marker code, range code 1-255
</syntaxhighlight>

<syntaxhighlight lang="matlab" line style="overflow:auto;">
% At the end of your script, close the buttonbox serial object
:
bb.close();
</syntaxhighlight>

Reset marker using a timer:
<syntaxhighlight lang="matlab" line style="overflow:auto;">
% At the start of your script, define timer object and callback function
pulseTime = 0.004; % trigger pulse duration in s. NB: extra time will be added due to overhead in calling Matlab functions related to the timer event.
resetMarker = timer('TimerFcn',@(x,y)bb.sendTrigger(0),'StartDelay',pulseTime);

% replace the code to send a marker with:
val = 1; % val: this is your marker code, range code 1-255
bb.sendTrigger(val);
resetMarker.start(); % this will call bb.sendTrigger(0) after pulseTime seconds (plus some additional overhead)

</syntaxhighlight>

DataHub

2026-08-11T15:24:35Z

E.vandenberge:

{{Infobox software
| name = Lab Streaming Layer
| developer = Christian Kothe; Chadwick Boulay.
| status = -in development-
| programming language = C, C++, Python, Java, C#, MATLAB
| operating system = Windows, Linux, MacOS, Android, iOS
| genre = Data collection
| license = Open source
| website = [https://labstreaminglayer.readthedocs.io/info/intro.html LSL webpage]
}}

=== Resources ===
{{Infobox tsg
| downloads = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/GLSnbBaYsbEWjPX|Viewer & Streamer}}
}}
| manuals = {{bulleted list
| [https://labstreaminglayer.readthedocs.io/ Documentation]
| [https://sccn.ucsd.edu/~mgrivich/LSL_Validation.html LSL Validation]
| [https://labstreaminglayer.readthedocs.io/info/supported_devices.html Supported Devices and Tools]
}}
| templates = {{bulleted list
| {{Surfdrive|https://surfdrive.surf.nl/s/gPenWNAqq8AXa7x|Example Scripts}}
}}
}}

The DataHub Makes use of the lab streaming layer. The lab streaming layer (LSL) is a system for the unified collection of measurement time series in research experiments that handles both the networking, time-synchronization, (near-) real-time access as well as optionally the centralized collection, viewing and disk recording of the data.



==Installation==
Our support for LSL is mainly done in python. Download python here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).
Open a command prompt, start with upgrading the pip installer by typing: 
<code style="background-color:#000; color:#fff; padding:1px 3px;">c:>python -m pip install --upgrade pip</code> 
Then: 
<code style="background-color:#000; color:#fff; padding:1px 3px;">c:>pip install pylsl</code>

more info: [https://github.com/labstreaminglayer/liblsl-Python cross platform pylsl]

===Versions===
Pylsl version 1.16.2 is installed on our [[Lab Computer]]s. Open a command and type the following to find the version used:

<code style="background-color:#000; color:#fff; padding:1px 3px;">c:>python</code> 
<code style="background-color:#000; color:#fff; padding:1px 3px;">>>> import pylsl</code> 
<code style="background-color:#000; color:#fff; padding:1px 3px;">>>> print(pylsl.__version__)</code> 

==Usage==
=== Python ===
Example demonstrating how to send LSL stream and marker data:
<syntaxhighlight lang="python" line>
#!/usr/bin/env python3.10
# -*- coding: utf-8 -*-

import time
import random
import keyboard
from pylsl import StreamInfo, StreamOutlet

from pylsl import local_clock

# --- Setup Marker Stream ---
print("Setting up marker stream...")
marker_info = StreamInfo(
name="MarkerStream",
type="Markers",
channel_count=1,
nominal_srate=0, # Irregular sampling
channel_format="string",
source_id="MarkerSource"
)
marker_outlet = StreamOutlet(marker_info, chunk_size=1)

# --- Setup Data Stream ---
print("Setting up data stream...")
data_info = StreamInfo(
name="TestStream",
type="TestData",
channel_count=4,
nominal_srate=100,
channel_format="float32",
source_id="TestStream_Source"
)

channels = data_info.desc().append_child("channels")
for name in ["A", "B", "C", "D"]:
chan = channels.append_child("channel")
chan.append_child_value("name", name)
chan.append_child_value("unit", "unitless")
chan.append_child_value("type", "TestData")

data_outlet = StreamOutlet(data_info, chunk_size=1)

# --- Start Streaming ---
print("Start streaming... Press 'q' to stop.")
marker_outlet.push_sample(["Start"])

while not keyboard.is_pressed('q'):
random_numbers = [random.randint(1, 2) for _ in range(4)]
data_outlet.push_sample(random_numbers)
time.sleep(0.01)

marker_outlet.push_sample(["Stop"])
print("Streaming stopped.")
</syntaxhighlight>

=== Matlab ===
Please, read the instructions on the GitHub labstreaminglayer website (https://github.com/labstreaminglayer/liblsl-Matlab) on how to prepare Matlab to work with LSL. You can either use the latest release for your Matlab version, or if that doesn't workout well, build it from the source files. Make sure to add the liblsl-Matlab folder to your path recursively to make it available to your own scripts.

A short example for sending lsl streaming data:
<syntaxhighlight lang="matlab" line>
%% instantiate the library
disp('Loading library...');
lib = lsl_loadlib();

% make a new stream outlet
disp('Creating a new streaminfo...');
info = lsl_streaminfo(lib,'BioSemi','EEG',8,100,'cf_float32','sdfwerr32432');

disp('Opening an outlet...');
outlet = lsl_outlet(info);

% send data into the outlet, sample by sample
disp('Now transmitting data...');
while true
outlet.push_sample(randn(8,1));
pause(0.01);
end
</syntaxhighlight>

A short example for receiving lsl streaming data:
<syntaxhighlight lang="matlab" line>
%% instantiate the library
disp('Loading the library...');
lib = lsl_loadlib();

% resolve a stream...
disp('Resolving an EEG stream...');
result = {};
while isempty(result)
result = lsl_resolve_byprop(lib,'type','EEG'); end

% create a new inlet
disp('Opening an inlet...');
inlet = lsl_inlet(result{1});

disp('Now receiving data...');
while true
% get data from the inlet
[vec,ts] = inlet.pull_sample();
% and display it
fprintf('%.2f\t',vec);
fprintf('%.5f\n',ts);
end</syntaxhighlight>

Meta:Guidelines

2026-08-11T15:21:08Z

E.vandenberge: /* Surfdrive */

This is a sample page for the tsgdoc Wiki and can be used as reference for creating new pages. Note that this introduction is conventionally placed above the Table Of Contents (TOC), so visitors can immediately see what this page is about, instead of having to scroll passed the TOC.

For more general wiki conventions and formatting help , visit the [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Formatting Guide].

If you're looking for something to contribute to this Wiki, look here for pages that need fixing:
*[[:Category:Pages that need updating]]
*[[:Category:Articles with dead external links]]

==Page Names==
Page names should be descriptive and unique. Use singular nouns instead of plurals when possible (e.g. "Keyboard" instead of "Keyboards"). This makes linking from singular words easier: 

✅<code><nowiki>One [[Keyboard]], Two [[Keyboard]]s.</nowiki></code> 
❌<code><nowiki>One [[Keyboards|Keyboard]], Two [[Keyboards]].</nowiki></code>

Both result in: One [[Keyboard]], Two [[Keyboard]]s.

==Sections==
Always try to group and categorize your information in a logical and user-friendly way. Prevent redundancies: only create subsections if there are more of them at the same level (levels are indicated by number of = signs before and after the section header), otherwise just collapse to the parent.

For some reason, Erik seems to always start at level 2 ('=='). It makes the jump in font-size between the header and text a bit less jarring, but it's mainly done out of a force of habit. Help him break this spell by properly starting your sections at level 1.

You can add many levels of subsections as you like, but after level 3 they become quite hard to distinguish and will clutter the TOC. If a subject requires many sub-subcategories, consider giving the subcategory its own page. Alternatively, if the sub-subcategories are only small in content, you could make non-TOC headers with simple '''bold text'''.

==Links==
Links should be '''descriptive''', and inform the user of where or what the link is directing them to.

'''Dos'''
:✅ Check [https://www.ru.nl/en/departments/faculty-of-social-sciences/technical-support-group-tsg our official website].
:✅ [[Meta:Guidelines#Links|How to format links]]
:⚠️ It can be ok to use full URLs if they're short and/or clear, like https://ru.nl/

'''Donts'''
:❌ Click [https://ru.nl here] for more info.
:❌ Visit https://www.ru.nl/en/departments/faculty-of-social-sciences/technical-support-group-tsg

===Download Links===
{{See also|Template:Download link}}

You can use a custom template for download links. This adds a little icon in front of it so users can see the link leads to a raw file or direct download. This is to prevent people accidentally downloading things they didn't intend to.

{{Download link|media=Placeholder.png|Placeholder image|png}}
<pre>{{Download link|media=Placeholder.png|Placeholder image|png}}</pre>

===Familiar Sites===
This Wiki has custom templates for linking to commonly used resources that are (more or less) under our control. It helps users identify where external links are going, and know it is safe to click on.

====Gitlab====
{{See also|Template:Gitlab}}

{{Gitlab|tsg/Labcomputer|Lab computer scripts}}
<pre>{{Gitlab|tsg/Labcomputer|Lab computer scripts}}</pre>

====Surfdrive====
{{See also|Template:Surfdrive}}

{{Surfdrive|b8Rp29u8MGhjb1v|LSL LabRecorder (zip)}}
<pre>{{Surfdrive|b8Rp29u8MGhjb1v|LSL LabRecorder (zip)}}</pre>

ℹ️ If you want to upload files to the Surfdrive to share on this Wiki, TSG members should place them in the folder "TSG Wiki Resources". This folder should be visible and accessible for all TSG and lab support members. If not, please contact [[Erik van den Berge]].

===Dead links===
If you encounter an external link that no longer works, e.g. if you get a 404 error message or the whole website doesn't exist anymore:
# Try to find where the intended content has moved to and replace the link url.
# Check the page history to see who may've created the link in the first place; ask them to fix it.
# Add the <code><nowiki>{{Dead link}}</nowiki></code> tag after the link. {{Dead link}}

Pages with dead links will automatically show up on [[:Category:Articles with dead external links]].

==Images==
[[File:placeholder.png|thumb|320px|Right-floating image thumbnail with description.]]

To optimize screen space, images should be placed in a floating window, aligned to the right side of the screen. Larger images can be automatically resized to thumbnails, by specifying the thumbnail width. 300px is the preferred thumbnail size. Adding a description underneath the image is appreciated.
For more image formatting guidelines, visit the [http://www.mediawiki.org/wiki/Help:Images MediaWiki Images Guide].

'''Inline Images'''

Images that are used, for instance, as part of a step-by-step tutorial can be placed inline, with larger size to make them more readable. The exact size is up to you, but the width should not exceed 720px.<ref>Thumbnails 720px wide still fit comfortably within a browser window on half a 1920px desktop monitor.</ref>
[[File:placeholder.png|thumb|none|480px|Caption]]

You can prevent text that is placed after the image from flowing next to the image by placing an HTML break behind it.

==Tables==

For tables, use the Wikitable markup. It is more readable and easy on the eye than the default one. There are multiple ways to create rows and columns, some used in the example below, but for more information, consult the [http://www.mediawiki.org/wiki/Help:Tables MediaWiki Table Formatting Guide].

By default, table columns will scale to fit the contents of the cell, but this usually results in a messy-looking table. Set fixed column-widths to keep the table nice and tight.

For binary entries (e.g. Yes/No), a background color can be used to make it easier to recognize.

{| class="wikitable"
! width="150px" |
! width="200px" | Item 1
! width="200px" | Item 2
! width="200px" | Item 3
|-
| Regular Info || Info 1 || Info 2 || Info 3
|-
! Comparison
! colspan="3" |
|-
| Template || <center><code><nowiki>{{Yes}}</nowiki></code></center> || <center><code><nowiki>{{No}}</nowiki></code></center> || <center><code><nowiki>{{Some}}</nowiki></code></center>
|-
| Result || {{Yes}} || {{No}} || {{Some}}
|-
! colspan="4" |
|-
| Custom name || <center><code><nowiki>{{Yes|Yeah!}}</nowiki></code></center> || <center><code><nowiki>{{No|Nuh-uh}}</nowiki></code></center> || <center><code><nowiki>{{Some|Maybe?}}</nowiki></code></center>
|-
| Result || {{Yes|Yeah!}} || {{No|Nuh-uh}} || {{Some|Maybe?}}
|-
! colspan="4" |
|-
| Manual colors
| style="background-color:#9F9;" | #9F9
| style="background-color:#F99;" | #F99
| style="background-color:#FFD;" | #FFD
|-
|}

==Code==

If you want to add code, the syntax might interfere with the Mediawiki syntax. To prevent this from happening, place your code in one of the following preferred ways:

<code>Fixed format text for short, single-line code.</code>

<syntaxhighlight lang="text">
Long code, spans entire width of the page.
Supports syntax highlighting of certain languages, like Python and HTML.
Change the lang="" attribute to the correct language, e.g. lang="python" or lang="html5"
Use lang="text" for non-supported languages.
</syntaxhighlight>

 

<syntaxhighlight lang="text" line style="height:15em; overflow:auto;">
You can also add line numbering.

If your code is longer than, say, 50 lines, you can add a style attribute to introduce a scrollbar, as sampled here. For a 50-line cutoff, use style="height:50em; overflow:auto;".
Note that this method will cause the print version of the page to cut off the code at the line limit mark and not print the rest of the code.
I might fix that, but if it's really crucial to have an entire page full of code, you should probably give it a separate page.


Prow scuttle parrel provost Sail ho shrouds spirits boom mizzenmast yardarm. Pinnace holystone mizzenmast quarter crow's nest nipperkin grog yardarm hempen halter furl. Swab barque interloper chantey doubloon starboard grog black jack gangway rutters.
Deadlights jack lad schooner scallywag dance the hempen jig carouser broadside cable strike colors. Bring a spring upon her cable holystone blow the man down spanker Shiver me timbers to go on account lookout wherry doubloon chase. Belay yo-ho-ho keelhaul squiffy black spot yardarm spyglass sheet transom heave to.
Sail ho Corsair red ensign hulk smartly boom jib rum gangway. Case shot Shiver me timbers gangplank crack Jennys tea cup ballast Blimey lee snow crow's nest rutters. Fluke jib scourge of the seven seas boatswain schooner gaff booty Jack Tar transom spirits.

</syntaxhighlight>

For command-line code, you can also style it like this for clarity:
<code style="background-color:#000; color:#fff; padding:1px 3px;">ping 127.0.0.1 -n 50 -l 1024</code>

You could also use the <nowiki><tt> <pre> and nowiki </nowiki> tags if better suited for your needs, whatever works best to present the code as clear and readable as possible.

==Emoji==
It is encouraged to use [https://unicode.org/emoji/charts/full-emoji-list.html unicode emojis] (which you can just copy-paste as text) in places where they can draw extra attention, help illustrate your point, or break up the monotony of a long text.

Be aware that emojis may be rendered differently in different browsers or operating systems, so try to pick ones that are common and unambiguous, and also recognizable at the scale they get reduced to when placed in-line on our Wiki. Also, Windows doesn't natively support flag emojis like 🇳🇱, for some reason.

Lastly, don't overdo the emojis, as that could make it seem like our wiki was written by AI.

====Examples====
:ℹ️ This is a piece of (extra) information.
:⚠️ This is a warning!
:❌ This is a no-go!
:✅ This is good.
:✨ This is something new!
:🚧 This is under construction.
:🐽 Oink.

These are just examples; feel free to come up with your own conventions so we can later compare and discuss what works best.

==Shields and Badges==
Github-style shields or badges are useful for providing software details like programming language and licensing at a glance. There's a case to be made for our Wiki and Gitlab READMEs to use similar layouts and features for more uniformity in our documentation, and so badges could help with that too. Unfortunately, it is currently a bit of a faff to implement badges on our wiki, as hotlinking or injecting dynamic content from external sources is disabled for security reasons.

The workaround:
# Generate a badge at https://shields.io
# Create a new CSS rule in [[MediaWiki:Common.css]] (see examples below)
# On the page you want to edit, add a custom span with class="shield" and the id as named in the CSS, e.g.: <code><nowiki></nowiki></code>
# Add to the list of shields below.

===Available Shields===
: <code><nowiki></nowiki></code>

==Banners==
If a page is, or needs to be, significantly changed, you can put a banner on top to warn/inform visitors.
<pre>{{Notice|Did you know you could add banners?}}</pre>
{{Notice|Did you know you could add banners?}}
<pre>{{Warn|'''Look Out!'''}}</pre>
{{Warn|'''Look Out!'''}}
<pre>{{Outdated}}</pre>
{{Outdated|nocat=true}}
<pre>{{Under construction}}</pre>
{{Under construction|nocat=true}}

==References==
<references />

Rode RODELink Filmmaker Kit

2026-08-11T12:48:26Z

E.vandenberge: /* External Links */

{{Infobox tsg
| name = RØDE RØDELink Filmmaker Kit
| image = Rodelink.jpg
| caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories.
| manuals =
}}

The RØDE RØDELink Filmmaker Kit is a wireless lavalier microphone system. It has a bodypack-style transmitter with exchangeable lavalier mic (via 3.5mm jack connector). 
The RØDELink kit has been made somewhat obsolescent by more modern, ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], however it still offers some distinct benefits (see [[#Comparison]]).



==Contents==
The RØDE RØDELink Filmmaker Kit contains:
* 1 Wireless transmitter (TX-BELT)
* 1 Wireless receiver (RX-CAM)
* 1 RØDELink Lav microphone
* Foam wind screen
* Microphone pouch
* 3.5mm jack M-M cable

==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDELink Filmmaker Kit
|-
! Microphone
! scope="row" colspan="2"|
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Accessories || Foam windshield
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS Jack
|-
! Transmitter
! scope="row" colspan="2"|
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Belt-clip/cold-shoe
|-
| Range (m) || 100 (LOS)
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
! Receiver
! scope="row" colspan="2"|
|-
| Connector || 3.5mm jack
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Clip/cold shoe
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
|}
<references group="fn" /> 

==Usage==
The RØDELink kit has no internal storage, so you will always have to connect it to a separate recording device, like a regular microphone. The transmitter was made to connect to a camera, but can also be connected to XLR recorder or [[Audio Interface]], or even to a PC, phone or laptop, using adapters that we have available.

# Insert batteries into the transmitter and receiver units (press button and slide back cover down), or connect them to a USB power source via microUSB.<ref>When powering the transmitter and/or receiver via USB, we recommend using clean and isolated power sources like a powerbank, NOT a regular wall-charger. The latter can introduce noise.</ref>
# Plug the lavalier microphone into the receiver.
# Connect the receiver to your recording device via 3.5mm jack cable.
# Turn on the transmitter and receiver. They should connect and pair automatically.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it. 
Attach a wind screen when recording outside in windy conditions.

When not using the kit, please remove the batteries from the transmitter and receiver.

==Comparison==
Compared to ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], the RØDELink system offers the following pros & cons:

'''Pros'''
:✅ Swappable batteries, or limitless power via USB. Lets you record long days without having to (remember to) charge internal batteries.
:✅ Smaller mic. The mic itself is smaller because it does not have a built-in transmitter, so it's easier to hide/less obtrusive.
:✅ Replaceable mic. The lavalier mic can potentially be swapped out for other microphone styles, or with other polar patterns.
:✅ Large, readable controls. Big buttons and clear OLED displays make the set fool-proof and easy to use.
:✅ "Unlosable"? The mic connection, sturdy clips, and bulky transmitter make the set harder to accidentally drop, lose, or forget.

'''Cons'''
:❌ Swappable batteries. You need to remember to always pack spare batteries, just in case.
:❌ No digital output. The USB port is for power input only.
:❌ Single channel. Each microphone requires its own transmitter and receiver. Most ultra-compacts offer 2 mics/channels per receiver.
:❌ Wired mic. The mic still connects to the transmitter via wire, which could snag, or has to run underneath your speaker's clothes (=more intrusive)
:❌ No noise-cancelling. Most ultra-compacts offer built-in ANC which helps when recording in noisy environments.
:❌ Bulky. The entire set is bulky and less portable.

The TSG will always consider these tradeoffs when advising a wireless microphone for you to use 🙂

==See Also==
*[[Microphones]]

==External Links==
*[https://rode.com/en-us/products/rodelink-filmmaker-kit Official website]

==References==
<references />

Rode RODELink Filmmaker Kit

2026-08-11T12:48:14Z

E.vandenberge: /* Comparison */

{{Infobox tsg
| name = RØDE RØDELink Filmmaker Kit
| image = Rodelink.jpg
| caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories.
| manuals =
}}

The RØDE RØDELink Filmmaker Kit is a wireless lavalier microphone system. It has a bodypack-style transmitter with exchangeable lavalier mic (via 3.5mm jack connector). 
The RØDELink kit has been made somewhat obsolescent by more modern, ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], however it still offers some distinct benefits (see [[#Comparison]]).



==Contents==
The RØDE RØDELink Filmmaker Kit contains:
* 1 Wireless transmitter (TX-BELT)
* 1 Wireless receiver (RX-CAM)
* 1 RØDELink Lav microphone
* Foam wind screen
* Microphone pouch
* 3.5mm jack M-M cable

==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDELink Filmmaker Kit
|-
! Microphone
! scope="row" colspan="2"|
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Accessories || Foam windshield
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS Jack
|-
! Transmitter
! scope="row" colspan="2"|
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Belt-clip/cold-shoe
|-
| Range (m) || 100 (LOS)
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
! Receiver
! scope="row" colspan="2"|
|-
| Connector || 3.5mm jack
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Clip/cold shoe
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
|}
<references group="fn" /> 

==Usage==
The RØDELink kit has no internal storage, so you will always have to connect it to a separate recording device, like a regular microphone. The transmitter was made to connect to a camera, but can also be connected to XLR recorder or [[Audio Interface]], or even to a PC, phone or laptop, using adapters that we have available.

# Insert batteries into the transmitter and receiver units (press button and slide back cover down), or connect them to a USB power source via microUSB.<ref>When powering the transmitter and/or receiver via USB, we recommend using clean and isolated power sources like a powerbank, NOT a regular wall-charger. The latter can introduce noise.</ref>
# Plug the lavalier microphone into the receiver.
# Connect the receiver to your recording device via 3.5mm jack cable.
# Turn on the transmitter and receiver. They should connect and pair automatically.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it. 
Attach a wind screen when recording outside in windy conditions.

When not using the kit, please remove the batteries from the transmitter and receiver.

==Comparison==
Compared to ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], the RØDELink system offers the following pros & cons:

'''Pros'''
:✅ Swappable batteries, or limitless power via USB. Lets you record long days without having to (remember to) charge internal batteries.
:✅ Smaller mic. The mic itself is smaller because it does not have a built-in transmitter, so it's easier to hide/less obtrusive.
:✅ Replaceable mic. The lavalier mic can potentially be swapped out for other microphone styles, or with other polar patterns.
:✅ Large, readable controls. Big buttons and clear OLED displays make the set fool-proof and easy to use.
:✅ "Unlosable"? The mic connection, sturdy clips, and bulky transmitter make the set harder to accidentally drop, lose, or forget.

'''Cons'''
:❌ Swappable batteries. You need to remember to always pack spare batteries, just in case.
:❌ No digital output. The USB port is for power input only.
:❌ Single channel. Each microphone requires its own transmitter and receiver. Most ultra-compacts offer 2 mics/channels per receiver.
:❌ Wired mic. The mic still connects to the transmitter via wire, which could snag, or has to run underneath your speaker's clothes (=more intrusive)
:❌ No noise-cancelling. Most ultra-compacts offer built-in ANC which helps when recording in noisy environments.
:❌ Bulky. The entire set is bulky and less portable.

The TSG will always consider these tradeoffs when advising a wireless microphone for you to use 🙂

==See Also==
*[[Microphones]]

==External Links==
[https://rode.com/en-us/products/rodelink-filmmaker-kit Official website]

==References==
<references />

Rode RODELink Filmmaker Kit

2026-08-11T12:47:59Z

E.vandenberge: Created page with "{{Infobox tsg | name = RØDE RØDELink Filmmaker Kit | image = Rodelink.jpg | caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories..."

{{Infobox tsg
| name = RØDE RØDELink Filmmaker Kit
| image = Rodelink.jpg
| caption = RØDELink Transmitter, Receiver, Lavalier mic and accessories.
| manuals =
}}

The RØDE RØDELink Filmmaker Kit is a wireless lavalier microphone system. It has a bodypack-style transmitter with exchangeable lavalier mic (via 3.5mm jack connector). 
The RØDELink kit has been made somewhat obsolescent by more modern, ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], however it still offers some distinct benefits (see [[#Comparison]]).



==Contents==
The RØDE RØDELink Filmmaker Kit contains:
* 1 Wireless transmitter (TX-BELT)
* 1 Wireless receiver (RX-CAM)
* 1 RØDELink Lav microphone
* Foam wind screen
* Microphone pouch
* 3.5mm jack M-M cable

==Specifications==

{| class="wikitable"
|-
! colspan="2"| RØDELink Filmmaker Kit
|-
! Microphone
! scope="row" colspan="2"|
|-
| Type || Lavalier (small condenser)
|-
| Polar Pattern || Omnidirectional
|-
| Frequency Response (Hz) || 20 - 20,000
|-
| Accessories || Foam windshield
|-
| Max. SPL (dB) || 110
|-
| Connector || 3.5mm TRS Jack
|-
! Transmitter
! scope="row" colspan="2"|
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Belt-clip/cold-shoe
|-
| Range (m) || 100 (LOS)
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
! Receiver
! scope="row" colspan="2"|
|-
| Connector || 3.5mm jack
|-
| Power requirement || 2* AA battery, or MicroUSB
|-
| Features || Wireless (2.4GHz)
|-
| Mount || Clip/cold shoe
|-
| Battery Capacity (mAh) || -
|-
| Weight (g) || 190
|-
|}
<references group="fn" /> 

==Usage==
The RØDELink kit has no internal storage, so you will always have to connect it to a separate recording device, like a regular microphone. The transmitter was made to connect to a camera, but can also be connected to XLR recorder or [[Audio Interface]], or even to a PC, phone or laptop, using adapters that we have available.

# Insert batteries into the transmitter and receiver units (press button and slide back cover down), or connect them to a USB power source via microUSB.<ref>When powering the transmitter and/or receiver via USB, we recommend using clean and isolated power sources like a powerbank, NOT a regular wall-charger. The latter can introduce noise.</ref>
# Plug the lavalier microphone into the receiver.
# Connect the receiver to your recording device via 3.5mm jack cable.
# Turn on the transmitter and receiver. They should connect and pair automatically.

For the best results, make sure the lavalier microphone is not covered by any layers of clothing or hair that may rustle against it. 
Attach a wind screen when recording outside in windy conditions.

When not using the kit, please remove the batteries from the transmitter and receiver.

==Comparison==
Compared to ultra-compact wireless microphone sets like the [[Hollyland Lark M2]], the RØDELink system offers the following pros & cons:

'''Pros'''
:✅ Swappable batteries, or limitless power via USB. Lets you record long days without having to (remember to) charge internal batteries.
:✅ Smaller mic. The mic itself is smaller because it does not have a built-in transmitter, so it's easier to hide/less obtrusive.
:✅ Replaceable mic. The lavalier mic can potentially be swapped out for other microphone styles, or with other polar patterns.
:✅ Large, readable controls. Big buttons and clear OLED displays make the set fool-proof and easy to use.
:✅ "Unlosable"? The mic connection, sturdy clips, and bulky transmitter make the set harder to accidentally drop, lose, or forget.

'''Cons'''
:❌ Swappable batteries. You need to remember to always pack spare batteries, just in case.
:❌ No digital output. The USB port is for power input only.
:❌ Single channel. Each microphone requires its own transmitter and receiver. Most ultra-compacts offer 2 mics/channels per receiver.
:❌ Wired mic. The mic still connects to the transmitter via wire, which could snag, or has to run underneath your speaker's clothes (=more intrusive)
:❌ No noise-cancelling. Most ultra-compacts offer built-in ANC which helps when recording in noisy environments.
:❌ Bulky. The entire set is bulky and less portable.

The TSG will always consider these tradeoffs when advising a wireless microphone for you to use 🙂

==See Also==
*[[Microphones]]

==External Links==
[https://rode.com/en-us/products/rodelink-filmmaker-kit Official website]

==References==
<references />