You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+26-20Lines changed: 26 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,44 +11,50 @@ The file format used by the LabRecorder is XDF. This is an open general-purpose
11
11
12
12
# Getting LabRecorder
13
13
14
-
## Dependencies
14
+
The [releases page](https://github.com/labstreaminglayer/App-LabRecorder/releases) contains archives of past LabRecorder builds. Try downloading and running an archive that matches your platform.
15
15
16
-
For LabRecorder to work on your system, you might need to first install some dependencies.
16
+
If there are no archives matching your target platform, or the ones available don't run, then continue reading below. If the instructions don't help then please post an issue to the [repo's issues page](https://github.com/labstreaminglayer/App-LabRecorder/issues).
17
17
18
-
### MacOS
18
+
##Dependencies
19
19
20
-
In the near future it will be necessary to use [homebrew](https://brew.sh/) to manage LSL Apps and their dependencies:
For LabRecorder to work on your system, you might need to first install some dependencies, specifically liblsl and optionally Qt.
22
21
23
-
### Linux Ubuntu
22
+
### Windows
24
23
25
-
The Ubuntu releases do not typically ship with their dependencies so you will also have to download and install those:
26
-
* Download and install the latest [liblsl-{version}-bionic_amd64.deb from its release page](https://github.com/sccn/liblsl/releases)
27
-
* We hope to make this available via a package manager soon.
28
-
* You can install liblsl directly by double clicking on it, or with with `sudo dpkg -i {filename}.deb`
29
-
* See the bottom of the [lsl build env docs](https://labstreaminglayer.readthedocs.io/dev/build_env.html).
30
-
* For most cases, this will amount to `sudo apt-get install qtbase5-dev`
31
-
32
-
## Downloading LabRecorder
24
+
The Windows archives ship with all required dependencies. If you suspect you are missing a dependency, try running [Dependencies.exe](https://github.com/lucasg/Dependencies/releases) then navigating to the LabRecorder.exe. It's important to launch Dependencies.exe from the same environment that you would use to launch this application: if you launch this application by double-clicking the executable in Windows' finder then do the same on the Dependencies.exe icon; if you launch this application in a Terminal window, then use that same Terminal to launch Dependencies.
33
25
34
26
### MacOS
35
27
36
-
*`brew install labstreaminglayer/tap/labrecorder`
28
+
In the near future, many LSL Apps (especially LabRecorder) will not ship with their dependencies and will look for the dependencies to be installed on the system. The easiest way to manage the dependencies is by using [homebrew](https://brew.sh/):
The LabRecorder displays a list of currently present device streams under "Record from Streams". If you have turned on a device after you have already started the recorder, click the "Update" button to update the list (this takes ca. 2 seconds).
47
-
> For testing you can use a "dummy" device from the `lslexamples` found in the [liblsl release assets](https://github.com/sccn/liblsl/releases) (for example SendData<!--, SendStringMarkers, and SendDataSimple-->).
53
+
> For testing, you can use a "dummy" device from the `lslexamples` found in the [liblsl release assets](https://github.com/sccn/liblsl/releases) (for example SendData<!--, SendStringMarkers, and SendDataSimple-->).
48
54
49
55
If you cannot see streams that are provided on another computer, read the section Network Troubleshooting on the NetworkConnectivity page.
50
56
51
-
You can select which streams you want to record from and which not by checking the check boxes next to them.
57
+
You can select which streams you want to record from and which not by checking the checkboxes next to them.
Note that if you have multiple streams with the same name and host, it is impossible to check only 1. If any is checked then they will all be recorded.
0 commit comments