labstreaminglayer / App-LabRecorder

An application for streaming one or more LSL streams to disk in XDF file format.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

I cannot get output file. a problem on windows 11 ?

atusiniida opened this issue · comments

Dear colleagues,

Following a tutorial. I tried to get data from AudioCapture on my windows 11 PC.
https://github.com/sccn/labstreaminglayer/wiki/Tutorial-1.-Getting-started-with-LSL-single-stream
However, I failed to get an output .xdf file.
I do not get any error or warning messages.
but the value indicating the size of the output file remains zero (a below figure) and I do not find any files in the specified path.

スクリーンショット 2021-12-15 102551

I have confirmed that this problem occurs in the following version.
LabRecorder-1.13.1-win64
LabRecorder-1.14.2-Win_amd64
LabRecorder-1.14.2-Win_i386

the same problem occurs when I tried data from BlueMuse on my windows 11 PC.
https://github.com/kowalej/BlueMuse
I successfully get the output file from AudioCapture on my MAC PC.

therefore, I suspect that this problem is specific to my windows 11 PC.

It is very helpful if you give any advice about this problem.
Thank you in advance.

Can you verify that data are coming through using another LSL application? For example, in a simple pylsl instance, or one of the viewers here: https://labstreaminglayer.readthedocs.io/info/viewers.html

Thank you for your response.
I tried a combination of BlueMuse and muse-lsl ( https://github.com/alexandrebarachant/muse-lsl).
It worked with no problem.

You have a very weird file name, actually it seems invalid for the Win11 filesystem, looks like Mojibake. My guess is that either LabRecorder or Win11 or the C++ runtime library can't handle that. Try changing the filename? Or changing the locale / language of the OS?
image

If that's the default filename for LabRecorder on Win11, there might be a decoding issue in the code. Weirdly enough, it seems that LabRecorder was able to load the config file, although that filename is also Mojibake...

Thanks! I have Japanese characters in the file name. As you point out, Mojibake is the cause of the problem. I got the data in a path without Japanese characters.