montage review, monitor mismatch
Posted: Thu Jan 12, 2017 10:47 am
Hi everybody,
i'm having some trouble understanding how "monitor review" feature works...
The montage review page, does not reproduce at all my monitor setup: in the timeline, monitor names in the left part of the screen, are completely messed up.
my setup currently consists in 9 monitor, of which m1,2,3,4 are in record mode, m5,6,7 are in modect mode (lower res streams of cam 1,2,3), and m8,9 are for testing purposes.
If you have a look at the screen, the first 4 monitors in montage review are in pink-reddish colour, which i think is correct because m1...4 are in record mode, BUT monitor names are not correct!!!!
1. "motion cancello" --> should be m5, in modect
2. "cancello" --> should be m1
3. "event record cancello" --> is currently disabled
4. "corte" should be m2
5. "androne" should be m3, record, but is represented in montage review as the modect source of the current event (which sould be m5)
...
7. is actually m9, that is in monitor only and is not producing events at all...
i can't figure out any solution to the problem, which apparenty is not browser related, as happens in FF,chrome,and safari.
i'm having some trouble understanding how "monitor review" feature works...
The montage review page, does not reproduce at all my monitor setup: in the timeline, monitor names in the left part of the screen, are completely messed up.
my setup currently consists in 9 monitor, of which m1,2,3,4 are in record mode, m5,6,7 are in modect mode (lower res streams of cam 1,2,3), and m8,9 are for testing purposes.
If you have a look at the screen, the first 4 monitors in montage review are in pink-reddish colour, which i think is correct because m1...4 are in record mode, BUT monitor names are not correct!!!!
1. "motion cancello" --> should be m5, in modect
2. "cancello" --> should be m1
3. "event record cancello" --> is currently disabled
4. "corte" should be m2
5. "androne" should be m3, record, but is represented in montage review as the modect source of the current event (which sould be m5)
...
7. is actually m9, that is in monitor only and is not producing events at all...
i can't figure out any solution to the problem, which apparenty is not browser related, as happens in FF,chrome,and safari.