Closed katerina-ds closed 3 years ago
@cboulay will know more about any issue with OSX. He will most likely post when the sun is up in his part of the world.
But, I can say that the fact that LabRecorder is recording clock offsets and not data suggests that there is something wrong with the data transmission---not LabRecorder. Maybe a firewall setting? I would try running the example ReceiveData.py. If that also does not get any data, it is not a problem with LabRecorder (not that that solves your problem :/). I am not a Mac user so that is about as much help as I can offer.
Hmm, that's pretty interesting. How did you install pylsl and LabRecorder? There's now a homebrew formula for LabRecorder, but to be honest I'm having trouble navigating Apple's latest round of restrictions and code-signing requirements, so I don't expect it to work on anyone's computer but my own. But it's worth a shot!
brew install labstreaminglayer/tap/labrecorder
If that doesn't work then my recommendation would be to build both liblsl and LabRecorder from source.
I'm occupied tomorrow so I won't be able to look into this. I'll try to circle back to it next week. Please feel free to ping me if you haven't heard anything.
Hi. I am having the same issue on my MacBook M1. LabRecorder is recording the header and footer, but no data. I am using Swift 5 in Xcode 12.5.1 on a MacBook Pro M1 in iOS Simulator mode. I've tried int16 and string types. If I use ReceiveStringMarkers.py and SendStringMarkers.py, in separate iTerm2 windows on my Mac, it works fine.
@cboulay I actually installed it using brew. I'll try to build it from source to see if that help.
Would a tcpdump help?
I think I've identified the issue. There was a protocol incompatibility introduced into liblsl. See here: https://github.com/sccn/liblsl/issues/134
What this means is that any apps that were using older liblsl were incompatible with apps that were using newly-compiled-from-source liblsl. @katerina-dandelion you were using a new build from source via homebrew (thank you for testing and reporting, by the way), and @ScottThomasMiller you were using a new build because we don't have an iOS or M1 release so you had no choice. These were incompatible with old liblsl, whether that was with pylsl from pip or a release of another application.
This is a major problem and we will try to solve it as soon as possible.
In the meantime, @katerina-dandelion you can try downloading LabRecorder from the release page (there are some mac builds there): https://github.com/labstreaminglayer/App-LabRecorder/releases
@ScottThomasMiller - you can checkout liblsl to a commit before the incompatibility was introduced. You might as well use the latest release tag: git checkout v1.15.0
.
I think that fixed it but I won't be sure until I can visualize the xdf file. I now see an entry in the footer which reads:
Whereas before, it had a sample_count of 0.
Thank you, @cboulay. I downloaded v1.14.2 release and the recording works fine!
Hi, I'm using LabRecorder on Mac OS (Catalina v. 10.15.7). I can see the streams and start recording. But the resulting file does not contain any data, only stream metadata and time offsets. Here is the content of the file read by
pyxdf.load_xdf()
. I usedpython -m pylsl.examples.SendData
to simulate a sensor.