-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sample Pushed when Streaming is closing #67
Comments
This is pretty interesting, though I'm not certain that I understand the problem exactly. Can you please provide minimal scripts to reproduce the problem (one for the inlet, one for the outlet)? |
If you record this outlet with labrecorder app you can see that at the end of pushing a sample equal to 0 or a int32 value choosed in the range of the pushed sample values is sent to LSL env. Idem if you receive with the inlet this markers streaming a sample is printed on console after having destroyed the outlet. In my code outlet and inlet run in 2 different processes (2 different spyder routines), to simplify the procedure the outlet is a for loop but for while loop of inlet must be stopped manually. Thank you for the support!!! Have nice day Outlet:
###################################################################
|
What version of pylsl and liblsl are you using on which operating system? |
I use a Window 10 sys and pylsl 1.16.1 ( I work on anaconda env with Spyder but from terminal I don't see liblsl package version with conda list command). |
Dear all,
I'm writing you to ask about an issue that I have when I'm closing my stream. I'm pushing one sample with a marker stream type and when I stop the execution of my script Labrecorder saves a marker equal to 0 or another number randomly if the sent markers are more than 100. I also used and not used the command "del" to destroy the outlet object but in both cases the randomic marker is saved on Labrecorder... Can you help me? Can you give me some information about this last marker automatically generated?
Have nice day!
The text was updated successfully, but these errors were encountered: