Tristan Stenner

Interesting problem. dpkg itself installs the problem without any warning, but other dpkg frontends can get confused. liblsl gets added to the dependencies by default because the automatic package dependency...

Not a thorough review, but from a quick glance the "signal handler" approach is better and even works in the console, you'd just need to switch to Ctrl+C when running...

With #19 the plain python reader's speed is within an order of magnitude compared to a pure C++ implementation so there's no binary extension / Cython magic needed (same for...

> The language-specific example code should sit next to the LSL source code for that language. In other words, the C/C++ examples should be moved into a folder within the...

> There was some agreement that having the documentation with the source code was desirable. Which parts? All of it is way too much so there'd be at least two...

Agreed, except for the "working C++ compiler and CMake installed"-part, but the solution for that is different. A portable SSD costs around $50 and even though it's hard it's possible...

Github also renders rst files, so a [copy of the build guide](https://github.com/sccn/liblsl/blob/6414b83816821461619026afe7f3f0c40d159fc7/doc/build.rst) could be kept in the main repository, but somebody would need to keep them in sync.

> One possible issue might be throughput. As long as your sampling rate is low enough (i.e. you don't try to send each voxel in its own sample) you should...

> It kinda depends on how desperate you are. Did the audio data pick up the keyboard presses? If yes, you can use those as reference points to manually rescale...

> In these cases it is convenient to have a buffer of only 1 sample, otherwise the user is forced to fetch until there are no samples remaining then use...