Closed oerix closed 6 months ago
Even if it doesnt work (I cant test it and not logs here) then assuming that two protobuffer sources are active in the same time causing full network saturation sending images at the same time I dont plan investigate it. And for logs you know: it's even in the issue template.
Even if it doesnt work (I cant test it and not logs here) then assuming that two protobuffer sources are active in the same time causing full network saturation sending images at the same time I dont plan investigate it. And for logs you know: it's even in the issue template.
The issue was posted in discussion initially, and I clicked the create issue button directly from discussion hence I didn't see no template before posting (or it was an oversight).
From what I can see even if two Protobuffers are active, only one is used at a time, so there shouldn't be any conflict. I would've thought the Auto Selection would priorities the higher priorty number, and disable the lower one no? If not, I think that would be a ideal change.
Edit: Apologies, System info and debug log has now been added to op.
The logs are not clear here, although I remember that I simplified the code here when it comes to handling the proto/flatbuffer stream, assuming that only one stream is active at the same time (due to network saturation, so I do not plan to change it, rather the streams may have different priorities but they cannot transmit at the same time) and only this scenario was tested. If you care about this functionality, you can try version 19.
Discussed in https://github.com/awawa-dev/HyperHDR/discussions/826
Edit:
Steps to reproduce
Have 2 or more sources with Auto selection on
What is expected?
It should prioritise the highest number and disable any other active sources.
What is actually happening?
When 2 or more sources are found it doesn't auto select the highest priority.
Debug log:
System: