-
Notifications
You must be signed in to change notification settings - Fork 31
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
Galicaster doesn't update status if capture.device.name is not set. #545
Comments
The reason why Galicaster was set to act like that I think has to do with how the "capture.device.names" property works. AFAIK, if you schedule a recording in Opencast, but don't mark any tracks to be recorded, the expected behavior would be that the capture agent would not actually record anything. In this case, it may have seen counterintuitive to send the status recording when no content is actually being recorded. However, this is inconsistent with two things:
So maybe changing this behavior, sending the recording status even if no tracks are set, may make sense. |
Hi. Sorry for delay, but I was 😭 on holidays 🌴 I'm not sure that I understood properly. What do you mean when you say:
You mean sources? (audio, presentation, presenter) |
Hi @mostolog, Sorry, I was mixing Galicaster and Opencast terms. I meant the capture.device.names values. It appear listed as Inputs in the Opencast UI when scheduling a recording. Here is a screencap: |
In our scenario we have 3 sources that can be selected: presenter, presentation and audio. All 3 are enabled by default and, having an eye on metadata shown if scheduled using GUI, it doesn't seem they are set by Opencast in any way. Neither on Javascript call, which doesn't work. |
As suggested by https://groups.google.com/a/opencast.org/d/msg/users/QM6Crf7FpHI/_FlLfhImAQAJ as a result of an undesired behavior, it seems Galicaster 2.0.0 only sends status updates if recording sets capture.device.name
The text was updated successfully, but these errors were encountered: