Search found 8 matches

by faturita
Tue Jul 31, 2018 8:13 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

Re: LSL Export (Gipsa) - Weird issue with lost markers

Jussi ! Absolutely thank you !! You rule !!! Stims are now there !! However, one more issue I would like to mention is the topic of this thread (after all). At time 0.000 sec <Box algorithm::(0x000000ea, 0x000057a1) aka Launch> Lua script terminated At time 35.875 sec <Box algorithm::(0x00007eb2, 0x...
by faturita
Fri Jul 27, 2018 6:36 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

Re: LSL Export (Gipsa) - Weird issue with lost markers

I coded an LSL Gateway in C++ that receives both streams from the LSL Export Box, paste them together and send them as it should have been sent by the "LSL Export Gipsa" (with +1 channel) and I can see all the markers. I bet that there must be some problem with this box when it's connected to the ac...
by faturita
Fri Jul 27, 2018 2:26 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

Re: LSL Export (Gipsa) - Weird issue with lost markers

I just tried that and I get exactly the same as you. I can see the tick stimulator from the clock out of the LSL Export Gipsa. The issue is found when you connect the Stimulation input of the LSL Export (Gipsa) to the Acquisition Client (which should be the way to do it). For some reason, which is a...
by faturita
Fri Jul 27, 2018 1:58 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

Re: LSL Export (Gipsa) - Weird issue with lost markers

Do you in some circumstances have two acquisition servers running at the same time? Not at all! I am just having one acquisition server (generic oscillator) and I have an Acquisition Client Box on the Designer which gets the data. From the acquisition client I am sending the stimulations and the st...
by faturita
Thu Jul 26, 2018 10:24 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

Re: LSL Export (Gipsa) - Weird issue with lost markers

Thanks J !! Yes we tried this on an p300-xdawn-4-online.xml scenario: *) Acquisition Client: Signal Stream --> Input Signal, Stimulations --> Input Stimulations LSL Export Gipsa *) Acquisition Client: Signal Stream --> Input Signal, Stimulations --> Input Stimulations LSL Export *) Acquisition Clien...
by faturita
Wed Jul 25, 2018 6:02 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

Re: LSL Export (Gipsa) - Weird issue with lost markers

Excellent Jussi thanks a lot !! The reason we are doing this merging of stimulations, is because of this thread: http://openvibe.inria.fr/forum/viewtopic.php?f=6&t=9421&p=15825#p15825. The markers that the LSL Export (Gipsa) is sending when its input is connected to the "Acquisition Client" output o...
by faturita
Mon Jul 23, 2018 10:19 pm
Forum: Boxes
Topic: LSL Export (Gipsa) - Weird issue with lost markers
Replies: 13
Views: 6040

LSL Export (Gipsa) - Weird issue with lost markers

Dear Friends, Scenario: P300 Speller (based on p300-xdawn-4-online.xml) Version: 2.1.0 We found that LSL Export (Gipsa) is loosing the first Marker for the P300 Speller when it is sent at the same time as "Segment Start" (32771) <Box algorithm::(0x0000445b, 0x000068e3) aka P300 accumulator> <In Scri...
by faturita
Mon Jul 23, 2018 10:16 pm
Forum: Designer
Topic: using LSL to send both data and stimulus
Replies: 3
Views: 4495

Re: using LSL to send both data and stimulus

We have the same exact issue when the "Stimulator Input" for "LSL Export (Gipsa)" is connected to the "Stimulator Output" of the Acquisition Server.
The only way to fix it was to connect it to a different Stimulator output.