Chadwick Boulay

I understand the over-the-wire protocol a little better now. We can't push a chunk of data through directly unless it's been a priori formatted as `1|2 (ts) ch0 ch1 ......

I figured out a way to do the blocking synchronous write with zero copies. With 2,000 channels at 30,000 samples per second, CPU utilization on the outlet process decreases from...

For now I am providing a manual timestamp to every sample. At 30 kHz this adds noticeable overhead. Note to self: I might be able to manually timestamp the 0'th...

Related to #156

Just thinking out loud... We could add another pylsl-only `channel_format` for `cf_bytestring`. This would require [an additional mapping](https://github.com/labstreaminglayer/liblsl-Python/blob/master/pylsl/pylsl.py#L1401-L1425) from `cf_bytestring` to the same lib.pull_ and lib.push_ functions as cf_string, but...

I heard from @ClaraKuper in Slack that you are now encountering a problem with your char-arrays being interpreted as null-terminated strings, effectively cutting your data whenever a `0` appears. This...

Even with the above change, I suspect you'll still encounter some difficulties on the receiving end. For example, xdf importers may attempt to coerce the blob into a string and...

1. Then we should rename the variable to `LSL_BUILD_ROOT` or something similar. 2. Are there any differences at all between the build output and what gets uploaded to the release...

IIRC, the .deb files on the liblsl release page will install liblsl to /usr/local. Sorry I can't check right now, but does this install also have LSLCMake.cmake? If so, then...

I'm sorry but I'm just not convinced that the `build` output is similar enough to the `install` output on all platforms and configurations that we can ignore testing the `install`...