No "update" function from TCP remote control about app-labrecorder HOT 6 CLOSED

Good catch and thanks for already writing the code :-). The change to hideWarnings wasn't needed, so the changes (#59) ended up a bit shorter.

from app-labrecorder.

Indeed it would be a great addition to a great tool. Out of the 5 buttons in the GUI, the update is the only one without a TCP equivalent command.
If the GUI is started before the creation of the streams, even after sending a select all, the new streams won't be detected. This greatly limits the functionality of remote control.

from app-labrecorder.

Sorry for crossing streams but I just updated the README and added a new tag.

from app-labrecorder.

By the way, for those who are following this issue, depending on your exact use case there may already have been a way to achieve what you want and it might even have worked better.

If you use the Required Streams feature in the config file then you can specify streams that might be initially considered missingStreams then will be passed into the recording thread in the list of watchfor streams: https://github.com/labstreaminglayer/App-LabRecorder/blob/master/src/recording.h#L60

These streams will each get their own query and thread that looks for them. When found they will be added to the recording automatically: https://github.com/labstreaminglayer/App-LabRecorder/blob/master/src/recording.cpp#L124-L159

In sum: if you already know the name and hostname of the origin streams that you want to record then you can add these to your .cfg file and you can start recording even before they're online. Once those streams do come online they will be automatically added to the recording.

from app-labrecorder.

Thanks @tstenner for the pull request ! Now the list of RCS supported functions looks more complete.
@cboulay I actually used the watchfor functionnality you mentionned.
I assumed undetected streams were marked as red to remind the user that those were missing, not that they would be caught later on, which is actually quite a nice desing!!!
I don't want to spam issues, but considering thus functionnality, I'm wondering if an onlyrecord-watchfor functionnality would help. I am on a university network and thus I get random lsl streams from everywhere :)

Thanks again!

from app-labrecorder.

Then I've got good news for you: the onlyrecord-watchfor is the only/default mode of operation :-)

The list entries have three states:

1. currently found (green) but not checked -> won't be recorded
2. currently found (green) and checked -> will be recorded
3. currently not found (red), but checked -> will be recorded as soon as it's found

from app-labrecorder.