Join the beta

Signal Studio is real software you can run on real recordings today. It is also unfinished, and the honest thing is to say so before you install it.

This is still in development

Not "beta" as a marketing word. Beta as in: the software is being built while you use it, and you will run into things that do not work.

Expect bugs. Some of them will be obvious. Some will be quiet and will only show up in an edge case with your particular montage.
The pipeline file format can change between versions. A graph saved today may need adjusting after an update.
Features are incomplete. Parts of the interface are stubs, and some cards exist but are not validated yet.
Windows only, for now. The macOS build is coming; the code already compiles there.
The installer is not code-signed yet. Windows will show a warning on first launch. You can proceed past it.

If you are about to run an analysis that goes into a paper, write down the exact version you used and archive the pipeline file alongside your data. That is what makes the run reproducible later.

Report what breaks

This is the single most useful thing you can do. A precise report is worth more than ten vague impressions. When something goes wrong, tell us:

the version you are running, from Help / About
what you were doing, step by step
what you expected, and what happened instead
the recording type if it matters: EEG, sEEG, iEEG, and roughly how many channels

Report a bug on GitHub Ask on Discord Open a forum thread

Become a contributor

The project is small and there is more to do than one person can carry. If you want to help, say what you would like to work on and we will get back to you. Contributors get access to the source repository.

Contributor registration

Name*

Tell us who you are.

Email*

A valid email is required.

Lab or affiliation

GitHub username

Needed to give you repository access.

How would you like to help*

Testing on my own recordings Writing or validating cards C++ / JUCE development Python signal processing Documentation and tutorials Interface and design Methods review and validation

Pick at least one.

What do you work on

Other ways to support the project

Publish a card

The card library grows by people adding what they needed. If you wrote a processing step for your own work, publishing it costs you nothing and saves someone else a week.

Publish

Cite it

If Signal Studio was part of an analysis you published, citing it is what makes the project legible to funders and to other labs.

How to cite

Tell a colleague

Most people who would find this useful have never heard of it. A mention in a lab meeting does more than any amount of marketing we could do.

Press kit