Tristan Stenner

You need liblsl compiled for M1; for some reason the linker doesn't quit when trying to link against a library with the wrong architecture and ignores the file instead: ```...

Ubuntu 16.04 still ships 5.6, so I'd rather not use anything newer than that before April 2019. In the end, we should use whichever version has precompiled binaries for a...

> This should be removed permanently, right? No one should be linking boost libraries anymore. One of the guys in Delmenhorst tried the latest MinGW and it was still needed,...

> I see the primary purpose of this task is to separate the LabRecorder back end from the front end. No more and no less. The more I work on...

> Also, note that the more isolated design is more naturally portable That's true, but how compared to liblsl, the recorderlib doesn't need to be portable. Most users will use...

I remember fixing the clock offsets bug as if it was yesterday, mostly because it was yesterday. I haven't had time to upload the new binaries, but in some very...

> In this block of code, shouldn't the rest of the code that depends on now and offset be inside the try block? Yes and I don't know why it...

So far I haven't had that issue personally, but I mostly have less than 10 streams and maybe my libstdc++ is less prone to it than others. My suggestion: create...

Could you create a packetdump during the initial LSL connection with [wireshark](https://www.wireshark.org/) and the capture filter `portrange 16571-16581`?

Presentation downgrades the data protocol to the old format (100): Request: ``` LSL:streamfeed/110 33a94754-a8ce-44e5-8f1d-54be42ed6366 Native-Byte-Order: 1234 Endian-Performance: 5.64634e+06 Has-IEEE754-Floats: 1 Supports-Subnormals: 0 Value-Size: 32 Data-Protocol-Version: 110 Max-Buffer-Length: 36000 Max-Chunk-Length: 0...